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

240 results found

  1. Currently, to have editable columns in a table, 'Edit Operations' must be enabled. This approach allows only the usage of pre-set buttons named "Update/Delete/Create". However, in some contexts, these pre-set names are not suitable or meaningful to the end-users.

    We suggest allowing customization of the button names in 'Edit Operations'. This feature will allow users to rename the "Update/Delete/Create" buttons to terms that better fit their specific use cases.

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

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

    We're glad you're here

    Please sign in to leave feedback

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

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

    We're glad you're here

    Please sign in to leave feedback

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

    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 →
    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 setup, when clicking on 'Help' -> 'About Flow Studio', a pop-up box appears with small print text on an image. This makes it hard to provide accurate and consistent Flow Studio information when submitting a support ticket.

    We propose adding a new feature that allows users to "Copy Flow Studio Information to Clipboard". With this feature, users will be able to copy their Flow Studio information in a single click, ensuring that accurate and consistent information can be quickly and easily included when submitting support tickets.

    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  ·  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)
  6. 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…

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

    We're glad you're here

    Please sign in to leave feedback

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

    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 →
    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 in Flow Studio, users are unable to bypass "interactive" elements, such as checkboxes, with a barcode scanner or the "Enter" button. This limitation disrupts the scanning process, adding unnecessary steps for the user.

    In the meantime, users have to create a workaround by placing the checkbox in a user step before or after the barcode scanning step. However, this is not an optimal solution as it requires additional user steps and makes the workflow less efficient.

    Proposed Solution: We request the development of a feature that allows the barcode scanner to bypass interactive elements in the flow. This will…

    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)
  9. Customers using our mobile client have reported inconsistent performance when scanning barcodes using the List multi-selection input component. Specifically, it appears that the barcode recognition feature is not always operational. Additionally, the List multi-selection input component in Flow Studio lacks barcode configuration options. There's no way to change the default "Match By: Rows" setting to "Match By: Specific Columns". This restriction limits the flexibility and usability of this component for developers.

    Proposed Solution: We propose to add the barcode configuration to the List multi-selection input component in Flow Studio. This should include the option to change the "Match By" settings…

    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)
  10. Currently Portal 2 datepicker has separate date and time pickers. This feature request would allow users to set both date and time by pressing the "Today" button.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. The feature request aims to bring back the "Multiline" behavior for text input boxes in the NG web client, similar to how it worked in the old web client. This enhancement will allow users to expand text input boxes to accommodate multiple lines of text, providing a more seamless and user-friendly experience when dealing with longer inputs or when composing messages that require a larger writing space. By reintroducing the "Multiline" behavior, users can effortlessly resize text input boxes, leading to improved productivity and enhanced user satisfaction.

    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)
  12. In the new web client, the current flow name search allows filtering by typing a partial name. However, we would greatly appreciate additional search options such as "wildcards," "starts with," "ends with," and "contains." These enhancements would enable more refined searches, specifically allowing users to locate flows that begin with a certain pattern, end with a specific string, or contain a particular sequence. Implementing these features would significantly improve the flow discovery process, increase user productivity, and enhance the overall user experience in the web client.

    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)
  13. Improve the import capability for complex customer start inputs, which include records, tables, and values. Currently, the system's ability to save such inputs has been compromised, even for minor changes like renaming a simple value. The proposed enhancement seeks to reinstate the previous functionality and ensure seamless saving of these inputs, thereby optimizing the user experience and productivity.

    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  ·  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. Currently, in the DataGrid component, setting a number format is fixed and cannot be parameterized. This limitation hinders the flexibility of developers to customize the number formatting based on different data and user requirements. As a user of the DataGrid component, I request the implementation of a customizable number format parameter to enhance the control and usability of this feature.

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. It would be fantastic if you could extend the application's compatibility to include Bluetooth-connected Zebra scanners that are paired with other Android devices. This enhancement would not only streamline my workflow but also open up new possibilities for other users who rely on similar scanning setups.

    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)
  17. Consider this scenario: A Novacura user, utilizing AD authentication, experiences an AD account lockout. As expected, Novacura restricts their access to prevent unauthorized logins. Despite attempting multiple login attempts, the user remains unable to access Novacura. Eventually, the AD account is unlocked by our help desk personnel. At this point, we anticipate that the user should be able to log in to Novacura again. However, the repeated unsuccessful login attempts have triggered the Novacura lockout mechanism, preventing their access. Since our help desk staff lacks admin privileges in Novacura, they are unable to unlock the Novacura account.

    To enhance 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

    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. The request is to include a feature that would allow all static texts, regardless of whether they are set by the end user or not, to be translated into Chinese. This would mean that both variable texts and static texts (those set through the studio and those not set by the end user) should be translated when the app's language setting is set to Chinese.
    By including this feature, the app would provide a more comprehensive and consistent translation experience for the users, ensuring that all the texts, whether they are user-defined or not, are appropriately translated into the desired…

    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  ·  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)
  19. There's a missing function to support an advanced shiping note receipts which could be integrated to Receive Purchase Order app.
    User should be able to fetch the lines either using Detail (scanning EDI-sent SSCC numbers) or Bulk Search (choosing a pending Delivery Note from the drop-down menu) branch.
    The feature will be of a great help to all customers which have EDI integration established with their suppliers as well as will support the receipts of Internal Sales Orders.

    Please have a look at the attachment of UI layout proposal.

    best regards,
    Adam Wojtyniak

    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  ·  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)
  20. As a Flow Developer, I should be able to disable focus on any element in a User Step.

    Currently, focus is set on User Step Elements sequentially. For example, if you have a Text Input and a Datagrid, once the text input is entered through scanning focus will be set on the Datagrid. In this same example, if focus was disabled on the Datagrid, the user could scan data into the text input and move forward with a default button control. This would allow a user enter text into a text input, and show the growing list in a data…

    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  ·  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)
1 2 8 9 10 12 Next →
  • Don't see your idea?