Copyright © 2019. Infor. All Rights Reserved. (1)

E R P 2 2 6 - M o d e r n i z e y o u r M 3 i n t e g r a t i o n sH e n r i k J o h a n s s o nS r . D i r e c t o r D e v e l o p m e n t M 3 I n t e g r a t i o n

E R P 2 2 6 - M o d e r n i z e y o u r M 3 I n t e g r a t i o n s

(4)

Full disclaimer

This presentation reflects the direction Infor may take with regard to the products or services

described herein, all of which is subject to change without notice. This presentation is not a

commitment to you in any way and you should not rely on any content herein in making any decision.

Infor is not committing to develop or deliver any specified enhancement, upgrade, product, service

or functionality, even if such is described herein. Many factors can affect Infor’s product development

plans and the nature, content and timing of future product releases, all of which remain in the sole

discretion of Infor. This presentation, in whole or in part, may not be incorporated into any

agreement. Infor expressly disclaims any liability with respect to this presentation.

(5)

05M 3 E D I – N ew d i r e c t i o n

f o r C l o u d

06

04 M 3 & D a t a l a k e

02 I n f o r M 3 C e r t i f i e d

I n t e g r a t i o n s

03S yn c h r o n o u s a n d

A s yn c h r o n o u s

I n t e g r a t i o n s

01

Agenda

A g l a n c e a t t h e p a s t

a n d t h e f u t u r e

(6)

M3 Strategic directions

Multi-tenant cloud suites

• Complete industry suites with integrations

Cloud-proven technologies

• Infor OS, IFS, thin client, security

• Birst, extensibility, Mongoose

Single version of the software

• Incremental development

• Test automation

• Continuous delivery of new features

(7)

M3 Strategic directions

Next On Premise M3

M 3 C l o u d E d i t i o nNew Major Version

• Single Version

• Automated Updates

• Scalable

• Secure

• Extensible

KEY INDUSTRY

FUNCTIONALITY

USER EXPERIENCE FOR

THE DIGITAL AGE

IMPROVEMENTS TO

EXTENSIBILITY TOOLING

INTEGRATIONS TO INFOR

BEST IN CLASS SOLUTIONS

INCREASING SOLUTION’S

GLOBAL COVERAGE

NEW TECHNOLOGIES, IOT,

INDUSTRY BI AND BIG DATA

2017 20202018 2019 2021

(8)

Infor OS – Common shared services

USER EXPERIENCE

Portal

In-context

Homepages

Search

Chat

Documents (IDM)

Mobile (GO)

INTEGRATION

Process Integration

Activity Monitoring

Workflow

API Gateway

Orchestration

Mapping

SECURITY

Single Sign-on

Users / Roles

Groups

Auditing / Monitoring

Insights

DATA MANAGEMENT

Data Lake

Graph

Data Catalogue

Data Services APIs

Data Pipelines

Archiving

APP. DEVELOPMENT

Dev Framework

Composite Apps

Soho UX Library

Reports

Extensibility

COLEMAN A.I.

Digital Assistant

Automated Skills

Contextual AI

Image Recognition

AI Platform

Robotic Process Automation

(RPA)

IoT

IoT Portal

Connectors

Embedded EAM

Analytics

RISK & COMPLIANCE

Analyze & track data

Fraud management

Audit management

Analytics & alerts

Regulatory Requirements

Cross-application connectivity

GRC & Local.ly

(9)(9)

A glance at the past and the future

SECTION 01

(10)

Infor M3 Integration: The PastA g l a n c e a t t h e p a s t a n d t h e f u t u r e

EBM

EDI

FBM

ABM

ABM

???

XBM

PBM

Customers,

Suppliers etc.

Bank

Other ERPs

WMS

EDI Broker

BOD

Infor M3

IEC

(13)(13)

Infor M3 Certified Integrations

SECTION 02

(14)

M3 Cloud Edition Super SetInfor Birst – M3 Industry Analytics

Sales Order Management

Rental & Lease Management

Over the Counter Sales

Customer & Market Management

ProjectManagement

Production Planning & Scheduling

Manufacturing Execution

Quality Management

Demand Planning

Supply Chain Planning

Plant & Equipment Structure

Work Management

Product & Equipment Costing

Product Data & Attribute Management

Depot and Field Service Management

Multi Company Management

Risk & Cashflow Management

Internal Cost Accounting

Financial AccountingAR/AP/GL

Fixed Asset Management

Procurement Management

Transport Management

Warehouse Management

