71 results found
-
Enhancing User Step Quality of Life
Introducing Record Key Targeting for User Step Input: Currently, to store user-entered text into a pre-existing record, an additional step is required after the User Step to combine the output into the record. Implementing the ability to directly target a record key for user step input will enable seamless pushing of the value output into the desired record, eliminating the need for an extra step. As an example, it would help stream line development if I could Use a Records Key/Value pair as the variable to output to. So “Foo.Bar” would be the output variable for single item inputs. Then…
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.
-
Add MFA/OTP support for direct Novacura Flow logins
As a user, I would like to use OTP/MFA (email, SMS, or authenticator app) when logging in directly to Novacura Flow Classic, so I’m not limited to only username + password.
This is especially important for external users outside the tenant who cannot use the organization’s external identity provider.
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.
-
Improved Version Update Mechanism in Studio
Currently, when an error occurs in Studio, such as "Item is not linked to the latest version," clicking on the error message automatically opens the fragment. This behavior is not always helpful, especially when the needed action is to update the version rather than edit the fragment. The limitation is compounded by the fact that version updates cannot be performed while the workflow is open in edit mode.
Proposed idea is to revise the error interaction process to better align with the user's likely intent. Instead of automatically opening the fragment for all types of errors, provide a more nuanced…
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.
-
Unlock locked user accounts in Flow with API
I would like the possibility to unlock locked user accounts in Flow environment via API.
As of now, our Servicedesk needs to have Studio installed and reserve one admin licence just to be able to support our organisation.
Thanks!
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.
-
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.
-
Group Connectors in Machine Steps
When you have a considerable amount of connectors it is not that easy to locate the connector you are looking for. If connectors can be grouped based on the type and then sorted alphabetically within the group will add immense value to the flow developers.
3 votesWe regret to inform you that this feature request has been declined for Classic as the feature already exist in Connect.
-
Facilitate Binary flow script function
We would like to have a feature to facilitate encode/decode Base64 with flow script function and be able to convert a flow variable to a binary file format.
3 votesWe regret to inform you that this feature request has been declined for Classic as the feature already exist in Connect.
-
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.
-
Seamless Marketplace Integration in Novacura Flow Studio Designer
To enhance the collaborative and content-sharing aspects of Novacura Flow Studio, we propose the integration of a user-friendly Marketplace directly within the Studio Designer. This marketplace will empower developers to effortlessly access, upload, and share content, fostering a vibrant ecosystem of tools and resources.
Key Benefits:
Simplified Content Discovery:
Developers can easily explore a wide range of resources available in the Marketplace, simplifying the discovery of valuable content.
User-Friendly Content Upload:The feature enables developers to upload their own content, whether it's templates, modules, connectors, or other assets, for others to benefit from, either for free or at a cost.…
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.
-
Enhanced Label Editing for Studio Elements within Flow Element Itself
In the current system, editing the label text of a canvas element requires double clicking on the element in the canvas view. This method can be time-consuming, especially when designing intricate flows. Moreover, without immediate renaming during the design phase, elements can end up with generic labels like “Machine Step”, “Machine Step [1]”, etc.
We propose to introduce an option to edit the label text directly when in the edit mode of a canvas element. This enhancement would provide designers the flexibility to rename elements on the fly, ensuring clarity and reducing the likelihood of generic, repetitive labeling.
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.
-
Change SQL validations in Studio
We frequently execute numerous queries on our M3 IBM DB2 iSeries database, and occasionally, I encounter issues where Flow Studio does not accept the query.
We've been able to adjust queries in the past to make them compatible with Flow Studio, but this time I'm facing difficulties. The problem specifically arises on line 7 of the query.
We make extensive use of "with" statements, so it's puzzling why I'm encountering an issue in this particular instance. It's possible that the problem is related to the brackets I'm using to dynamically insert parameters into the query, but despite the error, everything…
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.
-
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 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 Workflow Menu Filtering
Currently, when clicking "Add Workflow to Menu" in a workflow, the list of server objects displayed is filtered to show only menus, which is beneficial. However, the list still includes "folders" that do not contain any menus, leading to unnecessary clutter. We kindly request an improvement to this feature that removes folders without menus from the view.
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.
-
Setup a refresh option for inboxes
Sometimes, if a user is already logged into the system, the screens do not refresh automatically. As a result, certain inboxes may not display real-time data.
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.
-
Possibility to pre-approve devices in Flow Studio
As a user, I would like the ability to pre-approve devices in Flow Studio without manually logging in to each device. By utilizing device identifiers, such as MAC addresses,
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.
-
As a user, I would like to send SMS (Short Message Service) directly from Novacura Flow.
As a user, I would like to send SMS (Short Message Service) directly from Novacura Flow Classic.
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 suggest using a REST API with a service like Twilio to send SMS messages via Novacura Flow.
-
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.
-
Enhanced Flow History Management
The current system lacks efficient mechanisms for managing flow history, particularly in environments with numerous flows and versions. This leads to performance issues due to the accumulation of extensive history data. Additionally, the need to update flow IDs on the portal after importing and exporting flows complicates maintenance and disrupts workflow continuity.
Proposed solution is to implement a configurable option within the web configuration file to set a limit on the number of flow history entries retained, defaulting to the latest 10 entries. This setting would allow users to manage performance by controlling the volume of historical data stored.
Furthermore,…
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.
-
Accomodate Custom Aliases for Machine Step Queries
The issue arises when a column is modified in a complex SQL query and need to click the torch to have Flow recognize the changes in the output table. Unfortunately, the torch automatically reformats the SQL, which creates problems, particularly with UNION statements and other complex examples.
Is it possible to add a button that simply updates the output table to reflect any new or changed columns without performing a complete reformat of the SQL?
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.
- Don't see your idea?