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

32 results found

  1. Currently, when working with dates in Portal 2, the default format is often in a numerical representation (e.g., "03/28/2023" for March 28, 2023). While this format is functional, I would like to propose the implementation of an alternative date format to improve readability and user experience. Specifically, I am suggesting the adoption of the "DD-MMM-YY" format, where dates are presented in a more user-friendly manner, like "28-Mar-23" for the same example date.

    However, I understand the importance of sorting data chronologically, and simply changing the date format could lead to sorting issues, considering the alphanumeric nature of the proposed format.…

    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 →

    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. Hi,

    When we use CRUD option in a portlet in Portal2 it brings you ADD,UPDATe and DELETeE button on the basis of choice but can't control if not required.

    I have observerd belwo option is required to make it more flexible.

    If someone wants to make a work repository in portlet where CRUS is also required along with cutom button, there is no option to disable CRUD options on the basis of my choice of request type.

    eg . If my DB query gives a request type and I want to disable CRUD option on the basis of this it's…

    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.

  3. Hi,

    Presently there are options to run a machine worflow and redirect to open a weblink.

    Similar way it would be a good option for poratl2 in below way.

    I have found many occassions where we need to call a machine workflow after porviding user id and password in poratl2 login.

    This will help to validate the login for various key purposes.

    Regards,
    Bhaskar

    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.

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

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

  6. Customize custom and workflow buttons.
    - Color: Background and text
    - Position: Drag and drop
    - Size: height and width

    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 →

    Alignment and size, and limited colour options, are available in the Flow Connect portal.


    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.

  7. In the current version of Portal 2, users are limited to automatic width settings for table columns, lacking the flexibility that was available in Portal 1 where custom width values could be set during the configuration step. This limitation affects the usability and visual layout of tables, especially when dealing with varying content sizes that require more precise column adjustments.

    Proposed solution is to reintroduce the capability to set custom widths for table columns in Portal 2, similar to the functionality previously available in Portal 1. This feature should allow users to specify exact width values for each column during…

    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 →
  8. The new ability for users to freeze columns in data grids is very helpful. As a UX designer, it would be very helpful to save the current freeze column settings of a table portlet as the default user settings for the portlet, in the same way we are currently able to save column order and column widths by clicking the "copy from portlet" button in the Data Source Columns section of the portal editor. This would save us the trouble of having to teach every user how to use the freeze column feature and have them set that setting on…

    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 →

    This status indicates that the feature request has been rejected. The product team has determined that the feature is not aligned with the product roadmap or does not bring enough value to the platform to justify its implementation. The team should provide feedback on why the request was declined.

  9. I'd like to request return of Portal1 functionality: possibility to define column width (see attached screenshot). Lack of it makes designing challenging and less predictable.

    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 →
  10. Currently, Portal 2's assets only include support for English, Swedish, and Norwegian languages. This limitation impacts the usability of the Syncfusion components within the system for Portuguese and Spanish speaking users.

    We propose the inclusion of Portuguese and Spanish languages into Portal 2's assets. By expanding the supported languages, we can enhance the user experience for a broader audience and meet the needs of more diverse customer bases.

    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.

  11. Allows administrators to change the font globally in Portal 2 for its visual design.

    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.

  12. If authentication to IFS Cloud is done through external IDP like Azure AD, Novacura Flow should also be able to utilize the same external IDP to authenticate into Novacura Flow and then do a token exchange with IDP when running a User Flow that is connecting to IFS Cloud.

    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.

2 Next →
  • Don't see your idea?