Inventory Management &

Planning

Grower Contract Management

iPAAS Coleman A.I.Data Management PAASUX IoT L10nSecurity

• Demand Planner

• Scheduling workbench

• Planning Workbench

• Graphical Lot Tracker

• Inventory Planning Workbench

• Sales Hub

• Equipment Quotation

Management

• Mobile Field Service

Planned in Q4 2019-Q1 2020

• Customer Lifecycle

Management

• M3 Portals (Equip/Issue)

Factory Track

Infor CPQ

Infor EAM

Infor Rhythm

GT Nexus

Cloud Suite

Fashion PLM

Supplier

Rebate

Framework for

EDI

Infor IBP

XM Expense

ManagementInfor CRM

Infor GRC

Cloud Suite PLM

for Process

Infor d/EPM Infor HCM

Cloud Suite

WMS

Integrated add-ons

M3 Add-on applications

Infor OSS

Planned in 2019-Q1 2020

Infor M3 CE Core

InforSupplier

Exchange

IDM

Capture

(15)

Infor M3 13.4 – 15 Certified ION Integrations Local.ly

Business Vault

d/EPM

Supplier

Exchange

Supply Chain

Execution

Fashion PLMEnterprise Asset

Management

PLM - Optiva

BackOffice Connect

M3 SuiteInfor Rhythm

CPQ, Configure/

Price/Quote

Mobile Field Service

Supplier Rebate

Infor Nexus

IDM – Document Capture

Infor CRM

(16)

M3 Certified Integrations

▪ Deliverables

– Infor BODs based on OAGIS standard

– Preconfigured ION document flow

– Integration guide

– Cross BOD documentation

▪ Other value

– Quality assurance and design by Infor

– Maintained deliverables supported by Infor

– Continuous development of integrations over time

▪ In Cloud

– Basic setup of integration at provisioning in Cloud

I n f o r M 3 C e r t i f i e d I n t e g r a t i o n s

(17)

Planned Enhancements to Q1 2020

▪ Infor CloudSuite PLM for Fashion – Better basic data integration

▪ Infor Nexus – Enhancing the Procure to Pay process with supplier invoices

▪ Infor CloudSuite WMS - Improvements to Purchase Order-based Inbound ASN

▪ Infor EAM – Enhancement to the Goods Receipt process


(18)

Infor M3 CE BODsI n f o r M 3 C e r t i f i e d I n t e g r a t i o n s

Current numbers

Inbound – 49 (5)

Outbound – 83 (2)

Total BODs – 132

Code definitions – 54

Total number of mapping – 330

Facts

Continuous enhancements of

existing BODs, this year we have

made updates in +150 BODs

Breaking changes not allowed

Updates every month currently but

we are working on solutions to allow

updates without maintenance

windows

(19)

Infor M3 v13.4 BODsI n f o r M 3 C e r t i f i e d I n t e g r a t i o n s

Current numbers

Inbound – 35

Outbound – 69

Total BODs – 104

Code definitions – 51

Total number of mapping – 293

Future

New BODs added yearly

The next on-premises version will

follow M3 CE release schedule –

One version

Example CRM

CRM Basic Data

CRM Trasactions

(20)

M3 BODs – delivery process on-premises

▪ On-premises delivery process for M3 BODs

– Corrections per noun

– M3 BODs mappings delivered as .zap-files

– M3 BODs rules delivered as rules packages

▪ Delivered via KB-article – Updated weekly

– 15.4: 1902185

– 15.5: 1895800

▪ Patches will still be delivered, about every 6 months, on Product Download


https://www.inforxtreme.com/espublic/EN/AnswerLinkDotNet/SoHo/Solutions/SoHoViewSolution.aspx?SolutionID=1902185&kb_accessed_from=KBViews

https://www.inforxtreme.com/espublic/EN/AnswerLinkDotNet/SoHo/Solutions/SoHoViewSolution.aspx?SolutionID=1895800&kb_accessed_from=KBViews

(21)(21)

Asynchronous integration

SECTION 03

(22)

Asynchronous integrations

▪ Use case: Data transfer between systems where:

– Response times are not critical

– Transaction volumes are low to moderate

▪ Communication

– All communication protocols supported by ION Connectors

– M3 currently connects to ION through IEC using I/O box but will move to IMS

A s y n c h r o n o u s i n t e g r a t i o n

(23)

M3BODs - Current

▪ Currently all M3 CE messages are BOD based

▪ ION CE is used to transport the BODs

