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

244 results found

  1. Currently, the process of using a table variable within an SQL machine step in our workflow involves a workaround using JSON, which can lead to extended user wait times due to additional processing. Additionally, Flow's handling of table iteration within SQL is notably slower compared to direct SQL operations on large datasets. Our proposed feature request aims to streamline this process and enhance performance. We kindly request the implementation of the following enhancements to Flow's SQL machine steps:

    Direct Reference to Flow Tables: Enable the ability to directly reference Flow Tables within SQL machine steps. This functionality would eliminate the…

    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  ·  Studio  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. The current Pick menu within the workflow interface presents several counterintuitive aspects that could be streamlined for a more efficient and user-friendly experience. We propose the following enhancements:

    Automatic Selection of Single Versions:
    When a flow with only one version is selected, the system should automatically utilize that version instead of prompting the user to choose. This reduces unnecessary steps and simplifies the process.

    Default Selection of Current Version:
    Implement a feature that enables the automatic selection of the current version by default, allowing users to easily proceed without intervention. Users can then manually select a different version when required.

    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  ·  Studio  ·  Admin →
    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 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.

    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. I have several usersteps in multiple workflows, where the only purpose is to scan a barcode. I`ve been able to get the novacura app on mobile devices to automatically enter the input field (with the "Auto Focus input" turned on in the app), but I cannot get novacura to also select the camera. They need to click on the QR-icon every time. I could of course buy a bluetooth barcode reader, but I want this to work also with the mobile camera.

    Can you check if it`s possible to add QR code (camera) as keyboard type for text- and numeric…

    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

    2 comments  ·  Studio  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. We use at lot of Assertion Steps in our Flow to alert users that something went wrong. On typical example is that we usually compare the the input to a list of items. If it don’t match, the user gets a error.

    The problem with Assertion Steps is that the user have to click to remove the popup window. To be more efficient, a temporary popup would sometimes be enough.

    We can accomplish this using the Checkpoint-step and write text that covers the whole screen, as seen in the picture.

    But it would be nice to make this popup red,…

    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

    2 comments  ·  Studio  ·  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. 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)
  7. 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…

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

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

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

    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 times, certain servers may no longer be in use, or their names might change. In the current system, these outdated entries remain in the "Recent servers" list, potentially causing confusion or clutter.

    We propose to implement an option to delete previous connections from the "Recent servers" list. This feature would enhance the user experience by keeping the list tidy and up to date, reducing potential confusion or errors.

    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. We would wish that all calendars start with the same week day. For example in the filter portlet the weeks start on a sunday and in the gantt portlet on a monday.This uniform approach would ensure that everyone is on the same page regarding the start of the week.

    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

    1 comment  ·  Portal 2  ·  Admin →
    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, a search box appears automatically in a data grid, which may not be desirable in certain configurations. For example, when using a two-column data grid with interdependent list boxes, the presence of a search box can disrupt the intended user interaction.

    We propose to add an option to suppress the automatic appearance of the search box in data grids. This would give developers more control over the user interface and allow for a cleaner look in specific scenarios.

    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. We would like to have bigger scroll bars for all portlets in portal 2. Users use big screens zoomed out and have a hard time clicking on the scroll bars since they are so thin. A suggestion is to make the size of the scroll bars a user setting.

    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

    1 comment  ·  Portal 2  ·  Admin →
    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 a proper search mechanism in AD Groups and when we try to search for one group. data should be able to get sorted according to letters when we type.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Currently, modifying values in a table requires the use of Edit Operations. However, there is a need to allow temporary or inline editing of table records without employing Edit Operations. This would enable users to make temporary changes to selected records and then execute a custom workflow using a special button. The workflow's InputTable would include all records, reflecting any changes made.

    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 2  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Currently, when users render a result in the scheduler, then navigate to a different page, and later return to the scheduler page, the previously rendered result is not retained. This behavior contrasts with the functionality found in the filter portlets and the Gantt portlet, where results persist through page navigation.

    We propose that the scheduler should retain the rendered results even after navigating to a different page and then returning. This persistent rendering will provide a more consistent user experience and align the scheduler's functionality with other parts of the system.

    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 2  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Scheduler is often being used to manage allocations, with multiple allocations often tied to a single operation. While these allocations are perceived as the same object, they aren't currently treated as such in the Scheduler.

    We propose a feature that enables linked highlighting of allocations tied to the same operation. When one instance of the operation is selected, all corresponding allocations should be highlighted. The actual selected instance could be distinguished with a unique color while other instances are highlighted with another color. However, when interacting with a single instance (e.g., dragging it forward in time), only that instance should…

    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 2  ·  Admin →
    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 visual emphasis when an object is selected in the Scheduler is quite subtle. This could potentially cause users to struggle in identifying their selected object, especially in a dense schedule.

    We suggest enhancing the object highlighting functionality in the Scheduler. This could involve introducing a more pronounced visual cue, like a more prominent shadow or highlight. It would be beneficial to make the intensity of this visual cue customizable. Additionally, users should be allowed to choose the color of the highlight, providing another layer of customization and personalization.

    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 2  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. In the current design, when users scroll horizontally in data grids with many columns, the row selection checkbox moves with the scroll. This can make it difficult for users to select the correct line, especially when dealing with extensive data.

    We propose a feature to lock the row selection checkbox's position on the left side of the data grid. With this feature, even when a user scrolls horizontally through the grid, the checkbox remains in a fixed position, making it easier for users to handle selections.

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