Skip to content
← How can we improve Novacura Flow?

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

(thinking…)

How can we improve Novacura Flow?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

243 results found

  1. Introducing a Feature to Locate Published but Unshared Flows

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

  2. Enhanced Functionality for Identifying Flows Requiring Update

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

  3. Enhance Workflow Efficiency with Checklist Grouping Feature

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

  4. Evergreen IFS Rest Odata calls

    In the IFS Odata Connector we would benefit from first of all identification of all Odata projections used in a a flow and secondly to scan the IFS APIBreakingChanges release files to find out and mark Flow objects if there has been a change in any projection.

    There are two different APIBreakingChanges files:

    • Between Service Updates within a functional Release
    • Between Functional releases.

    See attached examples.

    8 votes
    2 comments  ·  Connectors  ·  Admin →
    How important is this to you?

  5. Enhanced Log Analysis Tool for REST M3 API Connector

    We urgently request an upgrade to the existing log analysis tool for the REST M3 API connector. Currently, the tool lacks the essential capability to efficiently search for specific transactions or data within the logs. With each call and response generating individual log files, the volume of transactions quickly becomes overwhelming, rendering effective analysis nearly impossible. In contrast, the previous socket-based M3 API connector generated a consolidated API text file that enabled easy data search and facilitated comprehensive analysis, including input and response times. The current limitation significantly hinders error diagnosis, making the troubleshooting process arduous and time-intensive. We propose…

    2 votes
    0 comments  ·  Connectors  ·  Admin →
    How important is this to you?

  6. Enhanced Record Selection Consistency for Multi-Select Data Grids

    Improve multi-select grid usability on the latest mobile client by enabling "Click Anywhere To Select" functionality, similar to single select grids. Also, align the de-selection behavior with single-select grids, allowing users to "Click again to de-select record," creating a consistent and intuitive user experience across different grid types. This enhancement aims to optimize record selection and de-selection, particularly on small screens, for enhanced usability and efficiency.

    2 votes
    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Admin →
    How important is this to you?

  7. Generative AI - ChatGPT Connector

    It would be helpful to have a ChatGPT Connector and templated process to use this connector. For example, using ChatGPT to create FlowScript based on natural language, personal recommendations based on Portal 2, document summarization in Portal 2. This connector should be set up to allow developers to see an example of how to use it, but be able to embed this connector into their own apps.

    4 votes
    planned  ·  0 comments  ·  Connectors  ·  Admin →
    How important is this to you?

  8. Enhanced Logging for Import Errors of OData Connector

    Users encounter an issue when changing connectors for a specific flow. Currently, when an operation result indicates a failure, it is challenging to pinpoint which step within the flow has encountered the issue. As a result, users are compelled to manually review each step to identify the failed ones, causing unnecessary delays and frustration.

    8 votes
    1 comment  ·  Connectors  ·  Admin →
    How important is this to you?
    under review  ·  AdminIrshad Hassan (Admin, Novacura) responded

    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.

  9. Improving Datagrid Row Addition

    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…

    1 vote
    2 comments  ·  Clients (Webclient, Android, iOS)  ·  Admin →
    How important is this to you?

  10. Improved Machine Step Script Error Handling for Oracle Code

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

  11. Offline Compatibility and Expanded Image Source Options for Image Selection Input Component

    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.

    1 vote
    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Admin →
    How important is this to you?

  12. Enable "Workflow Fragment" as Seed Item with Data Arrow in Flow Studio

    We kindly request the implementation of a new feature within Flow Studio, allowing the integration of "Workflow Fragment" as a Seed Item while utilizing a data arrow to the start step. Currently, any attempt to include a Workflow Fragment as a Seed Item leads to undesired outcomes. Specifically, when users press the "Run" button, the flow crashes, or upon selecting the "Publish" button, an error message surfaces: "Missing mapping for NovaCura.Flow.Designer.CanvasItems (..). Possible usage of unconverted elements from previous Flow versions."

    5 votes
    0 comments  ·  Studio  ·  Admin →
    How important is this to you?

  13. Enhanced DataGrid Selection Control with Default Row Selection

    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.

    8 votes
    0 comments  ·  Studio  ·  Admin →
    How important is this to you?

  14. Streamlined Fragment Version Update Button in Workflow View

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

  15. Enhance SQL Machine Steps for Direct Flow Table Usage and Improved Performance

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

  16. Improvements in the Pick Menu for Fragments in Studio

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

  17. Streamlined Row Deletion Process for NG Webclient Datagrid

    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
    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Admin →
    How important is this to you?

  18. Enhance 'checkpoint' workflow element

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

  19. Show Password Icon

    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.

    4 votes
    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Admin →
    How important is this to you?

  20. Enhanced Bluetooth Input Functionality After Manual Overwrite on Mobile Clients

    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
    under review  ·  0 comments  ·  Clients (Webclient, Android, iOS)  ·  Admin →
    How important is this to you?
1 2 … 6 8 10 11 12 13
  • Don't see your idea?