70 results found
-
Customized Button Placement in Clients
The suggested improvements to the current system involve enhancing the user experience and customization options in the graphical user interface (GUI). The proposal includes two main features:
Customizable Button Placement: The users express a strong interest in having the freedom to choose where the buttons (outputs) from user steps appear in the GUI. Currently, the system only allows the selection of priority, but the buttons always appear in the bottom right corner of the user step. The proposal seeks to provide flexibility, allowing users to position the buttons according to their preference, resulting in a more intuitive and user-friendly interface.
…
22 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.
-
Custom "Edit Operation" button labels
Currently, to have editable columns in a table, 'Edit Operations' must be enabled. This approach allows only the usage of pre-set buttons named "Update/Delete/Create". However, in some contexts, these pre-set names are not suitable or meaningful to the end-users.
We suggest allowing customization of the button names in 'Edit Operations'. This feature will allow users to rename the "Update/Delete/Create" buttons to terms that better fit their specific use cases.
1 vote -
Custom Timeline in Scheduler
Currently, the Scheduler lacks the ability to create a custom timeline, making it difficult for users to plan orders starting in one week/month and ending in the next week/month. This lack of functionality can lead to a lot of clicking and scrolling and difficulty in visualizing the total order.
We propose adding a feature that allows users to define a custom timeline in the Scheduler. For example, this could be a timeline starting from 'today + 1 week' or other similar custom periods.
This will allow users to have a more efficient and streamlined planning process, minimizing the need for…
4 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.
-
FlowScript Code Formatter
Currently, Flow Script does not offer any assistance in code formatting, which could lead to less readable and harder to manage scripts.
We suggest the introduction of a "Code Formatter" button in Flow Script. This button would apply some basic formatting rules, such as indentation, to make scripts more readable and easier to maintain. Even though users may request further customization options, having basic formatting support will be a significant improvement over the current situation.
9 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.
-
Both date & time set with "Today" button in Filter Portlet
Currently Portal 2 datepicker has separate date and time pickers. This feature request would allow users to set both date and time by pressing the "Today" button.
1 vote -
Configure font color, size or bold/italics in Portal 2 Scheduler
We would like to have an option to configure font color, size or bold/italics in Portal 2 Scheduler.
9 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.
-
Enhanced Flow Variable Update Capability Within Scripts
A feature enhancement that allows users to update the values of flow variables from outside of a script. Currently, when working with variables X and Y, executing a script step only allows for returning a value to overwrite one of them, or utilizing a complex workaround with a record to update both variables. We propose the addition of a simple syntax, such as ":flow.X = "something";" within the script, where the ":flow" prefix defines the scope of the variable being modified. This improvement will streamline the process of updating variables, eliminating the need for additional steps and making script operations…
6 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.
-
To make the Database connection option optional for HTML portlets in Portal 2
HTML portlets serve as a repository for exhibiting non-dynamic content in portal 1. However, in portal 2, it requires a select query and a database connection.
This limitation results in a less intuitive experience when working with them.
It would be greatly beneficial to restore this functionality in portal 2 for client applications, allowing for a smoother transition and enhanced user experience.2 votes -
Workflow Datasource Ordering in Portal
When listing workflows for data source in e.g. a table Portlet, the ordering is appearing randomly. Ideally, a selected workflow should be on top and the remaining preferably ordered alphabetically by name given in Studio.
2 votes -
Change Font, Colors, and Alignment within User Elements
Within a User Element in a User Step, I would like to be able to change the font, front size, font color, alignment, bold, italics, and more so that I can make more visually appealing workflows.
41 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?