18 results found
-
Simplify Input Parameter Management for Workflow Start Task in Novacura Studio
Introduce a feature that enables users to import input parameters directly into the workflow's start task from a JSON file or similar format. This would improve the efficiency and flexibility of parameter management, eliminating the need for manual entry while maintaining the security restrictions on the workflow header, which remains locked from editing by design. The feature ensures a more user-friendly experience without compromising the security protocols in place.
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.
-
Custom Device Naming in Studio
Currently, the device management page in Studio uses model numbers as the default for the Name field. This approach is inadequate for environments with multiple devices of the same model, as it creates confusion and inefficiency by not allowing easy identification of individual devices.
Proposed solution is to implement the ability to customize device names in Studio. This feature would allow administrators or users to rename devices according to their specific naming conventions or operational needs, making it easier to identify and manage multiple devices of the same model. This customization should be easily accessible from the device management interface…
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.
In Flow Connect, there is no longer the need for Device Approval using a standardized IDP with MFA.
-
Allow to Subscription of multiple flows at once
We have utilized some generally good programming concepts and have about 30 flows that all rely on the same fragment. When we make a change to that fragment, we can now easily publish all these flows in our test environment.
However, what we would like to do is share them all in one step, so that we can subscribe to the update in our production environment. Unfortunately, this proves to be a painstakingly long process, and with the passage of time, it will only exacerbate further.
17 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 for Flow Classic. We appreciate your continued feedback and look forward to hearing about future ideas.
Please see the upcoming changes that have been made to deploying applications in Flow Connect. The changes on Flow Connect will support this request.
-
Arrows are not easy to identify or get too long
Sometimes I have VERY long arrows. When i highlight the arrow I can see it nicely, but as soon as I try to move it is not highlighted. I want to be able to see my separate arrows ESPECIALLY WHEN THEY overlap.
A few options to consider.
Allow me to color arrows different colors for visibility.
Allow me to select an arrow and leave it “selected” so it stands out.
Allow me to have a shorter arrow that goes to a “GO TO” element which is just a pointer to another element in the flow.
7 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.
-
Extended information in server log
As a flow designer, I would like to see the Flow Task name and if possible also the Workflow Name for each of the log items. This would allow me to understand exactly where the problem is and shorten the time needed to fix the issue for the Flow users
4 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.
-
Customizable Navigation Bar: Add Option to Remove/Disable Calendar Button
We have successfully implemented the inbox feature and have identified that the calendar button is not currently necessary for our workflow. To enhance user customization and streamline the interface, we kindly request the addition of a feature that allows users to add, remove, or disable specific navigation buttons, including the calendar button. This flexibility would empower users to tailor the platform to their unique needs, optimizing the user experience and increasing efficiency.
3 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.
-
Introduce FlowScript in REST Service connector parameters
it would be highly advantageous to introduce the ability to execute this script as an option within a REST Service call. Currently, the REST Service connector parameters only offer limited choices such as "Variable," "Constant," and "Not Set." By incorporating this script execution as an alternative, it would empower users to execute more intricate operations within the flow, thereby providing greater flexibility and customization to the process.
11 votesWe regret to inform you that this feature request has been declined in Flow Classic track. After careful consideration, our product team has concluded that it does not align with the established product roadmap for Flow Classic, nor does it offer sufficient value to justify its implementation. We appreciate the feedback you have provided and remain open to hearing about future ideas.
That being said, we encourage you to explore the recent enhancements made to the REST connector in Flow Connect. The REST connector within Flow Connect already accommodates this particular request. Additionally, we are actively seeking beta customers for Flow Connect. If you are interested, please reach out to your local account manager for further details.
-
Test Automation
When a process is changed or altered it takes manual testing of scenarios. It takes time of a QA resource to a somewhat a repetitive task.
It would be nice to have a a process to record test scenarios (and incrementally add new scenarios, value combinations etc.) so those previously envisioned scenarios can be tested automatically every time something changes in the flow.
Feature could give out a summary of the testing along with the scenarios, values or flow steps that got failed during the testing
3 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.
-
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 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 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.
-
Simplified "For Each" Loop Element for Dataset Processing
Currently, when looping through a dataset/table, users need to create a copy of it, check if it is empty, fetch one row at a time, process it, and then exclude that row before continuing the loop. This process involves unnecessary steps and can be time-consuming. Therefore, I propose the implementation of an easy-to-use "For Each" loop element. This element should allow users to set the dataset and define the assignment of each row, simplifying the iteration process. It should automatically handle row traversal without requiring additional checks or dataset manipulation. This feature would enhance productivity by streamlining dataset processing and…
6 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.
-
Adding Restrictions for Date Inputs
When utilizing a date input field, the absence of input restrictions compels us to verify the entered information at a later stage, leading to a suboptimal user experience. However, by implementing limitations on date inputs, we can proactively uphold our business rules within the user interaction itself, rather than addressing them in subsequent stages. This not only enhances user interface quality but also streamlines the entire process.
5 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.
-
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.
-
Customize the Generated Web Link
We would like to have an option like to customize the "Generated Web Link"
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.
-
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.
-
Dynamic DataGrid Column Sizing Based on Header Text in Studio
In the current Studio setup, the DataGrid column width does not automatically adjust based on the length of the column header text. While there is a resizing behavior that triggers when there are numerous columns and users start scrolling horizontally, this behavior isn't necessarily intuitive or based directly on the column header text length.
Proposed Solution is to introduce a feature in Studio where the DataGrid column can dynamically adjust its width based on the length of the column header text. This feature would ensure that column headers are always fully visible without truncation, enhancing usability and readability. There should…
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?