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

154 results found

  1. The ability to edit data in a true table grid format, rather than having a separate screen for each record, refers to a user interface design where data is presented in a tabular structure that resembles a Excel format

    23 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

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

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

    This has been changed in Flow Connect.


    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  3. We have utilized some generally good programming concepts and have about 30 flows that all rely on the same fragment. When we make a change to that fragment, we can now easily publish all these flows in our test environment.

    However, what we would like to do is share them all in one step, so that we can subscribe to the update in our production environment. Unfortunately, this proves to be a painstakingly long process, and with the passage of time, it will only exacerbate further.

    17 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 →

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap for Flow Classic. We appreciate your continued feedback and look forward to hearing about future ideas.

    Please see the upcoming changes that have been made to deploying applications in Flow Connect. The changes on Flow Connect will support this request.

  4. Allow the user to have a forgot password option at the login screen. This option would allow the user to reset their password for access to the client similarly to how other clients manage forgotten passwords.

    16 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

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

    Please be sure to look at the changes coming in Flow Connect. Passwords will be handled through a standard identity provider, including password resets.

  5. it would be highly advantageous to introduce the ability to execute this script as an option within a REST Service call. Currently, the REST Service connector parameters only offer limited choices such as "Variable," "Constant," and "Not Set." By incorporating this script execution as an alternative, it would empower users to execute more intricate operations within the flow, thereby providing greater flexibility and customization to the process.

    11 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 →
    declined  ·  Irshad Hassan responded

    We regret to inform you that this feature request has been declined in Flow Classic track. After careful consideration, our product team has concluded that it does not align with the established product roadmap for Flow Classic, nor does it offer sufficient value to justify its implementation. We appreciate the feedback you have provided and remain open to hearing about future ideas.

    That being said, we encourage you to explore the recent enhancements made to the REST connector in Flow Connect. The REST connector within Flow Connect already accommodates this particular request. Additionally, we are actively seeking beta customers for Flow Connect. If you are interested, please reach out to your local account manager for further details.

  6. We would like to get more information on the error when an error is thrown by the remote system when communicating through the web service connector. Sometimes there is not much information available to the user or developer for that part. It would be great if this error in full could be written to the error log file which would make debugging this a lot easier. And of course also present the correct error message in full to the user.

    10 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 →

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  7. We would like to have new feature add to document viewer in order to view multiple pdf(s) in portal. Currently, when one clicks the table row (with a listener attached), they need to view particular line related Documents.

    9 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  ·  Portal 2  ·  Admin →

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

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

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.


    That said, in Flow Connect, we have an Extension on Flow Connect that does just this. Please see our help documentation on this extension for IFS Cloud.

    https://docs.novacura.com/marketplace-documentation/flow-platform-extensions/explore-extensions/ifs-api-change-impact-analyzer/documentation

  9. Requesting the addition of customizable spacing options between KPI cards in Portal 2. Currently, a gray KPI card is being utilized as a workaround for creating space between blue and green KPI cards. However, there is an inability to disable the border of this empty card. We propose the implementation of features that allow users to control spacing between KPI cards and provide the option to toggle borders on or off for improved layout flexibility.

    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  ·  Portal 2  ·  Admin →

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  10. Sometimes I have VERY long arrows. When i highlight the arrow I can see it nicely, but as soon as I try to move it is not highlighted. I want to be able to see my separate arrows ESPECIALLY WHEN THEY overlap.

    A few options to consider.

    1. Allow me to color arrows different colors for visibility.

    2. Allow me to select an arrow and leave it “selected” so it stands out.

    3. Allow me to have a shorter arrow that goes to a “GO TO” element which is just a pointer to another element in the flow.

    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

    2 comments  ·  Studio  ·  Admin →

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  11. The current Now() function in Flow retrieves the time based on the device's local time. This can lead to inconsistencies for users or workflows operating across different time zones. To improve this, there's a need for advanced time manipulation functions and settings.

    Proposed solution is to introduce new functions like Now().utc, allowing users to retrieve time based on specific time zones like UTC. Additionally, integrating a timezone setting for each user in Studio, similar to the existing Language and Locale settings, can ensure consistency and accuracy in workflows, catering to diverse customer needs. This enhancement will grant users greater flexibility…

    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 →

    Timezone functions have been introduced in Flow Connect. No change will be done in Flow Classic.


    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  12. Currently, in the IFS OData connector, date fields can be modified but not cleared (set to null), although it's possible to clear these fields directly in IFS. Converting to a custom operation allows null inputs but is not a desired solution due to its complexity.

    We propose to add functionality in the IFS OData connector to allow null inputs for date fields. This would align with the behavior seen directly in IFS and would enhance the versatility of data manipulation in the OData connector.

    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  ·  Connectors  ·  Admin →
    declined  ·  Irshad Hassan responded

    We regret to inform you that this feature request has been declined in Flow Classic track. After careful consideration, our product team has concluded that it does not align with the established product roadmap for Flow Classic, nor does it offer sufficient value to justify its implementation. We appreciate the feedback you have provided and remain open to hearing about future ideas.

    That being said, we encourage you to explore the recent enhancements made to the REST connector in Flow Connect. The REST connector within Flow Connect already accommodates this particular request. Additionally, we are actively seeking beta customers for Flow Connect. If you are interested, please reach out to your local account manager for further details.

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

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

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

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  15. Currently, when utilizing the Download functionality within the document viewer, the downloaded PDF file is named "undefined.pdf." This naming convention lacks user-friendliness and can lead to confusion among our users.

    We kindly request the implementation of a customizable filename option for the downloaded PDFs. This feature would allow us to set a more descriptive and meaningful filename, relevant to the content or context of the document being viewed. For example, users could have the ability to name the file based on the document title, date, or any other relevant data.

    The ability to customize the filename would significantly improve the…

    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  ·  Portal 2  ·  Admin →
  16. we would like to explore better alternatives as some users find the List Multi-Selection Input confusing on mobile and tablet devices. On computers, users can easily select and close the menu using the mouse. However, on mobile or tablet, the process involves opening the menu as a "new page," making selections, and confirming choices using the back button as the back button's current usage is unfamiliar and confusing to users. Perhaps adding a dedicated button for confirmation or a similar approach would improve the user experience. For a clearer understanding of the problem, refer to the provided pictures (pc 1-3…

    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

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  17. Microsoft is discontinuing basic HTTP authentication for Exchange on October 1st. While SMTP basic authentication, which appears to be used in our email connectors, will continue to function based on Microsoft's documentation:

    Deprecation of Basic Authentication in Exchange Online

    Considering this deprecation, Microsoft advises us to explore alternative options. Anticipating that similar queries may arise from various customers, we kindly request the development of a new email connector (or an update to the existing one) that supports alternative authentication protocols. This proactive approach will help address potential customer demands as they begin to inquire about this change more frequently.

    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  ·  Connectors  ·  Admin →
  18. We request the implementation of a new feature that enables users to apply color-coding to columns in data grid portlets based on a comparison against neighboring column values. This enhancement will provide users with a visual representation of data variances, facilitating quick and intuitive analysis within the platform.

    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

    1 comment  ·  Portal 2  ·  Admin →

    This functionality is available in Connect portal.


    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  19. We propose the implementation of advanced conditional formatting options for text within the Data Tree Portlet in Portal 2. Specifically, the ability to customize text appearance (color, style, etc.) based on conditions, such as distinguishing between unassigned and assigned work. This enhancement would significantly improve visual clarity and streamline data interpretation within the Portlet.

    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

    0 comments  ·  Portal 2  ·  Admin →

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

  20. When you create a sequence arrow then right click, there is no need to have the word "CREATE" before each element.

    Additionally, the list could be alphabetized to easier find the type of element you want to add.

    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

    0 comments  ·  Studio  ·  Admin →

    We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.

← Previous 1 3 4 5 6 7 8
  • Don't see your idea?