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

87 results found

  1. In the current system, editing the label text of a canvas element requires double clicking on the element in the canvas view. This method can be time-consuming, especially when designing intricate flows. Moreover, without immediate renaming during the design phase, elements can end up with generic labels like “Machine Step”, “Machine Step [1]”, etc.

    We propose to introduce an option to edit the label text directly when in the edit mode of a canvas element. This enhancement would provide designers the flexibility to rename elements on the fly, ensuring clarity and reducing the likelihood of generic, repetitive labeling.

    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. Currently it is required that the "Allowed File Ending" values are hardcoded when uploading documents to the File Gallery. This rigid setup limits adaptability and increases maintenance efforts, especially when file requirements change frequently.

    Proposed solution is to integrate the capability to accept variable values for specifying allowed file extensions in the File Gallery. This dynamic approach will enable administrators or developers to modify accepted file extensions on-the-fly without the need to alter the flow itself, enhancing flexibility and reducing the need for frequent flow modifications.

    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)
  3. We kindly request the enhancement of the machine step script error handling process related to Oracle code. Currently, an error is being flagged erroneously, even though the syntax is accurate and aligned with Oracle object specifications. We propose an update to the error detection mechanism to correctly recognize the valid syntax on Oracle objects, ensuring seamless execution of machine step scripts without unnecessary interruptions.

    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)
  4. We kindly request an enhancement to the DataGrid functionality in Studio, allowing users to pre-select one or more default rows when binding the DataGrid to a table and enabling selections, including single selection mode. Currently, users are unable to set default selections, which can result in additional manual steps for users to accomplish this. This proposed feature aims to improve the usability and efficiency of DataGrids by providing the ability to automatically mark specific rows as "selected" upon binding.

    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)
  5. We kindly request an enhancement to the workflow interface by adding a convenient "Update to Latest Fragment Version" button directly accessible within the workflow view. Currently, users are required to navigate through menus to initiate updates, leading to unnecessary disruptions and potential confusion. This proposed feature aims to improve user experience and workflow efficiency by providing a seamless and direct option for updating fragment versions.

    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)
  6. When multiple parties are involved in Flow Development (eg Novacura/Partners/Customer) it is essential to control access to different workflows. One of the ways to achieve this is to allow access control to the folders created on the root (and not allowing any workflows/menus to be created without a folder)

    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)
  7. 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)
  8. The aim of this feature request is to enhance the user experience and debugging efficiency by allowing users to copy error messages. Currently, when an error occurs, the message is displayed in a pop-up or inline notification. However, the text of these error messages is not selectable or copyable.

    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)
  9. If any user has been granted the Access Level: AdministerWorkflows, they can create a Novacura Flow in Novacura Studio to grant themselves AdministerBasicData.

    We would suggest One of two things to overcome this ;

    1. Remove this Access Level as it is essentially useless now

    2. Keep this Access Level, but restrict (remove) access to use the Flow Environment connector

    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

    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)
  10. This request aims to improve the flow management and collaboration capabilities in Studio by introducing the following functionalities:

    Find Locked Flows: Add a feature to easily discover all locked flows within the Studio environment, enabling users to quickly identify which flows are currently in use or being worked on by others.

    View User Information: Provide the ability to view the user who has locked a specific flow. This information will help users to understand who is currently working on a particular flow and facilitate communication and collaboration.

    User-based Filtering: Implement a filtering option that allows users to sort the list…

    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)
  11. This feature request seeks to enable users to right-click on a flow within the Server content panel without launching the flow, allowing them to directly SHARE the flow. By implementing this functionality, users can conveniently and efficiently share their flows with others, eliminating the need to open the flow first, which would enhance the overall user experience and streamline the flow sharing process in 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  ·  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. 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.

    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)
  13. 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)
  14. 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)
  15. 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)
  16. Empowering Precision and Control with MidpointRounding in rounding processes with two conventions
    1. Rounding away from zero
    2. Rounding to nearest even

    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

    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)
  17. As Flow Developers, we often find ourselves striving for optimal workflow efficiency and effectiveness. To facilitate this, we propose a feature that combines two essential elements: enhanced flow analytics and seamless Copilot integration.

    Key Benefits:

    Route Performance Insights:

    Percentage-Based Route Usage: Flow Developers can gain valuable insights by visualizing the most frequently used routes within a workflow, presented as a percentage. This helps in identifying bottlenecks and optimizing workflow paths.
    Average Time Tracking:

    Time Spent Between Workflow Steps: Users will have the capability to track and analyze the average time spent between each step of the workflow. This empowers developers…

    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)
  18. During development, I utilize a fantastic feature to update and auto-publish flows affected by changes. However, transitioning to the Production stage is less straightforward, requiring manual searching, opening, and sharing of modified flows.

    To enhance this process:

    Simplified Sharing: A 'Share' option accessible through right-clicking flows in the server view could eliminate the need for individual openings, complementing the existing 'Publish' link.

    Unified Sharing Checkbox: Similar to the 'Publish' checkbox, an equivalent 'Share' checkbox for updating flows could streamline post-approval sharing, especially for numerous flows influenced by fragment adjustments.

    Differential Version Listing: A feature listing flows with differing published and…

    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)
  19. When sharing a flow across different environments and switching between them, I notice the flow being marked with a green circle containing a white star, indicating the need for updates.

    Kindly introduce a feature that enables view filtering, allowing me to exclusively display flows requiring updates. This is particularly essential when dealing with a considerable number of shared flows, as manually clicking, scrolling, or searching by name becomes time-consuming. The ability to readily access 'All Subscribed Flows with Updates' would be greatly beneficial.

    I would appreciate the inclusion of a 'batch update' functionality for flows. Currently, updating each flow individually…

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

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