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

243 results found

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

    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. The "Auto Focus " option currently fails to place the cursor in the first input field when it is the second element in a flow after a list box. This results in a non-intuitive user experience, requiring users to navigate through other elements before reaching the input field. We request an enhancement to ensure the cursor is directly placed in the first input field, or at least the list box, when "Auto Focus Input" is enabled, providing a smoother user experience.

    7 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. 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)
  5. We request an enhancement to enable script steps to directly interact with included workflows and machine steps. Currently, this limitation leads to complex workarounds and inefficiencies, particularly when processing datasets in loops. With the proposed improvement, users can easily call included workflows and machine steps from within script steps, streamlining data processing and reducing the need for intermediary datasets. This enhancement will significantly improve workflow efficiency and simplify task execution.

    7 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)
  6. Currently, when clicking "Add Workflow to Menu" in a workflow, the list of server objects displayed is filtered to show only menus, which is beneficial. However, the list still includes "folders" that do not contain any menus, leading to unnecessary clutter. We kindly request an improvement to this feature that removes folders without menus from the view.

    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

    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)
  7. Currently, the menu sorting order in our system is limited to priorities 1-10, which restricts our ability to effectively organize a large number of menus. We kindly request an enhancement to the sorting functionality that allows for a broader range of priorities, specifically from 1 to 100 or, ideally, any integer. This would provide us with much-needed flexibility and control in managing our extensive menu collection, leading to a more seamless user experience and improved efficiency.

    7 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)
  8. Improve the import capability for complex customer start inputs, which include records, tables, and values. Currently, the system's ability to save such inputs has been compromised, even for minor changes like renaming a simple value. The proposed enhancement seeks to reinstate the previous functionality and ensure seamless saving of these inputs, thereby optimizing the user experience and productivity.

    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  ·  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)
  9. Currently, in the DataGrid component, setting a number format is fixed and cannot be parameterized. This limitation hinders the flexibility of developers to customize the number formatting based on different data and user requirements. As a user of the DataGrid component, I request the implementation of a customizable number format parameter to enhance the control and usability of this feature.

    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)
  10. Currently, when using the REST connector, if a stream is gzip or deflate compressed, the data received is successful with a StatusCode of 200, but the body content is garbled due to the Content-Encoding being gzip'd at the source. This requires additional manual effort in transforming the data to be usable.

    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  ·  Connectors  ·  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. The proposed feature centers on enabling developers to incorporate variables into the priority settings for buttons. This means developers can assign dynamic priority values to buttons based on contextual factors, such as user interactions, screen content, or application states. The platform will use these variable priorities to determine the order in which buttons appear on the user interface.

    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

    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)
  12. In Portal 2, the current record selection listeners provide a powerful feature to update portlets when new records are selected. However, we have noticed that the listeners do not trigger when records are deselected, resulting in stale data being displayed in other portlets. To improve the user experience and maintain data accuracy, we propose enhancing the record selection listeners to include deselect events or introduce a new listener specifically for deselecting records. This enhancement would enable portlets to refresh in real-time when records are deselected, ensuring that users always have up-to-date information displayed across all relevant portlets.

    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

    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)
  13. 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)
  14. 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)
  15. Currently, when right-clicking a user step in the application, users have the helpful option "Select Everything East of Item" available in the context menu. However, we propose the inclusion of additional options, specifically "Select Everything North of Item" and "Select Everything South of Item," to further enhance the usability and flexibility of the user interface.

    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

    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)
  16. While using the hover over menu on a fragment step, users face difficulty when sequence arrows are present and coming into the included workflow step that they are hovering over. When attempting to drag the mouse downward to access the update arrow on the hover menu, the system mistakenly interprets this action as an attempt to interact with the arrow, causing the hover menu to disappear.

    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)
  17. Currently, one of the challenges we face when reviewing the version history is the absence of timestamp details for when a specific change was made. This lack of chronological information makes it difficult for us to quickly ascertain whether a flow (or any other element) has been recently modified or if the changes were made a long time ago.

    To address this issue, I propose the implementation of a simple yet powerful addition to the version history – the inclusion of the date or year when each change was made. By adding this vital piece of information alongside the version…

    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)
  18. The feature in question is the "Offline Data Update Interval" setting, which prompts users to update their offline data after a specified time interval. While this functionality is beneficial in maintaining up-to-date data, we observed that users have the option to dismiss the update prompt by clicking "No" and proceed with launching the flow without refreshing their offline data.

    We have tested this behavior in the Windows 10 Flow Client, where we configured the offline data update interval to 1 hour. As expected, we received the "Offline Data Expired" notification when the interval elapsed. However, we found that clicking "No"…

    19 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. The MAP AS function has proven to be an invaluable tool for us to streamline our workflows and avoid using cumbersome for loops. Nevertheless, we have run into situations where we were forced to switch back to using for loops due to the absence of an auto-incrementing variable within the map function.

    To elaborate, we frequently encounter scenarios where we need to remap filenames within a FileGallery to conform to specific naming conventions or add suffixes like "Pic 1," "Pic 2," and so on. Currently, this cannot be efficiently achieved using the map function, as there is no straightforward way…

    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)
  20. We would like to have a new functionality to filter server content window to display only flows with updates

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