Skip to content

Novacura Flow Classic

Welcome to the ideas forum for Novacura Flow. Please share your ideas for how we can make Novacura Flow better. We are listening and we use this feedback to prioritize our roadmap!

Novacura Flow Classic

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

78 results found

  1. In the current Web NG client, when users perform searches, the results do not indicate the menu under which each workflow is located. This lack of contextual information can lead to confusion, especially when multiple workflows have identical or similar names but reside in different menus.

    Proposed solution is to improve the search functionality within the Web NG client to include additional details in the results, specifically the menu location of each workflow. This information should be displayed clearly beneath the workflow name in the search results. Providing this contextual detail will help users quickly identify the correct workflow, reducing…

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. It would be great to have two separate List Selections in a User Step. These list selections should impact each other such that what I select in List Selection 1 would change what is seen in List Selection 2. This is possible in 2023.3 Portal, but this functionality is needed in the Android, iOS and webclient.

    48 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Currently our offline mode is loading the data set into the client and later on the actions are pushed out and synchronized when a connection is established.

    Especially in Field Service, it is sometimes unclear and sometimes the technician has a connectivity and sometimes he has not. We would use the offline mode in that case to be safe. Also there are business cases, where the execution of work takes hours. But since the data sets can only be loaded before starting a flow, the new data can only be shown after the app is closed, the set reloaded and…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Currently offline workflows support downloading data into the client and run workflows without an internet connection. However this data purely reside on memory when it comes to mobile devices.

    If the application has to be closed for any reason, whole of the offline data will be lost.

    This is essential for situations like off site asset count in remote locations. etc.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. In the current Flow mobile client, when operating in offline mode, users face a restriction where items in the inbox are marked as "Finished" after being acted upon. This status change makes the items inaccessible for further review, although they remain visible in the inbox until the user reconnects to the internet. This behavior limits the ability of users to revisit completed items for verification or review purposes.

    Proposed solution is to implement a feature allowing users to toggle the visibility and accessibility of items marked as "Finished" in the inbox while in offline mode. This functionality would enable users…

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Requesting a feature enhancement in Portal to allow for the customization of pop-up controls during the review process. Currently, the mandatory provision of an exit button for publishing results in redundant close options (close button and 'x') at the bottom of the pop-up. It would greatly enhance user clarity and experience if administrators could define the visibility of the default close option, providing flexibility in tailoring the interface to specific workflow requirements.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. The feature in question is the "Offline Data Update Interval" setting, which prompts users to update their offline data after a specified time interval. While this functionality is beneficial in maintaining up-to-date data, we observed that users have the option to dismiss the update prompt by clicking "No" and proceed with launching the flow without refreshing their offline data.

    We have tested this behavior in the Windows 10 Flow Client, where we configured the offline data update interval to 1 hour. As expected, we received the "Offline Data Expired" notification when the interval elapsed. However, we found that clicking "No"…

    20 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Our customers have expressed a strong demand for a more efficient and seamless image annotation process within the FLOW Client app. Currently, users face inconvenience and inefficiencies as they need to save images locally and then upload them separately before performing annotations or markups. To address this concern and elevate the user experience, we request the integration of native image markup and annotation capabilities directly within the FLOW Client app, enabling users to capture images, annotate them, and instantly save or submit the annotated pictures.

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. In a lot of cases, the customer has a list of eg. 10 Time types, but he mostly only uses work and travel time. It would be great to have a function similar to "default", where you can define favorites that should be on top. Very similar to how we can define them in the inbox.

    Workaround is now to sort the list accordingly and solve it in flow script. But this would make life a bit easier.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. We utilize scanner events to scan barcodes, extract item numbers, and retrieve item descriptions, locations, and stock balances. While this process generally works fine, we've noticed that Flow attempts to execute the API for connector steps even before scanning.

    In the screenshot provided, you can see that there are three APIs that utilize the scanned item number to collect data. These APIs are triggered when the user step is displayed for the first time, even if the item number is blank. This leads to issues and longer response times.

    If we bypass scanner events, the APIs should still run. However,…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. At present, the NG Web Client lacks branding capabilities. This limitation restricts the ability to customize the look and feel of the platform, which could affect the user experience and the alignment with the company's branding guidelines.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. We propose a feature enhancement to address the inconsistency in link widths within the NG WebClient. Currently, varying link widths create a visual disparity, particularly when compared to mobile clients. To enhance the overall aesthetics and maintain visual coherence across platforms, we request the implementation of a feature that ensures consistent link widths in the NG WebClient. This adjustment will contribute to a more polished and uniform user interface, providing a seamless experience for users across different devices.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Currently Swedish, Norwegian, Finnish, German, French, Polish and English are the supported languages in flow similarly we need Italian added as well.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. In our current Flow design, the use of checkboxes creates unnecessary and excessive whitespace, particularly when two checkbox elements are placed close together. This not only affects the aesthetic appearance of the interface but can also impact the usability by requiring additional scrolling and making the layout appear disjointed.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. We would like to have the feature to export datagrids in workflows as excel files

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Users of the Flow mobile application face a limitation when interacting with data grids that contain checkboxes. Currently, to select a checkbox within a data grid column, users must navigate into each individual row and then set the checkbox. This process is seen as cumbersome and inefficient, especially for tasks requiring multiple selections across several rows.

    The proposed solution is to introduce the functionality that allows users to directly select checkboxes from the main view of the data grid, without the need to navigate into each row. This enhancement should apply to all Flow mobile clients, streamlining tasks that involve…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Current login screen only shows "Flow 6" (not even Novacura is mentioned).

    We are gearing up adding external partners to the portal. It both creates suspicion and looks amateurish without our company name, and preferable logo, in the login screen. Enabling us to brand the layout with name, logo and maybe even colour would have made a big impact on the first impression.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. In the current version of Studio, there is a limitation in detecting data changes made during a User Step. Proposed solution is to enhance Studio to include the capability of detecting any data changes that occur within a User Step. Following this detection, these changes should be easily accessible and usable as variables or properties in subsequent steps of the workflow. This feature would allow users and developers to dynamically adjust the workflow based on user inputs or changes, greatly enhancing the flexibility and functionality of Studio.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Currently, the warning message displayed when a user attempts to quit an application in Flow may not be sufficiently informative or persuasive in communicating the potential consequences of exiting, such as unsaved changes being lost.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Requesting the option to standardize the visual presentation of the Inbox button to match the flat layout of other interface elements. Currently, the raised "depth" of the Inbox button stands out and lacks consistency with the rest of the interface. Providing a toggle or setting to align the appearance of the Inbox button with other buttons would enhance visual coherence and streamline navigation for users.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4
  • Don't see your idea?