12 results found
-
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.
-
Add proper Report Print Layout configuration to Flow
There is a need for proper Report Print Layout configuration. Must allow dynamic sizing of all cells in a table/layout, logo, formatting, conditions etc. Today's HTML is far to rigid. For some use cases the layout is so poor that we can't even use it internally, not to mention externally.
Main need is for PDF, e.g. Word would have been nice, but less important
Ideally there should be an engine on the backside, allowing to be automatically sent on E-mail or printed to predefined print.
For IFS users, similar IFS Report Designer and Print Agent. The built in IFS tools…
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.
-
Return to parameter view from flow6 in Components
New version of parameters for Components in counteractive and in opposition to Lowcode philosophy behind Novacura products. Frankly it looks unfinished, which I hope it is. Moreover in old version you were able to open used Component, which would be even more important now, when they are all dumped in one place and not divided into folders or even show which flows they are assigned to.
2 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.
-
More effortless usage of types with typed output everywhere
Typed variables in Flow is a good thing, but most often it creates a lot of extra work to make it work.
As many of the ideas here suggests, while FlowScript provides a lot of possibilities, it has in its current form made Connect come a bit too far from being Low-Code.To simplify the handling of types it would be of great help to be able to easily make sure that the output variables always are of the wanted and expected type.
For example:
- In a IFS DB Machine Step be able to easily ("low-codish") define types for…1 voteThank 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.
-
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.
-
Revert to an old version of an app or component
I want to be able to automatically revert an old version into to the current working version, similar to Flow 6.
Currently you have to open both the working version and the old version in Designer and manually copy between them.2 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.
-
Better visualization of committed versions in Designer
Immediately after committing a version in Designer, a new working version is created and I can not see the information about the last commit.
2 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.
-
Duplicate an Application in Hub
I want to be able to duplicate applications. If an application using components is duplicated, it should keep the existing references.
2 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.
-
Duplicate a Component in Hub
I want to be able to duplicate both package and organization components. If a component with sub components is duplicated, it should keep the existing references.
2 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.
-
Component workflow parameters as default template for added components
When I add a component to a workflow I want to have all the component parameters as a default input to the component when I add it to a workflow.
As it is now I have to open the component to figure out what parameters to use, copy them and paste them into the component step in the workflow.
1 voteThank 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.
-
When importing an Flow 6 archive (wap files), get the question if you want to auto-commit components without errors
When I'm importing a Flow 6 file with a lot of fragments, I need to open all new components and commit a version before I can use them in my app. This is very time consuming.
1 voteThank 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?