83 results found
-
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 -
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 -
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…
2 votesThank 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.
-
Ability Access Control to root Folders of Flow Studio
When multiple parties are involved in Flow Development (eg Novacura/Partners/Customer) it is essential to control access to different workflows. One of the ways to achieve this is to allow access control to the folders created on the root (and not allowing any workflows/menus to be created without a folder)
1 vote -
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.…
2 votes -
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 -
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 ;
Remove this Access Level as it is essentially useless now
Keep this Access Level, but restrict (remove) access to use the Flow Environment connector
1 vote -
Enhanced Flow Management and Collaboration Features in Studio for Checked Out Flows
This request aims to improve the flow management and collaboration capabilities in Studio by introducing the following functionalities:
Find Locked Flows: Add a feature to easily discover all locked flows within the Studio environment, enabling users to quickly identify which flows are currently in use or being worked on by others.
View User Information: Provide the ability to view the user who has locked a specific flow. This information will help users to understand who is currently working on a particular flow and facilitate communication and collaboration.
User-based Filtering: Implement a filtering option that allows users to sort the list…
2 votes -
Right-Click Flow Sharing in Server Content Panel
This feature request seeks to enable users to right-click on a flow within the Server content panel without launching the flow, allowing them to directly SHARE the flow. By implementing this functionality, users can conveniently and efficiently share their flows with others, eliminating the need to open the flow first, which would enhance the overall user experience and streamline the flow sharing process in the system.
2 votes -
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.
2 votes -
Improved Hover Over Menu Behavior for Fragment Steps
While using the hover over menu on a fragment step, users face difficulty when sequence arrows are present and coming into the included workflow step that they are hovering over. When attempting to drag the mouse downward to access the update arrow on the hover menu, the system mistakenly interprets this action as an attempt to interact with the arrow, causing the hover menu to disappear.
2 votes -
Improved Version History Timestamps
Currently, one of the challenges we face when reviewing the version history is the absence of timestamp details for when a specific change was made. This lack of chronological information makes it difficult for us to quickly ascertain whether a flow (or any other element) has been recently modified or if the changes were made a long time ago.
To address this issue, I propose the implementation of a simple yet powerful addition to the version history – the inclusion of the date or year when each change was made. By adding this vital piece of information alongside the version…
2 votes -
Auto-incrementing Variable in MAP AS Function
The MAP AS function has proven to be an invaluable tool for us to streamline our workflows and avoid using cumbersome for loops. Nevertheless, we have run into situations where we were forced to switch back to using for loops due to the absence of an auto-incrementing variable within the map function.
To elaborate, we frequently encounter scenarios where we need to remap filenames within a FileGallery to conform to specific naming conventions or add suffixes like "Pic 1," "Pic 2," and so on. Currently, this cannot be efficiently achieved using the map function, as there is no straightforward way…
2 votes -
Empowering Precision and Control with MidpointRounding in Flowscript's Rounding Process
Empowering Precision and Control with MidpointRounding in rounding processes with two conventions
1. Rounding away from zero
2. Rounding to nearest even1 vote -
Business Process Mining from Telemetry Data
As Flow Developers, we often find ourselves striving for optimal workflow efficiency and effectiveness. To facilitate this, we propose a feature that combines two essential elements: enhanced flow analytics and seamless Copilot integration.
Key Benefits:
Route Performance Insights:
Percentage-Based Route Usage: Flow Developers can gain valuable insights by visualizing the most frequently used routes within a workflow, presented as a percentage. This helps in identifying bottlenecks and optimizing workflow paths.
Average Time Tracking:Time Spent Between Workflow Steps: Users will have the capability to track and analyze the average time spent between each step of the workflow. This empowers developers…
1 vote -
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…
1 vote -
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…
1 vote -
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 -
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 -
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
- Don't see your idea?