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

299 results found

  1. 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)
  2. 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)
  3. 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)
  4. 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)
  5. 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)
  6. 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)
  7. 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)
  8. 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)
  9. 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.

    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. Currently, users must manually select dates in both the filter portlet and the Gantt date picker when they wish to restrict the data source to specific dates. This process is tedious and requires the portlet to load twice.

    We propose a feature that allows synchronization between date pickers in the filter portlet and the Gantt. There should be a setting in the listening portlet that enables users to link its date pickers to one or two date pickers in the filter portlet. When the user filters on specific dates, the linked date pickers should automatically update, reducing manual steps and…

    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)
  11. 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  ·  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.

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

    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. Currently in Flow Studio, users are unable to bypass "interactive" elements, such as checkboxes, with a barcode scanner or the "Enter" button. This limitation disrupts the scanning process, adding unnecessary steps for the user.

    In the meantime, users have to create a workaround by placing the checkbox in a user step before or after the barcode scanning step. However, this is not an optimal solution as it requires additional user steps and makes the workflow less efficient.

    Proposed Solution: We request the development of a feature that allows the barcode scanner to bypass interactive elements in the flow. This will…

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

    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. In the new web client, the current flow name search allows filtering by typing a partial name. However, we would greatly appreciate additional search options such as "wildcards," "starts with," "ends with," and "contains." These enhancements would enable more refined searches, specifically allowing users to locate flows that begin with a certain pattern, end with a specific string, or contain a particular sequence. Implementing these features would significantly improve the flow discovery process, increase user productivity, and enhance the overall user experience in the web 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)
  16. Empowering Precision and Control with MidpointRounding in rounding processes with two conventions
    1. Rounding away from zero
    2. Rounding to nearest even

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

    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. As a Flow Developer, I should be able to disable focus on any element in a User Step.

    Currently, focus is set on User Step Elements sequentially. For example, if you have a Text Input and a Datagrid, once the text input is entered through scanning focus will be set on the Datagrid. In this same example, if focus was disabled on the Datagrid, the user could scan data into the text input and move forward with a default button control. This would allow a user enter text into a text input, and show the growing list in a data…

    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. Currently, end users can be grouped, but all users with access to a Page can see all Applications on that Page, including Applications they may never use.

    In Classic, workflows could be added to multiple menus, and menu visibility could be controlled for different users or roles. This allowed the same workflow to be available in multiple places while controlling which users actually saw it.

    We would like similar functionality for Applications, allowing visibility to be controlled by user group or role at the individual Application level. This would allow Pages to contain Applications for multiple user groups while ensuring…

    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. Currently external systems can only authenticate with the Automation Access Key in x-api-key.

    There are some systems that are limited to what they can send, like the IFS External Reporting Gateway:

    Authorization Request Header format: "Authorization": ["Bearer <API Key>"]

    From https://docs.ifs.com/techdocs/26r1/050_reporting/000_reporting/251_operational_reporting/001_report_design/010_operational_reports/400_external_reporting_gateway/#report_generation_trigger_requests_via_ifs_connect

    Increasing the authentication options for our Automations, in this case changing the header name zo "Authorization", would enable some use cases for Flow around IFS Reporting

    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

    0 comments  ·  Integration  ·  Admin →
    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?