180 results found
-
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.
-
Navigation workflow
A clear and flexible way to move between user steps in navigation-based apps.
Navigation items replace the fixed buttons at the bottom of the step and allow navigation to other steps in the app. An exit can carry data to the next user step, for example, passing the data of a selected item in a repeated control.8 votesThe feature request has been approved and is now scheduled for development. Our product team has determined that it aligns with our product roadmap and will bring value to our platform. We will keep you updated on its progress.
-
Allow Client messages to display for Flowscript step
Since Flowscript is so powerful now we can put extensive Scripts/loops in the script. If we do that in a userflow we cannot tell the user what's happening, because currently we have no way to add a client message like in other steps. Would be nice if we can get a flowscript function to add messages at different steps of the script execution. Otherwise UX for long running processes will be poor (missing user feedback)
8 votes -
Liquid & XLST Transformers for automations
All ow automations to perform transformations on input and output for webhook triggers so we can support current classic customers in connect
8 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 Logging for Import Errors of OData Connector
Users encounter an issue when changing connectors for a specific flow. Currently, when an operation result indicates a failure, it is challenging to pinpoint which step within the flow has encountered the issue. As a result, users are compelled to manually review each step to identify the failed ones, causing unnecessary delays and frustration.
8 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.
-
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.
8 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.
-
Flexible layouts
User steps need flexible layouts to support dynamic, section based designs to place buttons and controls exactly where you need them.
7 votesWe 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.
-
Web Service Connector in Flow Connect
Support for Web Service Connector in Flow Connect
7 votes -
Push Notifications
Flow Classic has a way to send push notifications via swimlanes. I have never been a fan of using swimlanes, but you could at least use them to send push notifications.
In Flow Connect, I'd like to see Novacura implement a "connector" that could perform the same functionality. The connector could: iterate through a list of users, require a Push Notification message, optionally pass in an app GUID that would "forward" the user once they click on push notification to.
Bonus points if you could use a websocket backend so this could also be implemented in the webclients as well…
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.
-
"Finished" Status Visibility when Offline on Flow Inbox Items
In the current Flow mobile client, when operating in offline mode, users face a restriction where items in the inbox are marked as "Finished" after being acted upon. This status change makes the items inaccessible for further review, although they remain visible in the inbox until the user reconnects to the internet. This behavior limits the ability of users to revisit completed items for verification or review purposes.
Proposed solution is to implement a feature allowing users to toggle the visibility and accessibility of items marked as "Finished" in the inbox while in offline mode. This functionality would enable users…
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 name of Filter button PORTAL 2
Be able to change the name of the Filter button on the Filter portlet.
Example:
7 votes -
Customer brand login (sign in) screen
Current login screen only shows "Flow 6" (not even Novacura is mentioned).
We are gearing up adding external partners to the portal. It both creates suspicion and looks amateurish without our company name, and preferable logo, in the login screen. Enabling us to brand the layout with name, logo and maybe even colour would have made a big impact on the first impression.
7 votes -
Access the User's language as a variable inside the Designer
We want to be able to access the user's client language selection as an environment variable (just like we can access 'userId') inside the Designer.
A common scenario is where we call a third-party system from an App (a "workflow") and need to send it a language code, which returns different results. And we don't (and can't) always call an ERP in every app to fetch the user's language. Hence, we need to be able to make logical decisions within an app/designer based on the "Windows Entra language" of the user currently executing it, or the language the user selects…
6 votes -
Return assertion step when Running Debug in Designer
When debugging and you come to assertion step or script step that prompts an error or information you can not go back like you do if you do not debug. You need to restart. This is super annoying and a bad legacy from how it worked in Classic so please add the same function as it is in the client when you are not debugging.
Thank you!6 votes -
Remember enduser selected settings - Data grid
Remember from before if end user chose card or table layout and open it the next time they log in. Can be extended to other user step elements.
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.
-
Simplify commit and deploy for assets
I'm missing the functionality "Update all to use this version" that exists in Flow classic. Updating assets are currently very time consuming and have an increased risk of human error since we need to manage all dependencies manually (and in the right order).
6 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…
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.
-
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.
-
expand option in web client
In the web client, when a grid is present in the user step, an option appears to expand the UI to the full browser window.
Feature request: always show the expand option for the user's step (regardless of whether there is a grid inside).
Also, make it a designer option to default to expanded or collapsed. Today it seems to remember my choice next time I run the app, but that is probably only for that app and that browser. Be able to control it more generally, both as an admin and as a user.
5 votes -
Direct Client-to-External System calls via OpenID Connect
Enable connect Apps built on Novacura Flow Connect to communicate directly to external systems (e.g., IFS Cloud or other REST-based services) when the external system supports OpenID Connect (OIDC) for client authentication.
This will allow secure, client-only communication, reducing dependency on the Flow Connect Cloud for certain REST API calls and improving performance by eliminating unnecessary round trips through the cloud.Business Value
Performance: Reduce latency by avoiding cloud roundtrip.Scalability: Offload traffic from the Flow Connect cloud.
Security: Leverage OpenID Connect’s standardized authentication and token handling.
Scope
Applicable only for Mobile & windows clients (assuming it will not work…5 votesWe 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.
- Don't see your idea?