Skip to content

Novacura Flow Connect

Welcome to the ideas forum for Novacura Flow Connect. Please share your ideas for how we can make Novacura Flow Connect better. We are listening and we use this feedback to prioritize our roadmap!

Novacura Flow Connect

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

182 results found

  1. When selecting a row or row(s) in a portlet table and then starting a workflow, the row selected is no longer showing as (gray) selected, making it hard to find what row was just worked with and pulled into the workflow. This may not always pertain to selected rows because some are actually deleted or removed from a portlet table.

    However, a good addition would be to allow for tables in Portal 2 to deselect/not deselect the row and to allow the table to automatically update/not update the table after completing or closing a workflow. These are possibly some things…

    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  ·  Portal  ·  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. In current version of FlosScript {} symbol is used for declaring arrays(Pic A), inside IF and FOR loops(Pic B) and to showcase when Flowscript will be used(Pic C).

    I think, using same symbol for everything makes it's purpose unclear and can cause unnecessary confusion. Was change from [] to {} for array declaration cause by some real need?

    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  ·  Designer  ·  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. Is there any way that when adding records for an employee, the name stays highlighted. After each record I enter, I have to re-click on the name to enter more or even see anything pertaining to the employee.

    the user wants the name to be able to remain highlighted while they are doing processes for named user until the processes are completed instead of having to click on the user name each time to create additional processes for them.

    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

    under review  ·  0 comments  ·  Portal  ·  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. I want to be able to automatically revert an old version into to the current working version, similar to Flow 6.
    Currently you have to open both the working version and the old version in Designer and manually copy between them.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.

  5. Immediately after committing a version in Designer, a new working version is created and I can not see the information about the last commit.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.

  6. I want to be able to duplicate applications. If an application using components is duplicated, it should keep the existing references.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.

  7. When a filter field is setup with the "List Of Values" for the "Edit as" type, it would be very helpful to be able to select the "Contains" operator. Currently the "Equals" operator is the only available selection for list of values fields.

    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  ·  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. This comes from Billerud: As a user
    I want to be able to click one button to navigate to the current date
    so that change dates to look at information but still with one click come back to the now

    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  ·  Portal  ·  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. We would like to use the same flow for multiple buttons in Portal 2. We use the input table to drive what the buttons do. Therefore, we would like to have that functionality in Portal 2 to connect one workflow to multiple buttons. Today, I need to duplicate the workflow to connect one button to one workflow. This adds unnecessary maintenance.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    The feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.

  10. Currently, users must manually select dates in both the filter portlet and the Gantt date picker when they wish to restrict the data source to specific dates. This process is tedious and requires the portlet to load twice.

    We propose a feature that allows synchronization between date pickers in the filter portlet and the Gantt. There should be a setting in the listening portlet that enables users to link its date pickers to one or two date pickers in the filter portlet. When the user filters on specific dates, the linked date pickers should automatically update, reducing manual steps and…

    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

    under review  ·  0 comments  ·  Portal  ·  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. Currently, when users render a result in the scheduler, then navigate to a different page, and later return to the scheduler page, the previously rendered result is not retained. This behavior contrasts with the functionality found in the filter portlets and the Gantt portlet, where results persist through page navigation.

    We propose that the scheduler should retain the rendered results even after navigating to a different page and then returning. This persistent rendering will provide a more consistent user experience and align the scheduler's functionality with other parts of the system.

    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)

    Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.

  12. Currently, the visual emphasis when an object is selected in the Scheduler is quite subtle. This could potentially cause users to struggle in identifying their selected object, especially in a dense schedule.

    We suggest enhancing the object highlighting functionality in the Scheduler. This could involve introducing a more pronounced visual cue, like a more prominent shadow or highlight. It would be beneficial to make the intensity of this visual cue customizable. Additionally, users should be allowed to choose the color of the highlight, providing another layer of customization and personalization.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.

  13. Possibility to modify an already added component step in a work flow. Currently after we add a component as a step in a workflow, there is no possibility for us to modify that step. We have to create a new step and map the component from scratch. In flow classic, it was possible for us to change the existing step. This additional work is hectic. please allow developer to change the Component step within a flow when by modifying the current step. Also make component workflows available for every application instead of the application it is developed in.

    0 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  ·  Designer  ·  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. Could you add to DateTime module possibility to extract week number from a date in script? Like in std .net: System.Globalization.ISOWeek.GetWeekOfYear(DateTime.Now).

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Flow Classic had an environment variable type of "Table". Possible we could add that to Connect? I think this would allow a cleaner setup of variables and reduce the number of variables needed.

    Ex: If I want to send emails, per flow, I will need an env var for each flow.

    InventoryAdjustmentEmail - <value>
    MaterialRequisition
    Email - <value>
    TransportTask_Email - <value>

    If we had a table type, we could have a table with "Flow" and "Email" columns.

    One variable, multiple rows.

    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  ·  Hub  ·  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. Having a way to stop users or groups of users from being in the web client could be nice. The problem we are having is when users are completing registration they are getting driven to apps, but right now we are onboarding a lot of "portal only" users. So they get confused. We are sending a welcome email to link them to the board, but sometimes people don't read the email. When everything is said and done we have people who are web client only, portal only, and some who need both.

    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  ·  Hub  ·  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. The Image Selection user step option has the ability to show base64 encoded images. Can you apply the same logic for the Image Viewer? This request is for the NG Webclient and Connect web.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. https://cxl.com/blog/form-validation/

    See the inline section --> For Flow text input field, being able to configure a condition (or multiple) connected to a relevant error text

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Some customers don't want the option to use barcode scanning (camera) on some input fields and want it on others (to prevent data errors)
    We should have an option to enable / disable this.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Since there is no function in the portal today to determine whether user steps are present in components, all components start silently. And at runtime, if the component has a user step, an error saying: "Invalid usage of user step within component" is displayed.

    Such a function would allow components with and without user steps, increasing the usability

    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  ·  Admin →
    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?