84 results found

1. Introducing a Feature to Locate Published but Unshared Flows

   During development, I utilize a fantastic feature to update and auto-publish flows affected by changes. However, transitioning to the Production stage is less straightforward, requiring manual searching, opening, and sharing of modified flows.

   To enhance this process:

   Simplified Sharing: A 'Share' option accessible through right-clicking flows in the server view could eliminate the need for individual openings, complementing the existing 'Publish' link.

   Unified Sharing Checkbox: Similar to the 'Publish' checkbox, an equivalent 'Share' checkbox for updating flows could streamline post-approval sharing, especially for numerous flows influenced by fragment adjustments.

   Differential Version Listing: A feature listing flows with differing published and last shared versions would greatly assist in identifying flows for Production migration, especially after extended development phases.

   During development, I utilize a fantastic feature to update and auto-publish flows affected by changes. However, transitioning to the Production stage is less straightforward, requiring manual searching, opening, and sharing of modified flows.

   To enhance this process:

   Simplified Sharing: A 'Share' option accessible through right-clicking flows in the server view could eliminate the need for individual openings, complementing the existing 'Publish' link.

   Unified Sharing Checkbox: Similar to the 'Publish' checkbox, an equivalent 'Share' checkbox for updating flows could streamline post-approval sharing, especially for numerous flows influenced by fragment adjustments.

   Differential Version Listing: A feature listing flows with differing published and… 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. 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

3. Simplifying Workflow Conversion

   Frequently, I design a workflow and realize the need to switch it from a User Flow to a Fragment, either due to oversight during creation or the newfound requirement for reusability. The current process of converting the workflow in the studio is rather cumbersome. Although I've managed to export the Flow, manually tweak the XML, and then re-import it to achieve a Fragment, it strikes me that this procedure could be streamlined. Perhaps a more user-friendly approach would involve incorporating a 'Convert To' option, accessible through a simple right-click within the server explorer, offering a range of flow type transformations

   6 votes

   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

   2 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

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

5. Improved Machine Step Script Error Handling for Oracle Code

   We kindly request the enhancement of the machine step script error handling process related to Oracle code. Currently, an error is being flagged erroneously, even though the syntax is accurate and aligned with Oracle object specifications. We propose an update to the error detection mechanism to correctly recognize the valid syntax on Oracle objects, ensuring seamless execution of machine step scripts without unnecessary interruptions.

   •  

   2 votes

   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. Enable "Workflow Fragment" as Seed Item with Data Arrow in Flow Studio

   We kindly request the implementation of a new feature within Flow Studio, allowing the integration of "Workflow Fragment" as a Seed Item while utilizing a data arrow to the start step. Currently, any attempt to include a Workflow Fragment as a Seed Item leads to undesired outcomes. Specifically, when users press the "Run" button, the flow crashes, or upon selecting the "Publish" button, an error message surfaces: "Missing mapping for NovaCura.Flow.Designer.CanvasItems (..). Possible usage of unconverted elements from previous Flow versions."

   5 votes

   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. Enhanced DataGrid Selection Control with Default Row Selection

   We kindly request an enhancement to the DataGrid functionality in Studio, allowing users to pre-select one or more default rows when binding the DataGrid to a table and enabling selections, including single selection mode. Currently, users are unable to set default selections, which can result in additional manual steps for users to accomplish this. This proposed feature aims to improve the usability and efficiency of DataGrids by providing the ability to automatically mark specific rows as "selected" upon binding.

   8 votes

   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. Streamlined Fragment Version Update Button in Workflow View

   We kindly request an enhancement to the workflow interface by adding a convenient "Update to Latest Fragment Version" button directly accessible within the workflow view. Currently, users are required to navigate through menus to initiate updates, leading to unnecessary disruptions and potential confusion. This proposed feature aims to improve user experience and workflow efficiency by providing a seamless and direct option for updating fragment versions.

   2 votes

   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

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

   2 votes

   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.

10. Improvements in the Pick Menu for Fragments in Studio

    The current Pick menu within the workflow interface presents several counterintuitive aspects that could be streamlined for a more efficient and user-friendly experience. We propose the following enhancements:

    Automatic Selection of Single Versions:
    When a flow with only one version is selected, the system should automatically utilize that version instead of prompting the user to choose. This reduces unnecessary steps and simplifies the process.

    Default Selection of Current Version:
    Implement a feature that enables the automatic selection of the current version by default, allowing users to easily proceed without intervention. Users can then manually select a different version when required.

    Prioritize Filtering in Advance:
    Optimize the loading process for flows within the Pick menu by allowing users to start typing and filtering before initiating the server content search. This minimizes wait time and enhances the efficiency of selecting workflows.

    Open Included Workflows Outside Edit Mode:
    Enable the option to open an included workflow from the Pick menu, even when the current flow is not in edit mode. This facilitates quick access to included workflows for reference or updates.

    Implicit Check-Out and Check-In for Version Updates:
    Streamline the version update process by automatically checking out the flow when updating to a new version. After the update, the system should automatically perform the check-in, reducing the need for explicit user actions.

    Registering Changes after Updating Included Workflow Versions:
    Address the issue where updating a version of an included workflow does not register as a change, preventing users from committing updates. This problem can be resolved through the implementation of point 5, ensuring that version updates are correctly tracked.

    The current Pick menu within the workflow interface presents several counterintuitive aspects that could be streamlined for a more efficient and user-friendly experience. We propose the following enhancements:

    Automatic Selection of Single Versions:
    When a flow with only one version is selected, the system should automatically utilize that version instead of prompting the user to choose. This reduces unnecessary steps and simplifies the process.

    Default Selection of Current Version:
    Implement a feature that enables the automatic selection of the current version by default, allowing users to easily proceed without intervention. Users can then manually select a different version when required.

    … more

    2 votes

    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

