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

80 results found

  1. buttons need to be short text, but to explain a button a tiptool function should be very great to have where we may explain a longer text.

    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)
  2. We would like to see tabs in the Webclient with startad flows. It's a modern efficient way of switching between ongoing work or to get information.

    On example is that we want got an item search and we want to keep that open and accessible regardless of what other flows we have started.

    Thanks!

    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)
  3. Managing the installation and setup of the Novacura mobile app involves utilizing application configurations. In this process, offshore crews receive devices upon boarding, and configurations are implemented to ensure a seamless transition when transferring devices to the next crew during off-hitch periods. This approach facilitates efficient deployment and setup, allowing for a smooth handover of devices and continuity of Novacura mobile app functionality across different crews.

    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)
  4. We have recently incresed the use of the Webclient on stationary desktops and the users are missing some features.

    The UI works fine with autoselet-lists and grids, but it still requires the users to use the mouse a lot.

    We would like to see the possibillity to add keyboard shortcuts to elements and buttons.

    We got a user step with seven buttons and it would be great if we could connect F-keys to these button for a better user experience.

    Thanks

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

    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)
  6. 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)
  7. 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)
  8. Implementing an auto-logout feature for a mobile client on idle time is a common security measure to protect user data and privacy

    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)
  9. Currently, the Enter key does not advance to the next step when an editable datagrid (DG) is present. This feature request proposes that when there's an input field activating a button before the editable datagrid, pressing Enter should progress to the next step. Similarly, if a default button follows the editable datagrid, Enter should activate that button and proceed to the next step. This enhancement aims to streamline user interaction by treating the editable datagrid as if it does not exist or behaves similarly to non-editable datagrids in terms of Enter key navigation.

    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. 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)
  11. The WebNG Datepicker currently lacks a "Today" button, a feature that was available in the old web client. This button allowed users to quickly return to the current date, enhancing usability and navigation efficiency.

    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)
  12. Currently this feature is not available in the web client and only available for the mobile devices. The idea is to implement a push notification to a user or a group whenever a swimlane handover happens (i.e inbox items handover).

    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. 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)
  14. When data is loaded for a user step, sometimes the user may have to search for data in LOV with large volumes. Eg adding a spare part to a work order.

    Adding such a LOV to a user step may take time to load as the flow wouldn't move to the next step without completing that step. In order to improve the user experience, it is better to have the following;

    1. Load batch-wise
      The user step will get populated once the first 100 records are fetched, and the list has the option to load all or the next 100...

    2. Load…

    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)
  15. 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)
  16. After appending a new row to a datagrid, the new row insertion occurrs at the concluding section of the DataGrid, even though my current view is confined to page 1. This outcome holds the potential to bewilder users, as it contrasts with the anticipated experience. When a user undertakes the action of appending a new row to a DataGrid, it is a logical expectation that the newly added row should be prominently visible upon transitioning to the creation interface. To align with this user-centric principle, it is recommended that a design modification be implemented to guide users to the end…

    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. In ERP systems, item descriptions that are 90 characters long are common. These descriptions are crucial for end-users, especially when picking unpacked items. However, due to the current Data Grid's single-line layout, users often need to scroll both vertically and horizontally to view all the necessary information, which is not efficient.

    While questions regarding how to determine what should be displayed and how to show column headers in the second row need to be addressed, the dual line option could start as an optional element. The benefits of this improved data presentation format would likely extend to other customers with…

    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. Customers using our mobile client have reported inconsistent performance when scanning barcodes using the List multi-selection input component. Specifically, it appears that the barcode recognition feature is not always operational. Additionally, the List multi-selection input component in Flow Studio lacks barcode configuration options. There's no way to change the default "Match By: Rows" setting to "Match By: Specific Columns". This restriction limits the flexibility and usability of this component for developers.

    Proposed Solution: We propose to add the barcode configuration to the List multi-selection input component in Flow Studio. This should include the option to change the "Match By" settings…

    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. The feature request aims to bring back the "Multiline" behavior for text input boxes in the NG web client, similar to how it worked in the old web client. This enhancement will allow users to expand text input boxes to accommodate multiple lines of text, providing a more seamless and user-friendly experience when dealing with longer inputs or when composing messages that require a larger writing space. By reintroducing the "Multiline" behavior, users can effortlessly resize text input boxes, leading to improved productivity and enhanced user satisfaction.

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