Release notes version 6.10 - Novacura Flow Community
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Release notes version 6.10
Novacura Flow® version 6.10
Release date: 2019-09-24
Introduction
In Novacura Flow 6.10 we’ve added the new concept of creating Applications in place. This concept
can be used in many different ways, which will be further developed going forward with Novacura
Flow.
Furthermore, the release is a small start on the journey to a new user experience in Novacura Flow.
Expect more UX notes in future releases!
We have also a few, but nice, improvements in the Flow Studio for our Flow Designers. These will
make your daily life as a Flow Designer a little easier.
System requirements
No changed or new system requirements in this release.
New features
Application package ................................................................................................................................ 3
Client improvements .............................................................................................................................. 4
Android: scanning with Data Wedge on Zebra devices ...................................................................... 4
Windows 10: updated table control ................................................................................................... 4
Windows 10: UI improvements .......................................................................................................... 5
Studio improvements ............................................................................................................................. 5
Better interface for editing long text.................................................................................................. 5
Remember window size ..................................................................................................................... 6
Include domain in AD Sync ................................................................................................................. 6
Do not create a new version if nothing is changed ............................................................................ 6
Force commit message ....................................................................................................................... 7
Workflow improvements ........................................................................................................................ 7
Always enabled exits .......................................................................................................................... 7
App friendly URLs ............................................................................................................................... 8
Performance update .......................................................................................................................... 8
Connectors .............................................................................................................................................. 8
PDF Connector: dynamic page size .................................................................................................... 8
End-of-life notice: Windows CE client .................................................................................................... 9
2
Application package
The application package feature is just what it sounds like; different things put together into one
package to create an application. The purpose of an application package is to be able to package a
complete solution into an easily manageable unit that can be distributed to many different
environments.
A package can be anything from a simple workflow to a complex process solution.
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.
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.
Note! The application package was previously released as a beta, but is in this release a part of the
standard platform. 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.
3
Client improvements
Android: scanning with Data Wedge on Zebra devices
We’ve added many new ways to control scanning on Zebra devices in Flow
version 6.10. Instead of a few select settings to control scanning, we are
now entirely using Zebra’s Data Wedge to control and execute scanning.
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. Please read the
Help for more information.
Please also note that this only applies to Zebra devices. For Honeywell
devices, the old type of settings still apply.
Windows 10: updated table control
Table control has been updated in the Windows 10 client, with a better layout and—most
importantly—improved performance.
Previously, tables would start getting slow when reaching about 100 rows. Now you can handle
thousands of rows in the same table. Still with good performance.
4Windows 10: UI improvements
On the journey to great user experience, we’ve made
some visual improvements to the Windows 10 client.
Text and fonts have been harmonized, lists and grids
have been polished, input fields have been improved. In
general, all parts of a user step have been visually
improved.
Studio improvements
Better interface for editing long text
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, hence making the Studio more user friendly as the data otherwise is only displayed in the
single line field.
To close the dialog box:
• With save:
o Click OK
o Ctrl + Enter
• Without save:
o Click upper right-hand
corner x
o Escape
Available on all Flow Script fields with no translations.
5Remember window size
In Flow Studio the work element window size and position will, as of Flow 6.10, be remembered as a
profile. This mean you will not have to change the window size all the time: you can set it to the
required size and the same size will be used when opening the next element of the same kind.
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.
Please note: the profile is connected to the computer and not the user.
Include domain in AD 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.
Do not create a new version if nothing is changed
When working with workflows, it’s quite common to have a lot of versions as the commit button is
always enabled: 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. This way you can see that
nothing has been changed in the
workflow, and revert the current
edit session and go back to non-
edit without the risk of losing any
changes.
6Force 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. Workflow improvements 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 which are always enabled, regardless of mandatory data being filled in or not. 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. The workflow designer should take care to make sure that an “always enabled” exit is not used when the next step requires mandatory data. 7
App friendly URLs
Previously the URL to start a workflow didn’t work on all
devices.
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.
Performance update
Slow (read: old) devices, plus a lot of data, can lead to
not-so-good performance. 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.
Connectors
PDF Connector: dynamic page size
A "manual width" and "manual height" input box accepting FlowScript has been added to the
connector. If no input is supplied, the selected paper format and orientation will be used. If a
width/height is entered, the resulting pdf page size will use these numbers.
8End-of-life notice: Windows CE client
We started developing our Windows CE client
over a decade ago, and it has been a strong deal
breaker in many cases since then. But technology
is constantly evolving, and Microsoft ended the
support for Windows CE some years ago.
Now it’s time to phase out Windows CE in Flow.
Many former Windows CE customers are moving
to Android devices, with more processing capacity
and more flexible hardware. So, we’re putting a
lot of effort into making the Flow Android client
the prime choice for warehouse and other
barcode-intense environments. With less clients
to develop, we can also focus our efforts where we think they will benefit our customers the most.
However, to make the transition to as smooth as possible for our customers that still use Windows
CE, we will continue to maintain the Windows CE client over the coming two years. For the full
schedule, please see below.
Milestone Description Date effective
End of life Novacura makes a public End-of-life announcement of the September 25, 2019
product.
End of development The last date when new features are developed for the October 31, 2019
product. After this date the product will only be maintained
according to the Maintenance Contract between Novacura
and the customer.
End of sale The last date to order the product. After this date, the December 31, 2019
product is no longer for sale.
End of support The last date to receive any type of support or maintenance September 30, 2021
of the product. After this date the product becomes
obsolete.
If you have any questions regarding the phase out of Windows CE, please contact your Novacura
representative!
Happy flowing!
9You can also read