– Ming.le, workflows, data mapping, ION API and other functionality is available

– All external communication is handled by ION CE


M3 CE

ION

App. A

App. B

BOD BOD

BOD

I/O

(24)

Messaging - Future

▪ ION CE is used to transport the BODs

– Ming.le, workflows, data mapping, ION API and other functionality is available

– All external communication is handled by ION CE

– IMS/Any Message allows for non BOD messages to be transferred


M3 CE

ION

App. A

App. B

BOD

/Any

IMS

BOD

/Any

BOD

/Any

(25)

M3 CE integration components

▪ M3 CE contains several components for asynchronous integration:

– Event Hub

– Event Analytics

• Event Analytics Rules UI

– M3 BOD Processor

– Infor Enterprise Collaborator

• Infor Business Document Mapper tool

▪ Custom & Standard BODs are developed using these components and tools, similar

extensibility options as before are available

▪ Currently only BOD’s are supported but the plan is to support additional message

formats


(26)

Component overviewA s y n c h r o n o u s i n t e g r a t i o n

Infor M3 CE Core

Enterprise

Collaborator

Event

Event Hub

Event

M3

Business

EngineM3 A

PI

Info

r C

loud

M3 BOD

Processor

Event

Analytics

I/O

Box

Events Events

BOD

(28)

Event Analytics Rules

▪ Same functionality as for the on-prem tool Smart Rules

▪ Rules developed in Smart Rules are compatible with cloud.

– Note that rules developed directly using drools are not!

▪ Export and import custom sessions

▪ Currently 127 standard sessions for BODs

– 12 standard sessions for FBMs


(29)

Event Analytics, standard content

▪ Standard Event Analytics sessions are automatically installed and updated by Infor

▪ Customers can start and stop standard sessions

– All standard sessions are started as default

– Start/stop state is remembered

▪ Infor Product Development is responsible for standard sessions

– Standard sessions cannot be created, modified or deleted by customers


(30)

Event Analytics, custom content

▪ Customers can copy standard sessions, or create new custom sessions

– Standard sessions is copied to custom sessions for customization

▪ Customers are responsible for custom sessions

– Custom content and settings will not be altered by Infor

– Custom sessions can be exported and imported


(31)

Composite events

▪ You cannot subscribe to joined events

– For example order line and order header

▪ M3 CE Business Engine program CMS042 creates composite events, i.e. joins

– CMS042 can subscribe to the order line event, add data from the order header, and then publish a

new event containing data from both order line and order header

– This new event can then be filtered in Event Analytics, for example on order type in the order

header


(32)

Mapper Tool

▪ Infor Business Document Mapper tool

▪ Graphical mapping tool to create XML based on the BE API layer

▪ Can use old EBMs or other XML if wrapped in a BOD

▪ Whitelist with allowed Java functions

– Will have to be taken into account


(33)

M3 BOD Processor

▪ M3 BOD Processor

– Activate/Deactivate BOD’s

– Add Accounting Entity


(34)

ION

▪ Deals With all external communication using ION Connection points

▪ Transformation of different file formats to XML/BODs

▪ Workflow capabilities

▪ Routing


(35)


Infor ION

Infor M3 CE Core

Enterprise

Collaborator

Event

MBM initiator

Event Hub

Event Analytics

Event

Published

M3

Business

Engine

ION Enterprise Connector (EC)

Infor

Ming.le

ION API

M3 A

PI

Standard

Integration

Apps

On-P

rem

ises

3rd

Part

y C

loud

sFTP EC

Infor M3

(BOD)

Infor

Ming.le Infor App

DatabaseInfor AppJMSIMSFile

Infor

Data Lake

Standard

Integration

Apps

ION

Integrated

Apps

Info

r C

loud

Date

Lake

Ext. Target APIs FTP server

IMS

(Future)

(36)

Hybrid Integration with M3CE

▪ Infor OS is designed to have a mixed integration landscape

▪ Enterprise connector is used to connect to 3rd Party Cloud Solutions or On Prem

applications/databases


(37)

Hybrid integration with M3 on-premise

▪ Infor OS is designed to have a mixed integration landscape

– Cloud Connector is used to connect to cloud applications

▪ M3 13.4

– BOD integration to other cloud applications with Infor OS on-premises

– Infor OS MT not supported for onprem

▪ Next M3 on-premises will support full hybrid deployments

– Integration to Infor Data Lake, other MT applications etc.


(38)

Standard message deliveries

▪ BODs is the main asynchronous message strategy

