Infor CloudSuite Industrial

Configuration Guide for Infor

Operating Service

Release 10.x
Copyright © 2020 Infor

Important Notices
The material contained in this publication (including any supplementary information) constitutes and
contains confidential and proprietary information of Infor.
By gaining access to the attached, you acknowledge and agree that the material (including any
modification, translation or adaptation of the material) and all copyright, trade secrets and all other
right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or
interest in the material (including any modification, translation or adaptation of the material) by virtue
of your review thereof other than the non-exclusive right to use the material solely in connection with
and the furtherance of your license and use of software made available to your company from Infor
pursuant to a separate agreement, the terms of which separate agreement shall govern your use of
this material and all supplemental related materials ("Purpose").
In addition, by accessing the enclosed material, you acknowledge and agree that you are required to
maintain such material in strict confidence and that your use of such material is limited to the Purpose
described above. Although Infor has taken due care to ensure that the material included in this publication
is accurate and complete, Infor cannot warrant that the information contained in this publication is
complete, does not contain typographical or other errors, or will meet your specific requirements. As
such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss
or damage to any person or entity which is caused by or relates to errors or omissions in this publication
(including any supplementary information), whether such errors or omissions result from negligence,
accident or any other cause.
Without limitation, U.S. export control laws and other applicable export and import laws govern your
use of this material and you will neither export or re-export, directly or indirectly, this material nor any
related materials or supplemental information in violation of such laws, or use such materials for any
purpose prohibited by such laws.

Trademark Acknowledgements
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or
related affiliates and subsidiaries. All rights reserved. All other company, product, trade or service
names referenced may be registered trademarks or trademarks of their respective owners.
Publication Information
Release: Infor Cloudsuite Business (Industrial) 10.x
Publication Date: August 6, 2020
Document code: csbi_10.x_csbixicg_op_csind_en-us
 Contents

Contents

About this guide.................................................................................................................................7

Intended audience.............................................................................................................................7
Contacting Infor.................................................................................................................................7
Chapter 1: Requirements...................................................................................................................8
Required products.............................................................................................................................8
Required information.........................................................................................................................8
Chapter 2: Configuration checklist.................................................................................................10

Chapter 3: Overview.........................................................................................................................12
Infor OS...........................................................................................................................................12
Infor Ming.le.................................................................................................................................12
Infor ION......................................................................................................................................13
Infor ION Grid...............................................................................................................................14
Infor Document Management.......................................................................................................14
Integration with other products in the CloudSuite............................................................................14
BOD integrations..........................................................................................................................15
Point to point integrations.............................................................................................................15
Concepts and definitions specific to this configuration....................................................................16
Tenant ID......................................................................................................................................16
Accounting entity..........................................................................................................................16
Location.......................................................................................................................................16
Logical ID.....................................................................................................................................16
Chapter 4: Configuring your browser.............................................................................................18
Allowing popups for browsers..........................................................................................................18
Avoiding multiple connections in a browser.....................................................................................18
Chapter 5: Configuring security......................................................................................................19
Setting up your application to use Single Sign On..........................................................................19

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 3

 Contents

Installing Windows Identity Foundation........................................................................................19

Setting up the Web client with AD FS access..............................................................................19
Creating a relying party trust for Infor Ming.le and the ERP........................................................20
Configuring Active Directory authentication groups.....................................................................21
Importing a security certificate for each user computer...............................................................21
Single Sign Out...............................................................................................................................22
Setting the timeout option for all applications...............................................................................22
Chapter 6: Adding your application in Infor Ming.le.....................................................................23

Chapter 7: Configuring your application and ION to send and receive BODs............................25
Configuring your application for ION...............................................................................................25
Verifying that the SQL Server no count option is not set.............................................................25
Setting master data to standardized values.................................................................................25
Setting up a default configuration for each site............................................................................26
Setting up BOD replication and logical IDs, tenants, accounting entities, and locations in the
ERP..............................................................................................................................................26
Setting up information that will flow to other products..................................................................29
Verifying BOD replication.............................................................................................................29
Connecting the ERP to ION............................................................................................................29
Understanding connection points and data flows........................................................................29
Using the Enterprise Connector in a hybrid environment............................................................30
Creating an ERP connection point...............................................................................................30
Defining BODs for the ERP connection point...............................................................................31
Using the Cloud Connector to connect to cloud applications..........................................................32
Configuring document flows............................................................................................................32
Setting up a document flow to Infor Ming.le to pass user and role information............................32
Configuring other data flows between applications......................................................................33
Publishing BODs.............................................................................................................................34
Starting products and services....................................................................................................34
Initial data load.............................................................................................................................34
BOD dependencies......................................................................................................................35
Turning off BOD replication to reduce traffic....................................................................................36
Verifying the ION configuration........................................................................................................37
Verifying that BODs are published...............................................................................................37
Verifying that ION receives data...................................................................................................38
Verifying the data flow between applications...............................................................................38

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 4

 Contents

Chapter 8: Configuring user access to your application through Infor Ming.le.........................39

Users and roles...............................................................................................................................39
How Infor Ming.le users and roles work with ERP users and groups..........................................39
Configuring user access to the ERP through Infor Ming.le..........................................................40
Configuring users for separately licensed modules.....................................................................44
Configuring additional system administrator access to applications through Infor Ming.le..........44
Configuring power user access to Infor OS applications.............................................................45
Configuring additional system administrator access to the ERP through Infor Ming.le................45
Setting up additional roles or groups...........................................................................................46
Automatic login and selecting configurations...............................................................................46
About accounting entities................................................................................................................47
About locations................................................................................................................................47
Verifying user access......................................................................................................................47
Setting up distribution groups..........................................................................................................48
Service accounts.............................................................................................................................48
Chapter 9: Configuring ION APIs for your product........................................................................49
Using ION APIs to consume Mongoose REST services.................................................................49
Using Mongoose to consume APIs from other applications through ION APIs...............................50
Chapter 10: Configuring workflows and ION messages for the ERP..........................................51
ION messages.................................................................................................................................51
About alerts sent from the ERP to Infor Ming.le..............................................................................52
Configuring applications to process alerts......................................................................................55
Configuring applications to process workflows for tasks and notifications......................................56
Other workflow options....................................................................................................................56
Chapter 11: Verifying drillbacks to the ERP through Infor Ming.le..............................................58
Available drillbacks..........................................................................................................................58
Loading the BODs that are used in drillbacks.................................................................................59
Verifying a drillback.........................................................................................................................59
Chapter 12: Configuring context apps and utility apps that are used with the ERP..................61
Understanding business context messages....................................................................................61
Process default settings that allow context messages to be sent................................................62
Supported business context messages.......................................................................................62
Context and utility apps that work with the ERP..............................................................................63
Enabling a context or utility app for the ERP................................................................................63

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 5

 Contents

Authorizing users to display critical numbers in widgets..............................................................64

Chapter 13: Verifying Homepages for the ERP..............................................................................65
Verifying the homepage and widget content...................................................................................65
Modifying permissions for standard pages......................................................................................66
Chapter 14: Configuring Infor Document Management to work with the ERP...........................67
About the Document Management integration................................................................................67
Prerequisites for IDM integration.....................................................................................................68
Setting up the IDM connection in the ERP......................................................................................69
Importing ERP-related definitions into Document Management.....................................................70
Activating the IDM workflows in the ERP........................................................................................71
Verifying the configuration for IDM workflows..................................................................................71
Configuring Infor Document Capture with Infor OS.........................................................................72
Other document management options............................................................................................72
Appendix A: User and role BOD usage..........................................................................................73
BODs that send roles (authorization groups) from the ERP to Infor Ming.le...................................73
Person IDs.......................................................................................................................................74
Person IDs in Infor Ming.le...........................................................................................................74
Sending the Person ID from the ERP to Infor Ming.le..................................................................74
BODs that send user information from Infor Ming.le to the ERP.....................................................74
BODs that send user information from the ERP to Infor Ming.le.....................................................75
CloudSuite Portals users.............................................................................................................76
Adding users in the ERP.................................................................................................................76
Appendix B: Troubleshooting..........................................................................................................78
Data is not flowing properly.............................................................................................................78
BOD information needs to be purged..............................................................................................79
ERP help is not working..................................................................................................................79
Appendix C: Business events that generate outbound BODs.....................................................80

Appendix D: Inbound BOD usage...................................................................................................91

Appendix E: BODs used in integrations with this application.....................................................93

Outbound BODs from the ERP to integrated applications...............................................................93
Inbound BODs to the ERP from integrated applications.................................................................96
Appendix F: Updating configuration of existing environment.....................................................98

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 6

 About this guide

About this guide

This guide provides configuration and implementation information for the integration of Infor CloudSuite
Industrial with Infor Operating Service (OS).
Use this guide in either of these cases:
• CloudSuite Industrial and Infor OS are both installed on-premises
• CloudSuite Industrial is installed on-premises and Infor OS is in the cloud.

Intended audience
This guide is intended for the system administrator or consultant who configures CloudSuite Industrial
for use with Infor OS.

Contacting Infor
If you have questions about Infor products, go to Infor Concierge at https://concierge.infor.com/ and
create a support incident.
The latest documentation is available from docs.infor.com or from the Infor Support Portal. To access
documentation on the Infor Support Portal, select Search > Browse Documentation. We recommend
that you check this portal periodically for updated documentation.
If you have comments about Infor documentation, contact [email protected].

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 7

 Requirements

Chapter 1: Requirements

Ensure that all requirements are met.

Required products
Ensure that you have installed and configured these products:
• CloudSuite Industrial 10.x
See the Infor CloudSuite Industrial Installation Guide.
• Infor Operating Service, latest version
The installation of Infor OS includes these products: Infor Ming.le, Infor ION, Infor Document
Management, ION Grid, and ION API.
• If you are using Infor OS in the Cloud, with CloudSuite Industrial on-premises, the Infor Cloud
team provisions Infor OS and its components for you. Use the instructions in this guide to
configure Infor OS to communicate with your on-premises application through the Enterprise
Connector. See the Infor ION Desk User Guide - Cloud Edition for the Enterprise Connector
server prerequisites.
• If Infor OS is installed on-premises, the server where you install Infor OS must be able to
connect to the servers where you install CloudSuite Industrial and other BOD-enabled products.
ADFS is used for Single Sign On authentication with Infor OS. SAML Session Provider, the
default provider for ADFS, is installed with Infor OS and must be configured correctly for your
application.
See the Infor Operating Service Installation Guide.
Note: If you are upgrading from an earlier version of Infor OS, check the Infor OS release
notes for any pre-upgrade actions that must be performed.

Required information
Obtain this information before you begin the integration:
• Credentials to connect to the application interface, for example, database user, password, server
name, port or instance.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 8

 Requirements

• Name of the CloudSuite Industrial instance or logical ID that is used to connect with ION; tenant
ID that is used to connect the application to Infor OS in ION; and enterprise organization structure,
that is, accounting entities.
SeeSetting up BOD replication and logical IDs, tenants, accounting entities, and locations in the
ERP on page 26 for information about how to set up the logical ID, tenant ID and accounting entities
for your application.
• CloudSuite Industrial sites that are used in the integration, and either the queue server name or
the bootstrap site that is used to communicate with the sites through replication inboxes and
outboxes.
• Names of physical locations where your CloudSuite Industrial databases exist, if your company
has multiple physical locations.
• A URL and an administrator account for Infor Ming.le and ION. Verify that you can access the URL
and log into Infor Ming.le.
• Location or source of files to be imported into ION and Infor Ming.le for content.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 9

 Configuration checklist

Chapter 2: Configuration checklist

Follow this checklist to integrate this application with the components of Infor Operating Service:

Complete Task Reference

❑ Collect all of the documents listed in the
Reference column from the Infor Support
Portal site. These documents could pro-
vide helpful background during this config-
uration.
❑ Understand the concepts of ION and Infor ION Desk User Guide. Find this guide
BODs, and how these concepts relate to in the ION section of the Infor Support
this application. Portal.
❑ Review the description of how this applica- BOD integrations on page 15
tion interacts with Infor OS. Concepts and definitions specific to this
configuration on page 16
❑ Configure your application for Single Sign Configuring security on page 19
On:
• Set up your application to use Single
Sign On.
• Install Windows Identity Foundation
• Set up the Web client with AD FS ac-
cess
• Edit the web.config file.
• Create a relying party trust for Infor
Ming.le and CloudSuite Industrial.
• Configure Active Directory authentica-
tion groups.
• Import a security certificate for each
user computer.
• Set the time out option for all applica-
tions.
❑ Configure your web browser: Configuring your browser on page 18
• Allow popups
• Set up compatibility for Internet Explor-
er browsers.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 10

 Configuration checklist

Complete Task Reference

❑ Add your application in Infor Ming.le. Configuring your browser on page 18
❑ Configure your application and ION to Configuring your application and ION to
send and receive BODs: send and receive BODs on page 25
• Configure this application for ION
• Configure a connection point for this
application.
• Set up a document flow to pass user
and role information
• Publish BODs.
• Verify that the BODs are received in
ION.
❑ Configure user access to your application Configuring user access to your application
through Infor Ming.le: through Infor Ming.le on page 39
• Configure user access to your applica-
tion in Infor Ming.le.
• Configure system administration ac-
cess to your application through Infor
Ming.le.
• Set up roles or groups.
• Optionally, add accounting entities
and locations to the users or roles.
• Optionally, set up distribution groups.
❑ Set up ION APIs for your application Configuring ION APIs for your product on
page 49
❑ Optionally, configure workflows and ION Configuring workflows and ION messages
messages for your application. for the ERP on page 51
❑ Configure drillbacks to your application. Verifying drillbacks to the ERP through Infor
Ming.le on page 58
❑ Configure context and utility apps that are Configuring context apps and utility apps
used with your application that are used with the ERP on page 61
❑ Configure homepages for your application Verifying Homepages for the ERP on page
65
❑ Configure your application to work with Configuring Infor Document Management
Infor Document Management: to work with the ERP on page 67
• Set up the Document Management
connection in CloudSuite Industrial.
• Activate the Document Management
workflows in CloudSuite Industrial.
• Import the definitions in Document
Management.
• Verify the configuration.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 11

 Overview

Chapter 3: Overview

Before you complete the configuration tasks, you must understand how this application is used with
Infor OS. You should also be familiar with a list of related concepts and definitions.

Infor OS
Infor Operating Service is a technology platform that supports fully integrated, industry-specific solution
suites with mobile-first design, a consumer-inspired user experience, and science-driven analytics. It
leverages the convergence of information, analytics, cloud computing, mobility, and social business.
This platform includes these products:
• Infor Ming.le™
• Infor ION
• Infor ION Grid
• Infor Document Management
• Infor Data Lake
• Analytics
• Infor Localization Services™

Infor Ming.le
Infor Ming.le is a web-based application framework that provides a common user interface for Infor
applications, third-party applications, and in-house developed applications integrated through Infor
ION. It is a centralized platform for social collaboration, business process improvement, and contextual
analytics.
Infor Ming.le provides drillback capability so that users can navigate across the applications to track
transactions, the transfer of data, and report updates. Additionally, Infor Ming.le provides an infrastructure
for sharing content with context applications.
Infor Ming.le uses Homepages, configurable by users to organize information and activities at a high
level to focus on critical areas of concern.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 12

 Overview

Within Infor Ming.le, you can use ION API, a managed API layer across all applicable Infor and non-Infor
APIs, allowing existing APIs to be presented in a standardized, managed, and controllable way.
Infor Ming.le uses Infor Federation Services (IFS) for centralized authentication.
Infor Ming.le is available as a mobile app, supported by iOS, Android™, and Windows Mobile operating
systems.

Infor ION
Infor ION is a business process management platform that integrates applications, people, and business
processes. The ION platform converts data into the common language of standardized XML to enable
disparate business systems such as Infor products, third-party applications, and in-house developed
applications to share information.
ION simplifies the connectivity and data sharing across the connected applications. It enables users
to configure a routed infrastructure, set up workflows, and design and activate business event monitors
and manage tasks and alerts.

ION features
Infor ION has these features:
• You can establish connections between applications which can either be Infor applications or third
party applications through ION Desk.
• You can model document flows between applications to represent a business process. More
technical flows can also be defined, for example, mapping data from a third party application to a
standard business object document as required by an Infor application. You can also include filtering
or content-based routing.
From ION Desk you can deploy your models by activating them. ION Desk also provides
management screens to monitor the behavior of the ION service and to help in troubleshooting
when needed.
• You can monitor business events and create alerts when exceptions occur.
The start point of monitoring are the business object documents that are published by applications
when business events occur. Monitors are processes that run in the Event Management engine
and evaluate these documents by applying predefined business rules. When exceptions are
detected, these are reported as alerts to the business users. The distribution list of alerts is part
of the monitor definition.
• You can model and run business processes such as authorizations, work distribution, or task-driven
workflows across several components.
For authorizations, you can use an approval workflow to approve a purchase order or to sign off
a new item. Such workflows are triggered by the creation of a new item or the submission of a new
order.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 13

 Overview

