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

243 results found

  1. Now we can set Alternate row coloring only for single portlet. It should be possible to set it for all portlets globally.

    Now we can set it for single portlets in menu Edit / Style / Row.
    It should be added to global settings in Style / Branding / Theme

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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…

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. We would like to have bigger scroll bars for all portlets in portal 2. Users use big screens zoomed out and have a hard time clicking on the scroll bars since they are so thin. A suggestion is to make the size of the scroll bars a user setting.

    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 →
    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 the current design, when users scroll horizontally in data grids with many columns, the row selection checkbox moves with the scroll. This can make it difficult for users to select the correct line, especially when dealing with extensive data.

    We propose a feature to lock the row selection checkbox's position on the left side of the data grid. With this feature, even when a user scrolls horizontally through the grid, the checkbox remains in a fixed position, making it easier for users to handle selections.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The "Auto Focus " option currently fails to place the cursor in the first input field when it is the second element in a flow after a list box. This results in a non-intuitive user experience, requiring users to navigate through other elements before reaching the input field. We request an enhancement to ensure the cursor is directly placed in the first input field, or at least the list box, when "Auto Focus Input" is enabled, providing a smoother user experience.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Role-Based Push Notifications in Portal 2: Delivering Customized Alerts to Specific Users

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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…

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

    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)
  14. Customers want to be able to add production reporting and operational equipment time reporting to my crew sheet in Crew Time Reporting application.

    Production Reporting in IFS Cloud is done in Schedule of Work Production by WBS where the reporting on these activities is done in Work Recording screens in Cloud.

    Equipment should be tied to a Crew member and production hours should be reported by equipment to be add as a billable line item to the IFS Project.

    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

    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)
  15. Current login screen only shows "Flow 6" (not even Novacura is mentioned).

    We are gearing up adding external partners to the portal. It both creates suspicion and looks amateurish without our company name, and preferable logo, in the login screen. Enabling us to brand the layout with name, logo and maybe even colour would have made a big impact on the first impression.

    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)
  16. The idea is to allow form creation with built in logic, similar to a the tool used when building a form in SurveyMonkey. You could have Interaction Items for multiple choice, true/false, 1-10 scales, short answer, etc. This would allow customers to build surveys, or in the case of Flow academy design the certification exam. An example of the backend logic would be if you had a question "Did you the instructor covered the material in a clear and concise manner?", and the respondent said "No", then a short answer box would appear next asking them to explain what could…

    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

    3 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)
  17. 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)
  18. When incorporating Chinese characters into a document flow in Novacura cloud, some corruption issues arise, often due to missing fonts.

    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

    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)
  19. The IFS .NET Access Provider is expected to support a timeout parameter, allowing users to configure how long a task should wait before timing out. However, this functionality is not currently implemented in Novacura's IFS10 connector. As a result, all long-running tasks time out after one minute, with no available option to extend this limit.

    This limitation hampers the execution of tasks that take more than one minute to complete, making it impossible to include them in flows. This leads to inflexibility in designing complex workflows and might impede the completion of important business processes.

    We propose implementing the timeout…

    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  ·  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)
  20. Flow currently requires users to download files in order to view them, a process that some customers find inconvenient. There is a clear preference for viewing image files within the flow itself without the need for downloading.

    Therefore, we propose an enhancement to enable viewing of common image file types (e.g., JPEG, PNG) directly within the Flow interface. This feature will enhance the user experience, allowing quick and convenient access to image content and reducing the steps required for users to interact with image files.

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