88 results found

1. Enhanced Functionality for Identifying Flows Requiring Update

   When sharing a flow across different environments and switching between them, I notice the flow being marked with a green circle containing a white star, indicating the need for updates.

   Kindly introduce a feature that enables view filtering, allowing me to exclusively display flows requiring updates. This is particularly essential when dealing with a considerable number of shared flows, as manually clicking, scrolling, or searching by name becomes time-consuming. The ability to readily access 'All Subscribed Flows with Updates' would be greatly beneficial.

   I would appreciate the inclusion of a 'batch update' functionality for flows. Currently, updating each flow individually by clicking and selecting 'UPDATE' can be cumbersome. It would be highly efficient if I could either multi-select or utilize an 'update all' option, streamlining the update process. While I understand that updates might still be executed individually behind the scenes, eliminating the need for repetitive right-click actions and manual updates would significantly enhance the user experience

   When sharing a flow across different environments and switching between them, I notice the flow being marked with a green circle containing a white star, indicating the need for updates.

   Kindly introduce a feature that enables view filtering, allowing me to exclusively display flows requiring updates. This is particularly essential when dealing with a considerable number of shared flows, as manually clicking, scrolling, or searching by name becomes time-consuming. The ability to readily access 'All Subscribed Flows with Updates' would be greatly beneficial.

   I would appreciate the inclusion of a 'batch update' functionality for flows. Currently, updating each flow individually… more

   1 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  ·  Studio  ·  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

2. Enhance Workflow Efficiency with Checklist Grouping Feature

   We kindly request the addition of a new feature, "Grouping," to the control checklist subtask within workflows. This enhancement aims to optimize user experience and efficiency when dealing with extensive checklists. By introducing a grouping option, users can achieve a clearer overview of checklist items, particularly in cases where there is a substantial number of items. This feature will greatly improve workflow management and streamline task execution, contributing to a more productive and organized working environment. Your consideration of this feature request is greatly appreciated.

   1 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  ·  Studio  ·  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

3. Enhance SQL Machine Steps for Direct Flow Table Usage and Improved Performance

   Currently, the process of using a table variable within an SQL machine step in our workflow involves a workaround using JSON, which can lead to extended user wait times due to additional processing. Additionally, Flow's handling of table iteration within SQL is notably slower compared to direct SQL operations on large datasets. Our proposed feature request aims to streamline this process and enhance performance. We kindly request the implementation of the following enhancements to Flow's SQL machine steps:

   Direct Reference to Flow Tables: Enable the ability to directly reference Flow Tables within SQL machine steps. This functionality would eliminate the need for the current workaround involving JSON encoding, leading to more efficient and faster processing.

   Avoid Iteration via Machine Step Configuration: Provide an option to bypass the need for manual iteration configuration within the machine step settings. This would streamline the workflow and reduce the complexity of setting up SQL operations on Flow Tables.

   Output Flexibility: Maintain the capability to output values, records, or entire tables when using Flow Tables in SQL machine steps. This flexibility is essential for various use cases and ensures seamless integration with downstream steps.

   Currently, the process of using a table variable within an SQL machine step in our workflow involves a workaround using JSON, which can lead to extended user wait times due to additional processing. Additionally, Flow's handling of table iteration within SQL is notably slower compared to direct SQL operations on large datasets. Our proposed feature request aims to streamline this process and enhance performance. We kindly request the implementation of the following enhancements to Flow's SQL machine steps:

   Direct Reference to Flow Tables: Enable the ability to directly reference Flow Tables within SQL machine steps. This functionality would eliminate the… more

   1 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  ·  Studio  ·  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
   under review  ·  AdminPaul Phillips (VP Product Management, 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.

4. Copy Flow Studio Information to Clipboard

   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

   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  ·  Studio  ·  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

5. Enhanced Import Capability for Complex Customer Start Inputs

   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

   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  ·  Studio  ·  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

6. Overriding Novacura Lockout for Users Synced through AD

   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 situation, it would be beneficial to implement a solution where synced users do not get locked out from Novacura due to AD account issues. This modification would alleviate the complications arising from lockouts and prevent users from being denied access to Novacura even after their AD accounts have been resolved.

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

   1 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  ·  Studio  ·  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

7. Include the ability to translate variable and static text

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

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

   1 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  ·  Studio  ·  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

8. Disable Focus on User Step Element

   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 grid on the same screen without a user needing to click next.

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

   1 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  ·  Studio  ·  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