284 results found
-
Facilitate debugging of offline flows in flow studio
Currently, the inability to run offline flows in debug mode in Studio complicates development and testing, significantly increasing development time. Resolving this issue soon will streamline the process and improve efficiency
3 votesWe are happy to inform you that development work has begun on your requested feature. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.
-
Get list of apps/users/user groups from hub
It would be great to have a variable or a connector/API I could call and get a list of apps/users/user groups from hub/environments.
(or few extra features such as sending invitation to a user via flow).Like in flow classic, see attached picture.
If updating users are not available due to security reasons, but at least fetching a list of users would be great.
3 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 -
Connect pins in Map Portlet
When I have multiple pins in the map portlet, it would be great to select a group of them or being able to connect two pins. These two pins could then be the input for a machine flow that calculates the time of travel via rest call.
This would help to use the portal for planning.3 votes -
Option to make a cell read-only or editable in a DataGrid
It would be nice to have a feature that can make a cell in a grid read-only or editable with a similar option to 'Cell Color'.
For example, if the contidion is true/false , then the cell is read-only or editable.
On the attached picture, yellow cells are editable, white cells are read-only.
Now, both 'Value' and 'Value List' columns are editable.3 votes -
Data Change Detection and Variable Utilization in Studio User Steps
In the current version of Studio, there is a limitation in detecting data changes made during a User Step. Proposed solution is to enhance Studio to include the capability of detecting any data changes that occur within a User Step. Following this detection, these changes should be easily accessible and usable as variables or properties in subsequent steps of the workflow. This feature would allow users and developers to dynamically adjust the workflow based on user inputs or changes, greatly enhancing the flexibility and functionality of Studio.
3 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])"
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.
-
Image Selection with Additional Inputs
We have startad using a lot of images in our Flows to show product images. There are however quite some limitations in this area.
I would like a see a Image function that allows us to display a image in any element.
The function should take image source, width and height (and maybe something to keep aspect ration or not). The width and height would rezise the image server side for faster load times on the client.
Img(url, 300, 300, 1)
This would allow us to display a list of items with images in List Selection Input or in a…
3 votes -
Duplicate a Component in Hub
I want to be able to duplicate both package and organization components. If a component with sub components is duplicated, it should keep the existing references.
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.
-
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…
3 votes -
Selective Column Search in Data Grids
In the current implementation, the data grid search functionality searches through all columns, including those that aren't displayed in the data grid or are not set up under "Edit columns."
Proposed solution is to introduce a customizable search functionality in data grids where users can selectively choose which columns to include in the search. This can be achieved by adding a checkbox option under "Edit columns" labeled as "Searchable". By default, all columns can have the "Searchable" checkbox marked to ensure compatibility with the existing behavior. Users can then choose to deselect certain columns if they don't want them to…
3 votes -
Enhancements to Offline Workflows while on Multiple Networks
Users experience challenges with offline workflows in Flow-app due to network variability. Devices connect to various networks throughout the day, but only one network provides the required server connection for data sync. As a result, offline transactions get stuck in a "failed" state, necessitating manual retries once the device reconnects to the secure network.
Proposed solutions are to implement a feature in the Flow-app to detect the current network. The app should only attempt to write back to the server when connected to a predefined, specific network. Alternatively provide users with an option to bulk retry all failed offline transactions…
3 votes -
Enhanced Log Analysis Tool for REST M3 API Connector
We urgently request an upgrade to the existing log analysis tool for the REST M3 API connector. Currently, the tool lacks the essential capability to efficiently search for specific transactions or data within the logs. With each call and response generating individual log files, the volume of transactions quickly becomes overwhelming, rendering effective analysis nearly impossible. In contrast, the previous socket-based M3 API connector generated a consolidated API text file that enabled easy data search and facilitated comprehensive analysis, including input and response times. The current limitation significantly hinders error diagnosis, making the troubleshooting process arduous and time-intensive. We propose…
3 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.
3 votes -
Allow developer to connect one flow to multiple buttons in Portal 2
We would like to use the same flow for multiple buttons in Portal 2. We use the input table to drive what the buttons do. Therefore, we would like to have that functionality in Portal 2 to connect one workflow to multiple buttons. Today, I need to duplicate the workflow to connect one button to one workflow. This adds unnecessary maintenance.
3 votesThe feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.
-
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,…
3 votes -
Include previous entries as suggestions in text input fields
Our goal is to enhance the filterportlet by adding text input fields that offer auto-suggestions in the form of a drop-down list, displaying previous entries. This feature is already available in portal1. Users will experience a more user-friendly and efficient filtering process, as they can conveniently select from past entries suggested by the drop-down list.
3 votes -
Personal Saved Searches in Filter Portlet
Users desire a feature that allows them to save personal search parameters within the Filter Portlet, similar to the functionality provided in IFS. This will enable users to quickly reuse complex filters and searches, enhancing their productivity and efficiency.
3 votes -
Temporary Editable Columns Table Portlet
Currently, modifying values in a table requires the use of Edit Operations. However, there is a need to allow temporary or inline editing of table records without employing Edit Operations. This would enable users to make temporary changes to selected records and then execute a custom workflow using a special button. The workflow's InputTable would include all records, reflecting any changes made.
3 votes -
Persistent Rendering of Results in Scheduler
Currently, when users render a result in the scheduler, then navigate to a different page, and later return to the scheduler page, the previously rendered result is not retained. This behavior contrasts with the functionality found in the filter portlets and the Gantt portlet, where results persist through page navigation.
We propose that the scheduler should retain the rendered results even after navigating to a different page and then returning. This persistent rendering will provide a more consistent user experience and align the scheduler's functionality with other parts of the system.
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.
- Don't see your idea?