In the area of work distribution, the workflow ensures that all tasks for a certain event are being
distributed and executed by different users. The advantage of using a workflow is that you can
model how these tasks are performed, for example sequential or in parallel.
• You can manage the alerts, tasks and notifications and distribute them to users. When users take
actions in Infor Ming.le, these actions are recorded and a reply is sent to the engine that generated
the user activity.
For more information about these features, see the Infor ION Desk User Guide.
To understand common ION concepts such as BOD nouns and verbs, document flows and workflows,
listeners and connection points, see the Infor ION Desk User Guide.

Infor ION Grid

Infor ION Grid is a Java-based application server that provides a distributed runtime environment for
other applications. Those other applications may, at any time, be added (deployed) or removed
(undeployed) from a grid. The distributed nature of a grid means that an instance of the ION Grid may
span multiple server machines.

Infor Document Management

Infor Document Management (Document Management) is an integration platform that enables you to
take advantage of document solutions already in use within your organization.
Infor Document Management is used to integrate your documents with your business processes and
to provide a central repository for them. Soft links are used, based on document metadata, to provide
integration between your documents and your Infor ERP solution. You can view a document from within
the context of your application, or click a document link to retrieve the document from the central
repository.
Infor Document Management supports the entire lifecycle of your business documents, from input
through storage, retrieval, and sharing.

Integration with other products in the CloudSuite

The CloudSuite Industrial ERP application uses different integration methods to communicate with
other products in the suite.
You might need to configure additional parameters or master data in each of the applications to complete
the integration. See the appropriate integration guides or chapters in this guide.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 14

 Overview

BOD integrations
An outbound operation typically begins when a user performs an action in CloudSuite Industrial that
requires a data exchange with another ION-enabled application. A Business Object Document (BOD)
XML message is generated by CloudSuite Industrial and placed in an area designated as the CloudSuite
Industrial message outbox. At scheduled intervals, ION connects to the outbox and retrieves the BODs
from it.
In ION Desk, you create application connection points. The connection point defines the information
needed to connect to the application database. It also holds a list of all the BOD documents that the
application can send or receive.
You define data flows between CloudSuite Industrial and other applications that represent the business
flows between the applications. A document flow is a type of data flow, used with BODs. For example,
you set up a document flow between CloudSuite Industrial and Infor Ming.le to pass BODs that contain
user and role information. Use the Modeler in ION Desk to define these document flows. Use the
Modeler in ION Desk to define these document flows.
ION routes BODs according to the document flows between BOD-enabled products. If a document
flow is defined from CloudSuite Industrial to another application for a particular BOD, then at specified
intervals, ION places the outbound BOD from CloudSuite Industrial in the other application’s designated
message inbox. Products are responsible for validating and incorporating the data in inbound BODs
according to their rules.
If a document flow is defined from CloudSuite Industrial to another application for a particular BOD,
then at specified intervals, ION places the outbound BOD from CloudSuite Industrial in the other
application’s designated message inbox. Products are responsible for validating and incorporating the
data in inbound BODs according to their rules.
If a flow is defined from another application to CloudSuite Industrial, ION retrieves BODs from the
sending application’s message outbox and delivers them to CloudSuite Industrial’s message inbox for
processing. CloudSuite Industrial retrieves, validates, and processes the BODs.

Point to point integrations

Point to point integrations are used in cases where you need more immediate (real-time) transfer of
information between the products than a BOD integration provides.
Integrations such as the one with Infor Enterprise Quoting use calls to web services to get immediate
responses from the other application. This is useful when the information is time-critical; for example,
when users need current pricing.
Other integrations use ION API calls or IMS messages to send information between the applications.
For example, the integration with Infor Data Lake uses these methods.
In some other integrations, a direct connection between the databases of the products might be used.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 15

 Overview

Concepts and definitions specific to this configuration

To configure the tenant, logical ID, accounting entity and location correctly, you must understand these
terms and how they are defined in this application. Together, these terms determine where inbound
BOD information is processed, or the outbound instance and location to which the BOD information
should be associated.

Tenant ID
The tenant is a container for accounting entities and locations and is required in each BOD. The value
of the tenant must be the same in all of the products that exchange BODs. Data is not shared or
accessible between tenants.
See the information about using tenants in the Infor ION Desk User Guide.
For an on-premises configuration, verify that all of the other products are using the default value of
infor for the tenant ID, and if so, use that as your tenant ID for CloudSuite Industrial.

Accounting entity
An accounting entity usually represents a legal or business entity that owns its general ledger. Every
transaction belongs to only one accounting entity. An accounting entity can also be defined as the
owner of certain master data among the enterprise. CloudSuite Industrial is the system of record for
accounting entities.
For CloudSuite Industrial, the site is used as the accounting entity.
Do not confuse this Infor definition of “accounting entity” with the CloudSuite Industrial definition of
“entity,” which is a type of site that is used only for financial consolidation.

Location
A location is the physical location that is associated with data or transactions. The location can be, for
example, a warehouse, a manufacturing location, a project location, or an office. Locations are published
in the Location BOD. A location is required for all transactional BODs and is usually the location from
which a transaction or record is generated. CloudSuite Industrial is the system of record for locations.

Logical ID
The logical ID is a unique identifier used in the communication of data between the applications in the
tenant’s environment. Each instance of an application, for example, a site, is assigned one logical ID.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 16

 Overview

In ION, the logical ID is used to properly route BODs. Infor Ming.le uses the logical ID to determine
which application to start when you click a drillback.
This logical ID is defined in the CloudSuite Industrial Sites/Entities form. You must provide the logical
ID when you define the ION connection point for on-premises applications.
In Infor Ming.le, each application is assigned a logical ID. Infor Ming.le supports only one logical ID per
application.
For more information, see the CloudSuite Industrial online help.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 17

 Configuring your browser

Chapter 4: Configuring your browser

Configure your browser for use with Infor Ming.le.

Allowing popups for browsers

Ensure that any browser that is used with CloudSuite Industrial allows pop-ups. If pop-ups are disabled,
the help will not work properly.

Avoiding multiple connections in a browser

You can have as many configurations as you want in a single application or server instance.
However, you cannot have multiple concurrent connections to the same CloudSuite Industrial application
server in a single browser, even using different configurations. The session connection attributes use
the server name as the key and are not differentiated by configuration name.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 18

 Configuring security

Chapter 5: Configuring security

Single sign on allows users to use one set of credentials to log into all Infor applications.
CloudSuite Industrial is set up for Single Sign On in Infor Ming.le through the use of SAML authentication,
Microsoft AD FS and Integrated Windows Authentication. This requires an environment where a
Windows domain trust between the client systems and the AD FS host is configured.
See the Infor Operating Service Installation Guide for information about the client Single Sign On
experience and about the SAML session provider.
Note: Before you configure security for your CloudSuite, contact your Infor representative to discuss
your requirements and get a complete listing of certified identity providers. The representative might
engage the Infor Global Identity and Access Management (IAM) team to assist you in setting up SSO
for the CloudSuite.

Setting up your application to use Single Sign On

Use these steps to set up Single Sign On between the Infor Ming.le portal and CloudSuite Industrial.

Installing Windows Identity Foundation

Windows Identity Foundation 3.5 must be installed on the AD FS server and the CloudSuite Industrial
utility server. Parts of this are installed during the CloudSuite Industrial installation, but the full feature
must be installed in order to use SSO.
See the Infor CloudSuite Industrial Installation Guide for information about setting up CloudSuite
Industrial to work with AD FS.

Setting up the Web client with AD FS access

The CloudSuite Industrial Web client can run as an application inside the Infor Ming.le shell. Be aware
that there are some differences between the CloudSuite Industrial Web client and the smart client.
These differences are documented in the CloudSuite Industrial online help.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 19

 Configuring security

Ensure that these Web client requirements are met:

1 Install a CloudSuite Industrial Web client on a server, as described in the Infor CloudSuite Industrial
Installation Guide.
2 In order to access online help from CloudSuite Industrial in Infor Ming.le, install the utility server
where the help files reside on the same physical server where the Web client is installed.
3 Follow the steps to set up web clients with the AD FS authentication type, as described in the Infor
CloudSuite Industrial Installation Guide.
4 In AD FS, create a relying party trust and give it the appropriate claims rule.
5 In AD FS, add all of your CloudSuite Industrial users, which will allow automatic login to CloudSuite
Industrial through Infor Ming.le.
6 Verify that you can log in to the Web client configured with AD FS. Take note of the URL that you
use to log in, because you will need it for a later step.

Creating a relying party trust for Infor Ming.le and the ERP
This task uses a Power Shell script to create a relying party that associates Infor Ming.le with AD FS
for Single Sign On.
This Power Shell script is similar to the Power Shell scripts that you ran in the post-installation steps
of the Infor OS installation. See the Infor Operating Service Installation Guide.
1 In Infor OS Manager, open the Applications section.
2 Add an application and specify this information:
Application Name and Description
Specify a name of your choice that identifies the application.

Application Type
Select SYTELINE(SyteLine).

Relying Party Identifier

Specify a unique ID in this format, where URN is a name of your choice that identifies the application
and party ID:
Urn: URN :Syteline
For example, Urn:Infor_CloudSuite:Syteline.

SSO URL and SLO URL

For both options, specify the Web client URL, for example: https://sl_server/WSWebClient/
where sl_server is the CloudSuite Industrial web server.

Signing Certificate
Leave this field as (none).

3 Save your changes.

4 Click the arrow next to the new application and specify a location to download a Power Shell script
that is generated from this information.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 20

 Configuring security

5 Copy the Power Shell script to the AD FS server.

6 Open the Windows PowerShell as an administrator.
7 Run the Set-Execution Policy Unrestricted command and specify Y to confirm the Execution
Policy. Press Enter.
8 Run the PowerShell script that you downloaded.
9 Configure Forms Authentication:
a Open ADFS Management and click Authentication Policies.
b Click Edit in the Primary Authentication section.
c Select Forms Authentication for Extranet and Intranet, clear Windows Authentication for
Intranet, and click Apply.

Configuring Active Directory authentication groups

For access to the Infor Ming.le and CloudSuite Industrial sessions, you must associate all users’ domain
accounts with these predetermined Active Directory security groups:

Infor application Active Directory security group

Infor Ming.le Infor
CloudSuite Industrial CloudSuite Industrial Users

Create these security groups in Active Directory outside of Infor Ming.le. See the Microsoft documentation
about Active Directory for information about how to configure user accounts with security groups. Also
see the Infor CloudSuite Industrial Installation Guide for information about how to configure CloudSuite
Industrial for use with Active Directory.

Importing a security certificate for each user computer

To allow AD FS Single Sign On to Infor products, you must obtain a certificate that your users can add
to their computers by using the Microsoft Management Console.
To import the certificate to a user’s computer:
1 From the Windows menu, select Run and enter mmc.
2 Select File > Add/Remove Snap-in.
3 Select Certificate and click Add.
4 Select Computer Account and click Next.
5 Expand Certificates.
6 Right-click Trusted Root Certificate Authorities.
7 Select All Tasks > Import and import the certificate file.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 21

 Configuring security

Single Sign Out

When a user signs out of a portal such as Infor Ming.le, the user is automatically logged out of all
applications, context applications, and widgets that were opened by the user through the portal.

Setting the timeout option for all applications

Use the Time-out option in Infor Ming.le to configure the idle session time-out value for all the Infor
applications that are accessed through the Infor Ming.le portal. This time-out value applies to all users
and applications in Infor Ming.le. User activity is updated periodically by each application through a
common cookie in the root DNS domain. If no user activity is logged within the period specified in the
time-out value, the user is automatically logged out of all applications.
1 From the Infor Ming.le User Management menu, select Security Administration > Session
Configuration.
2 Click Time-out and configure the idle session time-out value to use for all Infor applications that
are accessed through the Infor Ming.le portal. The time is measured in minutes, and you can specify
a number from 10 to 470.
3 Configure a session timeout value for the CloudSuite Industrial web client that is at least as long
as the Infor Ming.le timeout value. Set the Timeout value in the CloudSuite Industrial Single Version
Installer tool, in Advanced Settings, in the Web Client tab. For more information, see the Infor
CloudSuite Industrial Installation Guide.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 22

 Adding your application in Infor Ming.le

Chapter 6: Adding your application in Infor Ming.le

Perform these steps to add CloudSuite Industrial as an application that can run in Infor Ming.le:
1 From the Infor Ming.le user menu, select Admin Settings.
2 Click Add Application.
3 Use this information to complete these fields:
Application Type
Specify Infor Non-Provisioned..

Application Name
Select your application name and version from the list. For all versions of CloudSuite Industrial
10.x, select Infor CloudSuite - 10.0.

Display Name
Specify CloudSuite Industrial.

Logical ID
The first part of the logical ID is set automatically based on the application name. Specify the rest
of the logical ID for the CloudSuite Industrial instance associated with this instance of Infor Ming.le,
for example, the site name. This ID must be lowercase and not contain special characters.

Application Icon
Click Choose Icon.
Each application has a default icon. You can only select the color which you want to apply to the
icon.

Use Https
Select this option if SSL is enabled for the CloudSuite Industrial user interface. If CloudSuite
Industrial is using SSL, ensure that you specify the SSL-related port number in the Port # field.

