181 results found

1. Built-in feedback function

   Why?
   Users need an easy way to provide feedback directly in context, whether they notice a small usability issue, experience performance problems, or encounter an error. Today, feedback is often reported outside the product, which can lose important context and make issues harder to understand and reproduce.

   What?
   Add a built-in feedback function in Novacura Flow that is available throughout the product.

   The user should be able to open the feedback function from anywhere, enter feedback in natural language, and submit it. The feedback can relate to anything from UI issues, such as a button being too small, to technical or performance issues, such as a connector step taking too long.

   When feedback is submitted, Flow should automatically collect relevant metadata, including app, app version, client, user context, current screen or step, and technical/runtime context where available.

   The same function should also be available when an error occurs, allowing the user to explain what they were trying to do in their own words. This should help support, consultants, and product teams understand the user intent and context behind the issue.

   Acceptance Criteria:
   [ ] A user can open the feedback function from anywhere in Flow.
   [ ] The user can enter free-text feedback in natural language.
   [ ] Feedback can be submitted for both general product/app feedback and error situations.
   [ ] Submitted feedback includes metadata such as app, app version, client, user, current context, and runtime information where available.
   [ ] When an error occurs, the user can add a description of what they were trying to do.
   [ ] Feedback is stored in a structured way so it can be reviewed, searched, and acted on.
   [ ] The feedback function does not block the user from continuing their work unless required by the error scenario.

   Why?
   Users need an easy way to provide feedback directly in context, whether they notice a small usability issue, experience performance problems, or encounter an error. Today, feedback is often reported outside the product, which can lose important context and make issues harder to understand and reproduce.

   What?
   Add a built-in feedback function in Novacura Flow that is available throughout the product.

   The user should be able to open the feedback function from anywhere, enter feedback in natural language, and submit it. The feedback can relate to anything from UI issues, such as a button being too small, to technical… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Configure app execution screen location per Portal button

   Why?
   End users experience Portal buttons as part of the solution, not as generic web client launches. Today, the app execution window location is not controlled per starting point, which can make the experience feel inconsistent or less tailored to the user workflow.

   What?
   Allow a designer to define the app execution screen location individually per Portal button.

   As an alternative or fallback, allow the end user to set and save the screen location per started app, regardless of whether it was launched from a button, double-click, or another start action. The saved location should be remembered per started app.

   Acceptance Criteria:
   [ ] Best case but optional: A designer can configure the app execution screen location for each Portal button .
   [ ] Apps launched from different buttons can open in different configured locations.
   [ ] If user-defined positioning is supported, the selected location is saved per started app.
   [ ] The saved location is reused the next time the same app is started.
   [ ] The behavior works consistently whether the app is started from a button, double-click, or another supported launch action.

   Why?
   End users experience Portal buttons as part of the solution, not as generic web client launches. Today, the app execution window location is not controlled per starting point, which can make the experience feel inconsistent or less tailored to the user workflow.

   What?
   Allow a designer to define the app execution screen location individually per Portal button.

   As an alternative or fallback, allow the end user to set and save the screen location per started app, regardless of whether it was launched from a button, double-click, or another start action. The saved location should be remembered per started app.

   … more

   •  

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Allow Client messages to display for Flowscript step

   Since Flowscript is so powerful now we can put extensive Scripts/loops in the script. If we do that in a userflow we cannot tell the user what's happening, because currently we have no way to add a client message like in other steps. Would be nice if we can get a flowscript function to add messages at different steps of the script execution. Otherwise UX for long running processes will be poor (missing user feedback)

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Configure color on End User Groups in Flow Connect (Hub)

   Configure color on End User Groups in Flow Connect (Hub).
   This feature is not possible as of today. I would like something similar to the way we can configure icon and color to apps and application packages.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Hub  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Remember enduser selected settings - Data grid

   Remember from before if end user chose card or table layout and open it the next time they log in. Can be extended to other user step elements.

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   under review  ·  AdminPaul Phillips (VP Product Management, Novacura) responded

   Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.

6. Add iterator field to Component

   If needed I would like to be able to run a component several times without the use of a "Flow loop" and instead use an iterator similair to Machine Step - SQL - iterator, using this method we can make the application clean and more presentable.

   •  

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Designer  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Magic wand in the query configurator for the IFS/SQL server

   Can we have the magic wand back that we had in Flow Classic, that autogenerates element names?

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Designer  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   started  ·  AdminOla Carlander (Admin, Novacura) responded

   We are happy to inform you that development work has begun on your requested feature. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.