▪ FBMs are delivered to bridge GAPs where local.ly have GAP’s or doesn't fit

▪ EDI BODs are delivered from Development and will be our future EDI direction

▪ EBMs (CA) will still be around but will not be our main go forward strategy


(39)(39)

Synchronous Integration

SECTION 03

(40)

Synchronous integrations

▪ Use case: Data transfer between systems where:

– Low response time is required

– Transaction volumes high

– Direction interaction with messaging, additional data, etc.

▪ Solution

– M3 APIs through ION API

▪ Communication

– RESTful APIs through M3-API-WS component over HTTPS

S y n c h r o n o u s i n t e g r a t i o n

(41)

M3 CE Core API support

▪ M3 Functionality

– M3 CE: 5500+ transactions (1550+ Updating)

• In 13.4: 4500+ transactions (1300+ Updating)

▪ Technical

– Configurable APIs

• CMS100MI - Custom list API

• MDBREADMI – Generic API to read one M3 table

• EXPORTMI – Data export

– Bulk API – Perform a group of APIs in same request

– IPS – Build API based on interactive programs

▪ IONAPI Gateway adoption


(43)

Interactive Program Services (IPS)

▪ Publishes SOAP web services based on M3 interactive programs

▪ Replaces M3 Web Services MPD

▪ Import of legacy MWS MPDs supported

▪ Rest support being added


(44)

Infor ION

Infor M3 CE Core

Enterprise

Collaborator

Event

MBM initiator

Event Hub

Event Analytics

Data Lake PublisherEvent

Published

M3

Business

Engine

ION API

Gateway

ION Enterprise Connector (EC)

Infor

Ming.le

ION API

M3 A

PI

Standard

Integration

Apps

Ext. Target APIs

On-P

rem

ises

3rd

Part

y C

loud

sFTP EC

Infor M3

(BOD)

Infor

Ming.le Infor App

DatabaseInfor AppJMSIMSFile

Data

Lake

Infor

Data Lake

Infor M3

(Event)

Authorized Apps

I n f o r O S - I n t e g r a t i o n

Standard

Integration

Apps

Standard

Integration

Apps

Info

r C

loud

(45)

Infor ION API GatewayS y n c h r o n o u s i n t e g r a t i o n

UNIFORM PROXY LAYER

Single managed layer for your APIs

on the internet

SECURITY

Using Industry standards for security

such as Oauth2

POLICY

Enrich APIs without changing them

Hybrid Integrations

Bridge local network to Infor or third

party cloud using APIs

API ORCHESTRATION

Chain your APIs to expose new

complex functionality

Manage

Monitor and track the usage of your

APIs

(46)

ION API PoliciesI n f o r O S i P a a S

Qual i ty of Serv ice

Cache response

Quota

Throttling

Fault handling

Mediat ion

Cookie rewrite

Header

Query parameter

XML to JSON

JSON transformation

Secur i ty

RegEx threat protection

XML threat protection

JSON threat protection

Anonymous inbound

security

User security claims

Cookie authentication

Troubleshoot ing

Monitoring

Auditing

Logging

(47)

Infor ION API GatewayS y n c h r o n o u s i n t e g r a t i o n

Infor Business

ApplicationsInfor OS

In House

ApplicationsCloud

Services

Non

Infor

Authorized Apps

Target APIs

Suite Definitions

Endpoint Definitions

Policies

Admin

• Manage• Monitor• Publish• Transform

APIAnalytics

Gateway

Infor M3

(48)

Communication

▪ Authorized apps (clients) use https to access M3 API via ION API Gateway


Infor M3 CE Core

M3

Business

Engine

ION API

Gateway

M3 A

PI

Authorized

Apps

Info

r C

loudOAuth2

Gateway Transition..

Pass-through

Proxying existing APIs

Backend as a

Service (Roadmap)

Create new target end point

APIs

Orchestration

Create one Proxy end point for

multiple backend APIs

(50)

API orchestrationS y n c h r o n o u s i n t e g r a t i o n

▪ Publishing Web services in Infor Enterprise Collaborator NOT supported

▪ Use future API orchestration in Infor IONAPI*

▪ Build external service and add it as 3rd party target API suite to the IONAPI Gateway

* Roadmap item

(51)

What you should consider

▪ Move away from BE Authentication/Certificates

▪ Move to ION API

▪ For large volumes and replication consider options like DL


(52)

M3 ION API Statement

▪ The go forward solution for all externa, synchronous integrations with M3 is to call M3

