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

66 results found

  1. We would like to explore the possibility of using Odata connector with IFS10. Currently when trying to enable a projection the system gives an error saying "No projections saved"

    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 →

    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. When an end user is logged out of a mobile client and receives a push notification from an inbox, the notification currently appears as coming from an “Uncategorized” inbox.

    In this scenario, there is no real inbox. The inbox is system-generated and automatically named “Uncategorized.” This placeholder name can cause confusion, as users do not know which inbox the notification belongs to and may not understand what “Uncategorized” means.

    It would be better if the notification displayed a more informative message such as “Log in to see which inbox you received this notification from,” or if the system allowed administrators…

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

  3. As a user, I would like to use OTP/MFA (email, SMS, or authenticator app) when logging in directly to Novacura Flow Classic, so I’m not limited to only username + password.

    This is especially important for external users outside the tenant who cannot use the organization’s external identity provider.

    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 →

    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.

  4. We are currently implementing offline work task. The user case is that 2 - 4 Work task are executed a day, the data might change every 4 hrs due to IFS PSO.

    This means, that the user needs to manually refresh the data set every four hours manually. We can set a time interval for forcing them to do so.
    While this works it would helpful help streamline a trigger of a download at the end of the workflow.

    Meaning, that after the execution of a workflow that uses a data source flow would try to load the Data source…

    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

    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.

  5. Sometimes, if a user is already logged into the system, the screens do not refresh automatically. As a result, certain inboxes may not display real-time data.

    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 →

    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.

  6. I would be very valuable to be able to configure more columns in the execution history, or atleast provide an "ExternalID" or "ID" column that you could set from the transformation or from within the workflow.

    The use case is that we have thousands of executions a day, but FLINT offers no way of finding a particular execution. The sender and receiver system have IDs that would be very beneficial to be able to add to the execution metadata displayed in the FLINT history interface.

    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  ·  Integration  ·  Admin →
  7. Hi! I would really appreciate a 'remember my password' checkbox for the Flow Classic application. This is a huge problem in our organization, as many users avoid using the app due to the complicated passwords they have to fill in when it's time to sign in for a job, for example.

    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

    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. As a user, I would like to check or uncheck a checkbox in a table portlet with a single click, as it was in Portal 1. Currently, in Portal 2, I must double-click the row first and then click again to check/uncheck the checkbox, increasing the interaction from 1 to 3 clicks. This extra effort slows down my workflow and makes the process less efficient. Restoring the single-click functionality would improve usability and streamline the 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

    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.

  9. As a user, I would like the ability to pre-approve devices in Flow Studio without manually logging in to each device. By utilizing device identifiers, such as MAC addresses,

    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 →

    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. As a user, I would like to send SMS (Short Message Service) directly from Novacura Flow Classic.

    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 →

    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 suggest using a REST API with a service like Twilio to send SMS messages via Novacura Flow.

  11. Currently, users do not have the capability to export or import connector configurations in Flow, which limits the ease of replication and backup of configurations across different environments or instances. This restriction can lead to inefficiencies and increased risk of errors when configurations need to be manually replicated.

    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 →

    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. Customer would like to have new feature that enable a user to determine which web client is being used

    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

    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.

  13. Add functionality to be able to zoom in and out on documents/images in the Document Viewer portlet in Portal2.

    Due to varying size of images a zoom in/out functionality would be very helpful.

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

  14. In the IOS client, all input fields are in light grey. A customer has expressed that they don't like the light grey color since that gives the impression that the field is not possible to enter data. They would want to turn this off or change the color of the field.

    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

    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. Introduce a feature that enables users to import input parameters directly into the workflow's start task from a JSON file or similar format. This would improve the efficiency and flexibility of parameter management, eliminating the need for manual entry while maintaining the security restrictions on the workflow header, which remains locked from editing by design. The feature ensures a more user-friendly experience without compromising the security protocols in place.

    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 →

    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.

  16. In Portal 1 - it was possible to double click on table row or single click on sprocket to initiate the flow.

    In Portal 2 - you need to click directly on triangle (counterpart for sprocket in Portal 1) to initiate the flow, double click does not work. It causes problem on production line, because employee need to navigate and click directly on triangle what it sometimes difficult.

    There should be an option to click on table row as it was in Portal 1

    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

    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.

  17. In the current configuration of Portal 2, locking the side menu causes it to overlay the main content area, leading to obscured or covered content. This can impair user interaction and accessibility, particularly when navigating or viewing crucial interface elements.

    Proposed solution is to modify the behavior of the Portal 2 interface so that when the side menu is locked, the main content area automatically adjusts to the right. This adjustment should ensure that no content is obscured by the locked menu. Implementing responsive design principles will allow the content to fluidly reposition and resize, maintaining usability and visibility regardless…

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

    The configuration panel has been changed in Flow Connect Portal to improve the user experience.

    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.

  18. Should be possible to reduce gaps (to set distance between next fields) between next fields in user step in flow triggered from ie. portal 2 or web client

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

    The pop-up shows the old web client being executed from the portal. The UI is better in the new client so I would suggest changing to using that one.

    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. Customers using mobile clients on compact, hand-held devices tend to utilize List Multi-Selection Input for its displayed data compression and dynamic fields. What is not available, when comparing to the data grid, is the possibility to mark-to-select-all. It's rather cumbersome to manually select/de-select all the records. We've currently designed a work-around but would appreciate if that is an in-buil feature. Take a look at the attachment.

    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

    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. Currently, the device management page in Studio uses model numbers as the default for the Name field. This approach is inadequate for environments with multiple devices of the same model, as it creates confusion and inefficiency by not allowing easy identification of individual devices.

    Proposed solution is to implement the ability to customize device names in Studio. This feature would allow administrators or users to rename devices according to their specific naming conventions or operational needs, making it easier to identify and manage multiple devices of the same model. This customization should be easily accessible from the device management interface…

    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 →

    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.

    In Flow Connect, there is no longer the need for Device Approval using a standardized IDP with MFA.

← Previous 1 3 4
  • Don't see your idea?