8. Image Viewer and Image Selection

   The Image Selection user step option has the ability to show base64 encoded images. Can you apply the same logic for the Image Viewer? This request is for the NG Webclient and Connect web.

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. inline field validation on input fields (text input to start with)

   https://cxl.com/blog/form-validation/

   See the inline section --> For Flow text input field, being able to configure a condition (or multiple) connected to a relevant error text

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Flow connector / Studio Reports in Flow Connect

    In classic customers are using the Flow Connector, or reports from the Studio, to extract meta data about the system such as:
    Last Logged in,
    Number of logins

    A similar report in Connect is needed

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Allow custom text for invitation mails to Connect

    Customer employees frequently ignore Connect invitations as Spam. It would be good if the customer can write their own custom invitaiton messages.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Simplify commit and deploy for assets

    I'm missing the functionality "Update all to use this version" that exists in Flow classic. Updating assets are currently very time consuming and have an increased risk of human error since we need to manage all dependencies manually (and in the right order).

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Default Landing Page when the user logged in - Portal

    Current Behavior
    On first-time login, the contractor portal is expected to default to the Dashboard (as per system design).

    However, users have observed that it sometimes lands on the Technician tab instead.

    For subsequent logins, the portal loads the last visited tab, as this preference is stored in the browser cache.

    Technical Clarification
    The system currently:

    Defaults to the first available page (Dashboard) only when no cached session data exists (e.g., incognito mode or cleared cache).

    Stores the user’s last visited page in browser cache, which determines the landing page on future logins.

    This behavior cannot currently be overridden without:

    Clearing cache, or

    Using a direct URL with a predefined page selection.

    Gap / Clarification Required
    There is no formally defined requirement confirming:

    Whether the landing page should always default to a specific tab (e.g., Dashboard), regardless of cache.

    Need confirmation if:

    Defaulting to the Technician tab in some scenarios is expected, or

    The system should always enforce Dashboard as the landing page.

    Requested Changes
    Default Landing Page: Dashboard (for every login, not only first-time use).

    Dashboard Default Filter: Last 30 days.

    Request
    Explore feasibility with R&D to:

    Override browser cache behavior and enforce Dashboard as the standard landing page without requiring a custom URL.

    Confirm level of effort compared to legacy CE portal behavior, where this was supported.

    Current Behavior
    On first-time login, the contractor portal is expected to default to the Dashboard (as per system design).

    However, users have observed that it sometimes lands on the Technician tab instead.

    For subsequent logins, the portal loads the last visited tab, as this preference is stored in the browser cache.

    Technical Clarification
    The system currently:

    Defaults to the first available page (Dashboard) only when no cached session data exists (e.g., incognito mode or cleared cache).

    Stores the user’s last visited page in browser cache, which determines the landing page on future logins.

    This behavior cannot currently be overridden without:

    … more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Portal  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Remove Option for SCIM managed users from Flow connect

    Currently there is no way to remove the SCIM managed users from Flow connect.
    I can only either revoke the token or regenerate it but it will break the entire SCIM provisioning done for all the organization.the best approach is to ask the customers to remove the required user groups from the SCIM app registration in Entra ID. However, we should also have our own control over this, specially if the configuration was originally done for a PoC and when the PoC ends, there should be a mechanism to ensure that access is also disabled from our side.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. User Context Switching for Kiosk mode apps

    We see more and more requirements from customers wanting to run Novacura Flow Connect in kiosk mode, where several users would use the same computer to basically run the same apps (e.g. for Inventory Operations or Shop Floor reporting).

    For this reason it would be super useful to be able to easily and quickly switch user context from the client.

    This would require two things:

    1. Having the practical option to switch user. Maybe even including a simplified login process using for example a pin code

    2. Being able to also switch back end user context. For IFS10 we can use Run As. For IFS Cloud there's no similar possibility. However, we have the ROPC authentication option. Would it be possible to have the ROPC User as a variable?

    Having this type of user context switching would also avoid license sharing, meaning would be able to keep license count equal to physical user count.

    We see more and more requirements from customers wanting to run Novacura Flow Connect in kiosk mode, where several users would use the same computer to basically run the same apps (e.g. for Inventory Operations or Shop Floor reporting).

    For this reason it would be super useful to be able to easily and quickly switch user context from the client.

    This would require two things:

    1. Having the practical option to switch user. Maybe even including a simplified login process using for example a pin code

    2. Being able to also switch back end user context. For IFS10 we can use Run… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Highlight hidden columns in calendar control

    Tiny request for those configuring calendar in user step: In the Edit columns section could it be possible to highlight columns that are hidden?

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. PDF Viewer

    Currently, the user step includes:

    Image Viewer

    Image Selection

    File Gallery

    However, we are missing a PDF Viewer, which would be a very powerful addition.

    Purpose and Benefits:

    In-app Document Viewing:
    Allow users to open and view PDF documents directly within the workflow, without needing to open an external application.

    Document Editing:
    Enable users to make basic changes to PDF documents (e.g., annotations, comments, or form filling) and save the updates.

    Multi-page Support:
    The viewer should support navigating through multiple pages easily.

    Digital Signature:
    Allow users to sign PDF documents directly within the viewer.

    Full-Screen Mode:
    Users should be able to view PDFs in full-screen mode, either by clicking the viewer or by setting it as the default viewing mode.

    Currently, the user step includes:

    Image Viewer

    Image Selection

    File Gallery

    However, we are missing a PDF Viewer, which would be a very powerful addition.

    Purpose and Benefits:

    In-app Document Viewing:
    Allow users to open and view PDF documents directly within the workflow, without needing to open an external application.

    Document Editing:
    Enable users to make basic changes to PDF documents (e.g., annotations, comments, or form filling) and save the updates.

    Multi-page Support:
    The viewer should support navigating through multiple pages easily.

    Digital Signature:
    Allow users to sign PDF documents directly within the viewer.

    Full-Screen Mode:
    Users should be able… more

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Designer  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Component Step in workflows

    Possibility to modify an already added component step in a work flow. Currently after we add a component as a step in a workflow, there is no possibility for us to modify that step. We have to create a new step and map the component from scratch. In flow classic, it was possible for us to change the existing step. This additional work is hectic. please allow developer to change the Component step within a flow when by modifying the current step. Also make component workflows available for every application instead of the application it is developed in.

    •  

    0 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Designer  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. View Code in Designer

    In Flow Connect, it would be nice to view the code of the workflow to make changes in bulk. This was possible in Flow Classic.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Designer  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Enforce Multi-Factor Authentication (MFA) for External Email Accounts

    Force Users to Enable Multi-Factor Authentication for External Email Providers

    Requested By:
    Customer Direktoratet for Samfunnssikkerhet og Beredskap

    Description:
    As requested by Customer DSB, the system should enforce Multi-Factor Authentication (MFA) for users who authenticate using external email providers such as Microsoft, Gmail, or other supported identity providers.

    This requirement is intended to enhance security and reduce the risk of unauthorized access caused by compromised passwords.

    Objective:
    Ensure that all users authenticate using two or more verification factors, improving account protection and aligning with modern security standards.

    Proposed Behavior:

    When a user logs in using an external provider (e.g., Microsoft, Google, or other supported identity providers), the system should verify whether MFA is enabled for the account.

    If MFA is not enabled:

    The user should be prompted to enable MFA before proceeding.

    Access to the application should be restricted until MFA is activated.

    The system should support common MFA methods, including:

    Authenticator applications (e.g., Microsoft Authenticator, Google Authenticator)

    Acceptance Criteria:

    Users signing in with Microsoft, Google, or other supported providers must have MFA enabled.

    If MFA is not enabled, the user is not allowed to access the system until MFA is configured.

    The system displays clear guidance for enabling MFA.

    MFA status is validated during authentication.

    Administrators may optionally enforce this policy globally.

    Benefits:

    Improved protection against account compromise.

    Reduced risk from phishing and password leaks.

    Compliance with customer security requirements.

    Stronger overall platform security.

    Force Users to Enable Multi-Factor Authentication for External Email Providers

    Requested By:
    Customer Direktoratet for Samfunnssikkerhet og Beredskap

    Description:
    As requested by Customer DSB, the system should enforce Multi-Factor Authentication (MFA) for users who authenticate using external email providers such as Microsoft, Gmail, or other supported identity providers.

    This requirement is intended to enhance security and reduce the risk of unauthorized access caused by compromised passwords.

    Objective:
    Ensure that all users authenticate using two or more verification factors, improving account protection and aligning with modern security standards.

    Proposed Behavior:

    When a user logs in using an external provider (e.g., Microsoft,… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating