42 results found
-
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.
-
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.
-
Introduce FlowScript in REST Service connector parameters
it would be highly advantageous to introduce the ability to execute this script as an option within a REST Service call. Currently, the REST Service connector parameters only offer limited choices such as "Variable," "Constant," and "Not Set." By incorporating this script execution as an alternative, it would empower users to execute more intricate operations within the flow, thereby providing greater flexibility and customization to the process.
11 votesWe regret to inform you that this feature request has been declined in Flow Classic track. After careful consideration, our product team has concluded that it does not align with the established product roadmap for Flow Classic, nor does it offer sufficient value to justify its implementation. We appreciate the feedback you have provided and remain open to hearing about future ideas.
That being said, we encourage you to explore the recent enhancements made to the REST connector in Flow Connect. The REST connector within Flow Connect already accommodates this particular request. Additionally, we are actively seeking beta customers for Flow Connect. If you are interested, please reach out to your local account manager for further details.
-
Descriptive Error details in Web Service connector logs
We would like to get more information on the error when an error is thrown by the remote system when communicating through the web service connector. Sometimes there is not much information available to the user or developer for that part. It would be great if this error in full could be written to the error log file which would make debugging this a lot easier. And of course also present the correct error message in full to the user.
10 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.
-
Option to Read multiple documents in portal via Document viewer
We would like to have new feature add to document viewer in order to view multiple pdf(s) in portal. Currently, when one clicks the table row (with a listener attached), they need to view particular line related Documents.
9 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.
-
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.
-
Null Date Inputs in IFS OData Connector
Currently, in the IFS OData connector, date fields can be modified but not cleared (set to null), although it's possible to clear these fields directly in IFS. Converting to a custom operation allows null inputs but is not a desired solution due to its complexity.
We propose to add functionality in the IFS OData connector to allow null inputs for date fields. This would align with the behavior seen directly in IFS and would enhance the versatility of data manipulation in the OData connector.
7 votesWe regret to inform you that this feature request has been declined in Flow Classic track. After careful consideration, our product team has concluded that it does not align with the established product roadmap for Flow Classic, nor does it offer sufficient value to justify its implementation. We appreciate the feedback you have provided and remain open to hearing about future ideas.
That being said, we encourage you to explore the recent enhancements made to the REST connector in Flow Connect. The REST connector within Flow Connect already accommodates this particular request. Additionally, we are actively seeking beta customers for Flow Connect. If you are interested, please reach out to your local account manager for further details.
-
Customizable Filename for Document Viewer Downloads
Currently, when utilizing the Download functionality within the document viewer, the downloaded PDF file is named "undefined.pdf." This naming convention lacks user-friendliness and can lead to confusion among our users.
We kindly request the implementation of a customizable filename option for the downloaded PDFs. This feature would allow us to set a more descriptive and meaningful filename, relevant to the content or context of the document being viewed. For example, users could have the ability to name the file based on the document title, date, or any other relevant data.
The ability to customize the filename would significantly improve the…
7 votesThe "undefined.pdf" bug fix was compeleted in 2022. Please look to upgrade if you have not already.
-
Enhanced Navigation in List Multi-Selection Input
we would like to explore better alternatives as some users find the List Multi-Selection Input confusing on mobile and tablet devices. On computers, users can easily select and close the menu using the mouse. However, on mobile or tablet, the process involves opening the menu as a "new page," making selections, and confirming choices using the back button as the back button's current usage is unfamiliar and confusing to users. Perhaps adding a dedicated button for confirmation or a similar approach would improve the user experience. For a clearer understanding of the problem, refer to the provided pictures (pc 1-3…
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.
-
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.
-
Simplifying Workflow Conversion
Frequently, I design a workflow and realize the need to switch it from a User Flow to a Fragment, either due to oversight during creation or the newfound requirement for reusability. The current process of converting the workflow in the studio is rather cumbersome. Although I've managed to export the Flow, manually tweak the XML, and then re-import it to achieve a Fragment, it strikes me that this procedure could be streamlined. Perhaps a more user-friendly approach would involve incorporating a 'Convert To' option, accessible through a simple right-click within the server explorer, offering a range of flow type transformations
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.
-
Simplified "For Each" Loop Element for Dataset Processing
Currently, when looping through a dataset/table, users need to create a copy of it, check if it is empty, fetch one row at a time, process it, and then exclude that row before continuing the loop. This process involves unnecessary steps and can be time-consuming. Therefore, I propose the implementation of an easy-to-use "For Each" loop element. This element should allow users to set the dataset and define the assignment of each row, simplifying the iteration process. It should automatically handle row traversal without requiring additional checks or dataset manipulation. This feature would enhance productivity by streamlining dataset processing and…
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.
-
Adding Restrictions for Date Inputs
When utilizing a date input field, the absence of input restrictions compels us to verify the entered information at a later stage, leading to a suboptimal user experience. However, by implementing limitations on date inputs, we can proactively uphold our business rules within the user interaction itself, rather than addressing them in subsequent stages. This not only enhances user interface quality but also streamlines the entire process.
5 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.
-
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.
-
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).
-
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.
-
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.
-
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.
- Don't see your idea?