APIs via ION API and to use the Data lake as data retrieval tooling for all M3 data

retrieval. This direction should be used for all new/re-built external integrations. Please

note that the possibility to direct external call to M3 API will be removed at some point in

the future.

▪ Course on Infor Campus:

– Infor OS: ION and ION API Gateway Overview, Course Code: 02_0951200_EEN0068_ION


(53)(53)

M3 & Data LakeSECTION 01

(54)

Infor M3 CE – Infor Data Lake integrationM 3 & D a t a L a k e

Birst/M3 Analytics

3rd party applications*

Data Catalog

Infor M3 CE Grid

Infor M3 CE

10x

Event Hub

M3 Data Lake

PublisherION Enterprise Search*

Infor Data Lake

EventsMetadata

IMS

M3 Data Lake Publisher registers subscribers to M3

events through Event Hub

When M3 publishes events, Data Lake Publisher

forwards these over IMS to ION

Events

(55)

Data Lake PublisherM 3 & D a t a L a k e

Configure document subscriptions

(56)

Infor M3

JDBC

P R O D U C E R S C O N S U M E R S

Infor M3 BE CE

Event Hub Data Lake Publisher

IMS

ION

M3 Analytics

Birst

Data Catalog

Infor Data Lake Highest level overview

D/EPM

IFS

D A T A L A K E

AnySQLBOD Files

Data Lake APIs

Compass

API/JDBC*

ITEM

ITEM

ORDER

CUSTOMER ITEM

CUSTOMERORDER

ORDER

Data Lake Services

Search Coleman

3p ETL**

*Q1- 20

**Q1-20

(57)

57 www.infor.com

Data Lakes & Data Warehouses

FACTOR DATA LAKE DATA WAREHOUSE

Data Structures Raw Highly Structured

Costs & Licensing Cheap Expensive

Schema “Schema on-read” “Schema on-write”

Consumers & Audience

• Master Data Services

• Data Scientists

• Data Warehouses & Wranglers

• Ad-Hoc BI

• Office+

• Business Intelligence & Reporting

Configuration Open, Agile, and semi-structured Pre-configured

Speed Fast Read, Fast Right Fast++ Read

Re-usability Highly flexible Limited reusability

(58)

Analytics for M3 Cloud Architecture – Future direction

So

urc

e

Dimensions

M3

Cloud

Edition

Event Hub IONIMSInfor

Data Lake

Min

g.le

BC

2.0Facts

Facts

Co

ns

um

er

ETL Consumer

IMS

Any SQL

API

EC

Dashboards

Reports

SQL

API

ETL

Other

Systems

Other

Systems

M3

Infor OS

Birst

Cloud

M3 DL

Publisher

Other

M3 Analytics based on

Birst

(59)

Infor M3 Antics for M3 Cloud SolutionM 3 A n a l y t i c s

Infor M3 Analytics for M3 CloudFirst step and accelerator towards Enterprise Analytics

Infor M3 Analytics for M3 Cloud Solution Offering

Infor OS Integration

“Brings analytics to all

CloudSuite users”

Industry Analytics

“To help you steer

your business”

Delivered Content

“Providing a first step

towards Enterprise

Analytics”

Analytics Content For Driving Business Value

Shorter Time

to Value

Improve User

Productivity

Unlock the

Value of Your

M3 Data

Embedded Analytics

“Building insight

within the CloudSuite

Applications”

Drill-Back Analytics

“Helps users take

action after gaining

valuable insight”

Reduce the

total cost of

ownership

Make Better

Informed

Decisions

Evolve into full cross-organization Analytics and BI with Birst Enterprise

(62)

Infor M3 Analytics for M3 Cloud SolutionM 3 A n a l y t i c s

16 Models

6 Domains

40 Dashboards

641 Metrics

277 Reports

90 Dimensions

September 2019

--------------

Procurement, Sales, Finance, Production, Rental, Equipment,

1218 Attributes

(63)

63Infor TechEd 2019

M3

Cloud

Edition

Event Hub IONIMSInfor

Data LakeCompas

Infor d/EPM for M3 Cloud Architecture

M3

Infor OS

d/EPM

Cloud

M3 DL

Publisher

Budgeting and Planning

Financial Consolidation

BOD

d/EPM Platform

Min

g.le

(64)

Integrations Build Using Data Lake

▪ M3 Analytics/Birst

▪ Infor GRC

▪ Infor d/EPM

▪ Coleman

▪ Infor Search

▪ IOT

M 3 & D a t a L a k e