11. Add QR-code(camera) as Keyboard type for text- and numeric unput in user steps

    I have several usersteps in multiple workflows, where the only purpose is to scan a barcode. I`ve been able to get the novacura app on mobile devices to automatically enter the input field (with the "Auto Focus input" turned on in the app), but I cannot get novacura to also select the camera. They need to click on the QR-icon every time. I could of course buy a bluetooth barcode reader, but I want this to work also with the mobile camera.

    Can you check if it`s possible to add QR code (camera) as keyboard type for text- and numeric inputs in user steps?

    In my workflows, the users will always try to scan a barcode first. If the barcode is broken, it needs to be possible to change back to keyboard, to write in the value which are written below the barcode. But this happens like 0,1% of the times for my use cases.

    I have several usersteps in multiple workflows, where the only purpose is to scan a barcode. I`ve been able to get the novacura app on mobile devices to automatically enter the input field (with the "Auto Focus input" turned on in the app), but I cannot get novacura to also select the camera. They need to click on the QR-icon every time. I could of course buy a bluetooth barcode reader, but I want this to work also with the mobile camera.

    Can you check if it`s possible to add QR code (camera) as keyboard type for text- and numeric… more

    3 votes

    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

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

12. Enhance 'checkpoint' workflow element

    We use at lot of Assertion Steps in our Flow to alert users that something went wrong. On typical example is that we usually compare the the input to a list of items. If it don’t match, the user gets a error.

    The problem with Assertion Steps is that the user have to click to remove the popup window. To be more efficient, a temporary popup would sometimes be enough.

    We can accomplish this using the Checkpoint-step and write text that covers the whole screen, as seen in the picture.

    But it would be nice to make this popup red, and play a “error”-sound instead of a “everything went fine”-sound.

    Maybe add some properties to the Checkpoint Step?

    We use at lot of Assertion Steps in our Flow to alert users that something went wrong. On typical example is that we usually compare the the input to a list of items. If it don’t match, the user gets a error.

    The problem with Assertion Steps is that the user have to click to remove the popup window. To be more efficient, a temporary popup would sometimes be enough.

    We can accomplish this using the Checkpoint-step and write text that covers the whole screen, as seen in the picture.

    But it would be nice to make this popup red,… more

    2 votes

    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

    2 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

13. Search ability enhancement in AD Sync Group in AD Sync

    We would like to have a proper search mechanism in AD Groups and when we try to search for one group. data should be able to get sorted according to letters when we type.

    3 votes

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

14. Resize images to fixed file size

    we would like to have enable a feature that allows downsizing to specified size (in MBs). Solution calculates the required resizing factor and use a quality down sampling algorithm (e.g. bicubic) that maintain adequate image quality and get it down to specified file size or just below. from the flow itself.

    7 votes

    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

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

15. Exclude uncommitted versions when checking for latest version of a workflow

    We would like to have uncommitted versions of a workflow excluded when checking for the latest version of a workflow while in 'edit mode'

    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

    2 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

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

17. Change Tracking Enhancement

    To increase auditability and reduce unnoticed changes in Flow Studio, we need a feature to track modifications made by third-party developers. The system should record changes made to flow components, noting the user and the commit timestamp. A comparison between changes (diff) would further enhance transparency.

    3 votes

    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

18. Enable Copying of Error Messages

    The aim of this feature request is to enhance the user experience and debugging efficiency by allowing users to copy error messages. Currently, when an error occurs, the message is displayed in a pop-up or inline notification. However, the text of these error messages is not selectable or copyable.

    2 votes

    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

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

    2 votes

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

20. Modify the Access Level "AdministerWorkflows" in Flow Studio

    If any user has been granted the Access Level: AdministerWorkflows, they can create a Novacura Flow in Novacura Studio to grant themselves AdministerBasicData.

    We would suggest One of two things to overcome this ;

    1. Remove this Access Level as it is essentially useless now

    2. Keep this Access Level, but restrict (remove) access to use the Flow Environment connector

    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

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