85 results found
-
Search and asset filtering (Flow Connect Conference 2024)
Search: currently we can search on all items inside the applications section in Hub. If you have any suggestions where else global search should reach, please let us know below!
Assets filtering: currently, only assets can be filtered. Should we add tagging and filtering to other places? Let us know below!
2 votes -
Add JSON sorter functionality to FlowScript (Playground)
Now and again I need to define my data type in FlowScript(by get the definition from IFS - API Explorer and using the Inferred result type functionality in the playground).
Usually I dont need the whole datatype only a few specific KeyPairs but these can sometimes be hard to find as the datatype can be large and not in any kind of order.
So a built in JSON sorter that will take a JSON as input and order the KeyPairs by KeyName or KeyValue (selectable by user) and return with a ordered JSON would be a nice to have feature.…2 votes -
Client Home Experience (Flow User Conference 2024)
In Flow Connect users can access apps quickly through favorites section on the Home screen.
In the future we would like to give users quick one click access to even more apps by opening up new possibilities to customize the client home screen.
Users would be able to see a large number of apps and launch them directly from the home screen without navigating a folder structure.2 votes -
Hub home screen widgets (Flow User Conference 2024)
Allow users to personalise their Home screen with widget-like sections.
2 votes -
Add picture/thumbnails option to buttons
It would be a nice feature if we could show pictures/logos in buttons (and not just unicode characters).
Similarly to the new 'list input with picture' feature.1 vote -
Create Component from part of an App
Typically when developing an App or a set of Apps, you don't exactly know how the Apps will end up and it is difficult to have a clear component strategy from the start.
It would therefore be super helpful to be able to take a part of an app, a sequence of workflow elements, and turn that into a component when needed. Directly from the Designer.
Preferably the function should be smart enough to suggest required input to the component.
When created, the selected sequence of workflow elements should be replaced automatically by the newly created component.
2 votes -
Navigator - lacking placement possibilities
The current Navigator in Connect Designer is lacking in functionality compared to the Classic Studio in regards to placement possibilities.
I always have the Navigator activated and when developing I prioritize canvas area left<->right and therefore I want the Navigator at the top, unfortunately this is not possible in the Connect designer (see picture from Classic Studio).2 votes -
Group Values in Datagrid
The datagrid should have a grouping header to make it easier for end users to find where the exact data they are looking for.
3 votes -
Facilitate debugging of offline flows in flow studio
Currently, the inability to run offline flows in debug mode in Studio complicates development and testing, significantly increasing development time. Resolving this issue soon will streamline the process and improve efficiency
3 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.
-
Get list of apps/users/user groups from hub
It would be great to have a variable or a connector/API I could call and get a list of apps/users/user groups from hub/environments.
(or few extra features such as sending invitation to a user via flow).Like in flow classic, see attached picture.
If updating users are not available due to security reasons, but at least fetching a list of users would be great.
2 votes -
HTML to PDF Connector
HTML to PDF connector is a frequently used connector for designing and generating PDF reports in Flow Classic. Additionally, it's also possible to merge existing pdfs with this connector.
As mentioned in this idea https://ideas.novacura.com/forums/956630-novacura-flow-connect/suggestions/48235034-add-proper-report-print-layout-configuration-to-fl
The design capabilities of the existing connector are somewhat limited/rigid. Ideally, it should be far easier/flexible to design a report layout in connect. Here are some options we can consider for HTML to PDF connector in Flow Connect.Option 1
Can be divided in to two sub sections.
a. Report design as its own step in the designer – The idea of this is to…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.
-
Toggles to Retain Table Row Selection and also Refresh Table in Portal 2
When selecting a row or row(s) in a portlet table and then starting a workflow, the row selected is no longer showing as (gray) selected, making it hard to find what row was just worked with and pulled into the workflow. This may not always pertain to selected rows because some are actually deleted or removed from a portlet table.
However, a good addition would be to allow for tables in Portal 2 to deselect/not deselect the row and to allow the table to automatically update/not update the table after completing or closing a workflow. These are possibly some things…
2 votes -
Customizable Header/Banner Color in Portal 2
In the current setup of Portal 2, users lack the ability to customize the color of the header/banner area, which limits the flexibility in aligning the platform's appearance with corporate branding or user preferences.
Proposed solution is to introduce an option within the Style settings of Portal 2 that allows users to set a distinct color for the header/banner area. This feature should provide an intuitive color picker or the ability to enter hex codes, enabling precise control over the color scheme. This customization capability will enhance the visual appeal of Portal 2 and allow for better branding consistency, improving…
3 votesThis request has been moved to the Flow Connect project and is under development.
-
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…8 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…8 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 -
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
- Don't see your idea?