84 results found
-
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!
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.
-
Remove warning messages
we would like to get rid of unnecessary and misleading warning messages when updating flows up the dependency chain
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.
-
Translation panel and standard buttons
Support for multiple languages in Flow can be a involved process and with many large workflows in a solution it can be challenging to provide a consistent translation (and terminology!) in your apps. In the translation industry, a common way to work is to have a side-by-side or spreadsheet view of all text with the original language on one side and the translations on the other. I would love it if the Languages tab in Environment could collect all text from one or multiple apps and then put that text in a table with editable fields where you can enter…
2 votes -
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 votes -
Update the version of the SqlParser
Update to the latest version of the SqlParser For Special SQL Server Functions such as string_agg([Column], [separator]) function in combination with "WITHIN GROUP (ORDER BY [Column])"
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.
-
Customize rows per page in the datagrid
The ability to show more than 100 rows per page in a datagrid for a Web NG Client is typically controlled by the settings and configuration of the datagrid component.
It was available in the old web client but is not present in the NG web client.
2 votes -
Native Data Layer
Our users seek more flexibility and independence in their application development, it becomes crucial to provide them with a native data storage solution that is seamlessly integrated into the Flow environment. This feature would empower users to set up and manage their own databases directly within Novacura Flow, offering a level of control and customization that aligns with their specific application needs.
Key Benefits:
Simplified Data Management: Users can create, modify, and manage their databases without the need for external database systems, simplifying the entire data management process.
Enhanced Security: By providing an integrated data layer, Novacura Flow can ensure…
2 votes -
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 votes -
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.
-
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 -
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,…
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 -
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 -
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
- Don't see your idea?