Infor M3 CloudSuite
This document guides on installing and configuring Flow applications for Infor M3 CloudSuite.
Installation
System and Version
| System | Version |
|---|---|
Infor M3 CloudSuite | 16.x |
Novacura Flow Server | 6.15.3 |
Novacura Flow Studio | 6.15.5 |
Connectors | Infor M3 REST API, Send Email, Flow Environment |
Establish Flow Connector
The Infor M3 REST API Connector is used to execute transactions in M3 via the M3-API-REST bulk API.
If you already have an Infor M3 REST API connector setup, you can skip this step and use the existing connector instead.
Check Infor M3 REST section to find out how to establish a connection.
Import Environment Properties
Check Import Flow Properties section to find out how to import them into your environment.
Import Workflows
Make sure that you have created all connectors and Flow properties before importing the workflows.
Import workflows in the file "Warehouse Management Cloud.wap."
For details see Import Workflows
Setting Menu Roles
Together with the imported workflows, there will also be a menu. Connect the menu to your roles to make them available for users.
For details see Setting Menu Roles
Publishing Workflows
Within the Server Contents Window, right-click on the Warehouse Management Apps folder and select “Publish.” This process can take a few minutes but once complete, a Publish Successful message will be displayed.
Configuration
All the roles, connectors, and properties of the Warehouse Management solution must be imported before importing workflows.
Environment Properties
Each workflow is equipped with embedded environment properties, which are constant variables that affect the applications' behaviour. These properties can be setup on either global or user level.
As an example, one can default the location that should always be suggested while goods receiving while other can automate and by-pass a user-step as long as all input fields are confirmed.
Full descriptions of the properties can be found under specific workflow, categorised into Infor M3 CloudSuite modules, inside Documentation tab.
To configure the properties, you might use:
System Environment
Use Environment Properties menu inside Users under Environment tab in Novacura Flow studio to configure the environment properties.
Choose a user from the list and tap on Environment Properties drill-down menu to the right.
Select a workflow you would wish to configure.
Adjust the values in the Value column according to the official Documentation.
Workflow Configurator
Use Workflow Configurator to configure the environment properties without login to the Novacura Flow studio.
Select User
Tap on (a) user(s) in the Users list to configure the properties for. You may filter them by their names or group they belong to.
Click MENU to get back to the main menu.
Click NEXT to proceed to Workflow selection.
Select Workflow
Tap on a workflow in the M3 Workflows list to configure their properties.
Click BACK to get back to Select User screen.
Click NEXT to proceed to Set Properties screen.
Set Properties
List is fetched and consolidated from the selected user(s).
If multiple users have been selected and a property's value differs between the users, * MULTI is shown.
Tap on a property in the Environment Properties list to set it.
Use Documentation to set the right values.
Changed value is marked with yellow color.
Two pinned step side menus are available:
Selected Users - shows the users the property changes will be applied for.
Info - provides a quick quide on properties' function and possible values.
Click BACK to get back to Select Workflow screen.
Click SAVE to save the eddited changes.
Managing Multiple Data Capture
All Flow applications for Infor M3 Cloud are equipped with embedded translation engine that decodes the information stored in barcodes (for the moment, only input fields Multi-Data and Calculator function).
The section below explains how the decoded string looks like when barcode reading is properly configured as well as how it's mapped and how to configure it for it's own use in the Flow application.
Components of the decoded barcode string
AIM Identifier
It's a 3 character ISO/IEC identifier, generated by the decoder of a scanner (it's not part of the barcode itself), and gives information about the symbology of the barcode which was scanned.
It consists of the following format:
] = flag character (ASCII 93)
c = code character (defined by AIM for that symbology)
m = modifier character
Example of the AIMs (check for more in the web):
]d2 - GS1 Data Matrix (DM)
]C1 - GS1 Code 128 (UCC/EAN-128)
]C0 - Code 128
]A0 - Code 39
AI (Application Identifier)
It's a prefix that identifies the meaning and format of the following data.
Most commonly, the AIs exist in GS1 barcode types which allows to encode multiple data values in one barcode
In certain cases, AI identifies the number of characters of the data value. Example could be, for instance, SSCC number (always 18) or GTIN (always 14)
Data
Value which could have a fixed or dynamic length
Separator
It's used to separate the values from each other where more than one is included in the barcode
In GS1 concept, separator is placed only when a preceeding data is of a dynamic length. Example could be a lot number and quantity.
It's important that a device is configured to properly translate the separator into a defined character.
Example of the barcodes (decoded strings), where:
Red represents the AIM
Yellow represents the AI
Green represents the translated separator
Black represents the data value
]A0A01-01-01
]C100312345610511001417
]d2024434567000751010230302004/371/3102000150
Decoding barcodes by Flow Apps
There are two global properties that are used to decode a barcode in the application
Infor_M3_AIMs
Used to map barcode's AIM with a defined separator.
By default, '/' (forward slash) is used which should be used in your device in translation.
You can always change the separator sign.
Infor_M3_AIs
Used to map AIM, AIs and Data Values.
Used to identify if the values have fixed length (and as such, do not require separator when any other value is parsed after it).
Used to identfy number of decimals which is decoded and parsed inside input values.
By default, most common AIs from GS1 Code 128 and GS1 Data Matrix have been used.
You can always change the mapped AIMs and AIs. Make sure, you respect the naming standard of the Data Values (in Fields)!
Workflows
This suite of applications consists of the following workflows divided into Infor M3 CloudSuite modules:
Supply Chain Execution
Manufacturing Execution
Sales Management
Procurement
Rental and Maintenance Management
Last updated
