234 results found
-
Enhanced Marketplace app attachments
Two things to report regarding attachments when creating an Expense Report.
The attachment type is set to MEDIA, that limits us to certain file types. Sometimes the user wants to add a PDF document, but that is not possible.
One of the final steps in the app is to attach a document (if that exists) to the expense row that was just created. Here step “Get Expense Details” fetches all expense rows, and the next assignment step fetches the first row {FirstOrEmpty(ExpenseDetailResult.Results)}. This first row is then used to create a keyref in the next step. The problem is that…
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.
-
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.
-
Consistent Link Widths: Improve Visual Harmony in NG WebClient
We propose a feature enhancement to address the inconsistency in link widths within the NG WebClient. Currently, varying link widths create a visual disparity, particularly when compared to mobile clients. To enhance the overall aesthetics and maintain visual coherence across platforms, we request the implementation of a feature that ensures consistent link widths in the NG WebClient. This adjustment will contribute to a more polished and uniform user interface, providing a seamless experience for users across different devices.
1 vote -
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 -
Enhanced Variable Management in Debug Mode (Test Bench)
When debugging workflows in the Studio with a high number of variables (200+), it is time-consuming and challenging to locate specific variables. Currently, variables are not presented in any particular order and cannot be sorted.
We propose to introduce the following enhancements for variable management in debug mode:
- Ability to sort variables by name and type.
- Search functionality to find specific variables (or part of a variable name).
- Option to monitor specific variables - a feature where the user can mark specific variables which will always be at the top of the list.
These features will significantly improve the efficiency…
9 votes -
Ability to ignore non-critical (yellow) Flow errors
This is related to ideas https://ideas.novacura.com/forums/953926-novacura-flow-classic/suggestions/47158924-change-sql-validations-in-studio and https://ideas.novacura.com/forums/953926-novacura-flow-classic/suggestions/47473418-update-the-version-of-the-sqlparser. Sometimes Flow Studio will flag steps with a yellow "non-critical" error because Flow can't parse the code correctly. Most often I see this in SQL Server machine steps, but it can happen in other kinds of connectors too. While it would of course be lovely if the parser could be better, I think it will be hard to make it 100% correct. That's why I would like a RMB option to Ignore a yellow error on a machine step, sort of like when I want a word processor to stop flagging…
4 votes -
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.
9 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 -
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 -
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 -
Offline WADACO (Warehouse Management) Functionality
IFS WADACO application and Novacura WM application does not work in offline mode.
It will be great if Novacura could include some of the WM apps with offline functionality.
Eg: Certain WADACO transactions such as Counting, Moving, Execute transport tasks etc.1 vote -
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.
-
FlowScript Code Formatter
Currently, Flow Script does not offer any assistance in code formatting, which could lead to less readable and harder to manage scripts.
We suggest the introduction of a "Code Formatter" button in Flow Script. This button would apply some basic formatting rules, such as indentation, to make scripts more readable and easier to maintain. Even though users may request further customization options, having basic formatting support will be a significant improvement over the current situation.
9 votes -
Checkbox Selection in Data Grid on Flow Mobile Clients
Users of the Flow mobile application face a limitation when interacting with data grids that contain checkboxes. Currently, to select a checkbox within a data grid column, users must navigate into each individual row and then set the checkbox. This process is seen as cumbersome and inefficient, especially for tasks requiring multiple selections across several rows.
The proposed solution is to introduce the functionality that allows users to directly select checkboxes from the main view of the data grid, without the need to navigate into each row. This enhancement should apply to all Flow mobile clients, streamlining tasks that involve…
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?