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

36 results found

  1. The filtering process will remove all records that contain the specified value or pattern, leaving a refined dataset that only contains the relevant data.

    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  ·  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. Enhancement to Portal2's document viewer to increase its compatibility with these common file formats (doc, xls, txt). This will improve user experience by enabling in-browser viewing of a wider variety of documents.

    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 →
    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 addition of an impactful feature to the Scheduler Portlet, specifically introducing the "Timeline Work Day" view, as per our customer's needs. The primary objective of this view is to display selected working hours instead of the conventional 24-hour format, enhancing the scheduler's relevance and usability.

    To achieve this, we propose two essential components:

    Custom Views: Empower users with the ability to create custom views within the scheduler. The "Timeline Work Day" view will be highly customizable, allowing users to tailor it according to their unique requirements and preferences. This feature would enable them to focus on their specific working…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. In Portal 2, the current record selection listeners provide a powerful feature to update portlets when new records are selected. However, we have noticed that the listeners do not trigger when records are deselected, resulting in stale data being displayed in other portlets. To improve the user experience and maintain data accuracy, we propose enhancing the record selection listeners to include deselect events or introduce a new listener specifically for deselecting records. This enhancement would enable portlets to refresh in real-time when records are deselected, ensuring that users always have up-to-date information displayed across all relevant portlets.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. We would like to enhance user experience by introducing a new feature: 'Function Selection' in the Portal2 filter settings, allowing users to customize and tailor their preferences more effectively. We need to be able to select the function we want to use with-in the filters settings (see file attached). Specifically the "Contains" function. Although we should be able to use the filter functions as a whole.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. A user should be able to save data when pressing the "Enter" key in a Table Portlet.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Currently, modifying values in a table requires the use of Edit Operations. However, there is a need to allow temporary or inline editing of table records without employing Edit Operations. This would enable users to make temporary changes to selected records and then execute a custom workflow using a special button. The workflow's InputTable would include all records, reflecting any changes made.

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

    We're glad you're here

    Please sign in to leave feedback

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

    0 comments  ·  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. Scheduler is often being used to manage allocations, with multiple allocations often tied to a single operation. While these allocations are perceived as the same object, they aren't currently treated as such in the Scheduler.

    We propose a feature that enables linked highlighting of allocations tied to the same operation. When one instance of the operation is selected, all corresponding allocations should be highlighted. The actual selected instance could be distinguished with a unique color while other instances are highlighted with another color. However, when interacting with a single instance (e.g., dragging it forward in time), only that instance should…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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 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)
  11. In the current design of the Scheduler, there is no option to alternate the color of lines. This can make it difficult for users to distinguish between tasks, especially when dealing with resources that have many lines and a long planning horizon.

    We propose adding a feature to configure alternating colors for each line in the Scheduler. This "zebra striping" will enhance visual distinction between tasks, making it easier for users to navigate and manage their tasks and resources, especially over long planning horizons.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Currently, the Scheduler lacks the ability to create a custom timeline, making it difficult for users to plan orders starting in one week/month and ending in the next week/month. This lack of functionality can lead to a lot of clicking and scrolling and difficulty in visualizing the total order.

    We propose adding a feature that allows users to define a custom timeline in the Scheduler. For example, this could be a timeline starting from 'today + 1 week' or other similar custom periods.

    This will allow users to have a more efficient and streamlined planning process, minimizing the need for…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Currently, when changing between weeks in the scheduler, it adds a week on top of the current day, rather than moving to the start of the next week (Mon-Fri). This behavior contrasts with the functionality when stepping to the previous week, where it scrolls back to Monday.

    We propose modifying the week navigation in the scheduler to ensure that moving to the next week always takes the user to the start of that week (Monday). This adjustment will create consistent behavior when navigating between weeks and align more closely with user expectations.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. The default values of the date filter in the Gantt portlet are currently based on today's date. This setup requires manual adjustments when looking at historical data, which can be cumbersome and time-consuming for users.

    We propose adding the ability to configure the end of period default value based on the start of period value in the Gantt portlet. For example, if the start of the period is set to two months ago, the end of the period could automatically be set to two weeks after that. This dynamic configuration would enable users to more quickly and intuitively navigate through…

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. In the current scheduler, the work hours are differentiated with a white background color (class e-work-hours), while the rest of the cells are light grey. The work hours seem to be hard-coded to 08:00 - 20:00, and no configuration settings are found to change them. Though there are settings for "Work start" and "Work end," they only control the display of columns and not the differentiation of work hour cells.

    We suggest enhancing the scheduler by allowing the "Work start" and "Work end" settings to define which cells are given the class e-work-hours (and thus, the white background). This will…

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

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?