48 results found
-
Double-clicking on a table row is not currently supported for Quick Action
In Portal 1 - it was possible to double click on table row or single click on sprocket to initiate the flow.
In Portal 2 - you need to click directly on triangle (counterpart for sprocket in Portal 1) to initiate the flow, double click does not work. It causes problem on production line, because employee need to navigate and click directly on triangle what it sometimes difficult.
There should be an option to click on table row as it was in Portal 1
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.
-
Allow users to export/import connector configurations
Currently, users do not have the capability to export or import connector configurations in Flow, which limits the ease of replication and backup of configurations across different environments or instances. This restriction can lead to inefficiencies and increased risk of errors when configurations need to be manually replicated.
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.
-
Zoom functionality in the Document Viewer portlet in Portal2
Add functionality to be able to zoom in and out on documents/images in the Document Viewer portlet in Portal2.
Due to varying size of images a zoom in/out functionality would be very helpful.
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.
-
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.
-
Possibility to chose color of input fields (text, list).
In the IOS client, all input fields are in light grey. A customer has expressed that they don't like the light grey color since that gives the impression that the field is not possible to enter data. They would want to turn this off or change the color of the field.
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.
-
Content Adjustment When Locking Side Menu in Portal 2
In the current configuration of Portal 2, locking the side menu causes it to overlay the main content area, leading to obscured or covered content. This can impair user interaction and accessibility, particularly when navigating or viewing crucial interface elements.
Proposed solution is to modify the behavior of the Portal 2 interface so that when the side menu is locked, the main content area automatically adjusts to the right. This adjustment should ensure that no content is obscured by the locked menu. Implementing responsive design principles will allow the content to fluidly reposition and resize, maintaining usability and visibility regardless…
3 votesThe configuration panel has been changed in Flow Connect Portal to improve the user experience.
We 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.
-
Select All function in List Multi-Selection Input
Customers using mobile clients on compact, hand-held devices tend to utilize List Multi-Selection Input for its displayed data compression and dynamic fields. What is not available, when comparing to the data grid, is the possibility to mark-to-select-all. It's rather cumbersome to manually select/de-select all the records. We've currently designed a work-around but would appreciate if that is an in-buil feature. Take a look at the attachment.
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.
-
Gaps between next fields in form window in Portal 2 are too big - missing option to reduce gaps
Should be possible to reduce gaps (to set distance between next fields) between next fields in user step in flow triggered from ie. portal 2 or web client
2 votesThe pop-up shows the old web client being executed from the portal. The UI is better in the new client so I would suggest changing to using that one.
We 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.
-
Permission-Based Visibility for "Settings" Tab in WebNG Sidebar
Currently, in WebNG, all users have visibility to the "Settings" tab on the sidebar, regardless of their permission levels. This one-size-fits-all visibility can lead to potential concerns or confusion among users who do not require access to these settings.
Proposed solution is to Implement a feature that allows the "Settings" tab visibility to be controlled based on user permissions. This would enable administrators to configure the sidebar such that the "Settings" tab is hidden from users who do not have the necessary permissions to modify application settings. This enhancement would improve both the usability and security of WebNG by ensuring…
3 votesAlready exist, see Mobile clients | Flow Classic Help | Flow Help (novacuraflow.com).
-
Enhanced Conditional Formatting for Text in Data Tree Portlet
We propose the implementation of advanced conditional formatting options for text within the Data Tree Portlet in Portal 2. Specifically, the ability to customize text appearance (color, style, etc.) based on conditions, such as distinguishing between unassigned and assigned work. This enhancement would significantly improve visual clarity and streamline data interpretation within the Portlet.
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.
-
Ability to edit data in a mobile client like Excel
The ability to edit data in a true table grid format, rather than having a separate screen for each record, refers to a user interface design where data is presented in a tabular structure that resembles a Excel format
23 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.
-
Automatic Retry of Integration
I want to be able to configure an interval and a number of retries that would happen automatically without any user intervention before being considered "failed"
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.
-
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.
-
Password Reset
Allow the user to have a forgot password option at the login screen. This option would allow the user to reset their password for access to the client similarly to how other clients manage forgotten passwords.
16 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.
Please be sure to look at the changes coming in Flow Connect. Passwords will be handled through a standard identity provider, including password resets.
-
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.
-
Custom Width Configuration for Table Columns in Portal 2
In the current version of Portal 2, users are limited to automatic width settings for table columns, lacking the flexibility that was available in Portal 1 where custom width values could be set during the configuration step. This limitation affects the usability and visual layout of tables, especially when dealing with varying content sizes that require more precise column adjustments.
Proposed solution is to reintroduce the capability to set custom widths for table columns in Portal 2, similar to the functionality previously available in Portal 1. This feature should allow users to specify exact width values for each column during…
1 voteFunctionality already exist; Data source columns - Copy from portlet.
-
Bulk Update Failed Executions
Given a set of searched executions, I want to be able to bulk update the executions as handled or retry them all in a few clicks of a button.
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?