71 results found
-
Remove warning messages
we would like to get rid of unnecessary and misleading warning messages when updating flows up the dependency chain
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Distinctive Column Naming in Flow Studio Variable List
In Flow Studio, users encounter a challenge where some column names appear twice in the variable list without any indication of their originating table. This lack of distinction can lead to confusion and potential errors in selecting the correct variable.
Proposed solution is to enhance the variable list display to include the source table's name along with the column name. This will enable users to easily distinguish between variables with the same name but from different tables, thereby reducing confusion and improving accuracy in variable selection. Implementing this feature could involve a format like "TableName.ColumnName" or a similar approach that…
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Separate Find & Problems Tabs or Stay On Find Tab
The Find and Problem tabs in studio are connected and cannot be pinned separately. This makes finding problems and debugging them more difficult. Also when you search for a term in the Find tab, and then open an object in flow to edit the node, upon exiting the node editor window, the Find tab automatically switches back to the Problems tab which is extremely annoying and inefficient. So either stopping the auto-switching to the Problems tab or separating the two tabs would be extremely helpful.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Improved Handling of Fragment Versioning and Error Navigation in Flow Studio
In the current system, when there's an error in a flow fragment version, navigating to the issue via the Problems window takes the user directly to the fragment version causing the error. While this might seem like a logical approach, it can be counterintuitive in scenarios where multiple versions of flows and fragments are being worked upon concurrently. Users might end up editing older versions of fragments unintentionally.
Use Case Scenario:
Consider two flows, A and B, where B is a fragment invoked by A. Both have versions Av1 and Bv1 as the latest. Now, if a new version of…2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
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 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
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 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
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 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
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 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
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 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
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 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
More Frequent Scheduling Options for Machine Flow in Studio
Currently, in Studio, the most frequent schedule available for scheduling a machine flow is set at 10 seconds. As a user with specific job requirements, I would like to request the implementation of more frequent scheduling options for machine flows. This enhancement will enable me to run certain jobs more frequently, providing greater flexibility and efficiency in managing time-sensitive tasks.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
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 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Rich Text options in Emails
We like to propose a feature enhancement for the Email Connector in Novacura Flow Studio. Currently, the email body supports only plain text with HTML tags, which limits and complicates formatting options for end users. It would be highly beneficial to have a Rich Text Editor (RTE) integrated into the Email Connector to allow for:
Basic formatting (bold, italics, underline)
Bullet points and numbered lists
Hyperlinks
Inline images or attachments (if feasible)This would significantly improve the readability and professionalism of automated emails sent from Flow apps, especially for customer-facing communications.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Machine Steps in Flow Studio - Failures on Iterator
Hi,
example for teh above asking
Suppose you have 2 data grid created for different purpose
Now you will be using iterating and using individual machine steps and insert data into table.
m1-->m2
Now m1 successfully executes though m2 fails but it's wrong if I want to execute whole flow successfully and all the machine steps should if successfully runs, complete the flow.Now because of the above action some data getting inserted but others not.
Can we have a process where we can decide all machine flow executes and then it gives a success. it can be a user…1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Option to Suppress Subscription Notifications for Disabled Environments
In instances where a TEST environment is disabled while PROD remains subscribed to TEST, users encounter a barrage of subscription notifications, disrupting workflow in PROD Studio. To mitigate this, we propose implementing a feature that provides users with the option to suppress subscription notifications temporarily. This could include a warning prompt with the choice to suppress notifications for the current session or for a customizable duration, such as 24 hours, ensuring uninterrupted productivity during critical work periods.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Copy values between user step input types
When changing a input type (say list selection with a menu) values need to be copied manually one by one. This is prone to error.
It would be ideal if comparable data is copied into the correct fields so any changes in the user step items could be done without loss of data
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Dark Mode
PLEASE, add a dark mode theme for Studio! For those of us that use dark mode themes on our computers, Studio's window colors are eye-watering bright. Every other program I have on my computer has a dark mode. This should be a very easy low-cost but high ux-value feature. See attachment for example.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Enhanced Select Language in real time
When using the flow environment connector to change language, we would like the language to change directly inside the flow, without having to log in or go to settings and change the language.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Remove arrows by drawing a line through them while holding a hotkey
Similar to how many other node based software allow you to hold a hotkey and draw through arrows with your cursor to "cut" the arrows, this could be very useful in Flow.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Paste Copied Element
When I copy an element, I want to be able to right click on a sequence arrow and paste. As things stand I have to paste onto the canvas and then drag until I get the green arrow. I should be able to right click and "insert copied element."
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
- Don't see your idea?