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

88 results found

  1. 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)
  2. 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)
  3. 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)
  4. 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)
  5. In instances where a TEST environment is disabled while PROD remains subscribed to TEST, users encounter a barrage of subscription notifications, disrupting workflow in PROD Studio. To mitigate this, we propose implementing a feature that provides users with the option to suppress subscription notifications temporarily. This could include a warning prompt with the choice to suppress notifications for the current session or for a customizable duration, such as 24 hours, ensuring uninterrupted productivity during critical work periods.

    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)
  6. 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)
  7. Requesting an upgrade to the timestamp resolution in logpoint data beyond seconds to milliseconds. Currently, the timestamp value retrieved from logpoints is limited to seconds, hindering detailed analysis and synchronization with higher resolution systems. Expanding the resolution to milliseconds would align with modern data processing requirements and enable more precise temporal analysis within the system.

    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)
  8. I would like the possibility to unlock locked user accounts in Flow environment via API.

    As of now, our Servicedesk needs to have Studio installed and reserve one admin licence just to be able to support our organisation.

    Thanks!

    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. 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)
  10. When changing a fragment and updating dependencies it can be VERY confusing to follow the changes in Flows that have been changed.
    In complex flows using a lot of fragments, some flow specific and some used in a lot of flows, when i do changes and want to update PROD i can frequently see that between my changes and the last shared version to PROD other changes have been made, but i cannot see a comment other than "Auto updated version dependencies". If there is a comment in the changed fragment, please use that comment in all dependencies as well,…

    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)
  11. When you have a considerable amount of connectors it is not that easy to locate the connector you are looking for. If connectors can be grouped based on the type and then sorted alphabetically within the group will add immense value to the flow developers.

    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)
  12. we would like to get rid of unnecessary and misleading warning messages when updating flows up the dependency chain

    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)
  13. 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)
  14. 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)
  15. we would like to have schedule cleaning jobs that clean treasure files and what is now saved on the server.which would maybe feel more safer and reasonable if we’d be able to write this from the Studio

    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)
  16. Support for multiple languages in Flow can be a involved process and with many large workflows in a solution it can be challenging to provide a consistent translation (and terminology!) in your apps. In the translation industry, a common way to work is to have a side-by-side or spreadsheet view of all text with the original language on one side and the translations on the other. I would love it if the Languages tab in Environment could collect all text from one or multiple apps and then put that text in a table with editable fields where you can enter…

    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. When I have a datagrid and I change the column type on a column, please keep the attributes that are the same.

    for example, I had a number column with Title = QTY

    I had to change it to text, but when I did I lost the Title and all the translations.

    If I had previously set a value on a column for Title or Color or any attribute that is the same for the new column type, please keep the previous value.

    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. Similar to how many other node based software allow you to hold a hotkey and draw through arrows with your cursor to "cut" the arrows, this could be very useful in Flow.

    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. This is related to ideas https://ideas.novacura.com/forums/953926-novacura-flow-classic/suggestions/47158924-change-sql-validations-in-studio and https://ideas.novacura.com/forums/953926-novacura-flow-classic/suggestions/47473418-update-the-version-of-the-sqlparser. Sometimes Flow Studio will flag steps with a yellow "non-critical" error because Flow can't parse the code correctly. Most often I see this in SQL Server machine steps, but it can happen in other kinds of connectors too. While it would of course be lovely if the parser could be better, I think it will be hard to make it 100% correct. That's why I would like a RMB option to Ignore a yellow error on a machine step, sort of like when I want a word processor to stop flagging…

    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  ·  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. When stepping through a workflow with breakpoints, the step that is about to be activated is highlighted. This could be made clearer by instead highlighting the arrow leading to the next step, indicating exactly what is about to happen. This would also show which path has lead to a step with multiple inputs.

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