60 results found
-
Trigger Download of Offline Resource from a offline workflow
We are currently implementing offline work task. The user case is that 2 - 4 Work task are executed a day, the data might change every 4 hrs due to IFS PSO.
This means, that the user needs to manually refresh the data set every four hours manually. We can set a time interval for forcing them to do so.
While this works it would helpful help streamline a trigger of a download at the end of the workflow.Meaning, that after the execution of a workflow that uses a data source flow would try to load the Data source…
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Setup a refresh option for inboxes
Sometimes, if a user is already logged into the system, the screens do not refresh automatically. As a result, certain inboxes may not display real-time data.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Remember me checkbox for password in FLOW
Hi! I would really appreciate a 'remember my password' checkbox for the Flow Classic application. This is a huge problem in our organization, as many users avoid using the app due to the complicated passwords they have to fill in when it's time to sign in for a job, for example.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Restore Single-Click Checkbox Functionality
As a user, I would like to check or uncheck a checkbox in a table portlet with a single click, as it was in Portal 1. Currently, in Portal 2, I must double-click the row first and then click again to check/uncheck the checkbox, increasing the interaction from 1 to 3 clicks. This extra effort slows down my workflow and makes the process less efficient. Restoring the single-click functionality would improve usability and streamline the experience.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Possibility to pre-approve devices in Flow Studio
As a user, I would like the ability to pre-approve devices in Flow Studio without manually logging in to each device. By utilizing device identifiers, such as MAC addresses,
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
As a user, I would like to send SMS (Short Message Service) directly from Novacura Flow.
As a user, I would like to send SMS (Short Message Service) directly from Novacura Flow Classic.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We suggest using a REST API with a service like Twilio to send SMS messages via Novacura Flow.
-
Allow users to export/import connector configurations
Currently, users do not have the capability to export or import connector configurations in Flow, which limits the ease of replication and backup of configurations across different environments or instances. This restriction can lead to inefficiencies and increased risk of errors when configurations need to be manually replicated.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Variable to check new web client
Customer would like to have new feature that enable a user to determine which web client is being used
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Zoom functionality in the Document Viewer portlet in Portal2
Add functionality to be able to zoom in and out on documents/images in the Document Viewer portlet in Portal2.
Due to varying size of images a zoom in/out functionality would be very helpful.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Possibility to chose color of input fields (text, list).
In the IOS client, all input fields are in light grey. A customer has expressed that they don't like the light grey color since that gives the impression that the field is not possible to enter data. They would want to turn this off or change the color of the field.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Simplify Input Parameter Management for Workflow Start Task in Novacura Studio
Introduce a feature that enables users to import input parameters directly into the workflow's start task from a JSON file or similar format. This would improve the efficiency and flexibility of parameter management, eliminating the need for manual entry while maintaining the security restrictions on the workflow header, which remains locked from editing by design. The feature ensures a more user-friendly experience without compromising the security protocols in place.
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Double-clicking on a table row is not currently supported for Quick Action
In Portal 1 - it was possible to double click on table row or single click on sprocket to initiate the flow.
In Portal 2 - you need to click directly on triangle (counterpart for sprocket in Portal 1) to initiate the flow, double click does not work. It causes problem on production line, because employee need to navigate and click directly on triangle what it sometimes difficult.
There should be an option to click on table row as it was in Portal 1
4 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Content Adjustment When Locking Side Menu in Portal 2
In the current configuration of Portal 2, locking the side menu causes it to overlay the main content area, leading to obscured or covered content. This can impair user interaction and accessibility, particularly when navigating or viewing crucial interface elements.
Proposed solution is to modify the behavior of the Portal 2 interface so that when the side menu is locked, the main content area automatically adjusts to the right. This adjustment should ensure that no content is obscured by the locked menu. Implementing responsive design principles will allow the content to fluidly reposition and resize, maintaining usability and visibility regardless…
3 votesThe configuration panel has been changed in Flow Connect Portal to improve the user experience.
We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Gaps between next fields in form window in Portal 2 are too big - missing option to reduce gaps
Should be possible to reduce gaps (to set distance between next fields) between next fields in user step in flow triggered from ie. portal 2 or web client
2 votesThe pop-up shows the old web client being executed from the portal. The UI is better in the new client so I would suggest changing to using that one.
We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Select All function in List Multi-Selection Input
Customers using mobile clients on compact, hand-held devices tend to utilize List Multi-Selection Input for its displayed data compression and dynamic fields. What is not available, when comparing to the data grid, is the possibility to mark-to-select-all. It's rather cumbersome to manually select/de-select all the records. We've currently designed a work-around but would appreciate if that is an in-buil feature. Take a look at the attachment.
3 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Custom Device Naming in Studio
Currently, the device management page in Studio uses model numbers as the default for the Name field. This approach is inadequate for environments with multiple devices of the same model, as it creates confusion and inefficiency by not allowing easy identification of individual devices.
Proposed solution is to implement the ability to customize device names in Studio. This feature would allow administrators or users to rename devices according to their specific naming conventions or operational needs, making it easier to identify and manage multiple devices of the same model. This customization should be easily accessible from the device management interface…
2 votesWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
In Flow Connect, there is no longer the need for Device Approval using a standardized IDP with MFA.
-
"Favorite" function in list and menue selection
In a lot of cases, the customer has a list of eg. 10 Time types, but he mostly only uses work and travel time. It would be great to have a function similar to "default", where you can define favorites that should be on top. Very similar to how we can define them in the inbox.
Workaround is now to sort the list accordingly and solve it in flow script. But this would make life a bit easier.
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
-
Permission-Based Visibility for "Settings" Tab in WebNG Sidebar
Currently, in WebNG, all users have visibility to the "Settings" tab on the sidebar, regardless of their permission levels. This one-size-fits-all visibility can lead to potential concerns or confusion among users who do not require access to these settings.
Proposed solution is to Implement a feature that allows the "Settings" tab visibility to be controlled based on user permissions. This would enable administrators to configure the sidebar such that the "Settings" tab is hidden from users who do not have the necessary permissions to modify application settings. This enhancement would improve both the usability and security of WebNG by ensuring…
3 votesAlready exist, see Mobile clients | Flow Classic Help | Flow Help (novacuraflow.com).
-
Custom Width Configuration for Table Columns in Portal 2
In the current version of Portal 2, users are limited to automatic width settings for table columns, lacking the flexibility that was available in Portal 1 where custom width values could be set during the configuration step. This limitation affects the usability and visual layout of tables, especially when dealing with varying content sizes that require more precise column adjustments.
Proposed solution is to reintroduce the capability to set custom widths for table columns in Portal 2, similar to the functionality previously available in Portal 1. This feature should allow users to specify exact width values for each column during…
1 voteFunctionality already exist; Data source columns - Copy from portlet.
-
Human Readable API Key
As a developer, I would like to make my own API key for each integration to make it "human readable".
1 voteWe regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
- Don't see your idea?