181 results found

1. 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

2. Add an “Archive” Option for Deleted Applications in Flow Connect

   I would like to have an archive option in flow hub as Currently, when an application is deleted in Novacura Flow Connect, it is permanently removed without an intermediate archive state. This limits the ability to recover deleted applications within a safe retention period and increases the risk of accidental data loss.
   I propose adding an Archive option for deleted applications in Flow Connect. With this feature Deleted applications would first move to an Archived state instead of being permanently deleted immediately.
   Archived applications remain visible in a dedicated “Archived Applications” list for a defined retention period (e.g., 30 days). Users can Restore an archived application to its previous state within the retention period. After the retention period, the application is permanently deleted automatically. Administrators can also manually Delete an archived application immediately if needed. This would align Flow Connect with common application-management patterns in other cloud platforms and provide a safer, more flexible workflow for teams managing migrations and application lifecycle changes.

   I would like to have an archive option in flow hub as Currently, when an application is deleted in Novacura Flow Connect, it is permanently removed without an intermediate archive state. This limits the ability to recover deleted applications within a safe retention period and increases the risk of accidental data loss.
   I propose adding an Archive option for deleted applications in Flow Connect. With this feature Deleted applications would first move to an Archived state instead of being permanently deleted immediately.
   Archived applications remain visible in a dedicated “Archived Applications” list for a defined retention period (e.g., 30 days).… 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  ·  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

3. 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

4. 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

5. 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

6. 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

7. Segregration of access for Manage User and groups

   The Novacura Access Group is not sufficiently segmented and should be divided into more clearly defined roles.
   A suggested structure is:
   Manage Users
   Provides access to invite users and assign them to End User Groups.
   Manage End User Groups
   Provides access to create and modify End User Groups.
   Manage Admin Groups
   Provides access to create and modify Admin Groups, as well as assign users to these groups.

   12 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

8. API Documentaion

   Hi When we create a machine workflow and want to expose them via API. A documentation integration like swagger would be nice to have an overview and specification of the APIs. Instead of going to the flow right click generate web link and there we see what are the inputs and endpoint

   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  ·  Integration  ·  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. 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

10. 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

11. AI-generated documentation for Novacura Flow apps

    Why?
    Users who create apps in Novacura Flow need an easier way to document what an app does, how it is structured, and how it should be maintained. Manual documentation is time-consuming, often skipped, and can quickly become outdated.

    What?
    Add a built-in AI function in Novacura Flow that can generate documentation for an app created in the product.

    The function should analyze the app structure, including flows, steps, data sources, variables, integrations, business logic, screens, and user interactions where available. Based on this, it should generate clear app documentation that can be reviewed, edited, and saved by the user.

    The documentation should help both app creators and future maintainers understand the purpose, behavior, dependencies, and important implementation details of the app.

    Acceptance Criteria:
    [ ] A user can trigger AI-generated documentation from within a Novacura Flow app.
    [ ] The generated documentation describes the app purpose, main flows, screens, logic, data sources, integrations, and dependencies where detectable.
    [ ] The user can review and edit the generated documentation before saving or exporting it.
    [ ] The documentation clearly identifies areas where AI is uncertain or where information is missing.
    [ ] The feature is available as a built-in product function, not as an external tool.
    [ ] The generated documentation is structured consistently so it can be reused for handover, support, and maintenance.

    Why?
    Users who create apps in Novacura Flow need an easier way to document what an app does, how it is structured, and how it should be maintained. Manual documentation is time-consuming, often skipped, and can quickly become outdated.

    What?
    Add a built-in AI function in Novacura Flow that can generate documentation for an app created in the product.

    The function should analyze the app structure, including flows, steps, data sources, variables, integrations, business logic, screens, and user interactions where available. Based on this, it should generate clear app documentation that can be reviewed, edited, and saved by the user.

    … more

    4 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  ·  AI  ·  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. 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

13. 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

14. Support for deciding which clients (portal vs. clients) an end-user can log in to

    Having a way to stop users or groups of users from being in the web client could be nice. The problem we are having is when users are completing registration they are getting driven to apps, but right now we are onboarding a lot of "portal only" users. So they get confused. We are sending a welcome email to link them to the board, but sometimes people don't read the email. When everything is said and done we have people who are web client only, portal only, and some who need both.

    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. Compressing images

    When compressing images it would be nice to be able to say what size you want the image to be uploaded in, not what percentage it should be compressed to. For example, if you take a picture with an iPhone the image will be 18MB while if you take the same picture with an iPad it will be 4MB, then it would be nice to be able to say that we want images that are 5MB and the Flow client will then compress the images that are larger than that to the desired size, while the images that are smaller will be in full quality.

    When compressing images it would be nice to be able to say what size you want the image to be uploaded in, not what percentage it should be compressed to. For example, if you take a picture with an iPhone the image will be 18MB while if you take the same picture with an iPad it will be 4MB, then it would be nice to be able to say that we want images that are 5MB and the Flow client will then compress the images that are larger than that to the desired size, while the images that are smaller… more

    4 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

16. 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

17. 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

18. 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

19. Share Functionality Exporting A Package or Application

    We understand the “share” functionality is Connect’s version of exporting .wap files, however we see the lack of being able to export…when there is an import functionality…as a miss. The process of exporting/cloning application into new locations has led to difficulties that could be better worked through with an export option.

    10 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  ·  AI  ·  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. Allow Barcode scanner feature on/off for input fields

    Some customers don't want the option to use barcode scanning (camera) on some input fields and want it on others (to prevent data errors)
    We should have an option to enable / disable this.

    •  

    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)  ·  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