We're excited to announce the official launch of a great new feature: the application package! Read on for all the details.
Announcing: the application package!
The application package feature is just what it sounds like; different things put together into one package to create an application.
A package consists of everything needed to run the application: workflows, portal tabs, connectors, menus, roles and properties. All of these things exist inside the package, so that the package can live its own life, without dependencies to the outer world. This is to make sure that you have everything that you need when you move application packages between environments.
Examples of application packages:
- Warehouse logistics
- Purchase to pay
- Work order execution
- Manufacturing execution system
Application packages can be locked with a password and copyrighted in order to protect the author’s intellectual property when the package is distributed between companies.
Please note: the application package was previously released as a beta. If you have created application packages using the beta version, you will need to delete these beta packages before you can create any new application packages.
New user type: AppUser
With the application package comes also a new type of licensed user; the AppUser. This type of user has only access to licensed application packages, which offers more flexible pricing for users who only want/need access to one (or a few) application packages.
Full users will still have access to everything, including application packages.
As of Flow version 6.10, we're using Zebra’s Data Wedge to control and execute scanning for all Zebra devices. This means that you can use all of Zebra’s features to decode barcodes, manage scanning actions and even manipulate the scanned data.
Important note: when upgrading to 6.10 on Zebra devices, you will have to update your scanning settings to make the scanning work. This only applies to Zebra devices. For Honeywell devices, the old settings still apply.
Windows 10 client
Table control has been updated in the Windows 10 client. Previously, tables would start getting slow when reaching about 100 rows. Now you can handle thousands of rows in the same table.
We’ve also made some visual improvements to the Windows 10 client. Text and fonts have been harmonized, lists and grids have been polished and input fields have been improved.
In Flow 6.10 we have added a dialog box which you can use when entering data in a Flow Script field. You can open the dialog box by pressing F11. From there you can add, edit and format data in the dialog box.
In Flow Studio the work element window size and position can now be remembered as a profile. Box window size and dividers are saved when:
- Resizing and clicking save/cancel/exit on the user step
- Logging out
When a user uninstalls and installs a new version of Flow, the user step size will not be remembered.
Azure directory sync
Previously, the Azure active directory sync removed everything after the @-sign. For customers with multiple domains, this caused problems since some users would get the same user id. This new feature gives you the option to run the sync with or without including the domain.
No new version if no changes
When working with workflows, a version is created at commit regardless of whether changes have been made to the workflow or not. This new feature disables the workflow edit button until changes has been made to the workflow.
Force commit message
It’s now possible to configure the workflow metadata to force commit message. This way admin can decide if comments must be added when committing a workflow or if it should be optional.
If force commit is true, the Commit button is disabled until a comment has been made when committing.
In Flow 6.10, we’ve made changes to the way data is managed in a workflow. The result of this optimization is that operations with a lot of data can be up to 10 times faster! The slower the device and the more data, the more difference you will notice.
Always enabled exits
Sometimes a user wants to exit a step without filling in all mandatory data. This feature gives the workflow designer the option to add exits throughout the workflow. If data is entered in the user step where an “always enabled” exit is used, the data is not cleared but can be used later in the workflow.
App friendly URLs
Flow 6.10 now has two different types of URL that should cover all cases:
Generate App URL: to be used as the default URL to workflows. Starts the default app for Novacura Flow, installed on the device.
Generate Web Link: to be used as a fallback link (“copy this link into your web browser”) if the above link does not work.
PDF connector: dynamic page size
We've added a manual width and manual height input box accepting FlowScript to the connector. If a width/height is entered, the resulting pdf page size will use these numbers.