57 results found
-
Navigator - lacking placement possibilities
The current Navigator in Connect Designer is lacking in functionality compared to the Classic Studio in regards to placement possibilities.
I always have the Navigator activated and when developing I prioritize canvas area left<->right and therefore I want the Navigator at the top, unfortunately this is not possible in the Connect designer (see picture from Classic Studio).1 vote -
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.
-
Enhanced Targeted Messaging Capabilities in Flow Server
Requesting an expansion of the Flow Server messaging functionality to support targeted communication beyond global message sends to Portal. While acknowledging the utility of global targeting, there's a strong need for more precise messaging options such as targeting specific Flow user IDs, user roles, and user workflows. This enhancement would significantly empower communication in multi-user setups, providing greater flexibility and efficiency in message delivery within the Flow environment.
1 vote -
Dark Mode for WebClient (NG Classic)
Sometimes we like to work at night. All major websites support dark mode at this point in time, why can't Novacura? Here is a "working" example of how it should operate.
1 voteWe are happy to inform you that development work has begun on your requested feature. Our product team has assigned resources and is actively working on implementing it. We will keep you updated on its progress.
-
Change back symbols for arrays to []
In current version of FlosScript {} symbol is used for declaring arrays(Pic A), inside IF and FOR loops(Pic B) and to showcase when Flowscript will be used(Pic C).
I think, using same symbol for everything makes it's purpose unclear and can cause unnecessary confusion. Was change from [] to {} for array declaration cause by some real need?
1 vote -
Enable listener for Record Portlet
Please enable the posibility to listen to the Record Portlet. We offer the possiblity to change data via Workflow, but any saved changes will never trigger an update of other portal objects. This needs to be done manually. I have encountered this in at least 4 projects now where this feature would have been needed.
1 vote -
Encrypt System Variables
In order to use secure values in system variables, it would be good to encrypt the values from other admin's visibility.
Currently, in our integration to Expensify the ID and Secret are handled in the body of the payload. In order to ease maintenance of these values, you could use System Values. However, it would mean that the secret would be visible to all with Admin privileges. See example Expensify API request below:
curl -X POST 'https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations' \
-d 'requestJobDescription={
"type":"file",
"credentials":{
"partnerUserID":"REPLACE",
"partnerUserSecret":"REPLACE"
},
"onReceive":{
"immediateResponse":["returnRandomFileName"]
},
"inputSettings":{
"type":"combinedReportData",
"filters":{
"reportIDList": "R00bCluvcO4T,R006AseGxMka"
}…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.
-
Add static tooltips in Charts
As in topic. Sometimes there is big difference in columns/bars in chart and it,s hard to even notice smaller values. AS in attached example first column has value around 150 remaining two are 1 and 2. I can't even get value for smallest one while trying to hoover over it. Adding Static tooltip, as it was in Portal1 would help with such cases.
1 vote -
Container in portal2
When we merge 2 portlets into a container there is no provision to have a button for containerized portlets.
There are requirements where in you need to have 2 datasources for 2 portlets but need to have a button wokflow which can be used for both or any of the portlets.1 vote -
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.
-
Explicitly set the type of values fetched in SQL machine steps
I want to be able to define the data types for my SQL query so that the Designer knows the types I can work with when designing my apps and components.
1 vote -
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.
-
Auto-Centering of Portal 2 Scheduler Based on Current Time
In the Portal 2 environment, users must manually adjust the scheduler's view daily to align it with the current time. This manual process becomes inefficient for users, especially in environments where the scheduler is in a read-only state across all departments.
Proposed solution is to implement an auto-centering feature for the Portal 2 scheduler that automatically aligns the view with the current time upon refresh. This ensures that users always have a centered view of their schedule relative to the present time without manual adjustments, enhancing user experience and operational efficiency.
1 vote -
Improved List of Values Display in Portal2 with Filtered Inputs
In Portal2, when using a List of Values (LoV) tied to a table column, there seems to be an issue displaying the data if the LoV's data source is a Flow with an input filter. The data is displayed if no input filter is considered, but it does not show up when inputs are taken from Portal.
Proposed solution is to address the inconsistency by ensuring that the List of Values in Portal2 displays data correctly even when the LoV uses a Flow with input filters from Portal. It's crucial to provide consistent visibility and accessibility of data irrespective of…
1 vote -
Enable scrolling of the page and portlet windows when 'Draggable' is enabled on Table Portlet
The users request an improvement in the table portlet's behavior when grabbing a row in 'draggable' mode. Specifically, they desire the page window to scroll up, down, left, or right automatically when they hold the row near the border. Additionally, they expect the same behavior to be applicable within other portlets. For example, when dragging a row from a table Portlet into a Scheduler Portlet, the current page stays stagnant. This means that if the Scheduler Portlet is not on the exact date and time to drop the table row into, the user needs to start over, ensuring that they…
1 vote -
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 -
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
- Don't see your idea?