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. In the current implementation of a DataGrid, when a user adds a new row, the text from non-editable (display-only) columns still appears, giving an impression of inconsistency in the UI. This can be confusing for users.

    Proposed solution is for non-editable columns to be hidden or made visually distinct when adding a new row to a DataGrid. This way, only the relevant editable fields will be displayed, providing a more intuitive user experience.

    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. We would like to have a new function where the portal 2 pages navigate automatically within given time period

    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  ·  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)
  3. Users experience challenges with offline workflows in Flow-app due to network variability. Devices connect to various networks throughout the day, but only one network provides the required server connection for data sync. As a result, offline transactions get stuck in a "failed" state, necessitating manual retries once the device reconnects to the secure network.

    Proposed solutions are to implement a feature in the Flow-app to detect the current network. The app should only attempt to write back to the server when connected to a predefined, specific network. Alternatively provide users with an option to bulk retry all failed offline transactions…

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

    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)
  5. We frequently execute numerous queries on our M3 IBM DB2 iSeries database, and occasionally, I encounter issues where Flow Studio does not accept the query.

    We've been able to adjust queries in the past to make them compatible with Flow Studio, but this time I'm facing difficulties. The problem specifically arises on line 7 of the query.

    We make extensive use of "with" statements, so it's puzzling why I'm encountering an issue in this particular instance. It's possible that the problem is related to the brackets I'm using to dynamically insert parameters into the query, but despite the error, everything…

    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)
  6. 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)
  7. 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)
  8. Frequently, I design a workflow and realize the need to switch it from a User Flow to a Fragment, either due to oversight during creation or the newfound requirement for reusability. The current process of converting the workflow in the studio is rather cumbersome. Although I've managed to export the Flow, manually tweak the XML, and then re-import it to achieve a Fragment, it strikes me that this procedure could be streamlined. Perhaps a more user-friendly approach would involve incorporating a 'Convert To' option, accessible through a simple right-click within the server explorer, offering a range of flow type transformations

    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

    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)
  9. 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)
  10. 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

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

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

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

    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

    planned  ·  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)
  14. 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.

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

    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.

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

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

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

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

    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 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)
1 2 5 7 9 12 13
  • Don't see your idea?