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

235 results found

  1. In the current Web NG client, when users perform searches, the results do not indicate the menu under which each workflow is located. This lack of contextual information can lead to confusion, especially when multiple workflows have identical or similar names but reside in different menus.

    Proposed solution is to improve the search functionality within the Web NG client to include additional details in the results, specifically the menu location of each workflow. This information should be displayed clearly beneath the workflow name in the search results. Providing this contextual detail will help users quickly identify the correct workflow, reducing…

    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

    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 offline workflows support downloading data into the client and run workflows without an internet connection. However this data purely reside on memory when it comes to mobile devices.

    If the application has to be closed for any reason, whole of the offline data will be lost.

    This is essential for situations like off site asset count in remote locations. etc.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. It would be nice to be able to view data grid columns without first having to be in edit mode in studio. As it stands, when you select a datagrid element while not in edit mode, it only previews the column names in that boxed area, and depending on the length of the names, only shows a few of them. It would be super helpful if we could go a layer deep to view each column, it's data source, and perhaps just the entire edit screen in general without having to officially open it up for editing.

    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

    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. Even the assertion steps could replaced to bypass the timeout, the next steps of the flow which are file connectors and OData connectors could not be handled within the flow if an error occurred.

    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

    1 comment  ·  Integration  ·  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. Dear Novacura R&D,

    As much as powerful the grid element in the User Step is, it would be great to enhance it with dynamic features.
    Like the 'Condition to hide' that affects the elements in the User Step, it would be great to have something similar for the content of the grid. And thus, if a particular condition is met, say a column is empty, then it could be hidden.
    We quite often find ourselves in situation where we have multiple scenarios and data that differ from each other. Instead of creating multiple grid variants in one User Step, it…

    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)
  6. More descriptive error messages in the web client to pinpoint the exact issue in the workflow, instead of generic errors like "invalid step" or "string literal error."

    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)
  7. Currently, you CAN export a portal 2 page and then it imports with lists of values included (as for filter drop downs that we've tested). I'd propose that when exporting Portal pages that have LOVs, on import, it will bring any updated items on the LOVs as well.

    We've tested that if a LOV exists in an environment where you're importing the portal page to, it will use the current existing LOV with the same name, but it will not bring any updates to the query. This is an extra step for the portal admin to need to manually modify…

    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

    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)
  8. In the current Flow mobile client, when operating in offline mode, users face a restriction where items in the inbox are marked as "Finished" after being acted upon. This status change makes the items inaccessible for further review, although they remain visible in the inbox until the user reconnects to the internet. This behavior limits the ability of users to revisit completed items for verification or review purposes.

    Proposed solution is to implement a feature allowing users to toggle the visibility and accessibility of items marked as "Finished" in the inbox while in offline mode. This functionality would enable users…

    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)
  9. Enabling Technicians to release material not only from the task connected site, but also through other connected site warehouses.

    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

    2 comments  ·  Marketplace  ·  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. Requesting a feature enhancement in Portal to allow for the customization of pop-up controls during the review process. Currently, the mandatory provision of an exit button for publishing results in redundant close options (close button and 'x') at the bottom of the pop-up. It would greatly enhance user clarity and experience if administrators could define the visibility of the default close option, providing flexibility in tailoring the interface to specific workflow requirements.

    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

    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 issue arises when a column is modified in a complex SQL query and need to click the torch to have Flow recognize the changes in the output table. Unfortunately, the torch automatically reformats the SQL, which creates problems, particularly with UNION statements and other complex examples.

    Is it possible to add a button that simply updates the output table to reflect any new or changed columns without performing a complete reformat of the SQL?

    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

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

    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

    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)
  13. The current system lacks efficient mechanisms for managing flow history, particularly in environments with numerous flows and versions. This leads to performance issues due to the accumulation of extensive history data. Additionally, the need to update flow IDs on the portal after importing and exporting flows complicates maintenance and disrupts workflow continuity.

    Proposed solution is to implement a configurable option within the web configuration file to set a limit on the number of flow history entries retained, defaulting to the latest 10 entries. This setting would allow users to manage performance by controlling the volume of historical data stored.

    Furthermore,…

    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, when an error occurs in Studio, such as "Item is not linked to the latest version," clicking on the error message automatically opens the fragment. This behavior is not always helpful, especially when the needed action is to update the version rather than edit the fragment. The limitation is compounded by the fact that version updates cannot be performed while the workflow is open in edit mode.

    Proposed idea is to revise the error interaction process to better align with the user's likely intent. Instead of automatically opening the fragment for all types of errors, provide a more nuanced…

    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 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"…

    20 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)
  16. In some connectors for example FileSystem we need the ability to handle errors and sometimes ignore them.

    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

    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)
  17. When running the app to create a Handling Unit there is no information to the user of what Handling Unit ID’s that are created. There should be a field in the summary that list the ID’s (can be multiple) that are generated.

    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

    planned  ·  2 comments  ·  Marketplace  ·  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. It would be ideal to have a chat user-step element that could be configured in Flow. This would allow us to more easily use GPT in a dynamic way inside of the Novacura Flow Client.

    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)
  19. Please allow us to brand/color the studio based on the connection.

    I frequently work in different flow environments and it is really easy to switch to the wrong studio window.

    If I could either
    1)set the branding on the server level so all studio logins for that server had the same color/branding whatever
    2) or set the branding locally in studio

    ...that would be great

    My thoughts are
    1) Allow for the studio header/border to be a different color
    2) Make the SERVER I'm connected to more prominent, like in the same area as "Application/Environment/Monitoring"

    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  ·  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 feature to facilitate encode/decode Base64 with flow script function and be able to convert a flow variable to a binary file format.

    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  ·  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)
← Previous 1 3 4 5 11 12
  • Don't see your idea?