(65)(65)

EDI - Future DirectionSECTION 01

(66)

EDI BODs

▪ What is an EDI BOD?

– A specific BOD for EDI with a M3 Specific XML Schema

▪ Why EDI BODs?

– Different use cases and verbs than standard BODs

– SOR conflicts if standard BODs where to be used

– It is format agnostic 1 BOD can be mapped to several EDI

documents and standards

– It uses standard ION functionality which enables powerful

messaging and monitoring

E D I - F u t u r e D i r e c t i o n

(67)

EDI BODs

▪ What are we delivering?

– Mapping & Agreement in MEC

– Message Implementation Guide

– M3 Analytics Rules for triggering

▪ Opens up for partners and EDI brokers to create

and sell mapping packages between M3 EDIBODs

and specific EDI formats

▪ It is general and not restricted to EDI. It can be used

integrating to other external system when translation

and partner handling is needed


(68)

M3 EDI Integration Framework


M3 EDI BOD

EDI translator:

• Translates Standard M3 EDI BOD to trading partner

specified format. For example:

• ANSI X12, EDIFACT, CSV

• Provides communication link with trading partners

ION:

• Communicates with EDI translator

• Routes EDI BODs between M3 and EDI translator

• Transformation, Alerts and Workflow capabilities

EDI BOD

ANSI X12

EDIFACT

CSV

EDI

Translator

Trading Partner 1

Trading Partner 2

Trading Partner 3

(69)

Supported Processes

Order to Cash

▪ Customer Order processing

▪ Shipment processing

▪ Invoice processing

▪ Remittance Advice processing

Procure to Pay

▪ Purchase Order processing

▪ Shipment notification processing

▪ Supplier Invoice processing

▪ Receive Delivery processing


(70)

Currently supported BOD’s BOD/Noun Verb Direction ANSI X12 EDIFACT

M3EDISalesOrder Load Inbound 850 ORDERS

M3EDISalesOrder Sync Outbound 850 ORDERS

M3EDISalesOrderAcknowledge Sync Outbound 855 ORDRSP

M3EDIShipment Sync Outbound 856 DESADV

M3EDIShipmentDelivery Sync Outbound 856 DESADV

M3EDIInvoiceCustomerOrder Sync Outbound 810 INVOIC

M3EDIPurchaseOrder Sync Outbound 850 ORDERS

M3EDIPurchaseOrder Process Inbound 855 ORDRSP

M3EDIAdvanceShipNotice Load Inbound 856 DESADV

M3EDISupplierInvoice Load Inbound 810 INVOIC

M3EDIReceiveDelivery Load Inbound 861 RECADV

M3EDIRemittenceAdvice Load Inbound 820 REMADV

M3EDIShipment Load Inbound 856 DESADV

M3EDICarrierRoute Sync Outbound 853 IFTMIN

M3EDICarrierRouteDelivery Sync Outbound 853 IFTMIN


(71)

EBMs

▪ Available in M3CE under controlled availability

– Ability to use M3 EDI Business Messages through ION as custom BODs

– All content available for selected customers (more than 100 messages)

– Infor will continue to support EBM messages to allow for smother migration to cloud and a

richer repository of EDI messaging templates

• Will be made available I the future as stand alone messages using IMS (custom BOD not needed)

– Targeting to have the EBM solution GA during 2020

– KB article: 2055544 - White paper for EBMs in M3 CE


https://www.inforxtreme.com/espublic/EN/AnswerLinkDotNet/SoHo/Solutions/SoHoViewSolution.aspx?SolutionID=2055544

(72)

Announcing Infor TechEd for Infor M3

product experts

deep-divebreakout sessions

speedsessions

Infor M3

December 10-12, 2019 | Stockholm

Choose from deep dive session where you can:

• Experience the brand new User Interface for Infor M3

• Understand the new business logic extensions tool

• Learn the best practices with Infor M3 applications

• Empower your business intelligence with Data Lake and Birst

• Explore the newest Infor OS innovations with Infor Coleman

(AI), Infor Go and many more

A unique technical training event

Register now

https://pages.infor.com/20191210-oth-edu-technical-hands-on-training-for-Infor-M3.html

(73)

1. Go to Agenda Builder

2. Click on the appropriate session

3. Scroll down to “rate this session”

4. Rate session using the 1-5 scale

Rate this sessionin the mobile app

Copyright © 2019. Infor. All Rights Reserved. (1)

Documents

Transcript of Copyright © 2019. Infor. All Rights Reserved. (1)