293 results found

1. Persistent Rendering of Results in Scheduler

   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.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   under review  ·  AdminMalin Johansson (Admin, Novacura) responded

   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.

2. Linked Highlighting of Allocations in Scheduler

   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 be affected.

   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… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Alternate Line Coloring in Scheduler

   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.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Improved Week Navigation in Scheduler

   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.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Dynamic Date Filter Configuration in Gantt Portlet

   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 different date ranges, especially when analyzing historical data.

   This feature could include settings that allow users to specify the relative offset between the start and end dates, providing further flexibility in defining date ranges.

   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… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Portal  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Improve 'Menu Selection Input' Workflow element to limit screen touches

   When there is a menu selection in a user step, we need to click on it to enter text. Previously, we could simply type to make our selection.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Customizable Number Format Parameter in DataGrid

   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.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Designer  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Automatic Decompression for GZIP and DEFLATE Content-Encoding in REST Connector

   Currently, when using the REST connector, if a stream is gzip or deflate compressed, the data received is successful with a StatusCode of 200, but the body content is garbled due to the Content-Encoding being gzip'd at the source. This requires additional manual effort in transforming the data to be usable.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Connectors  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Request for Enhanced Compatibility with Bluetooth-connected Zebra Scanners

   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.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Silent authentication for initial REST connector token acquisition

    Why?
    When a user starts the Novacura client without a previous Novacura session, they authenticate with Entra ID before opening an application.

    When the application is started for the first time and a REST Connector needs to acquire a token, the token request is currently performed as an interactive sign-in. This is visible as an interactive authentication request in the Entra ID sign-in logs.

    At this point, the user already has a valid Entra ID session. Requiring another interactive authentication request is therefore unnecessary and prevents the initial REST call from providing a seamless single sign-on experience.

    Refresh token handling for subsequent requests is already working correctly when offline_access is configured. The requested change concerns the initial token acquisition in a new Novacura session.

    What?
    When a REST Connector requests an authentication token for the first time in a new Novacura session, it should attempt to acquire the token silently when the user already has a valid Entra ID session.

    Expected flow:

    1. User starts the Novacura client without a previous Novacura session.
    2. User signs in using Entra ID.
    3. User starts an application for the first time.
    4. The application performs a REST call requiring an Entra ID token.
    5. The REST Connector acquires the token silently using the existing Entra ID session instead of initiating another interactive sign-in.

    Or if the popup dialog box for the REST connector could be bypassed, this would likely work.

    Why?
    When a user starts the Novacura client without a previous Novacura session, they authenticate with Entra ID before opening an application.

    When the application is started for the first time and a REST Connector needs to acquire a token, the token request is currently performed as an interactive sign-in. This is visible as an interactive authentication request in the Entra ID sign-in logs.

    At this point, the user already has a valid Entra ID session. Requiring another interactive authentication request is therefore unnecessary and prevents the initial REST call from providing a seamless single sign-on experience.

    Refresh token handling… more

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Connectors  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Function to Rename/Change Microsoft User name
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Issue with Saving and History for Flow Connect

     I encountered issue with Flow Connect Designer that, in my believe, can cause issues in future.
     I’m testing flows for client and as I open it had some errors. I added debug step and committed (lets call it v2) to test. After a while I realized that previous commit (lets call it v1) did not have errors. Somebody worked on that flow before me, saved it but not committed. Now, looking through flow history it looks like my commit (v2) caused errors.
               A bit similar issue can arise when importing flow. We can import flow, work on it, run it for testing, all without committing. Other people also can work and save without committing. But since nobody committed all this work is not stored in history. 
                Because now multiple people can work on same flow, ability of saving without committing and creating new version in history, can cause huge problems even by accident.
    

     I encountered issue with Flow Connect Designer that, in my believe, can cause issues in future.
     I’m testing flows for client and as I open it had some errors. I added debug step and committed (lets call it v2) to test. After a while I realized that previous commit (lets call it v1) did not have errors. Somebody worked on that flow before me, saved it but not committed. Now, looking through flow history it looks like my commit (v2) caused errors.
               A bit similar issue can arise when importing flow. We can import flow, work on it, run it

    … more
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Designer  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Auto Retry Errors in Offline Queue Lanes

    In our workflow, we have an app where we use offline Queue lanes. What happens is when the driver gets connected to internet, it begins to transfer data to the ERP, but they are often driving. So at some point during the transfer, they lose internet connectivity in remote locations. They are presented this error on the client "Software caused connection abort". The drivers resolve this by just hitting retry to continue the process.

    We would like to request that these steps are automatically retried once connectivity is established. This would keep the users from having to retry many steps over and over again when they get connected to internet.

    In our workflow, we have an app where we use offline Queue lanes. What happens is when the driver gets connected to internet, it begins to transfer data to the ERP, but they are often driving. So at some point during the transfer, they lose internet connectivity in remote locations. They are presented this error on the client "Software caused connection abort". The drivers resolve this by just hitting retry to continue the process.

    We would like to request that these steps are automatically retried once connectivity is established. This would keep the users from having to retry many steps… more

    •  

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Increase Text Box Height When Making Edits in Mobile Client

    Currently, it's difficult to make edits within a notes text box on mobile apps due to the heigh restriction of the box.

    When reading the notes entered before going in to edit, a user can read multiple lines of text entered and can navigate what was entered easily. Once you begin to enter text, the view switches from a multi-line text box to a single line text box. It requires end users to scroll left to right to read text and determine their position inside of text box, making it difficult to write up large entries here.

    When users go to make an edit, the text box should remain in a multi-line view with line breaks included as they make additions. Having this and the ability to scroll up and down to view multiple lines of text entered will make it easier to read and enter information.

    Currently, it's difficult to make edits within a notes text box on mobile apps due to the heigh restriction of the box.

    When reading the notes entered before going in to edit, a user can read multiple lines of text entered and can navigate what was entered easily. Once you begin to enter text, the view switches from a multi-line text box to a single line text box. It requires end users to scroll left to right to read text and determine their position inside of text box, making it difficult to write up large entries here.

    When users go… more

    •  

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Add an “Archive” Option for Deleted Applications in Flow Connect

    I would like to have an archive option in flow hub as Currently, when an application is deleted in Novacura Flow Connect, it is permanently removed without an intermediate archive state. This limits the ability to recover deleted applications within a safe retention period and increases the risk of accidental data loss.
    I propose adding an Archive option for deleted applications in Flow Connect. With this feature Deleted applications would first move to an Archived state instead of being permanently deleted immediately.
    Archived applications remain visible in a dedicated “Archived Applications” list for a defined retention period (e.g., 30 days). Users can Restore an archived application to its previous state within the retention period. After the retention period, the application is permanently deleted automatically. Administrators can also manually Delete an archived application immediately if needed. This would align Flow Connect with common application-management patterns in other cloud platforms and provide a safer, more flexible workflow for teams managing migrations and application lifecycle changes.

    I would like to have an archive option in flow hub as Currently, when an application is deleted in Novacura Flow Connect, it is permanently removed without an intermediate archive state. This limits the ability to recover deleted applications within a safe retention period and increases the risk of accidental data loss.
    I propose adding an Archive option for deleted applications in Flow Connect. With this feature Deleted applications would first move to an Archived state instead of being permanently deleted immediately.
    Archived applications remain visible in a dedicated “Archived Applications” list for a defined retention period (e.g., 30 days).… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Built-in feedback function

    Why?
    Users need an easy way to provide feedback directly in context, whether they notice a small usability issue, experience performance problems, or encounter an error. Today, feedback is often reported outside the product, which can lose important context and make issues harder to understand and reproduce.

    What?
    Add a built-in feedback function in Novacura Flow that is available throughout the product.

    The user should be able to open the feedback function from anywhere, enter feedback in natural language, and submit it. The feedback can relate to anything from UI issues, such as a button being too small, to technical or performance issues, such as a connector step taking too long.

    When feedback is submitted, Flow should automatically collect relevant metadata, including app, app version, client, user context, current screen or step, and technical/runtime context where available.

    The same function should also be available when an error occurs, allowing the user to explain what they were trying to do in their own words. This should help support, consultants, and product teams understand the user intent and context behind the issue.

    Acceptance Criteria:
    [ ] A user can open the feedback function from anywhere in Flow.
    [ ] The user can enter free-text feedback in natural language.
    [ ] Feedback can be submitted for both general product/app feedback and error situations.
    [ ] Submitted feedback includes metadata such as app, app version, client, user, current context, and runtime information where available.
    [ ] When an error occurs, the user can add a description of what they were trying to do.
    [ ] Feedback is stored in a structured way so it can be reviewed, searched, and acted on.
    [ ] The feedback function does not block the user from continuing their work unless required by the error scenario.

    Why?
    Users need an easy way to provide feedback directly in context, whether they notice a small usability issue, experience performance problems, or encounter an error. Today, feedback is often reported outside the product, which can lose important context and make issues harder to understand and reproduce.

    What?
    Add a built-in feedback function in Novacura Flow that is available throughout the product.

    The user should be able to open the feedback function from anywhere, enter feedback in natural language, and submit it. The feedback can relate to anything from UI issues, such as a button being too small, to technical… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Configure app execution screen location per Portal button

    Why?
    End users experience Portal buttons as part of the solution, not as generic web client launches. Today, the app execution window location is not controlled per starting point, which can make the experience feel inconsistent or less tailored to the user workflow.

    What?
    Allow a designer to define the app execution screen location individually per Portal button.

    As an alternative or fallback, allow the end user to set and save the screen location per started app, regardless of whether it was launched from a button, double-click, or another start action. The saved location should be remembered per started app.

    Acceptance Criteria:
    [ ] Best case but optional: A designer can configure the app execution screen location for each Portal button .
    [ ] Apps launched from different buttons can open in different configured locations.
    [ ] If user-defined positioning is supported, the selected location is saved per started app.
    [ ] The saved location is reused the next time the same app is started.
    [ ] The behavior works consistently whether the app is started from a button, double-click, or another supported launch action.

    Why?
    End users experience Portal buttons as part of the solution, not as generic web client launches. Today, the app execution window location is not controlled per starting point, which can make the experience feel inconsistent or less tailored to the user workflow.

    What?
    Allow a designer to define the app execution screen location individually per Portal button.

    As an alternative or fallback, allow the end user to set and save the screen location per started app, regardless of whether it was launched from a button, double-click, or another start action. The saved location should be remembered per started app.

    … more

    •  

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Portal  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Configure color on End User Groups in Flow Connect (Hub)

    Configure color on End User Groups in Flow Connect (Hub).
    This feature is not possible as of today. I would like something similar to the way we can configure icon and color to apps and application packages.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. inline field validation on input fields (text input to start with)

    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

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Clients (Webclient, Android, iOS)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Flow connector / Studio Reports in Flow Connect

    In classic customers are using the Flow Connector, or reports from the Studio, to extract meta data about the system such as:
    Last Logged in,
    Number of logins

    A similar report in Connect is needed

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hub  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating