Skip to content

Novacura Flow Connect

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

Novacura Flow Connect

Categories

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

284 results found

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

    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)
  2. I want to be able to automatically revert an old version into to the current working version, similar to Flow 6.
    Currently you have to open both the working version and the old version in Designer and manually copy between them.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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.

  3. Immediately after committing a version in Designer, a new working version is created and I can not see the information about the last commit.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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.

  4. I want to be able to duplicate applications. If an application using components is duplicated, it should keep the existing references.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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.

  5. When a filter field is setup with the "List Of Values" for the "Edit as" type, it would be very helpful to be able to select the "Contains" operator. Currently the "Equals" operator is the only available selection for list of values fields.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Portal2 Gantt sorting by click on one of the columns presented. Example: Standard sorting is to sort by work task number. One of the columns shown is equipment object id or department and the user wants to sort by Equipent object by click on that column. (or date, or department, or priority etc)

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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).

    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. This comes from Billerud: As a user
    I want to be able to click one button to navigate to the current date
    so that change dates to look at information but still with one click come back to the now

    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

    1 comment  ·  Portal  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. The Flow app's iOS version currently offers inconsistent barcode scanning performance, especially when barcodes have certain backgrounds. Users experience significant delays and challenges in positioning the device correctly for a successful scan. This poses a problem for customers with large asset tracking needs who prefer to use Apple devices. To address this, integrating a dedicated scanner library for the iOS version will enhance performance, ensuring that it matches or exceeds the capabilities of the Android client.

    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. In the current NG webclient, the GRID columns with "FIT" size mode aren't dynamically adjusting to window resizing. When viewed on full screen, all columns are visible. However, when the window size is reduced, certain columns disappear, forcing users to scroll horizontally.

    Proposed solution is to enable truly responsive design for GRID columns, especially those with the "FIT" size mode. When a user adjusts the window size, columns should auto-adjust their width proportionally, eliminating the need for horizontal scrolling. This ensures a seamless user experience across various window sizes.

    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. In Portal2, when using a List of Values (LoV) tied to a table column, there seems to be an issue displaying the data if the LoV's data source is a Flow with an input filter. The data is displayed if no input filter is considered, but it does not show up when inputs are taken from Portal.

    Proposed solution is to address the inconsistency by ensuring that the List of Values in Portal2 displays data correctly even when the LoV uses a Flow with input filters from Portal. It's crucial to provide consistent visibility and accessibility of data irrespective of…

    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

    under review  ·  0 comments  ·  Portal  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. In the current implementation of a DataGrid, when a user adds a new row, the text from non-editable (display-only) columns still appears, giving an impression of inconsistency in the UI. This can be confusing for users.

    Proposed solution is for non-editable columns to be hidden or made visually distinct when adding a new row to a DataGrid. This way, only the relevant editable fields will be displayed, providing a more intuitive 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)
  13. We kindly request the addition of a new feature, "Grouping," to the control checklist subtask within workflows. This enhancement aims to optimize user experience and efficiency when dealing with extensive checklists. By introducing a grouping option, users can achieve a clearer overview of checklist items, particularly in cases where there is a substantial number of items. This feature will greatly improve workflow management and streamline task execution, contributing to a more productive and organized working environment. Your consideration of this feature request is greatly appreciated.

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

    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. Our customers have expressed a need for offline compatibility and expanded image source options for the Image Selection Input Component. Currently, the component only supports URL-based image sources, limiting its use when offline access is required. To enhance the component's utility, we propose enabling additional image sources, such as JEPG, allowing users to utilize local data sources like tables in IFS. This enhancement would make the Image Selection Input Component fully offline compatible, significantly extending its usability and versatility for various use cases.

    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. We kindly request the implementation of a more intuitive and efficient row deletion process in the NG Webclient datagrid, reminiscent of the user-friendly experience offered by the previous Novacura web client. The proposed enhancement aims to simplify the current multi-step deletion procedure, which includes clicking an empty circle, moving to the top of the datagrid, and confirming the deletion.

    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. Our users have reported an issue with the Bluetooth input in user fields on a mobile device. The problem arises when a value is input via Bluetooth into a user field, then manually overwritten, and a subsequent attempt is made to input a new value via Bluetooth. In these cases, the Bluetooth input fails to populate the field unless the user navigates to a different user step and then returns. This could potentially be due to the iOS keyboard taking over control after manual entry. This problem has been encountered while capturing Ultrasonic Thickness readings from an Olympus 38DL+ thickness…

    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)
  18. Users want the ability to record videos directly from Android devices using the Flow File gallery and Camera input. Currently, they are able to take pictures and access files, but they cannot record videos directly from the app.

    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)
  19. In the current NG webclient, search queries are not maintained after completing a flow. Users have to re-enter their search each time they finish a flow, which can disrupt their workflow and reduce efficiency.

    To enhance user experience and productivity, we propose to preserve the search queries even after completing a flow. This means that after a user finishes a flow, their previous search query would still be in place, saving them the effort of having to re-enter it.

    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)
  20. Currently in WebNG, the workflow interface occupies the entire screen, hiding the left sidebar which houses important menus and settings. This design requires users to exit their workflows to access these menus, which can disrupt their workflow and reduce efficiency.

    To enhance user experience and productivity, we propose a design change to allow the left sidebar to remain visible and accessible even while within a workflow. This change would allow users to quickly access menus and settings without needing to exit their workflows.

    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?