86 results found
-
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 -
Allow eq and in operator on the same entity
we would like to use both the eq and the in operator on the same entity within a set and if the IN operator consist of only one “value” then the connector will crash and give the following error “Operation failed. Multiple key predicates cannot be specified for the same entity set.“ but if you set more than one “value” it will work as intended.
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.
-
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 -
Datepicker in Filter Portlet Start Date by User's Locale
The starting day of the week in a datepicker in Portal 2 should be influenced by the locale settings. For instance, if en-US, the week start should be Sunday. If sv-SE local is set on the Flow User, then Monday should be the start date.
7 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.
-
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.
43 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?