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

77 results found

  1. Currently in the flow any file (image/ documents) need to be downloaded in to the device before we can view them. Flow does enable displaying images in the user step, but they need to be be deployed into ftp or other hosting location.

    We commonly gets asked from the customers for the possibility of preview/view this documents within the app without needing to downloading to the device.

    Downloading the files to devices will cause files been left in download folders reducing the disc space as well as making too many copies of the sensitive information.

    Some customers has gone to…

    3 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. In many cases user would like to use the data in Novacura Clients in other apps. Like to copy text from a work order and past into an e-mail. Or to fetch the work order number and query in another app.

    Today it works in Android client and of course the web client. It doesn't work in the iOS client.

    ==>Make all clients similar with same capabilities.

    3 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. We would like to have the feature for reloading sub-tasks within a User Step. The subtask should be updated with data from a Machine Step, provided that the a machine Step is connected to the User Step using a Data Arrow. If so, the User Step will be updated when a sub task in the User Step is done and the User returns back to the User Step. The reload of data can also be triggered manually by swiping down. Works in Android app but not in Web client.

    3 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. As a user, when working with a datagrid, I often find it difficult to determine whether the data is editable and which specific columns allow editing. This lack of clarity can lead to confusion and potential errors when interacting with the grid. To enhance user experience and improve usability, I would like to request the implementation of a visual indication for editable columns in the datagrid.

    3 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. Customers using mobile clients on compact, hand-held devices tend to utilize List Multi-Selection Input for its displayed data compression and dynamic fields. What is not available, when comparing to the data grid, is the possibility to mark-to-select-all. It's rather cumbersome to manually select/de-select all the records. We've currently designed a work-around but would appreciate if that is an in-buil feature. Take a look at the attachment.

    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)
  6. 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)
  7. As a consultant/developer, managing multiple clients often requires logging in and out frequently due to the limitation of one user/license per session. This process is time-consuming and inefficient.

    Proposed solution is to enable admin users to be concurrently logged into multiple platforms - namely the Portal, Flow Client, and Flow Portal - without the need for separate licenses for each. This will streamline workflow management for consultants and developers who regularly need access to multiple clients or sessions simultaneously, significantly enhancing productivity and user experience.

    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)
  8. In the current implementation, the data grid search functionality searches through all columns, including those that aren't displayed in the data grid or are not set up under "Edit columns."

    Proposed solution is to introduce a customizable search functionality in data grids where users can selectively choose which columns to include in the search. This can be achieved by adding a checkbox option under "Edit columns" labeled as "Searchable". By default, all columns can have the "Searchable" checkbox marked to ensure compatibility with the existing behavior. Users can then choose to deselect certain columns if they don't want them to…

    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)
  9. Users experience challenges with offline workflows in Flow-app due to network variability. Devices connect to various networks throughout the day, but only one network provides the required server connection for data sync. As a result, offline transactions get stuck in a "failed" state, necessitating manual retries once the device reconnects to the secure network.

    Proposed solutions are to implement a feature in the Flow-app to detect the current network. The app should only attempt to write back to the server when connected to a predefined, specific network. Alternatively provide users with an option to bulk retry all failed offline transactions…

    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)
  10. Improve multi-select grid usability on the latest mobile client by enabling "Click Anywhere To Select" functionality, similar to single select grids. Also, align the de-selection behavior with single-select grids, allowing users to "Click again to de-select record," creating a consistent and intuitive user experience across different grid types. This enhancement aims to optimize record selection and de-selection, particularly on small screens, for enhanced usability and efficiency.

    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)
  11. Currently, when logging into the mobile Flow application, users input their passwords into an obscured field. This feature request proposes the inclusion of an option to show the password while typing to aid users who may struggle with entering their passwords correctly when they can't see the input.

    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)
  12. When we need to switch in the NG Client from one environment to another (ex : from prod to test) we have to do the following:

    1. click three dots

    2. click sign out (why make this two steps?)

    3. click yes to confirm logout

    4. click disconnect

    5. click yes to confirm disconnect

    6. then click prod link

    In previous versions of flow, we could just click a favorite and go to the other server.

    There needs to be a much quicker way to a) signout and b) disconnect and get to the main page.

    Ideally, there would just be a disconnect link within flow…

    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)
  13. Implement a feature that allows users to customize menus and create favorites within the application. This feature will enable users to add frequently used flows to a personalized favorites section for quick access. Additionally, users should have the option to show or hide specific flows on the menu, providing them with a more streamlined and efficient experience, particularly on mobile devices. By allowing users to tailor the menu to their specific needs, this feature will enhance productivity and user satisfaction.

    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)
  14. It would be fantastic if you could extend the application's compatibility to include Bluetooth-connected Zebra scanners that are paired with other Android devices. This enhancement would not only streamline my workflow but also open up new possibilities for other users who rely on similar scanning setups.

    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)
  15. When a generated flow link is pressed on a mobile device, an pop-up message appears, asking the user if they want to start the flow.

    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)
  16. 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)
  17. 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)
  18. To present relevant information our users, we type a lot of conditions and display variables practically everywhere. On arrows, in headers, in texts, in prompts and so on. Those fields can not be "opened" like a script-field (Condition To Hide) and when you try to navigate left or right in that field, it jumps around a lot.

    Development is overall fast in Flow but those finishing touches that makes a good applikation great takes time.

    Can we get the possibility to open these fields up to speed up development?

    Thanks!

    And I guess you already got a request to make…

    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. 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)
  20. It would be great to have a radio button 'list' input, like Binary Option Input, but more than 2 available options.

    Like a combination of Menu Selection Input and Binary Option Input: functinality from menu selection, interface like binary option input.

    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)
  • Don't see your idea?