Host Name
Specify the name of the CloudSuite Industrial web/utility server. This host name is also used for
drillbacks to the application.
Also, if you use a fully-qualified name, for example, server.infor.com, in one instance, you must
use it for all instances.
Note: The host name entered in Infor Ming.le must exactly match both of these:
• The web server URL (http://servername/WSWebClient), which is defined when you install the
Application & Web role on the server during CloudSuite Industrial installation. The IIS
application name for the web client defaults to WSWebClient and cannot be overridden in
the ApplicationSettings.xml file.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 23

 Adding your application in Infor Ming.le

• The host name that is specified on the server’s security certificate

The URL names are case-sensitive.

Port #
Specify the port used by the CloudSuite Industrial web/utility server. Typically this is 80 for HTTP,
and 443 for HTTPS.

Context
If any context is defined in the Infor Registry, it is shown as the default context when you select
the Application Name.

Default Tenant
We recommend that you specify Infor.

4 Click Save.
5 Review the default values in these tabs:
• Deployment Information: The connection information you specified for this application is
displayed.
• Permissions: Two default roles are created, Infor-SystemAdministrator and MingleAdministrator.
Additional roles are automatically generated that match the default authorization groups in
CloudSuite Industrial.
Later in the configuration process, you will use the Permissions tab to configure user access
to CloudSuite Industrial through Infor Ming.le.
• Context/Utility Apps: The default context apps that are included with your application are
listed on this tab.
See Context and utility apps that work with the ERP on page 63.
You can add other context or utility apps here, including context apps that are unique to your
application.
By default, all the required applications are enabled and optional applications are disabled.
You can enable or disable context applications at any time.
• Custom Parameters: Default custom parameters, if any exist, are displayed. You cannot edit
the default name of the custom parameter.
• Logical ID Fallback: By default, no logical ID fallbacks are displayed.
Default values are generated when the application is created. Do not change the default values.
6 Click Save.
7 Verify that you can access the CloudSuite Industrial application from the App Menu.
8 Verify that you can log in to the CloudSuite Industrial app.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 24

 Configuring your application and ION to send and receive BODs

Chapter 7: Configuring your application and ION to

send and receive BODs

This section describes how to configure your application to communicate with ION. Integrations between
this application and other applications use ION to send and receive BODs. For details about a specific
integration, see the appropriate integration guide.

Configuring your application for ION

You must set up this application so that it can generate BODs and place them in a message outbox
where ION can retrieve them.
You must also set up the inbound message configuration, so that BODs sent to this application can
process those messages.

Verifying that the SQL Server no count option is not set

In order to receive all of the BODs from ION into CloudSuite Industrial, the no count option must be
cleared in SQL Server Management Studio:
1 In SQL Server Management Studio, right-click on the CloudSuite Industrial database server name
and select Properties.
2 Select the Connections page.
3 In the Default Connection Options section, clear the no count option.
4 Click OK.

Setting master data to standardized values

To ensure consistent master data between integrated products, use the ISO standard values where
applicable.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 25

 Configuring your application and ION to send and receive BODs

You can map existing non-standard units of measure, currencies and countries to ISO values through
these CloudSuite Industrial forms:
• Currency Codes
Note: ISO currency codes are required for some integrations. ISO currencies are not defined as
part of an initialized database and must be set manually.
• Countries
• Unit of Measure

Setting up a default configuration for each site

On the Sites/Entities form, specify a default Configuration Name for the site. You must create a
configuration with this name, which will be mapped to this site record.
Alternatively, if you leave this field blank, you must create a configuration whose name exactly matches
the local site name, including the capitalization. For example, if your local site name is oh, you must
create a configuration named oh.
You can use the Copy button in the Configuration Manager utility to create configurations with different
names that are based on an original configuration.
Stop and start all Infor services after you create the configuration.

Setting up BOD replication and logical IDs, tenants,

accounting entities, and locations in the ERP
Use these steps to configure information that is required for BOD replication in CloudSuite Industrial.
Note: After you perform these steps on one site, some information is replicated to the other linked
sites.
1 If multiple sites on a CloudSuite Industrial intranet will send or receive BODs, make sure that
replication is set up between the sites as specified in the Infor CloudSuite Industrial Multi-Site
Implementation Guide. The sites must be replicating the Site Admin category to each other. On
the Sites/Entities form at each site that will send or receive BODs, verify that all of the other sites
are linked to this site.
2 On the Intranets form, to create a new intranet for Infor ION (bus), specify these values:
Intranet
Specify the name to identify the intranet, for example, InforBUS.

Description
Specify an appropriate description, for example, Infor ION BOD connection.

External
Select this check box.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 26

 Configuring your application and ION to send and receive BODs

Transport
In this field on the General tab, specify ESB.

ION Transfer Type

Specify ION Outbox for BOD transfer.

3 On the Intranets form, select the intranet used by your CloudSuite Industrial site and specify this
information:
Transport
Specify HTTP.

Queue Server
Optionally, specify the name of your MSMQ Server. You only need to specify a special queue
name here if your site names are not unique, or if the MSMQ is on a different machine than the
utility server. The queue server name can encompass both the name of the machine and the
prefixed names of the queues.
If this field is left blank, the default queue server names are used.

Tenant ID
To use the same tenant ID for all sites on this intranet, specify it here. You can also leave it blank
here and specify the tenant ID on the local site records, or leave that field blank to use the default
tenant ID value of infor. The tenant ID can be a maximum of 22 characters and must match the
tenant ID used in ION for other connecting products. For more information about how the tenant
ID is used with ION, see the Infor Operating Service Administration Guide.

4 On the CloudSuite Industrial utility server, specify configuration information on the Replication tab
of the Service Configuration Manager utility:
• In the Replicator/Inbound Bus Configurations field, specify all of the configurations that can
receive inbound or outbound messages from other sites on the intranet. The Replication
Document Outbox form at each site collects outbound BODs for that site. The Replication
Document Inbox form at each site collects inbound BODs for that site.
• In the Replication Queue Listener Servers field, set up a queue server name for every intranet
in your system.
Generally, the queue server name is set to localhost\private$ which uses the standards
private message queues named inbound and outbound on the utility server. However, if you
have specified a Queue Server Name on the Intranets form, that name is used to build a path.
For example, utilityserver3\private$\MyQueues results in the use of the queue names
MyQueues_inbound and MyQueues_outbound.
Note: If you are upgrading from a previous version and you already have replication set up through
a “bootstrap” site, it will still work as it did in the previous version. The Replicator/Inbound Bus
Configurations field contains one site set as the Master Site, and the ReplQListener Queue
Servers field has the Default field selected.
5 On the Sites/Entities form, create a logical "site" for ION:
Site
Specify a name to identify this site as your ION site, for example: InforBUS.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 27

 Configuring your application and ION to send and receive BODs

Site Name and Description

Specify an appropriate site name and description.

Type
Specify Site.

Intranet Name
Select the intranet you created in step 2.

From Site
On the Site User Map tab, specify the local site, for example, oh. The site name is used as the
accounting entity in BODs.

User Name
Specify the user ID used to send replication documents to the CloudSuite Industrial outbox for
ION to retrieve. This user must already be set up on the CloudSuite Industrial Users form at the
local site. We recommend that you specify the repl_user here, if it is defined. Otherwise, specify
a user with Full User editing permissions. Also, the Automation license module must be assigned
to the user that you specify here.

6 On the Sites/Entities form, configure the local site, for example, oh, to generate or receive business
object documents (BODs).
a Specify the Message Bus Logical ID for the site. This identifies the CloudSuite Industrial site
to ION.
Specify the logical ID as tenant.syteline.site where tenant is the tenant ID, syteline
is the application type, and site is the name of the local site, for example infor.syteline.oh.
The logical ID must be all lowercase.
Note: The logical ID entered here must match the application type and name defined in the
ION connection point for this CloudSuite Industrial site.
b Optionally, specify a Tenant ID for the local site. If no tenant ID is specified here or on the
Intranets form, the default tenant ID value is infor.
7 At each site that is sending or receiving BODs, open the Replication Rules form and create a
new rule. Specify this information:
Source Site
Specify the local site that you configured in Step 6.

Target Site
Specify the ION site that you created in Step 5.

Category
Specify ESB.

Interval Type
Specify any option except Transactional.

8 At each site that is sending or receiving BODs, open the Replication Management form and click
Regenerate Replication Triggers.
Note: If you have multiple sites in one database, you only need to perform this step at one site.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 28

 Configuring your application and ION to send and receive BODs

Setting up information that will flow to other products

The values that you configure in CloudSuite Industrial - for example, customer, vendor or item master
records, or system parameters – often depend on the application with which CloudSuite Industrial will
exchange information. For more information, see the appropriate application integration guide.

Verifying BOD replication

To verify that replication is set up properly:
1 On the CloudSuite Industrial utility server, stop and start the Replication and Replication Queue
Listener services.
2 In CloudSuite Industrial, open a form whose information is being replicated to ION. For example,
the Vendors form information might be replicated.
3 Change a value and save the record. For example, you could change the vendor address.
4 Check the Replication Document Outbox form to see if a BOD was generated and marked as
processed. In our example, the SyncSupplierPartyMaster BOD is generated.
After CloudSuite Industrial is connected to ION, the BODs might be removed immediately from the
outbox after ION retrieves them. In that case, open ION Desk and select OneView to verify whether
the BOD was sent and processed.

Connecting the ERP to ION

A connection point must be set up for CloudSuite Industrial.
You can then set up and activate document flows that send BODs from the CloudSuite Industrial
connection point to other applications' connection points, or that receive BODs from other applications'
connection points.

Understanding connection points and data flows

You create connection points in ION Desk. Connection points provide the information that ION uses
to connect to an application. (For BOD-based integrations, the connection uses the application's
message inbox and outbox. Other integrations communicate through other methods, such as APIs.)
At least one connection point must be defined for each application instance that integrates to ION.
For each connection point, you select the documents that can be sent or received by the application
instance. For a BOD-based integration, these documents correspond to the BODs that are listed in
BODs used in integrations with this application on page 93.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 29

 Configuring your application and ION to send and receive BODs

In an integration between two BOD-enabled applications, document flows are set up to define the
BODs that flow between the application connection points. A document flow is a type of data flow.
A connection point can be reused multiple times in one or more data flows. You can also create
connection points during the modeling of a data flow in the details section of the data flow elements.
The connection points that are created during the modeling of a flow are added to the shared list of
connection points, and they can be reused.
Some integrations with CloudSuite Industrial use a solution XML file to set up sample connection points
and data flows. This file can be imported to ION to provide the basis for connection points and data
flows.
See the section on ION Connect Modeling in the Infor ION Desk User Guide for additional information
about connection points and data flows.

Using the Enterprise Connector in a hybrid environment

If you are using an on-premises version of CloudSuite Industrial, withInfor OS in the cloud, first see
the “Enterprise Connector application connection points” section of the Infor ION Desk User Guide -
Cloud Edition. Use that guide to create locations for your on-premises application and to download,
install, and configure the Enterprise Connector in each of those locations.
Then follow the steps in this section to create your CloudSuite Industrial connection points, one for
each site, and associate each connection point with a location. Use the appropriate integration guides
to set up document flows between the ERP and other applications.

Creating an ERP connection point

Add a connection point for each instance of the application.
See the Infor ION Desk User Guide for more detailed information about this process.
1 In ION Desk, select Connect > Connection Points.
2 Click Add and select Infor Application.
3 Specify this information:
Name
Specify the CloudSuite Industrial site ID.

Description
Optionally, specify a description for the site.

Location
If this is a hybrid environment, and you have installed the Enterprise Connector, specify the location
that you defined with the Enterprise Connector for the CloudSuite Industrial application.
See Using the Enterprise Connector in a hybrid environment on page 30.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 30

 Configuring your application and ION to send and receive BODs

In a cloud environment, this value could be the tenant ID. In an on-premises environment, this is
usually infor.

Logical ID Type
Specify syteline.

Database Driver
Specify SQL Server (Microsoft).

4 Select Use Advanced Settings.

5 Specify the CloudSuite Industrial application database connection details in the URL, including the
host name, port, and database schema name. Other advanced settings are available.
6 Specify the user name and password to connect to the database.
7 Select Delete Processed Messages to immediately delete BODs from the CloudSuite Industrial
Replication Document Outbox after ION processes them. Otherwise, the processed BODs remain
in the outbox for the number of minutes specified in the Outbox Cleaner Expire Time field.
8 Expand the Advanced section at the bottom of the pane.
9 Under Message Processing Preference in Outbox/Inbox, select both by Tenant and by Logical
ID.
The CloudSuite Industrial integration with ION uses a single IOBOX. However, CloudSuite Industrial
uses multiple logical IDs, one per site. Thus, messages must be processed based on the logical
ID.
10 Test and save the connection point.

Connection points are not activated separately. When you activate a document flow, the associated
connection points are activated.

Defining BODs for the ERP connection point

1 In ION Desk, select Connect > Connection Points.
2 Select an existing CloudSuite Industrial connection point.
3 Click the Documents tab.
4 Click + (Add) and specify all of the documents that can be sent or received by this CloudSuite
Industrial instance (site).
The inbound and outbound BODs that are required for each CloudSuite Industrial integration with
another Infor application are listed in BODs used in integrations with this application on page 93.
Add the BODS for integrations that you plan to implement. For “outbound” BODs, select Sent
from this application. For “inbound” BODs, select Received in this application.
5 Save your changes.
You can also add custom document types.
See the Infor ION Desk User Guide.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 31

 Configuring your application and ION to send and receive BODs

Note: If you later remove a BOD from a connection point, and that BOD is used in a document flow,
an error is reported in the document flow messages pane.

Using the Cloud Connector to connect to cloud

applications
If you are using an on-premises version of CloudSuite Industrial, with Infor OS also installed
on-premises, and you want to connect through Infor ION to an application in the Infor cloud, you must
use a Cloud Connector.
See the Infor ION Desk User Guide for information about the Cloud Connector - either version 1 or
version 2, depending on the cloud application. Use that guide to configure a cloud account and to
configure a connection point of type Infor Cloud 1.0 or Infor Cloud 2.0 for the cloud application.
If CloudSuite Industrial is on-premises, but Infor OS is in the cloud, then the Cloud Connector is not
needed. The Infor Cloud team will set up the connection points for Infor cloud apps.
Use the appropriate integration guides to set up document flows between the ERP and other applications.

Configuring document flows

You must create document flows in ION Desk in order to pass BODs between applications.

Setting up a document flow to Infor Ming.le to pass user and

role information
Ensure that connection points are set up and a document flow is activated in ION Desk so that BODs
are sent between CloudSuite Industrial and Infor Ming.le.
1 In ION Desk, verify that an Infor Ming.le connection point exists. You should have already set up
the connection point when you completed the post-installation steps when you installed Infor OS.
See the Infor Operating Service Installation Guide.
2 Ensure that the Infor Ming.le connection point is set up to send and receive these BODs:

Document Receive in application Send from application

Process.SecurityUserMaster X
Sync.SecurityRoleMaster X
Sync.SecurityUserMaster X

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 32

 Configuring your application and ION to send and receive BODs

3 Import the solution XML to create the erp_mingle document flow:

a From the CloudSuite Industrial Download Center on the Infor Support Portal site, download
the erp_mingle.xml file to a local folder.
b In ION Desk, select Connect > Data Flows.
c Click Import.
d Browse and select erp_mingle.xml.
e Click Open. The document flows and mappings from the file are imported.
f Select Connect > Data Flows and click on the erp_mingle document flow.

4 In the properties pane for each of the application boxes, click + and add the appropriate connection
points.
Note: You only need to add one CloudSuite Industrial site as a connection point. The sites are all
in one database, so basic user data is shared between all sites. However, if you want to ensure
that updates to roles (groups) are also shared between all sites, you must set up a master site and
shared user tables in CloudSuite Industrial. (See the Infor CloudSuite Industrial Multi-Site Planning
Guide – Cloud Edition.) If you don’t want to use a master site and shared user tables, then you
must include all of the CloudSuite Industrial site connection points in this document flow.
5 Select the document icon between MINGLE_1 and ERP_1 and ensure that it lists this document:
• Sync.SecurityUserMaster
6 Select the document icon between ERP_1 and MINGLE_2 and ensure that it lists these documents:
• Sync.SecurityRoleMaster
• Process.SecurityUserMaster
7 Save your changes.
8 Activate the document flow.
9 Open CloudSuite Industrial from the App menu.
10 In the Replication Document Manual Request Utility form, select the Sync SecurityRoleMaster
BOD. Select Initial Load and click Process. This publishes the security roles from CloudSuite
Industrial, which are sent to Infor Ming.le. The Infor-SystemAdministrator group fromCloudSuite
Industrial is synchronized with the Infor-SystemAdministrator role in Infor Ming.le.
For information about these BODs, see User and role BOD usage on page 73.

Configuring other data flows between applications

Usually, data flows are configured and activated in conjunction with integrations between CloudSuite
Industrial and another application. In that case, skip this section and follow the steps in the appropriate
integration guide. However, if you want to send BODs to another ION-enabled application but there is

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 33

 Configuring your application and ION to send and receive BODs

not an appropriate integration guide, you can follow these general steps. See the Infor ION Desk User
Guidefor more information
1 Define a new data flow that includes connection points for both CloudSuite Industrial and the other
application.
2 Define the documents or messages that flow between the applications, and the direction that they
flow.
3 Save the data flow.
4 Activate the data flow.

Publishing BODs
You publish BODs so that ION can retrieve them from your message outbox, viewed through the
Replication Document Outbox form. You can publish BODs for general use by any product that
subscribes to the BODs through Infor ION. After you perform an initial data load from your application,
you verify that data is flowing out of the application into ION. For details about a specific integration,
see the appropriate integration guide.
For a BOD-based integration between this application and another application, see the appropriate
integration guide for these instructions:
• Setting up the document flows
• Performing any additional configuration of the applications that is required for that integration
You can then use the steps in the integration guide to publish the BODs.

Starting products and services

Before publishing BODs from CloudSuite Industrial, start these products, services and processes if
they are not already running:
• CloudSuite Industrial
• Other products with which you are communicating through Infor ION
• ION Service
Use the ION Grid Management user interface to verify that the ION Service is running. See the
Infor ION Grid Administration Guide.

Initial data load

During normal processing, BODs are automatically generated (published) when a user makes a data
change or completes a transaction. However, when you start a new integration with another application,
you must manually publish BODs that pass the current set of data from your application to another

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 34

 Configuring your application and ION to send and receive BODs

application, so that the base systems are synchronized. The BODs are placed in the Replication
Document Outbox, from which ION retrieves them and passes them to the other application.

BOD dependencies
Be aware that you must load these BODs in this order to prevent errors in the integration due to missing
data:
• AccountingEntity: This is the first BOD you should publish from each site.
• FinancialCalendar: This must be published before the ChartOfAccounts or any financial transaction
BODs.
• AccountingChart: This must be published before any financial transaction BODs.
• ChartOfAccounts: This must be published before any financial transaction BODs.
• Master data, including:
• CodeDefinition
• Location
• CustomerPartyMaster
• ItemMaster
• BillToPartyMaster
• ShipFromPartyMaster
• ShipToPartyMaster
• SupplierPartyMaster
• Any required historical transaction data, including:
• SalesOrder
• Shipment
• Invoice

Sending the initial data load

To publish initial ERP master and transaction data into BODs that are placed in the Replication
Document Outbox:
1 In CloudSuite Industrial, open the Replication Document Manual Request Utility.
2 Select Initial Load so that the data is processed as an insert, that is, as new data.
3 Select the BODs to include in the data load. The BODs you select are different for each integration.
See the appropriate integration guide for the BODs to load.
Note: If you select multiple process BODs at one time, the BODs are processed in alphabetical
order. However, you must load certain BODs in a specific order, to prevent errors in the integration
due to missing data. See BOD dependencies on page 35.
4 Click Process to process the selected BODs.
5 Continue to select and process BODs until all of the BODs are processed that are required for a
specific integration.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 35

 Configuring your application and ION to send and receive BODs

6 Repeat this process at each CloudSuite Industrial site.

When you use this utility to publish BOD data, the current date is used for all Status/EffectiveDateTime
elements.
After the initial data load, CloudSuite Industrial automatically publishes BODs whenever users change
certain data or when certain transactions occur in CloudSuite Industrial.
For a list of the events that generate BODs, see Business events that generate outbound BODs on
page 80.

Turning off BOD replication to reduce traffic

CloudSuite Industrial can generate hundreds of BODs per day. By default, a BOD is generated whenever
the BOD trigger occurs. For example, a BOD is generated every time a user creates a new customer
order, or every time an invoice is created.
Unless you have integrations set up where other applications will receive the BODs, there is no need
to generate most of the BODs. Use these steps to stop publishing all unnecessary BODs.
1 If your system is not integrated with Infor Ming.le or any other application via BODs, go to the
Replication Rules form, filter for the ESB rule, and select Disable Replication. This disables all
BOD replication.

2 If your system is integrated via BOD with some other products, leave the ESB rule in Step 1 enabled.
Use these steps to only replicate BODs for the integrations you are using:
a Go to the Infor Support Portal site and download the script from KB 1964331.
b Run the script on each CloudSuite Industrial application database. This script enables users
to turn off replication of specific BOD triggers.
c Open the Replication Categories form.
d Specify ESB as the Category and click the filter.
e To stop publishing a BOD, update its Trigger* record in the ESB replication category. Select
the appropriate Skip Method check box.
This example shows how to turn off the Sync.ItemMaster BOD:

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 36

 Configuring your application and ION to send and receive BODs

Select Skip Method for any BOD triggers that you are not using, with these exceptions:
• See the appendixes of this guide for a list of the BODs required to integrate with Infor OS
components such as Infor Ming.le and Document Management. Leave the triggers for
those BODs enabled.
• See the appendixes of this guide for a list of the outbound BODs required to integrate with
any other products that you are using. Leave the triggers for those BODs enabled.
• Also leave these triggers enabled:
• FlushBusCacheForSiteSp
• FlushBusParmsForSiteSp
• SendEntireBodSp
• TriggerBODConfirmSp
• TriggerPulseNotificationSyncSp

3 If you later integrate CloudSuite Industrial with additional applications via BODs, you must turn on
the triggers for the required BODs when you integrate with the other applications.
See the appendixes of this guide, or the appropriate integration guide, for the list of outbound BODs
that are required for each integration.

Verifying the ION configuration

Use these tasks to verify that the connections are set up correctly.

Verifying that BODs are published

1 Use the information in Business events that generate outbound BODs on page 80 to determine
what user actions generate certain BODs.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 37

 Configuring your application and ION to send and receive BODs

2 Perform those user actions in CloudSuite Industrial.

For example, information from the Vendors form is replicated through the SyncSupplierPartyMaster
BOD, so you could change the vendor address and save your change.
3 Check the Replication Document Outbox form in CloudSuite Industrial to see if a BOD was
generated and marked as processed.
In our example, the SyncSupplierPartyMaster BOD is generated.
Depending on settings, the BODs might be removed immediately from the outbox after ION retrieves
them. In that case, you can check ION Desk OneView to verify whether the BOD was sent and
processed.
4 In ION Desk, review the messages by using ION Desk OneView or other ION Desk functions.
If messages are not displayed in ION Desk, check the CloudSuite Industrial Replication Document
Outbox form to see if the BODs were generated but not retrieved by ION.
5 If messages are not flowing, review the XML data for the BOD.

Verifying that ION receives data

To verify that ION is receiving BODs from CloudSuite Industrial, monitor these areas in ION Desk:
• Select Connect > Active Connection Points to show the message queue counts.
• Select OneView to show individual messages, if they are enabled.
• Select Connect > Error BODs to see if any errors were reported.
If you encounter problems, see Data is not flowing properly on page 78.

Verifying the data flow between applications

After you create and activate data flows to other applications, you can check the message inbox area
of the other applications, to ensure that data is flowing between the systems. See the other application’s
documentation to determine how to find the message inbox.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 38

 Configuring user access to your application through Infor Ming.le

Chapter 8: Configuring user access to your application

through Infor Ming.le

Users, roles, and person IDs are initially defined in Infor Ming.le and shared with all of the other
applications that run through the Infor Ming.le portal. Roles and some user information can later be
modified in CloudSuite Industrial.

Users and roles

Because Infor Ming.le is the system of record for users, you must set up users in Infor Ming.le. The
users are then synchronized through BODs to other BOD-enabled applications in the Infor Ming.le
portal. After the users are synchronized to your application, you can continue the user setup in your
application.
You can perform these user management tasks in Infor Ming.le:
• Create users, including manual import of users
• Update users
• Delete or deactivate users
• Reset passwords
• Monitor recent user activity and mobile sessions
• Manage sessions

How Infor Ming.le users and roles work with ERP users and
groups
Note: In a Cloud usage-tracking environment, licenses are not assigned to specific users, either in
CloudSuite Industrial or through Infor Ming.le roles.
When you create or update a user in Infor Ming.le, the information associated with that user is used to
automatically set up some user information in CloudSuite Industrial. This association is handled through
Sync SecurityUserMaster BODs that are passed through ION.
CloudSuite Industrial groups and license modules are mapped to security roles in Infor Ming.le.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 39

 Configuring user access to your application through Infor Ming.le

The list of available CloudSuite Industrial groups must be updated and maintained in CloudSuite
Industrial – not in Infor Ming.le - because the types of roles and the names of roles are dependent on
the requirements of CloudSuite Industrial. After the groups are set up in CloudSuite Industrial, they are
synchronized to Infor Ming.le through the Sync SecurityRoleMaster BOD, so that Infor Ming.le is aware
of all possible roles. The ability of security roles to perform specific operations and access specific data
is enforced by CloudSuite Industrial, not Infor Ming.le.
When you assign a user to a group or license module in either CloudSuite Industrial or Infor Ming.le,
that information is passed to the other application through a SecurityUserMaster BOD. Infor Ming.le is
the System of Record for this information.
CloudSuite Industrial licenses can be assigned to users either through the CloudSuite Industrial User
Modules form or through “CSI-LicenseModule-“ roles in Infor Ming.le.. However, these license
assignments are meaningless in a usage-tracking environment.
Note: All CloudSuite Industrial license modules are available as security roles in Infor Ming.le. However,
if you assign a license module security role to a user in Infor Ming.le, but your company is not licensed
for that module, or if the user count for that module is exceeded, then when CloudSuite Industrial
processes the inbound BOD, it will not assign the license module to the user. This can leave the two
applications out of sync.
Infor Ming.le provides a default Infor-SystemAdministrator role that allows for full access to all applications
that are linked to Infor Ming.le. CloudSuite Industrial has an Infor-SystemAdministrator group or role
that allows access to all CloudSuite Industrial screens. When a user who has the
Infor-SystemAdministrator role inInfor Ming.le is synchronized to CloudSuite Industrial, that user
automatically has access to all CloudSuite Industrial forms.
For more information about these BODs, see User and role BOD usage on page 73.

Configuring user access to the ERP through Infor Ming.le

You must add other users in Infor Ming.le before they can access CloudSuite Industrial through Infor
Ming.le.
1 From the Infor Ming.le User Menu, select User Management.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 40

 Configuring user access to your application through Infor Ming.le

2 From the menu on the left side, select Security Administration > Settings > General Settings.
3 Click Manage Features.
4 Configure these general properties to ensure that new or changed user information is synchronized
with other applications:
Publish Security User Master BOD
Select this option to publish the SecurityUserMaster BOD when a user’s details are changed in
Infor Ming.le. This synchronizes the user details with other applications that subscribe to the BOD.

User Synchronization Interval (min)

If you selected the Publish Security User Master BOD option, specify the interval, in minutes,
at which you want to publish the updated BODs to synchronize users.

5 To set up system administrator access for your account between Infor Ming.le and CloudSuite
Industrial, add the Infor-SystemAdministrator role to your account:
a In Infor Ming.le, select User Management from the user menu.
b Select your system administrator account and click the Details icon.
c Click the Security Roles tab.
d Click + and add the Infor-SystemAdministrator role.
e Click Add.
6 On the Users page, follow these general steps to add users. See the Infor Ming.le online help for
more information.
Note: If your application already has legacy users set up, you can import the users into Infor Ming.le
from a .CSV formatted file. See the Infor Operating Service Administration Guide. To temporarily
disable user synchronization before the import, clear the Publish Security User Master BOD
option and select Do not enable for the Enable SCIM Parameter configuration option. Then
select Allow Import. The Import option is then enabled on the Manage > Users page.
a Click + to add a user.
b Clear the Send Invitation option so that you can send the invitation later, after you have
completed the user setup.
c Save your changes.
d Click the details icon to view details for the user.
Note: The IFS ION-Person ID will be used to synchronize personnel records with CloudSuite
Industrial. It is generated automatically and should not be changed.
e In the Security Roles tab, assign the user to one or more roles, and click Add & Close.
In order for users to access CloudSuite Industrial through Infor Ming.le, they must be assigned
at least one CloudSuite Industrial role.
You might not see all of the application-specific roles that you need. If you do not see the roles
you need, those roles can be added and assigned later from within CloudSuite Industrial.
f Save your changes.
The information is sent through BODs to CloudSuite Industrial after you save your changes.

7 Open CloudSuite Industrial from the App Menu.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 41

 Configuring user access to your application through Infor Ming.le

8 If prompted, select a configuration, which is linked to one of your CloudSuite Industrial sites. If you
plan to use one site as a master site, select the configuration for the master site.

9 In CloudSuite Industrial, select Form > Open and open the Users form.
10 In the Users form, click the filter toolbar button to see all of the users who were defined in Infor
Ming.le.
11 Update the information for each user to specify additional required or optional fields that are not
shared with Infor Ming.le. See the CloudSuite Industrial online help for more information.
a After you add your users in Infor Ming.le, verify that the user information has been sent through
BODs to CloudSuite Industrial. This information should be shown in the CloudSuite Industrial
Users form:
• The user name (email address) that you set for each user in Infor Ming.le is shown in the
User Name field.
• The IFS ION-Person ID that was set for each user in Infor Ming.le is shown in the
Workstation Domain/ID field.
These values should not be changed.
b Assign the user’s form editing permission level, PO requisition limit, and multi-site group
authorization, as needed. See the online help.
c Set the user’s password for the CloudSuite Industrial web client or click once client.
(This is not the same password that is used to log into the Infor Ming.le portal. The Infor Ming.le
portal password uses the IFS ID tied to the Workstation ID, so no additional user login is
required to access the CloudSuite Industrial application in Infor Ming.le.)
When users access CloudSuite Industrial through the web client or the click once client rather
than through Infor Ming.le, they must know this password.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 42

 Configuring user access to your application through Infor Ming.le

d Ensure that the email address that you set for each user in Infor Ming.le is shown in the Primary
Email Address on the Users form. This value should not be changed. We recommend setting
these additional fields for the user:

e In the Groups tab, click in the grid and select Actions > New to add a new row.

f Click in the Group Name field to view the list of groups. Add any groups to which this user
should belong. If you were able to assign the groups as security roles for the user in Infor
Ming.le, you will see them listed here. Otherwise, you can assign the additional groups here.
g Click User Modules and assign the appropriate license modules to the user. If you were able
to assign the license modules as security roles for the user in Infor Ming.le, you will see them
listed here. Otherwise, you can assign the additional license modules here.
By default, users who are originally created in Infor Ming.le and sent through BODs to CloudSuite
Industrial are assigned a Transactional license in CloudSuite Industrial. This is handled through
the Admin License Module Name setting in the Process Defaults form.
Note: Some modules such as Service and QCS are separately licensed and require additional
configuration, as described in the next section.
h Save your changes.
12 In Infor Ming.le User Management, select the user’s record, and then select Action > Resend
Invitation.
The user receives a notification with a link that provides user-specific access to Infor Ming.le and
to CloudSuite Industrial.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 43

 Configuring user access to your application through Infor Ming.le

Configuring users for separately licensed modules

If your product includes separately licensed modules such as Quality Control (QCS), Service, or Tax
Interface, follow these steps to ensure that users have access to those modules.
1 Log into CloudSuite Industrial.
2 In the Optional Modules form, ensure that Enabled is selected for the modules for which you
have purchased licenses.
3 In the Users form, click the filter button on the toolbar to show all defined users.
4 In the grid on the left, select a user who needs licensing for an optional module.
5 Click User Modules to display the license modules assigned to the current user.
6 To add a license for the user, click the Create button on the toolbar.
7 In the Module Name field, select a license module for the user, for example, ServiceManagement
for the Service module or QualityControlSolution for the QCS module.
Required: For business partners in a demo environment, your administrative user must be licensed
for these modules:
• QualityControlSolution
• ServiceManagement
• TaxInterface
8 Click the Create toolbar button again to add another license module for the user, and repeat until
all licenses for that user are added.
9 Save your changes.
10 Repeat these steps for any other users that must be licensed for the optional modules.

Configuring additional system administrator access to

applications through Infor Ming.le
You can set up additional system administrators for all or some applications that are run inside of Infor
Ming.le.
1 From the Infor Ming.le User Menu, select User Management.
2 On the Users page, click the Detail icon for one of the users that you want to make an administrator.
3 In the Security Roles tab for that user, click + to add roles.
4 In the Search field, specify Admin to filter for all administration roles, and click the search icon.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 44

 Configuring user access to your application through Infor Ming.le

5 Select the check box at the top of the column, to select all admin roles.
Note: If you have "power users" who only need administrator access in some applications, select
the “administrator” roles only for specific applications for those users.
6 Click Add & Close.
7 Click + again and specify Mingle in the filter field. Add all displayed roles to the admin user.
8 Click + again and specify Homepage in the filter field. Add all displayed roles to this user.
9 Click the Save icon on the Security Roles tab to save the roles for this user.

Configuring power user access to Infor OS applications

You might have "power users" who do not need full System Administrator access to all applications,
but who need administrator access to certain apps. Use the steps in Configuring additional system
administrator access to applications through Infor Ming.le on page 44, but only select the “administrator”
roles for specific applications for those users.

Configuring additional system administrator access to the

ERP through Infor Ming.le
1 In Infor Ming.le, add the Infor-SystemAdministrator role to the appropriate users.
After you update the user information, a BOD is sent from Infor Ming.le to CloudSuite Industrial to
synchronize the system administrator users with this role.
2 Assign additional system administration roles, either in Infor Ming.le or in the CloudSuite Industrial
Users form, to the appropriate users.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 45

 Configuring user access to your application through Infor Ming.le

Setting up additional roles or groups

Predefined security roles (groups) are used in both the CloudSuite Industrial application and Infor
Ming.le. If you need to create security roles (groups) that are specific to your company for use with
CloudSuite Industrial, follow these steps.
1 In CloudSuite Industrial, use the Groups form to create any additional groups (security roles) that
you need in order to access specific forms, programs, and logical folders.
Your updates to the list of groups/roles are then sent to Infor Ming.le through the
Sync.SecurityRoleMaster BOD. The information from this BOD is used in Infor Ming.le to
automatically create a matching security role.
2 Associate the security roles with users. This can be done in either Infor Ming.le or CloudSuite
Industrial:
• To associate security roles with users in Infor Ming.le:
a Select User Management.
b Select a user.
c Click the Details icon.
d In the Security Roles tab, click +.
e Select the roles you want for the user, and click Add & Close.
Infor Ming.le generates a Sync.SecurityUserMaster BOD for each user to which a role was
added. It sends the BOD to all applications that run in the Infor Ming.le portal. CloudSuite
Industrial uses the information from this BOD to associate the role or group with the CloudSuite
Industrial user record.
• To associate groups (roles) with users in CloudSuite Industrial, go to the Users form, filter for
the user, and use the grid on the Groups tab to associate the user with the appropriate groups.
CloudSuite Industrial generates a Process.SecurityUserMaster BOD which is sent to Infor
Ming.le. Infor Ming.le then sends another BOD to all applications that run in the Infor Ming.le
portal, to update the user records in all applications.
If you delete a role in either CloudSuite Industrial or Infor Ming.le, you must also delete the
corresponding role in the other application.

Automatic login and selecting configurations

When users first access CloudSuite Industrial through Infor Ming.le, they see a dialog box. Because
of Single Sign On, the user ID and password are not requested; however, users must select a CloudSuite
Industrial configuration. The Use Workstation Logon option on this dialog box is hidden and is
automatically selected for the user.
Subsequent logins depend on how the user signs in and out of the application and Infor Ming.le:
• If users sign out of the CloudSuite Industrial application before exiting Infor Ming.le, then the next
time they open the CloudSuite Industrial application, they must select a configuration.
• If users close the browser without signing out, or exit Infor Ming.le without signing out of CloudSuite
Industrial, then the next time they open the CloudSuite Industrial application, the previous

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 46

 Configuring user access to your application through Infor Ming.le

configuration is automatically selected and no dialog box is shown. To switch to a different

configuration, the user can select Form > New Sign In.

About accounting entities

Accounting entities are set up through BODs that are sent by your application to Infor Ming.le.
After the accounting entities exist in Infor Ming.le, you can assign users and groups to them. Infor
Ming.le then sends BODs to your application with the information to be synchronized.
The application is the system of record for accounting entities.

About locations
Locations are set up through BODs that are sent by your application to Infor Ming.le.
After the locations exist in Infor Ming.le, you can assign users and groups to them. Infor Ming.le then
sends BODs to your application with the information to be synchronized.
The CloudSuite Industrial application is the system of record (SOR) for locations.

Verifying user access

To verify that users were created properly and can access the appropriate forms in CloudSuite Industrial:
1 Log into Infor Ming.le portal as a user. The user must belong to a role that is defined as an
administrator in both Infor Ming.le and CloudSuite Industrial.
2 From the App Menu, open CloudSuite Industrial.
3 If prompted, select the appropriate configuration and click OK. The application session is opened.
4 Open the Users form and verify this information for several users:
• User Name matches the Email address in Infor Ming.le.
• Workstation Domain/ID matches the IFS ION-Person ID in Infor Ming.le.
• Groups that you assigned to this user are set as roles in Infor Ming.le.
5 Click User Modules and verify the license modules assigned to the user.
6 Sign out of the application and Infor Ming.le. Close the browser.
7 Log into Infor Ming.le and CloudSuite Industrial as a non-administrative user who has access.
8 Ensure that you can open any forms that the user has authorization to open, and that you cannot
open any forms for which the user is not authorized. as a non-administrative user who has access
to both

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 47

 Configuring user access to your application through Infor Ming.le

Setting up distribution groups

Optionally, you can set up distribution groups in Infor Ming.le for CloudSuite Industrial users who require
access to ION in order to view or update information or to troubleshoot errors.
See the Infor Operating Service Administration Guide.

Service accounts
The Infor Ming.le Service Accounts page shows accounts that have been created to allow applications
a resource owner grant to contact the Infor Authorization Service to obtain a token for use in making
API requests.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 48

 Configuring ION APIs for your product

Chapter 9: Configuring ION APIs for your product

Use this information to set up the APIs.

Using ION APIs to consume Mongoose REST services

The ION API service is a broker for Infor applications that use web service APIs. The service handles
synchronous communications to application specific APIs, versus asynchronous BOD communications
that conform to the OAGIS standard.
Currently CloudSuite Industrial does not require any configuration of ION APIs. However, you can
configure any Mongoose-based application running in Infor Ming.le to allow calls to the Mongoose
REST service through ION API.
Settings in the IDO Request Service web.config file determine whether the Mongoose REST service
is enabled for use with ION API or is using the traditional Mongoose token exchange.
To use ION API to connect to CloudSuite Industrial, the application’s web.config file must be modified
to use these settings:
• enableRestWorkstationLogon: Set this option to true.
• restOAuthConsumerKey: Specify a key value. You will provide the same consumer key value to
ION API later.
• restOAuthConsumerSecret: Specify a secret value. You will provide the same consumer secret
value to ION API later.
For more information about authenticating against ION API to consume Mongoose REST web services,
see the Infor Ming.le ION API User Guide.
For more information on consuming Mongoose REST web services and which methods are available,
see Mongoose REST Web Services (on the Mongoose portal) or use the Open API documentation
that is available in this area: https://mongoose_application_server/IDORequestService/
MGRestService.svc/api-docs/ where mongoose_application_server is your server.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 49

 Configuring ION APIs for your product

Using Mongoose to consume APIs from other

applications through ION APIs
The Mongoose application user has an Infor Ming.le identity that is set up through Single Sign On
(SSO). Mongoose can exchange the SSO credentials for an ION API token. This token is used to
interact with other systems via ION API Gateway.
With the ION API token, Mongoose can invoke web services for other applications on behalf of that
user, which are exposed through ION API. These include but are not limited to Infor Ming.le, Infor
Document Management, and M3.
All interactions are performed with the user credentials in the source and target systems, complying
with any security configuration, and ensuring that the audit trail is not compromised.
You can also invoke APIs without having a current SSO session (such as in a scheduled task or AES
event). This is done using a service account, without the user’s own identity; the service account identity
is chosen when you provision the Mongoose application as an authorized backend app.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 50

 Configuring workflows and ION messages for the ERP

Chapter 10: Configuring workflows and ION messages

for the ERP

You can configure workflows and ION messages for your application.

ION messages
This table shows the types of ION messages:

Type Description
Alert Alerts are generated by Event Management in Infor OS or by a
PulseAlert BOD. An alert is a business notification or exception indi-
cating that something out of the ordinary has happened in the flow of
application documents.
Task Tasks are generated by Workflow in Infor OS or by a PulseTask BOD.
A task is an activity that must be completed within a defined period
of time. When the task is generated by Workflow, it suspends the ex-
ecution of the workflow until the task is completed. When a task is
completed, the user's response is sent back to Workflow to resume
execution of the workflow.
Notification Notifications are generated by Workflow or by a PulseNotification
BOD. A notification is similar to a task, but it does not require immedi-
ate user action. A notification does not suspend the execution of the
workflow.
Alarm The ION Alarms mobile application for Android devices is available
to create monitors, called alarms.
In ION Desk, the business administrator can create alarm templates.
After the templates are activated, mobile users can use the templates
to create alarms in the ION Alarms mobile application. The alarm
creator can specify the distribution list for the resulting alert. See the
Infor ION Alarms Mobile Application User Guide.
The users receive the alert on their Infor Ming.le page, in the Infor
Ming.le mobile application, or by email.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 51

 Configuring workflows and ION messages for the ERP

About alerts sent from the ERP to Infor Ming.le

CloudSuite Industrial can send PulseAlert BODs to ION that can be displayed as alerts in Infor Ming.le,
as shown in this process flow:

A Process PulseAlert BOD is generated when a business event associated with one of these publications
occurs in CloudSuite Industrial:

Publication Description Where defined

CustomerCreditHoldAlert A customer was put on credit Event: IdoOnItemUpdate, Seq
hold 15
CustomerInteractionFollowUpAlert A follow-up is needed to a cus- Event: CustomerInteractionFol-
tomer interaction. Key Value 1 lowupAlert, Seq 1
defines the customer number.
CustomerOrderCreditHoldAlert A customer order was put on Event: IdoOnItemUpdate, Seq
credit hold 16
CustomerShipmentAlert An order was shipped to a cus- Event: IdoOnItemUpdate, Seq
tomer (for specific orders/cus- 17
tomers)
DCShopFloorTransactionErro- A specified number of Data Trigger on dcsfc_mstIup
rAlert Collection shop floor transaction
errors occurred. Key Value 1
defines how any errors must be
generated before the user re-
ceives an alert
JobMaterialCostAlert The quantity issued against a Trigger on jobmatl_mstIup
job is more than required and
the total material cost (actual)
of the job exceeds the required
cost by a certain percent (toler-
ance) set by the user
JobOperationHoursAlert Labor hours for a job were more Trigger on jobroute_mstIup
than estimated
JobOverProductionAlert The completed quantity of a job Trigger on job_mstIup
is greater than the released
quantity

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 52

 Configuring workflows and ION messages for the ERP

Publication Description Where defined

JobProjectedLateForCus- A job is projected to be late for Trigger on job_sch_mstIup
tomerAlert a specified customer. Key Val-
ue 1 is the customer number.
LateOrderShippingAlert At least one open order line for Event: LateOrderShippin-
a customer has a due date prior gAlert, Seq 1
to the current date. Key Value
1 is the customer number
LeadAssignedAlert A lead is assigned to a salesper- Event: IdoOnItemUpdate, Seq
son 19
LockedUserAlert A user is locked out Trigger on UserNamesIup
OpportunityDueAlert An opportunity is due Event: OpportunityDueAlert,
Seq 1
OverBudgetAlert The specified account's actual Event: OverBudgetAlert, Seq
amount is above budget for the 1
current fiscal period. Key Value
1 is the account number, and
Key Value 2 is the percentage
over budget that triggers an
alert
ProjectedLateShipAlert An order line is projected to Event: IdoOnItemUpdate, Seq
ship late. Key Value 1 is the 18
customer number.
ProspectInteractionFollowUpAlert A follow-up is needed with a Event: ProspectInteractionFol-
prospect. Key Value 1 is the lowUpAlert, Seq 1
prospect ID.
ScheduledMainte- A scheduled maintenance task Trigger on MO_re-
nanceAddedAlert is added for a resource. This source_maint_mstIup
alert is used only with the
Molding Industry Pack.
ScheduledMaintenanceAlert A scheduled maintenance task Event: ResourceMainte-
has been changed from nanceScheduleUpdateStatus,
Planned to Scheduled for a re- Seq 1
source. This alert is used only
with the Molding Industry Pack.
TransactionAmountAlert The amount of a transaction for Event: TransactionAmoun-
a specified account is over the tAlert, Seq 1
specified amount. Key Value 1
is the account number. Key
Value 2 is the amount to which
transactions should be limited.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 53

 Configuring workflows and ION messages for the ERP

CloudSuite Industrial users can subscribe to the appropriate publications. Then, when an alert occurs
and a BOD is generated, the email addresses for all subscribers are included in the BOD.
The email address that is used in the BOD is determined by the Email Type Description field on the
Users form. If an address is specified where the Email Type Description is set to PersonID, then the
email address that is associated with the PersonID type is used. If no PersonID type is found, then the
address in the Primary Email Address field is used, as shown in this example:

If neither of these areas are populated, then a BOD is not sent.

ION attempts to match the email address from the BOD with a PersonID or primary email address that
is defined for a user in Infor Ming.le, so that it can pass along the alert. If a matching address is found,
and if the user has the appropriate Infor Ming.le permissions, the alert is displayed on the user's Alerts
panel in Infor Ming.le.
This is the general process flow:

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 54

 Configuring workflows and ION messages for the ERP

Configuring applications to process alerts

1 Configure CloudSuite Industrial to send alerts.
a In the Process Defaults form, set ION Pulse Interface to 1.
b For publications (alerts) that have associated event handler sequences, activate the sequences
so that the BOD will be sent when the events fire. In the Workflow Event Handler Activation
form, select the appropriate event and sequence, and select Active for this Site.
See the list of publications and their associated event handler sequences in About alerts sent
from the ERP to Infor Ming.le on page 52.
c CloudSuite Industrial users must subscribe to the appropriate publications (alerts) from the list
above, through either the Mobile Alerts form or the Publication Subscribers form.
d Set up CloudSuite Industrial users with either a PersonID email address or a primary email
address, or both. In the Email Addresses tab on the Users form, add a record to the grid
where Email Type Description is set to PersonID and an email address is assigned. You
can optionally set the Primary Email Address to another email address for the user.
See Person IDs on page 74.

2 Configure ION to process alerts from this application.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 55

 Configuring workflows and ION messages for the ERP

Ensure that the Process PulseAlert BOD is included in the list of BODs that can be sent from the
CloudSuite Industrial connection point.
a In ION Desk, select Connect > Connection Points.
b Select the Infor Ming.le connection point and add Process.PulseAlert in the Documents tab
(as Send from Application) if it does not exist.
Through an internal API, ION passes the alert to Infor Ming.le as a Sync.PulseAlert BOD. See the
Infor ION Desk User Guide.
3 Configure Infor Ming.le to display alerts for this application.
4 Set up Infor Ming.le users with the appropriate roles to access tasks and alerts. See information
about configuring user access for tasks and alerts in the Infor ION Desk User Guide.
In addition, the value in the Infor Ming.le IFS ION-Person ID field must match the
Workstation/Domain ID field for the same user in CloudSuite Industrial, and the User Name field
in Infor Ming.le must match either the PersonId email address or Primary email address for the
same user in CloudSuite Industrial. This is handled automatically if you set up users first in Infor
Ming.le/IFS and then use SecurityUserMaster BODs to populate the user records in CloudSuite
Industrial, as described in Configuring user access to the ERP through Infor Ming.le on page 40.

Configuring applications to process workflows for tasks

and notifications
1 Configure this application to send tasks and notifications.
2 Configure ION to process tasks and notifications from this application.
See the Infor ION Desk User Guide.
3 Configure Infor Ming.le to display tasks and notifications for this application.
See the Infor ION Desk User Guide.

Other workflow options

In addition to the ION workflow features, CloudSuite Industrial has a built-in event and workflow feature
called the Application Event System (AES). There might be times when you want to use AES instead
of the ION workflow features.
Use AES when you need to handle any of these tasks with no coding:
• Capture what is happening inside the application and take action on it. ION can only capture events
that consist of BODs being transmitted.
• Suspend an update within the application and wait for approval. The resulting workflow can be
routed out to ION and back in the UI if desired, but ION cannot suspend a transaction.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 56

 Configuring workflows and ION messages for the ERP

• Perform automated processing, like inserting orders, updating customers, etc. In AES, you can
select any IDO for any of these operations from drop-downs, and update, insert, delete, or query
without having to write code.
Use ION when you are orchestrating interactions between applications via BODs.
You can use the two systems together in a variety of ways as well-AES can send and respond to the
receipt of ION BODs.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 57

 Verifying drillbacks to the ERP through Infor Ming.le

Chapter 11: Verifying drillbacks to the ERP through

Infor Ming.le

Verify the drillbacks that are included for your application.

Available drillbacks
An Infor Ming.le search result, alert, or share can include a link to the form with a reference to specific
CloudSuite Industrial data. This type of drillback is displayed in the Infor Ming.le user interface as a
link that opens CloudSuite Industrial to a specific form filtered for specific results.
This table shows the BODs associated with drillbacks, the views that are currently available for this
drillback, and the CloudSuite Industrial form that is launched:

BOD Noun Drillback view CloudSuite Industrial form

BillToPartyMaster BillToPartyView Customers
ContactMaster ContactMasterView CustomerSalesContactCrossReferences
CustomerPartyMaster CustomerView Customers
CustomerReturn CustomerReturnView RMAs
InventoryAdjustment AdjustmentOrderView MaterialTransactions
ItemMaster ItemView Items
PayFromPartyMaster PayFromPartyView Customers
Person EmployeeView Salespersons
PurchaseOrder PurchaseOrderView PurchaseOrders
Quote QuoteView Estimates
ReceiveDelivery ReceiptView MaterialTransactions
RemitToPartyMaster RemitToPartyView Vendors
Requisition RequisitionView PurchaseOrderRequisitions
SalesOrder SalesOrderView CustomerOrders

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 58

 Verifying drillbacks to the ERP through Infor Ming.le

BOD Noun Drillback view CloudSuite Industrial form

ShipFromPartyMaster ShipFromPartyView Vendors
Shipment ShipmentView MaterialTransactions
SupplierPartyMaster SupplierView Vendors

Loading the BODs that are used in drillbacks

In order to use these drillbacks, you must perform an initial load of the BODs listed in “Available
drillbacks,” using the Replication Document Manual Request Utility in CloudSuite Industrial.
See Sending the initial data load on page 35.

Verifying a drillback
To verify that the drillbacks are working for shared links in Infor Ming.le:
1 From the App menu, open CloudSuite Industrial.
2 Open a form that has a drillback, for example, Customers.
Note: The user interface does not indicate whether a screen has a drillback. In order for a screen
to have a drillback, a drillback must be configured and a business context message must also be
sent. See Available drillbacks on page 58 and Understanding business context messages on page
61.
3 Display the information that you want to share, for example, the record for a particular customer.

4 Click the Share icon on the Infor Ming.le screen.

If prompted, click Share to Feed.
5 On the Share overlay, verify that the drillback icon is displayed, add a comment, and click Share.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 59

 Verifying drillbacks to the ERP through Infor Ming.le

6 In the Infor Ming.le feed, find the message that contains the drillback icon, and click the drillback
icon to verify that it is working.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 60

 Configuring context apps and utility apps that are used with the ERP

Chapter 12: Configuring context apps and utility apps

that are used with the ERP

On the right side of the Infor Ming.le page is a collapsible panel that hosts a series of Infor Ming.le
context and utility applications.
Context apps are lightweight applications that communicate with the application frame to present
contextual information to the user. These applications subscribe to information published by the
application frame and display relevant content only when it is available. The values and content of the
application depend on the current context (form or field) that is shown in the CloudSuite Industrial
application panel in Infor Ming.le.
Utility apps are lightweight applications that represent information unrelated to content in the application.
They do not communicate with the application frame and, if activated, show only when the application
is open.

Understanding business context messages

A business context message is a JSON message that is sent from a CloudSuite Industrial screen, field
or other user interface object to establish the current context. These messages can be used for many
contextual purposes within Infor Ming.le, including drillbacks.
Business context messages are used with context-sensitive apps when a certain CloudSuite Industrial
form is displayed:
• Determine which related files from IDM are shown in the Related Information context app, based
on the context
For more information about the available context-sensitive IDM documents, see the Infor CloudSuite
Industrial User Guide for Infor Operating Service.
To find the business context message that is sent by a specific object, use theInfor Ming.le Context
Viewer app. See the Infor Ming.le online help.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 61

 Configuring context apps and utility apps that are used with the ERP

Process default settings that allow context messages to be

sent
In CloudSuite Industrial, these options are set on the Process Defaults form:
• Send Context Message on Form Focus enables sending of business context messages for
forms. This value is automatically set to 1 for CloudSuite Industrial through initialized data. When
set to 1, the context message "screenId": "mongoose_Formname" is sent for all forms, where
Formname is the form name, for example, “screenId”: “mongoose_UsersMaint”.
• Optional Context Message Form Prefix replaces the mongoose_ default prefix on all forms with
a specified prefix. For CloudSuite Industrial, the prefix is set to CSI_. So, for example, the UsersMaint
form is sent as CSI_UsersMaint.
The context messages sent from forms allow Infor OS context apps to display context-sensitive
information related to the form.

Supported business context messages

Business context messages contain sets of contextual information called entities, which include
information similar to that of Infor BODs. CloudSuite Industrial can pass information about multiple
entities in one business context message.
When each CloudSuite Industrial form is displayed, a script runs that passes standard metadata in a
JSON message. The standard metadata includes the screen ID of the form and the logical ID of the
CloudSuite Industrial application. However, the message can contain additional context-sensitive
metadata that is specific to the form and current record.
This example shows an inforBusinessContext context message that was sent from the Customers
form:

{"type":"inforBusinessContext","data":{"screenId":"CSI_Customers","enti
ties":[{"entityType":"InforAccountingEntity","id1":"DALS"},{"entity
Type":"InforShipToPartyMaster","id1":"4851","id2":"0","accountingEnti
ty":"DALS","drillbackURL":"?LogicalId=lid://infor.syteline.dals&page=for
monly&form=Customers(FILTER(CustNum%3D%27%20%20%20%20%2013%27%20AND%20Cust
Seq%3D0)SETVARVALUES(InitialCommand%3DRefresh))","bodRefer
ence":{"noun":"BillToPartyMaster","documentId":"4851","accountingEnti
ty":"DALS","logicalId":"lid://infor.syteline.dals"}},{"entityType":"Infor
CustomerPartyMaster","id1":"4851","name":"Brand Central Dept Store","ac
countingEntity":"DALS"}]}}

The message informs context apps that the Customers form is currently displaying a record for the
Brand Central Dept Store, which has the customer ID 4851 and the Ship To address ID 0, in the
accounting entity DALS. The message contains one or more business entities, or collections of
information, associated with the current record. The entity information can include a relative URL that
can be used to drill back into the application and display the form and record. It also can include a BOD
reference that maps from the current entity in the user interface to a corresponding BOD noun.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 62

 Configuring context apps and utility apps that are used with the ERP

Any context apps that are associated with CloudSuite Industrial receive all of the information in this
message. Each context app searches its data to determine whether it has contextual information to
display that is related to information in this message.
For example, you might display the Customers form with the customer ID 4851. The Related Information
context app uses the entity type, or context, and its parameters from the message to determine if there
are any documents related to that context in its database. If so, the documents are listed in the app
and can be opened. If you drag and drop files into the Related Information app pane while this form
and record are displayed in CloudSuite Industrial, the files are automatically linked in Infor Document
Management to each of the entity types (contexts) listed in the context message.

Context and utility apps that work with the ERP

These standard context and utility apps are available for use with CloudSuite Industrial.
• Alerts
• Context Viewer
• Paparazzi
• Posts
• Related Information
• Tasks
For information about how to use most of the standard apps, see the Infor Ming.le online help or user
guide.
For information about using Related Information, see the Infor Document Management User Guide.
These application-specific context apps are also available:
• Related Information
This app can display context-sensitive files that are stored in Infor Document Management but that
are associated with specific CloudSuite records. You can set up workflows in CloudSuite Industrial
to handle this. See About the Document Management integration on page 67.

For information about how to use the other application-specific apps, see the Infor CloudSuite Industrial
User Guide for Infor Operating Service.
Some of the apps are initially disabled. When the apps are enabled for CloudSuite Industrial, their
content is displayed in small app panes to the right of your application.

Enabling a context or utility app for the ERP

To enable one or more of the context or utility apps to work with CloudSuite Industrial:
1 From the User Menu, select Admin Settings.
2 In the Manage Applications tab, double-click to select the CloudSuite Industrial application.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 63

 Configuring context apps and utility apps that are used with the ERP

3 In the Manage Context/Utility Apps tab, select the app that you want to enable.
4 in the Permissions tab for that app, either select Grant access to all users or click Add new
users and/or IFS security roles to specify certain users or roles in CloudSuite Industrial that can
access this context app.
5 In the Applications tab for that app, select your application and enable it for the app.
6 Save your changes.
In order to see the changes, you might need to sign out of the application and Infor Ming.le. Close your
browser and reopen it.

Authorizing users to display critical numbers in widgets

To enable users to view and select critical numbers for display in widgets or home pages, you must
set up the appropriate authorizations in CloudSuite Industrial.
1 In CloudSuite Industrial, open the Critical Number Users form.
2 Select a user record.
3 On the Categories tab, specify user authorizations for a critical number category, or on the
Permissions tab, specify user authorizations for specific critical numbers.
4 Save your changes.
5 Ask the user to log out of CloudSuite Industrial and then log in again, so the changes can take
effect.
6 Verify that users can view critical numbers that they are authorized to view.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 64

 Verifying Homepages for the ERP

Chapter 13: Verifying Homepages for the ERP

Homepages are a flexible and configurable way to present information and activities to users.
Administrators can build pages for various groups of users, roles, departments, or business functions.
You can select from the library of available Infor widgets or build your own.
The predefined Homepages and widgets for CloudSuite Industrial were imported automatically when
the application was added to Infor Ming.le.
In this section, you will verify that they are working for your users.
For general Homepages administration tasks, see the Infor Operating Service Administration Guide.
For information about using the homepages and widgets, see the Infor CloudSuite Industrial User
Guide for Infor Operating Service.

Verifying the homepage and widget content

1 Log into Infor Ming.le as a non-administrative user who has access to both Infor Ming.le and
CloudSuite Industrial.
2 Open the Homepages application.
3 Add a Homepage:
a Click the ellipses (…) and select Page Catalog.
b Select All to see all available homepages.
c Select one of the predefined CloudSuite Industrial Homepages, such as Controller Home or
Project Manager Home and click +.
You must be authorized in CloudSuite Industrial to open that “home page” form. These are
the default authorization groups/roles associated with each home page and its widgets:

Homepage name Security role/group

Controller Home Mobile Controller
Customer Service Home Order Entry, Service
Executive Home Mobile Executive
Inventory Control Home Inventory
Production Planner Home Shop Floor Control

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 65

 Verifying Homepages for the ERP

Homepage name Security role/group

Project Manager Home Projects
Purchasing Home Purchasing
Quality Control Home QA Process
Salesperson/Sales Manager Home Order Entry
System Administration Home System Administration

d Close the catalog to view your new Homepage. Verify that the widgets display as expected.
4 Add a CloudSuite Industrial widget to a custom homepage:
a From the ellipses (…) menu, select New Page.
b Specify a title, description and color for the page and click Create.
c Click Add Widget.
d Under Categories, select Application. You should see a lot of application-related widgets.
You can use the filter icon in the toolbar to find specific widgets.
e Select the CloudSuite Industrial widget and click + (Add Widget).
f Close the catalog and save the page to view your new widget.
g Initially the widget shows a default page. Click the ellipses (…) in the widget and select
Configure.
h Leave the Title and Application values as-is. Select a widget from the list and click Save.
You must be assigned the appropriate CloudSuite Industrial authorization group/role to display
the .home form that underlies this widget.

5 Add a critical numbers widget, and configure it. Ensure that you can view critical numbers that you
are authorized to view in this widget.
You must be authorized in CloudSuite Industrial to view the critical numbers.
6 Drill down to CloudSuite Industrial forms from the appropriate widgets.

Modifying permissions for standard pages

The CloudSuite Industrial Home pages are included in the Standard Pages tab.
If you want only a specific group of users to access the standard page, you can restrict the standard
page to a security role in Infor Ming.le.
To view or change the permissions that are assigned to a page:
1 Open the Homepages application.
2 Click the ellipses (…) button and select Advanced > Administration.
3 Click the Standard Pages link and select the home page you want to edit.
4 Select Permissions > Edit Permissions.
Note: Permissions can be set at the group, role or user level.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 66

 Configuring Infor Document Management to work with the ERP

Chapter 14: Configuring Infor Document Management

to work with the ERP

This section describes the process to integrate Infor Document Management (Document Management)
and CloudSuite Industrial.

About the Document Management integration

Some reports and documents that are generated in CloudSuite Industrial can be automatically sent to
Infor Document Management for storage. You can then view the documents in Document Management
or in the context of a CloudSuite Industrial form, through the Related Information context app. For
example, you can view a specific customer invoice while you are in that customer’s record in the
Customers form.
You can also manually add documents and tag them with CloudSuite Industrial-specific document
types, which allow them to be associated with certain CloudSuite Industrial forms.
This integration uses predefined CloudSuite Industrial document workflows, APIs that transmit the data
from CloudSuite Industrial to Document Management, and this predefined CloudSuite Industrial-specific
information in the Document Management app:
• A predefined business context model that is used to link context-sensitive documents stored in
Document Management to the appropriate forms in CloudSuite Industrial
• A set of Document Type definitions
• Access control list (ACL) security definitions
You can customize the integration to include additional document workflows, or to modify the existing
workflows. You can also customize the ERP-specific information in Document Management.
Attribute values are assigned as metadata that accompanies the documents. The attributes can be
used for filtering within Document Management, and for associating related documents in the Related
Information context app.
For example, the metadata for a purchase order includes the PO number and the number of the vendor
to whom the PO is assigned.
The API integration has this high-level flow:

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 67

 Configuring Infor Document Management to work with the ERP

In the case of failure, a notification is sent to the email address that is assigned on the CloudSuite
Industrial Users form to the user who originated the report. The PDF file that could not be stored in
Document Management is included as an attachment in the email.
CloudSuite Industrial also supports a BOD-based integration with Infor Document Capture (using
Ephesoft). See the Infor CloudSuite Industrial Integration Guide for Infor Document Capture.

Prerequisites for IDM integration

Before you start integrating Document Management with CloudSuite Industrial, ensure that these
prerequisites are met:
• The Application Event Service is configured to monitor the CloudSuite Industrial site, as described
in the CloudSuite Industrial Multi-Site Implementation Guide. As part of this, ensure that each site
which is monitored by the service has a configuration name defined on the Sites/Entities form, in
the Configuration Name field. The name in this field should exactly match the configuration name.
• On the CloudSuite Industrial Document Types form, ensure that the document type PDF exists,
with the pdf extension.
• On the CloudSuite Industrial Report Options form, verify that every defined output type matches
an extension shown on the Document Types form.
• In the Shared Groups tab on the Document Types form, for any document type that you want to
send to Document Management (including PDF), ensure that appropriate groups are assigned to
the document type. Then ensure that those groups are assigned to the users who will be generating
the documents that are sent to Document Management.
• On the Event Handlers form, verify that an event handler called TaskPostPerform is defined
and active.
• Ensure that users who will generate documents through these workflows have the IDM-User and
IDM-RelatedInformation security roles, as well as the appropriate roles to access the CloudSuite
Industrial forms, assigned in Infor Ming.le. Users who will view the generated documents in

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 68

 Configuring Infor Document Management to work with the ERP

Document Management or the Related Information context app must also have the appropriate
roles assigned.
• If you have enabled TaskMan Options and set the value to debugrep on the Process Defaults
form, then you must define a txt extension for a document type in the Document Types form. This
setting should only be used for report debugging purposes, and must be removed as soon as
testing is done.

Setting up the IDM connection in the ERP

In CloudSuite Industrial, set up the IDM integration:
1 Use the External App Parameters form to set up the connection to Document Management.
You must use this form at each site to set up a connection to the Document Management application.
Multiple sites can connect to the same instance of Document Management. Specify this information:
Note: If Infor OS is in the Cloud, your Infor representative can provide the URL and connection
information.
Application Name
Specify IDM.

Application Instance
If you are defining more than one instance of Document Management, describe the difference.

URL
Specify the URL of the Document Management application, typically
https://hostname.infor.com:9543/ca.
If Infor OS is in the Cloud, you can find the URL in the Control Center home page of the Document
Management application.

Authorization Method
If you select OAuth1, the API call functions as a back-end service, facilitating the impersonation
of the user who is actually creating the documents. In this case, specify the consumer key as the
User Name and the secret key as the Password. We recommend that you use the OAuth1 method
so that multiple CloudSuite Industrial users can generate reports and send them to IDM.
For help obtaining the OAuth user name and password, contact Document Management support
by logging a support incident and selecting Infor Document Management as the product line.
If you select Basic, IFS user authentication is used. In this case, specify a domain name and
password.
CloudSuite Industrial users are matched to Document Management users through the Infor Ming.le
(IFS) GUID value, which is shown in the Workstation/Domain ID field of the Users form.

Is Active
Ensure that this field is selected for the instance of Document Management that you want to use.

See the online help for assistance with the fields on this form.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 69

 Configuring Infor Document Management to work with the ERP

2 Click Verify. If a green check mark is displayed beside the button, the connection is working. If a
red X is displayed, the connection is not working.

Importing ERP-related definitions into Document

Management
1 Log into the Infor Support Portal site and select Downloads > Products to go to the Download
Center.
2 From the Product List, select Infor > Enterprise Resource Planning > Infor CloudSuite Business
& Industrial (SyteLine). Select the appropriate version of Infor CloudSuite Industrial.
3 Download the IDM_Configuration.xml file to a local folder from the CloudSuite Industrial
Download Center on the Infor Support Portal site.
This file contains document type definitions, Access Control List (ACL) security definitions, and a
business context model (BCM) that is used to link context-sensitive documents stored in Document
Management to the appropriate forms in CloudSuite Industrial.
4 In Infor OS, open the Document Management app as a user with the IDM-Administrator role.
5 Click the ellipses (…) and select Control Center.
6 Select Administration > Import/Export.
7 Click the Import tab.
8 Browse to the IDM_Configuration file from step 3.
Depending on the version of Document Management, you might see a message that shows the
impact of the import configuration file.
9 Click Import.
10 To confirm that the import was successful, return to the Documents page, click Document Type
and look for items with a “CS_” prefix.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 70

 Configuring Infor Document Management to work with the ERP

Activating the IDM workflows in the ERP

When CloudSuite Industrial users generate a document that has an active workflow, the document is
sent to Document Management. To activate the workflows:
1 In CloudSuite Industrial, open the IDM Document Workflows form.
2 Select Active for each predefined workflow if you want that type of document to be sent to Document
Management. Your choices should be based on business decisions for the company.

Note: Any generated output format from a workflow background task must have a Document Type
record associated with that extension and appropriate groups assigned.
3 Save your changes.
Later, you could use the advanced features on this form, along with the Application Event System, to
customize the integration. See the online help for assistance with the advanced fields.

Verifying the configuration for IDM workflows

After the configuration is set up in all applications, use these steps to generate a document in CloudSuite
Industrial and verify that the document is available, with the appropriate attributes, in Document
Management.
For verification purposes, just ensure that the PO report is generated and displayed:
1 In CloudSuite Industrial, open the Purchase Order Report form and print a purchase order.
2 Open the IDM Workflow Logs form and verify that a record exists for the new PO.
See the online help for an explanation of the fields on this form.
3 In the Infor Document Management application, verify that you can find and preview the document
using these options in the Search:
Document Type
Specify CS_PurchaseOrder.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 71

 Configuring Infor Document Management to work with the ERP

Property or Attribute
Verify that these attributes are in the list: Purchase Order and Vendor Number. Select
Purchase Order.

Operation
Select Like.

Search Value
Specify the PO number. Use the % wildcard character to allow for leading and trailing spaces.

4 In CloudSuite Industrial, open the Vendors form.

5 Select the vendor associated with the purchase order number that you printed.
In the Related Information context app, the document should be displayed automatically. The
default entity type is All, which displays any document that matches the current record.
6 Verify that you can preview the purchase order.
If you encounter problems with workflows, see the help topic on troubleshooting IDM workflows.

Configuring Infor Document Capture with Infor OS

Infor Document Capture (Ephesoft Transact) enables you to convert a high volume of unstructured
document data from multiple formats into structured information by using machine learning and analytics.
The automated conversion of document data categorizes each document by type and captures and
stores relevant data for each document, providing greater efficiency, productivity, and a more detailed
analysis of your business processes within the ERP.
To configure Document Capture with CloudSuite Industrial, see the Infor CloudSuite Industrial Integration
Guide for Infor Document Capture.

Other document management options

In addition to the features of the Document Management application, there are document management
features built into CloudSuite Industrial. The CloudSuite Industrial built-in feature can associate
documents with IDO rows and IDOs. There might be times when you need to use these features instead
of, or in combination with, the Document Management features.
See the CloudSuite Industrial help topic about working with document (file) attachments.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 72

 User and role BOD usage

Appendix A: User and role BOD usage

This appendix provides detailed information about how the security BODs are used between CloudSuite
Industrial and Infor Ming.le.

BODs that send roles (authorization groups) from the

ERP to Infor Ming.le
Some authorization groups from CloudSuite Industrial are preconfigured as security roles in Infor
Ming.le when the CloudSuite Industrial application is added in Infor Ming.le.
When you create or edit an authorization group in CloudSuite Industrial, a Sync.SecurityRoleMaster
BOD is generated. This BOD is defined at the tenant level. The information from this BOD is used in
Infor Ming.le to automatically create a matching security role. The name of the role created in The
name of the role created in Infor Ming.le depends on whether the group name is currently mapped to
an External Role Alias. If so, the alias is used. If not, the group name is used.
Note: Remember that CloudSuite Industrial is the system of record for roles/groups. It sends the
Sync.SecurityRoleMaster BOD when a group is created or changed in CloudSuite Industrial.
Alternatively, you can create a security role in Infor Ming.le that does not exist in CloudSuite Industrial.
If you assign that role to a user, then when Infor Ming.leInfor Ming.le sends the Sync.SecurityUserMaster
BOD for that user to CloudSuite Industrial, CloudSuite Industrial automatically creates a “placeholder”
group for that role. (First, it checks both the External Role Alias table, for license modules, and the
Groups table, to make sure the Infor Ming.le security role does not already exist in CloudSuite Industrial.
If not, CloudSuite Industrial assigns the placeholder group to the user.) The placeholder group is just
a name and description, with no assigned privileges. CloudSuite Industrial then sends a
Sync.SecurityRoleMaster BOD back to Infor Ming.le for the new group/role.
If you delete a role in either CloudSuite Industrial or Infor Ming.le, you must also delete the corresponding
role in the other application.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 73

 User and role BOD usage

Person IDs
Any CloudSuite Industrial users who plan to use Infor Ming.le or other Infor OS components must be
set up as users in Infor Ming.le, and the user’s Person ID must be synchronized between Infor Ming.le
and CloudSuite Industrial.

Person IDs in Infor Ming.le

The user details page in Infor Ming.le includes an ERP Person ID tab. The ERP Person ID tab is
populated if CloudSuite Industrial publishes the Sync Person BOD. The ERP Person ID is used as the
identifier of the user in the ERP application, and allows you to link the Infor Ming.le user to the ERP
application user. The ERP Person ID tab shows all ERP person IDs that are associated with this Infor
Ming.le user.
The IFS ION-Person ID is used as the user identifier in ION, which then links the Infor Ming.le user
with the ION BODs. By default, the IFS ION-Person ID is set to the User Principal Name (UPN) of the
user. UPN is an AD FS concept.
The IFS Globally Unique Identifier (GUID) is the same as the UPN.

Sending the Person ID from the ERP to Infor Ming.le

When certain information is manually added or updated in CloudSuite Industrial for a user, a
Process.SecurityUserMaster BOD is published by CloudSuite Industrial.
The Workstation/Domain ID field on the Users form in CloudSuite Industrial contains the IFS
ION-Person ID for a user. This value should not be changed. It is possible to update this value in
CloudSuite Industrial and then manually publish the Process.SecurityUserMaster BOD to Infor Ming.le;
however, Infor Ming.le is the system of record for user information, so you should only maintain the
IFS ION-Person ID value In Infor Ming.le.

BODs that send user information from Infor Ming.le to

the ERP
When you add a user in the Infor Ming.le portal, a SecurityUserMaster BOD is sent through ION to
your application at the specified intervals, where a matching user record is created or updated. This
BOD contains the user name, login, creation date, status, description, email address, and the roles,
or groups, to which the user is assigned.
Infor Ming.le is the system of record for the SecurityUserMaster BOD.
When CloudSuite Industrial receives the BOD, these actions occur:

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 74

 User and role BOD usage

• For a new user that does not exist in CloudSuite Industrial:

• A new user record is added.
• The Workstation Domain/ID field is populated with a row pointer value that should not be
changed.
• The group authorizations for that user are added.
• By default, the Transactional license module is assigned to all new users in CloudSuite Industrial.
(In a usage-tracking environment, this assignment is ignored.)
• In addition, if any CSI-License-xxxx security roles were assigned to the user in Infor Ming.le,
the matching license modules are assigned in CloudSuite Industrial, as mapped in the External
Role Alias form. (In a usage-tracking environment, this assignment is ignored.)
• A primary email type description is added that contains the user’s email address.
• The user’s First Name and Last Name values from Infor Ming.le are combined into the
CloudSuite Industrial User Description field, separated by a space.
• For an existing user in CloudSuite Industrial:
• The user status, user descriptions, and primary email address are updated.
• The user record is updated with any new user group authorizations, user modules, based on
the assignments in Infor Ming.le.
• An Acknowledge SecurityUserMaster BOD is sent back to Infor Ming.le.

About the "Keep Groups in SecurityUserMaster" process default

You can set a process default in the Process Defaults form that determines how the groups assigned
to a user should be treated in CloudSuite Industrial when synchronizing user records with Infor Ming.le:
• When set to 0 or left as null (the default), any groups that are assigned to the user in CloudSuite
Industrial, but that are not referenced by (or known by) Infor Ming.le are automatically removed
from the user record in CloudSuite Industrial during synchronization.
• When set to 1, the default behavior is overridden and the groups assigned to the user are left intact
in CloudSuite Industrial. In this case, if you want to remove a group membership for a user in
CloudSuite Industrial you must remove it manually on the Users form.
Note: This process default has no effect on the ability to add roles to users in Infor Ming.le, which end
up as group memberships for that user in CloudSuite Industrial. It also has no effect on whether the
role/group itself is deleted entirely from the application.

About the "Keep Modules in SecurityUserMaster" process default

This process default handles license module updates the same way that the "Keep Groups in
SecurityUserMaster" process default handles updates for groups.

BODs that send user information from the ERP to Infor

Ming.le
When any of this information is manually added or updated in CloudSuite Industrial for a user, a
Process.SecurityUserMaster BOD is published by CloudSuite Industrial:

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 75

 User and role BOD usage

• User login status

• User description: A value is required in this field if you are passing user information from CloudSuite
Industrial to Infor Ming.le through the Process SecurityUserMaster BOD. The field must contain
values separated by a space. The first value becomes the First Name in Infor Ming.le. Everything
after the space becomes the Last Name in Infor Ming.le. For example, if the CloudSuite Industrial
User Description is Tom Van Winkle, Tom is the First Name and Van Winkle is the Last Name in
Infor Ming.le.
• Workstation login
• Primary email address: A value is required in this field if you are passing user information from
CloudSuite Industrial to Infor Ming.le through the Process SecurityUserMaster BOD.
• Group authorizations
• License modules (In a usage-tracking environment, this information is ignored.)
However, if the user information was changed in CloudSuite Industrial because of an incoming
Sync.SecurityUserMaster BOD from Infor Ming.le, the Process.SecurityUserMaster BOD is not published.

CloudSuite Portals users

If a new user is created in CloudSuite Industrial based on a request from the CloudSuite vendor,
customer or reseller portals, the BOD is not sent to Infor Ming.le.
See the portal administration guide for information about creating new portal users.

Adding users in the ERP

It is possible to add users in CloudSuite Industrial rather than in Infor Ming.le. If the user information
is set up correctly, it will be transmitted in the Process.SecurityUserMaster BOD to Infor Ming.le and
the user is created automatically there, too.
Note: This method is not recommended, because Infor Ming.le is the system of record for users. We
recommend that you instead use the method described in Configuring user access to the ERP through
Infor Ming.le on page 40.
1 If you are using AD FS, create the user in AD FS before you add the user in CloudSuite Industrial.
Otherwise, Infor Ming.le will reject the BOD.
2 In the CloudSuite Industrial Users form, specify this information:
User Name
Specify the user name in the format domain_name\user_name.

Workstation Domain/ID
Specify the user name in the format domain_name\user_name.

Email Type Address

For the Primary email address, specify the user's email address.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 76

 User and role BOD usage

3 For the rest of the field values, see the online help.
4 After the Process.SecurityUserMaster BOD is received by Infor Ming.le, the user is created there.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 77

 Troubleshooting

Appendix B: Troubleshooting

This section describes actions that you can perform to solve Infor OS integration issues.

Data is not flowing properly

Cause: A problem is preventing the flow of BOD data to ION.
Solution: After you complete the configuration setup, if BOD data is not flowing to ION, use ION OneView
to identify the problem.
ION OneView can be found in the menu for ION Desk. You can perform these actions in ION OneView:
• Track business documents from a single consolidated view; search for documents using different
search criteria.
• View all ION components that were triggered by the incoming document: Connection Points;
document flow filters and content-based routing; mappings; ION engines for example, Monitor,
Workflow, and Pulse; monitors; activation policies and workflows.
• View more details about these ION components:
• Detailed properties for each ION component
• List of events that were logged by each ION component while processing the message
• Drilldown views that are used to display the appropriate management pages for the selected
ION component
• Visibility and correlation of the different messages sent or generated:
• Original BOD messages that triggered the whole list of components displayed; Confirm BOD
messages that were generated due to any error while processing the Original BOD message.
Mapped/Updated BOD messages that were created during the processing of the Original BOD
message
• View content of BOD messages. This information is only available to authorized users, based
on the roles and permissions that are configured.
For more information, see the section on ION OneView in the Infor ION Desk User Guide.
To avoid business discrepancies between this application and integrated applications, correct any
errors as soon possible.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 78

 Troubleshooting

BOD information needs to be purged

Information from every inbound BOD, including sequencing information, is collected in a table in the
CloudSuite Industrial application. This data constantly builds up and, over time, could cause performance
issues. For this reason, system administrators should periodically use the Purge BOD Information
form to purge information from that table. You can set up a background task to perform this function
automatically
You can also use the Replication Document Inbox/Outbox Utilities form to clear out older BODs
from the Replication Document Inbox and Replication Document Outbox.

ERP help is not working

Verify that the user’s web browser has popup blockers turned off. Clear the browser cache, restart
Infor Ming.le and try again.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 79

 Business events that generate outbound BODs

Appendix C: Business events that generate outbound

BODs

This table shows the events, which are user actions in CloudSuite Industrial that generate an outbound
BOD from CloudSuite Industrial:

Verb Noun User action to generate the BOD

Process AccountingBookDefinition Run the Replication Document Manual Request
Utility with AccountingBookDefinition selected.
This should be done once per site.
Sync AccountingChart Run the Replication Document Manual Request
Utility with AccountingChart selected. This should
be done once per site, after the Chart of Ac-
counts is set up at the site.
Sync AccountingEntity Run the Replication Document Manual Request
Utility with AccountingEntity selected. This should
be done once per site, after the tenant ID is set
up at the site.
Process AdvanceShipNotice * Ship the order, either manually with the Trans-
fer Order Ship form, or automatically in response
to a received Sync Shipment BOD.
* Perform material transactions that remove in-
ventory tied to these types of orders: Project,
Job, Customer Order, Purchase Order (with a
negative quantity), RMA, Production Order or
Transfer Order.
* Run the Multi-Site Quantity Move utility.
Acknowledge BillofMaterials Acknowledge the receipt of a BillofMaterials from
an external application.
Sync BillofMaterials Indicate that changes have been made in the
application after receipt of a Process BillofMate-
rials from an external application

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 80

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync BillofResources Perform a cost rollup in:
* Current BOM Cost Roll Up form (current item
BillOfResources BOD)
* Single Level Current BOM Cost Roll Up form
(current item BillOfResources BOD)
* Roll Current Cost to Standard Cost form (finan-
cial standard BillOfResources BOD)
(BOD is not currently active)
Acknowledge BillToPartyMaster Acknowledge the receipt of a BillToPartyMaster
from an external application.
Sync BillToPartyMaster Change any information on the Customers form.
Change any information on the Ship Tos form.
Confirm BOD The system could not process a BOD sent from
another system because of validation or other
errors.
Sync Calendar * Delete a Resource Group.
* Add or update a resource on the Resources
form (creates a BOD for each shift line)
* Add or update a Resource Group, or change
the elements of a group (creates a BOD for each
shift line that is affected)
* Add or update a shift calendar in Scheduling
Shifts.
* Update a Shift Exception (creates a BOD for
the affected resource with WORKFG (Work) set
to Y if the resource is free or N (Down Time) if
the resource is busy.
* Update a resource schedule (creates a BOD
for the affected resource and resource group,
indicating that the resource is busy).
* Add a holiday. This creates a BOD that indi-
cates all resources are busy on that day.
Sync CarrierRoute Select the Physically Shipped check box on the
Special tab of the Delivery Orders form.
Sync ChartOfAccounts Create or update an account record in the Chart
of Accounts form. Statistical and allocation ac-
counts are not included.
Acknowledge CodeDefinition Acknowledge the receipt of a CodeDefinition
from an external application

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 81

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync CodeDefinition * Add or update Billing Terms
* Add an Education Major
* Add a Certification/License
* Add a Commodity Code
* Add an External Expense Type
* Add an Indirect Labor Code
* Add an Inventory Adjustment Reason Code
* Add or update an ISO U/M on the Unit of Mea-
sure Codes form
* Add an Item Category
* Add an Obsolete Slow Moving Reason Code
* Add an Opportunity Source
* Add an Opportunity Stage
* Add a Payment Type
* Add a Position
* Add a Price Code
* Add a Product Code
* Add a Project Cost Code
* Add a Province/State
* Add a Shift ID on the Scheduling Shifts form
* Add a Ship Via Code
* Add a Skill
* Add a Tax Code of type Exempt
* Add a Tax Jurisdiction
* Add a Territory
* Add a Training Course
* Add a unit code on the Unit Code 1 - 4 forms
* Add a Work Code
* Add a Work Experience
BODS for some other codes, such as language
IDs and cost methods, are automatically gener-
ated when the Replication Document Manual
Request Utility is run.
Process ConstrainedResource Insert or modify a Shift ID (creates a BOD for
associated resources)
Acknowledge ContactMaster Acknowledge the receipt of a ContactMaster from
an external application

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 82

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync ContactMaster * Add or change a Contact
* Create a Customer Sales Contact Cross-Refer-
ence
Sync Contract * Add or update Customer Order header
* Add or update Customer Order Blanket Line
Sync CreditTransfer * Create a Bank Reconciliations record for a
vendor payment, employee payment, or cus-
tomer payment
* If certain country packs such as Sweden or
Poland are enabled, only vendor payments from
the AP EFT and Wire Payments form are used
to generate a CreditTransfer BOD. Employee or
customer payments do not generate this BOD.
Sync CurrencyExchangeRateMaster Add or update a Currency Rate
Acknowledge CustomerPartyMaster Acknowledge the receipt of a CustomerPartyMas-
ter from an external application
Sync CustomerPartyMaster Change any information on the Customers,
Prospects, Customer Sales Contact Cross Ref-
erences, or Sales Contact Salesperson Cross-
References, or Customer ShipTos form
Sync CustomerReturn * Print the RMA Order Verification Report
* Change the status of an RMA
Sync DebitTransfer Post a direct debit transaction from a customer
on the A/R Direct Debit Posting form.
Acknowledge ExpenseReport Acknowledge the receipt of an expense report.
Sync FinancialCalendar * Change any information on the Accounting
Periods form
* Run the change Reports To Entity utility
Sync InventoryAdjustment * Perform Quantity Adjustment
* Perform Miscellaneous Receipt or Miscella-
neous Issue
* Perform Cycle Count Posting - one BOD is
generated for each combination of item, ware-
house, and location where the quantity on hand
has changed
* Perform Physical Inventory Posting - one BOD
is generated for each combination of item,
warehouse, and location where the quantity on
hand has changed

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 83

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync InventoryCount * Run the Cycle Count Posting utility
* Run the Physical Inventory Posting utility
One InventoryCount BOD is sent for each
item/warehouse combination
Sync InventoryHold Change either of these for an Item Stockroom
Location record: Location Type or Non-Nettable
Flag
(BOD is not currently active.)
Sync Invoice * Print and post an invoice through the Consoli-
dated Invoicing form
* Post an invoice through the Invoice Posting
(A/R) form
Note: The Invoice BOD publishes one line for
every order line included in the Invoice. When
Line Summarization is turned on in Consolidated
Invoicing, the summary invoice lines are not
published; instead, each customer order line will
be published as a line in the Invoice BOD.
Acknowledge ItemMaster Acknowledge the receipt of an item from an ex-
ternal application.
Sync ItemMaster * Create a new item on the Items form
* Make a change to these fields on the Items
form: Item, Description, ABC Code, Commodity,
Cost Method, Material Status, Reason, Back-
flush, Last Change, U/M, Unit Cost, S/N Track,
Lot Track, Source, Order Minimum, Order Maxi-
mum, Alternate Item, Country of Origin
* Add or change an item description on the Multi-
Lingual Items form
Sync LCLTradeStatistics * Print EU Sales List Report
* Print SSD Transaction Listing Report
Sync Location * Create a new Warehouse
* Update General Parameters form (creates a
Location BOD with the site as the location)
Sync Opportunity * Create or update a record on the Opportunities,
Customer Orders, or Opportunity Tasks form
* Delete an Opportunity

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 84

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync PayableTracker * Post a voucher or an Adjustment through the
A/P Voucher Posting form
* Post a payment from any of these forms: A/P
Check Printing/Posting, A/P Draft Printing/Post-
ing, A/P EFT Posting, A/P Wire Posting
Sync PayableTransaction * Post a voucher through the A/P Voucher Post-
ing form
* Post a payment from any of these forms: A/P
Check Printing/Posting, A/P Draft Printing/Post-
ing, A/P EFT Posting, A/P Wire Posting
* Set or release a Hold status on a voucher
Acknowledge PayFromPartyMaster Acknowledge the receipt of a PayFromPartyMas-
ter from an external application
Sync PayFromPartyMaster * Change any information on the Customers form
* Change any information on the Ship Tos form
Sync Person * Add or update information about a salesperson
or sales manager on the Salespersons form
* Update information related to a salesperson on
the Employees form (for employee sales people)
or Vendors form (for outside sales people)
Sync Personnel * Add or update information on these forms:
Employee, Employee Skills, Employee Cert/Li-
cense, Employee Education, Employee Training
Courses, Employee Work Experience, or Employ-
ee Position
Acknowledge PlanningSchedule Acknowledge the receipt of a Planning Schedule
from an external application.
Acknowledge ProductionOrder Acknowledge the receipt of a ProductionOrder
from an external application

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 85

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync ProductionOrder * Applied filters on the Background Task gener-
ate this BOD for a firm job that is scheduled for
the first time. This does not apply to jobs that
have just been processed by the TriggerProduc-
tionOrderBGSyncSp Background task. You can
add subsequent filters to reduce the number of
BODs triggered by this task. Without filtering,
after every scheduling or planning function a
significant number of BODs could be created.
* Delete a job or production schedule release,
where the job status is not Firm or the production
schedule status is not Planned.
* Change the status of a job or production
schedule.
* Change the Qty Released of a job or production
schedule when the status is Released.
Notes: Creating a job generates this BOD, but
changes to a firm job do not generate this BOD.
This BOD must be included in an initial load of
ProductionOrder data.
Sync ProductionReceiver * Create or update an unposted job transaction
that moves inventory into stock for a job order
or a co-product job order
* Delete an Unposted Job Transaction that was
to receive inventory.
(BOD is not currently active)
Sync ProjectMaster Create a Project or update the project status on
the project header.
Process PulseAlert One or more of these publications is triggered
by a system event: CustomerCreditHoldAlert;
CustomerInteractionFollowupAlert Cus-
tomerOrderCreditHoldAlert; CustomerShipmen-
tAlert; DCShopFloorTransactionErrorAlert; Job-
MaterialCostAlert; JobOperationHoursAlert;
JobOverProductionAlert; JobProjectedLateFor-
CustomerAlert; LateOrderShippingAlert;LeadAs-
signedAlert; LockedUserAlert; OpportunityDueAl-
ert; OverBudgetAlert; ProjectedLateShipAlert;
ProspectInteractionFollowupAlert; Scheduled-
MaintenanceAddedAlert; ScheduledMainte-
nanceAlert; TransactionAmountAlert
Note: This BOD is not related to the Replication
Document forms.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 86

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync PurchaseOrder * Print the Purchase Order Report
* Print the Builder Purchase Order Report
* Change the Purchase Order status to Complete
* Delete a Purchase Order
* Print a Change Order Report
Acknowledge Quote Acknowledge the receipt of a Quote from an ex-
ternal application.
Sync Quote Change the Estimate status to Quoted
* Delete an Estimate
Sync ReceivableTracker Create an invoice, payment, credit memo, debit
memo or finance charge transaction for a cus-
tomer with a 'Balance Forward' balance method.
Sync ReceivableTransaction * Generate an invoice for customers with an
'Open Item' balance method. The status is set
as Open.
* Generate a debit memo/finance charge for
customers with an 'Open Item' balance method.
The status is set as Open.
* Make a payment and apply it to an invoice for
customers with an 'Open Items' balance method.
The status changes to Paid.
* Generate a credit memo and attach it to an in-
voice for customers with an 'Open Item' balance
method. This changes the status to Paid.
(For bullet points 2, 3, and 4: If all or part of the
debit memo/finance charge, payment, or credit
memo is left unapplied, a second BOD is gener-
ated. Similar transactions are grouped and
shown under an invoice number '0' with a status
of Unapplied Cash.)* Create an invoice, payment,
credit memo, debit memo or finance charge
transaction for a customer with a 'Balance For-
ward' balance method. The system maintains
one balance under invoice number '0'. Its status
is set as follows: for a debit balance, the status
is set as Paid; for a credit balance, the status is
set as UnappliedCash.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 87

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync ReceiveDelivery * Perform material transactions that add inventory
tied to these types of orders: Project, Job, Cus-
tomer Order (with a negative quantity), Purchase
Order, RMA, Production Order or Transfer Order
that cause a material transaction to occur
* Run the Multi-Site Quantity Move utility
When Poland Country Pack is enabled, Re-
ceiveDeliveryPL is sent instead
Sync RemittanceAdvice * Post a payment from any of these forms: A/P
Check Printing/Posting, A/P Draft Printing/Post-
ing, A/P EFT Posting, A/P Wire Posting, or
Print/Post Payroll Checks
Sync RemitToPartyMaster * Add or update Vendor information
* Update the vendor's address information
* Update Bank Address information
Acknowledge Requisition Acknowledge receipt of a Requisition from an
external application
Sync Requisition * Print the requisition on either the Purchase
Requisition Report or the PO Requisition Report
forms
* Delete a requisition
* Convert a requisition to a purchase order
* Convert additional items on an existing requisi-
tion (in this case, another BOD is created, replac-
ing the original BOD)
Acknowledge SalesOrder Acknowledge the receipt of a SalesOrder from
an external application
Sync SalesOrder * Print the Customer Order Verification Report
* Delete an order
* Change order header status to Completed
Sync SecurityPermissionMaster Add, delete or change the objects that a group
or user can access.
Sync SecurityRoleMaster Add or delete a group authorization, change the
group description, or change the permissions
associated with the group..
Acknowledge SecurityUserMaster Acknowledge the receipt of a SecurityUserMaster
from an external application.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 88

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Process SecurityUserMaster Add or change the user status, user description
or workstation login, or add/change a group as-
signed to the user.
Sync ServiceOrder Add or update Service Order or Service Order
Operations or Lines.
Sync ShipFromPartyMaster * Add or update Vendor information
* Update the vendor's address information
* Update Bank Address information
Process Shipment * For customer orders or lines that are assigned
to the local site and that are assigned to an ex-
ternal controlled warehouse, print the Order
Verification Report.
* For transfer orders or lines where the Ship
From site is the local site and the Ship From
warehouse is an external controlled warehouse,
print the Transfer Order Report.
When Poland Country Pack is enabled, Shipment-
PL is sent instead
Sync Shipment * Perform material transactions that remove in-
ventory tied to these types of orders: Project,
Job, Customer Order, Purchase Order (with a
negative quantity), RMA, Production Order or
Transfer Order
* Run the Multi-Site Quantity Move utility
Acknowledge ShipmentSchedule Acknowledge the receipt of a ShipmentSchedule
from an external application
Acknowledge ShipToPartyMaster Acknowledge the receipt of a ShipToPartyMaster
from an external application
Sync ShipToPartyMaster * Change any information on the Customers
form, Ship Tos form, or Customer Sales Contact
Cross References form
Sync SourceSystemGLMovement * Run the Change Reports To Entity utility
* Run the Copy Balances to Budgets utility
* Modify Chart of Accounts Budget and Plan in-
formation
* Run the Rebalance Ledger Period Totals utility
* Run Ledger Posting for Journals
* Run the Mass Journal Posting utility
Sync SourceSystemJournalEntry * Post journal entries to a ledger

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 89

 Business events that generate outbound BODs

Verb Noun User action to generate the BOD

Sync SupplierBalance * Change the price on a Purchase Order Line
* Change the status or vendor on a Purchase
Order
(BOD is not currently active)
Sync SupplierInvoice * Post voucher
Sync SupplierPartyMaster * Add or update Vendor information
* Update the vendor's address information
* Update Bank Address information
Sync Transfer * Perform a Transfer Order Ship
* Perform a Transfer Order Receive
* Perform a Combined Transfer Order Ship/Re-
ceive
Sync WorkCenter Add a Work Center

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 90

 Inbound BOD usage

Appendix D: Inbound BOD usage

This table shows the incoming BODs that CloudSuite Industrial can accept. It also indicates, when
possible, what area of CloudSuite Industrial shows the processed inbound data.

Destination of processed data in

Verb Noun CloudSuite Industrial
Load BankStatement Bank Statements form, and A/P automat-
ic payments generated
Process BillOfMaterials Engineering Workbench, Current Opera-
tions, Engineering Board
Process BillToPartyMaster Customers form and related forms
Process ChartOfAccounts chart table
Process CodeDefinition Depends on type of code
Sync CodeDefinition Depends on type of code.
Process ContactMaster Contacts form and related forms
Process CurrencyExchangeRateMaster currate table
Process CustomerPartyMaster Customers form and related forms
Sync EmployeeTimesheet Service order transactions, attendance,
project Labor transactions, unposted job
transactions (Indirect, Run or Setup)
Sync EmployeeWorkSchedule Employee absence/time-off forms
Sync ExpenseReport prtrx table
Sync InventoryAdjustment Miscellaneous Receipt and Miscella-
neous Issue forms
Sync InventoryCount Miscellaneous Receipt and Miscella-
neous Issue forms
Process ItemMaster Items form and related forms
Process PayableTransaction Updates Vendor Paid YTD, Paid Fiscal
YTD and Last Paid Date
Sync Personnel Employees form and tables

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 91

 Inbound BOD usage

Destination of processed data in

Verb Noun CloudSuite Industrial
Sync PlanningSchedule coitem table (blanket items)
Process ProductionOrder job table
Process Quote Estimates form and related forms
Acknowledge PulseAlert N/A
Process ReceivableTransaction Updates Customer Posted Balance
Sync ReceiveDelivery If Type=”Transfer” and Status=”Re-
ceived” create transfer order receipt.
If Type=”Purchase Order” and Sta-
tus=”Received”create PO receipt
If Type=“Customer Return” create RMA
receipt
If Type=“Sales Order” create negative
CO receipt.
Process Requisition preq table
Process SalesOrder Customer Orders form and related forms
Sync SecurityUserMaster coitem or trnitem table (depending on
record type), last_external_ship-
ment_doc_id
Acnowledge Shipment If Type=“Transfer” and Status=”Shipped”
create Transfer Order Shipment
If Type=“Purchase Order” create Pur-
chase Order Return
If Type=“Sales Order” and Sta-
tus=”Shipped” create Customer Order
Shipment
Sync Shipment coitem or trnitem table (depending on
record type), last_external_ship-
ment_doc_id
Sync ShipmentSchedule coitem table (blanket items)
Process ShipToPartyMaster Customer Ship Tos form and related
forms
Load SupplierInvoice Creates an unposted AP voucher that
must be manually cross-referenced to a
PO.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 92

 BODs used in integrations with this application

Appendix E: BODs used in integrations with this

application

This section contains the list of BODs that are available for integrations with CloudSuite Industrial.

Outbound BODs from the ERP to integrated

applications
This table shows the BODs that are available with CloudSuite Industrial. Where the application is blank,
the BOD is not currently used by interfacing applications, but the BOD is generated by CloudSuite
Industrial and is available to be processed through ION and any application that is set up to receive it.

Verb Noun To applications

Sync AccountingChart d/EPM
Infor Localization Services
Sync AccountingEntity d/EPM
Infor Localization Services
Process AdvanceShipNotice CloudSuite WMS Warehouse
Management
Acknowledge BankStatement Infor Localization Services
Sync BillToPartyMaster CPQ/EQ
CRM
e-Commerce
CloudSuite WMS Warehouse
Management
Sync ChartOfAccounts d/EPM
Infor Localization Services

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 93

 BODs used in integrations with this application

Verb Noun To applications

Sync CodeDefinition CPQ/EQ
CRM
d/EPM
EAM
Expense Management
Infor Localization Services
Sync ContactMaster CRM
CurrencyExchangeRateMaster CPQ/EQ
Sync Expense Management
Sync CustomerPartyMaster CPQ/EQ
CRM
e-Commerce
Infor Localization Services
CloudSuite WMS Warehouse
Management
Sync CustomerReturn CRM
Sync DebitTransfer Infor Localization Services
Sync FinancialCalendar Infor Localization Services
Sync InventoryAdjustment Infor Localization Services
Sync InventoryCount Infor Localization Services
Sync InventoryHold Infor Localization Services
Sync Invoice CRM
e-Commerce
Infor Localization Services
Sync ItemMaster CPQ/EQ
CRM
e-Commerce
Infor Localization Services
CloudSuite WMS Warehouse
Management
Sync Location CRM
e-Commerce
Infor Localization Services
Sync PayableTracker Infor Localization Services
Sync PayFromPartyMaster CRM

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 94

 BODs used in integrations with this application

Verb Noun To applications

Sync Person CRM
Sync Personnel Expense Management
Sync ProductionOrder Expense Management
Sync ProjectMaster Expense Management
Process PulseAlert Infor Ming.le
Sync PurchaseOrder EAM
CloudSuite WMS Warehouse
Management
Sync Quote CPQ/EQ
CRM
Sync ReceivableTracker Infor Localization Services
Sync ReceivableTransaction CRM
Infor Localization Services
Sync ReceiveDelivery (sends Re- EAM
ceiveDeliveryPL when Poland Infor Localization Services
Country Pack is enabled)
CloudSuite WMS Warehouse
Management
Sync RemittanceAdvice Expense Management
Acknowledge Requisition EAM
Sync SalesOrder CRM
e-Commerce
Sync SecurityPermissionMaster IRC ( Approva)
Sync SecurityRoleMaster Infor Ming.le
IRC (Approva)
Process SecurityUserMaster Infor Ming.le
IRC (Approva)
Sync ServiceOrder Expense Management
Sync ShipFromPartyMaster Infor Localization Services
CloudSuite WMS
Process Shipment (sends ShipmentPL Infor Localization Services
when Poland Country Pack is CloudSuite WMS
enabled)
Sync Shipment CRM
e-Commerce

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 95

 BODs used in integrations with this application

Verb Noun To applications

Sync ShipToPartyMaster CPQ/EQ
CRM
e-Commerce
Infor Localization Services
CloudSuite WMS Warehouse
Management
Sync SourceSystemGLMovement d/EPM
Infor Localization Services
Sync SourceSystemJournalEntry d/EPM
Infor Localization Services
Sync SupplierInvoice Infor Localization Services
Sync SupplierPartyMaster EAM
CloudSuite WMS Warehouse
Management
Infor Localization Services

Inbound BODs to the ERP from integrated applications

This table shows the BODs that can be received and processed by CloudSuite Industrial. Where the
application is blank, the BOD is not currently used by integrating applications.

Verb Noun From applications

Load BankStatement Infor Localization Services
Process BillToPartyMaster CRM
Sync CaptureDocument Document Management
Sync CodeDefinition Global HR
Process ContactMaster CRM
Process CustomerPartyMaster CRM
Sync EmployeeTimesheet Expense Management
Sync EmployeeWorkSchedule Global HR
Sync ExpenseReport Expense Management
Sync InventoryAdjustment CloudSuite WMS Warehouse
Management

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 96

 BODs used in integrations with this application

Verb Noun From applications

Sync InventoryCount CloudSuite WMS Warehouse
Management
Sync Personnel Global HR
Acknowledge PulseAlert Infor Ming.le
Process Quote CRM
CPQ/EQ
Sync ReceiveDelivery CloudSuite WMS Warehouse
Management
Process Requisition EAM
Process SalesOrder CPQ/EQ
CRM
e-Commerce
Sync SecurityUserMaster Infor Ming.le
Acknowledge Shipment CloudSuite WMS Warehouse
Management
Sync Shipment CloudSuite WMS Warehouse
Management
Process ShipToPartyMaster CPQ/EQ
CRM
Load SupplierInvoice Infor Localization Services

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 97

 Updating configuration of existing environment

Appendix F: Updating configuration of existing

environment

For information about upgrading from previous versions of Infor CloudSuite Industrial, see the Infor
CloudSuite Industrial Installation Guide.

Infor CloudSuite Industrial Configuration Guide for Infor Operating Service | 98