42 results found
-
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.
-
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.
-
"Favorite" function in list and menue selection
In a lot of cases, the customer has a list of eg. 10 Time types, but he mostly only uses work and travel time. It would be great to have a function similar to "default", where you can define favorites that should be on top. Very similar to how we can define them in the inbox.
Workaround is now to sort the list accordingly and solve it in flow script. But this would make life a bit easier.
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.
-
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).
-
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.
-
Human Readable API Key
As a developer, I would like to make my own API key for each integration to make it "human readable".
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.
-
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.
-
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.
-
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.
-
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.
-
Grouping in DataGrids
Just like in Multi/Single Selection Lists in a user step, it would be nice to have the same grouping feature in data grids.
On the attached picture, the grey rows should be the grouping and not a 'normal' row.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.
-
Copy values between user step input types
When changing a input type (say list selection with a menu) values need to be copied manually one by one. This is prone to error.
It would be ideal if comparable data is copied into the correct fields so any changes in the user step items could be done without loss of data
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.
-
Save Default Setting For Freeze Columns In Data Grids
The new ability for users to freeze columns in data grids is very helpful. As a UX designer, it would be very helpful to save the current freeze column settings of a table portlet as the default user settings for the portlet, in the same way we are currently able to save column order and column widths by clicking the "copy from portlet" button in the Data Source Columns section of the portal editor. This would save us the trouble of having to teach every user how to use the freeze column feature and have them set that setting on…
1 voteThis status indicates that the feature request has been rejected. The product team has determined that the feature is not aligned with the product roadmap or does not bring enough value to the platform to justify its implementation. The team should provide feedback on why the request was declined.
-
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.
-
Local Update Capability for Offline Data in Flow
In the current setup of Flow, offline workflows rely on static downloaded data, which cannot be updated locally. This limitation restricts users from making necessary changes to data when offline, potentially impacting productivity and workflow continuity.
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.
-
Dark Mode
PLEASE, add a dark mode theme for Studio! For those of us that use dark mode themes on our computers, Studio's window colors are eye-watering bright. Every other program I have on my computer has a dark mode. This should be a very easy low-cost but high ux-value feature. See attachment for example.
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.
-
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.
-
Enhanced Select Language in real time
When using the flow environment connector to change language, we would like the language to change directly inside the flow, without having to log in or go to settings and change the language.
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.
-
Define width of columns in Table portlet
I'd like to request return of Portal1 functionality: possibility to define column width (see attached screenshot). Lack of it makes designing challenging and less predictable.
1 voteFunctionality already exist; Data source columns - Copy from portlet.
- Don't see your idea?