70 results found
-
Enabling online/offline versatility
Our framework is currently stringent in how to work offline: you download your sources (like in the morning), start working (deliberately offline) and your transactions are synced as soon as you are back online.
In many circumstances Flow users in service do not know whether they will have internet while working though and they work offline foregoing on many advantages of being online.
Ideally, we would have a variable available in our start variables (like DeviceId and ClientType) so that in the flows we can take different paths depending on whether the user has internet or not - analog to…6 votes -
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.
-
Variable Types - Table
Flow 6.15 and the earliest versions offer a possibility to choose a type of property which is either text or table. The latter ensures that more data can be stored under one property.
Infor M3 Labs uses that funcitonality to store a dynamic data that affects the way how each and every workflow behaves, ie. the prompt proposals, buttons and input fields, automation of user steps are just a few to mention.
In other words, the end-users, who more often than not are function-oriented, can utlize the table to adjust the values in the table.
By that, workflows can be…5 votes -
Tablet and Mobile Optimization for Portal 2
Portal 2's current interface and interaction design do not cater effectively to tablet and mobile devices, presenting challenges for users on these platforms due to the lack of touch-friendly navigation and responsiveness.
The enhancement focuses on redesigning Portal 2 to be fully optimized for tablet and mobile devices. This entails revising the user interface to ensure that all elements are easily navigable via touch interactions. Key considerations include increasing button sizes, ensuring that dropdown menus and other interactive elements are easily selectable, and implementing responsive design principles so that the layout adjusts dynamically to fit various screen sizes and orientations.…
25 votes -
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.
-
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?
2 votes -
Can items remain highlighted once clicked on them?
Is there any way that when adding records for an employee, the name stays highlighted. After each record I enter, I have to re-click on the name to enter more or even see anything pertaining to the employee.
the user wants the name to be able to remain highlighted while they are doing processes for named user until the processes are completed instead of having to click on the user name each time to create additional processes for them.
2 votes -
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.
-
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 -
Customizable Spacing and Border Controls for KPI Cards in Portal 2
Requesting the addition of customizable spacing options between KPI cards in Portal 2. Currently, a gray KPI card is being utilized as a workaround for creating space between blue and green KPI cards. However, there is an inability to disable the border of this empty card. We propose the implementation of features that allow users to control spacing between KPI cards and provide the option to toggle borders on or off for improved layout flexibility.
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.
-
Better Offline Data Caching
Today, a customer can download offline data. But if the app crashes, or the user in the field (who is offline) makes changes and then app crashes or they quit out by accident, its confusing to the user as to what has been completed. To the user, it feels like the data has been lost.
An example, lets say I have an offline flow which downloads 10 records in a table. While offline, I add 2 new records to that table, and go to the next step. If the app crashes when the app reopens, and the flow is rerun,…
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.
-
Allow word wrapping on scheduler cards.
Allow word wrapping on scheduler cards. If my label goes too far right, it just disappears.
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.
-
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 -
Change name of Filter button PORTAL 2
Be able to change the name of the Filter button on the Filter portlet.
Example:
7 votes -
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.
-
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.
- Don't see your idea?