88 results found
-
View Data Grid columns without being in edit mode
It would be nice to be able to view data grid columns without first having to be in edit mode in studio. As it stands, when you select a datagrid element while not in edit mode, it only previews the column names in that boxed area, and depending on the length of the names, only shows a few of them. It would be super helpful if we could go a layer deep to view each column, it's data source, and perhaps just the entire edit screen in general without having to officially open it up for editing.
9 votes -
Hide Grid Column when empty
Dear Novacura R&D,
As much as powerful the grid element in the User Step is, it would be great to enhance it with dynamic features.
Like the 'Condition to hide' that affects the elements in the User Step, it would be great to have something similar for the content of the grid. And thus, if a particular condition is met, say a column is empty, then it could be hidden.
We quite often find ourselves in situation where we have multiple scenarios and data that differ from each other. Instead of creating multiple grid variants in one User Step, it…5 votes -
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 votes -
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 votes -
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…
2 votes -
Chat User-Step Element
It would be ideal to have a chat user-step element that could be configured in Flow. This would allow us to more easily use GPT in a dynamic way inside of the Novacura Flow Client.
3 votes -
colors/branding in studio to distinguish connected server
Please allow us to brand/color the studio based on the connection.
I frequently work in different flow environments and it is really easy to switch to the wrong studio window.
If I could either
1)set the branding on the server level so all studio logins for that server had the same color/branding whatever
2) or set the branding locally in studio...that would be great
My thoughts are
1) Allow for the studio header/border to be a different color
2) Make the SERVER I'm connected to more prominent, like in the same area as "Application/Environment/Monitoring"3 votes -
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 votes -
Seamless process to clean up treasure files
we would like to have schedule cleaning jobs that clean treasure files and what is now saved on the server.which would maybe feel more safer and reasonable if we’d be able to write this from the Studio
3 votes -
Request for Enhanced Timestamp Resolution in Logpoint Data
Requesting an upgrade to the timestamp resolution in logpoint data beyond seconds to milliseconds. Currently, the timestamp value retrieved from logpoints is limited to seconds, hindering detailed analysis and synchronization with higher resolution systems. Expanding the resolution to milliseconds would align with modern data processing requirements and enable more precise temporal analysis within the system.
1 vote -
Progress bar UI element
When doing complex operations in Flow, either as a loop of machine steps or as a machine step with an iterator, the user is left in the dark about what is happening. It would be great to be able to present the user with a progress bar that gradually fills while Flow is processing the operations. This could be a special User step that requires no interaction from the user and disappears when the process is done. Inputs would be a counter variable, a total of the number of operations and a user message detailing what is going on.
A…
8 votes -
Remove "Create" word in sequence arrow popup menu
When you create a sequence arrow then right click, there is no need to have the word "CREATE" before each element.
Additionally, the list could be alphabetized to easier find the type of element you want to add.
6 votes -
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 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.
-
Allow Developer to Open a Fragment Without being in Edit Mode
We would like to open up a fragment from the editor instead of either needing to enter edit mode or search in the server content window. There are times when multiple fragments of the same name exist in the server, and it becomes important to know which version is actually used. Furthermore, editing fragments, and not committing or reversing changes causes lock out of apps - all just to open an fragment to inspect.
12 votes -
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.
-
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.
-
Global Functions for Cross-Script Usability in Flow Environment
We request the implementation of a feature that enables users to create global functions within the Flow environment. These global functions should be accessible and usable from any script within the environment, irrespective of their location. By having the ability to define reusable functions at a global level, users can avoid redundancy and promote code modularity across their workflows. This enhancement would significantly improve the efficiency and maintainability of scripts within the Flow environment.
12 votes -
Date Column Option in DataGrid User Element
There's no direct support for formatting the date column in the DataGrid User Element.
11 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.
-
Timezone script and setting in Flow
The current Now() function in Flow retrieves the time based on the device's local time. This can lead to inconsistencies for users or workflows operating across different time zones. To improve this, there's a need for advanced time manipulation functions and settings.
Proposed solution is to introduce new functions like Now().utc, allowing users to retrieve time based on specific time zones like UTC. Additionally, integrating a timezone setting for each user in Studio, similar to the existing Language and Locale settings, can ensure consistency and accuracy in workflows, catering to diverse customer needs. This enhancement will grant users greater flexibility…
7 votes -
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 vote
- Don't see your idea?