241 results found
-
Remove warning messages
we would like to get rid of unnecessary and misleading warning messages when updating flows up the dependency chain
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.
-
Reduce Whitespace Between Checkbox Elements
In our current Flow design, the use of checkboxes creates unnecessary and excessive whitespace, particularly when two checkbox elements are placed close together. This not only affects the aesthetic appearance of the interface but can also impact the usability by requiring additional scrolling and making the layout appear disjointed.
11 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 Branding Capabilities to NG Webclient
At present, the NG Web Client lacks branding capabilities. This limitation restricts the ability to customize the look and feel of the platform, which could affect the user experience and the alignment with the company's branding guidelines.
12 votes -
Data Change Detection and Variable Utilization in Studio User Steps
In the current version of Studio, there is a limitation in detecting data changes made during a User Step. Proposed solution is to enhance Studio to include the capability of detecting any data changes that occur within a User Step. Following this detection, these changes should be easily accessible and usable as variables or properties in subsequent steps of the workflow. This feature would allow users and developers to dynamically adjust the workflow based on user inputs or changes, greatly enhancing the flexibility and functionality of Studio.
2 votes -
Survey/quiz functionality in Flow
The idea is to allow form creation with built in logic, similar to a the tool used when building a form in SurveyMonkey. You could have Interaction Items for multiple choice, true/false, 1-10 scales, short answer, etc. This would allow customers to build surveys, or in the case of Flow academy design the certification exam. An example of the backend logic would be if you had a question "Did you the instructor covered the material in a clear and concise manner?", and the respondent said "No", then a short answer box would appear next asking them to explain what could…
5 votes -
Ad connector needs an overview
The Active Directory connector is not well documented and some of the functions are not working as expected.
Example "Get users for Group" is not fetching the users, in sub/connected groups. And it´s also returning the groups.3 votes -
Export datagrid from workflows as Excel documents
We would like to have the feature to export datagrids in workflows as excel files
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.
-
Make it easier to write "Text"
To present relevant information our users, we type a lot of conditions and display variables practically everywhere. On arrows, in headers, in texts, in prompts and so on. Those fields can not be "opened" like a script-field (Condition To Hide) and when you try to navigate left or right in that field, it jumps around a lot.
Development is overall fast in Flow but those finishing touches that makes a good applikation great takes time.
Can we get the possibility to open these fields up to speed up development?
Thanks!
And I guess you already got a request to make…
2 votes -
Timezone script and setting in Flow
The current Now() function in Flow retrieves the time based on the device's local time. This can lead to inconsistencies for users or workflows operating across different time zones. To improve this, there's a need for advanced time manipulation functions and settings.
Proposed solution is to introduce new functions like Now().utc, allowing users to retrieve time based on specific time zones like UTC. Additionally, integrating a timezone setting for each user in Studio, similar to the existing Language and Locale settings, can ensure consistency and accuracy in workflows, catering to diverse customer needs. This enhancement will grant users greater flexibility…
7 votes -
Evergreen IFS Rest Odata calls
In the IFS Odata Connector we would benefit from first of all identification of all Odata projections used in a a flow and secondly to scan the IFS APIBreakingChanges release files to find out and mark Flow objects if there has been a change in any projection.
There are two different APIBreakingChanges files:
- Between Service Updates within a functional Release
- Between Functional releases.
See attached examples.
8 votes -
Include Italian language in Flow Client and Studio
Currently Swedish, Norwegian, Finnish, German, French, Polish and English are the supported languages in flow similarly we need Italian added as well.
1 vote -
Option to Suppress Subscription Notifications for Disabled Environments
In instances where a TEST environment is disabled while PROD remains subscribed to TEST, users encounter a barrage of subscription notifications, disrupting workflow in PROD Studio. To mitigate this, we propose implementing a feature that provides users with the option to suppress subscription notifications temporarily. This could include a warning prompt with the choice to suppress notifications for the current session or for a customizable duration, such as 24 hours, ensuring uninterrupted productivity during critical work periods.
1 vote -
Enhance the flexibility to Allowing same API Key Names with Different Identifiers
In REST endpoints where some operations require an apiKey in Header and some as a query parameter. Both the query and the header key got the Api key name “apiKey” but they got different names as "apiKey Query" and "apiKey Header". But it is only one of them shows up under Authentication. The fact that it says apiKey(apiKey) shows that it doesn’t recognize that the keys have different names even if the name of the key is the same. Request an enhancement to allow the same API key name with a different identifier name.
3 votes -
Export Logs Directly from OData Connector to CSV or XML
We request the functionality to export logs directly from the OData connector into CSV or XML format. This feature would streamline data management processes by allowing users to extract logs efficiently and in preferred formats, enhancing accessibility and usability of logged information.
1 vote -
Customize rows per page in the datagrid
The ability to show more than 100 rows per page in a datagrid for a Web NG Client is typically controlled by the settings and configuration of the datagrid component.
It was available in the old web client but is not present in the NG web client.
4 votes -
Highlight arrows when stepping through a workflow using breakpoints
When stepping through a workflow with breakpoints, the step that is about to be activated is highlighted. This could be made clearer by instead highlighting the arrow leading to the next step, indicating exactly what is about to happen. This would also show which path has lead to a step with multiple inputs.
4 votes -
Support Push Notifications for Swimlane Handovers with Multiple Languages
We would like to Enable push notifications for Swimlane Handovers to support multiple languages in the text.
8 votes -
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.
-
Resize images to fixed file size
we would like to have enable a feature that allows downsizing to specified size (in MBs). Solution calculates the required resizing factor and use a quality down sampling algorithm (e.g. bicubic) that maintain adequate image quality and get it down to specified file size or just below. from the flow itself.
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.
-
Improved "Auto Focus" Option Behavior
The "Auto Focus " option currently fails to place the cursor in the first input field when it is the second element in a flow after a list box. This results in a non-intuitive user experience, requiring users to navigate through other elements before reaching the input field. We request an enhancement to ensure the cursor is directly placed in the first input field, or at least the list box, when "Auto Focus Input" is enabled, providing a smoother user experience.
8 votes
- Don't see your idea?