ION DIFFERENTIATION FLEXIBLE STANDARDS BASED MESSAGING BUS CONNECT APPLICATIONS IN A VARIETY OF WAYS CREATE MONITORS / ALERTS CREATE CUSTOM WORKFLOWS

Transcription

1

2

3 ION DIFFERENTIATION FLEXIBLE STANDARDS BASED MESSAGING BUS CONNECT APPLICATIONS IN A VARIETY OF WAYS CREATE MONITORS / ALERTS CREATE CUSTOM WORKFLOWS ION PRACTICAL APPLICATION: INFOR APP TO INFOR APP INFOR APP TO 3RD PARTY APP 3RD PARTY APP TO 3RD PARTY APP

4 ION Activity Deck or Ming.le Enterprise Infor ION Process - Workflow Automated document routing and approvals via workflows across multiple Infor and non-infor apps. Infor ION Process Event Management Automated task monitoring in relation to promised completion and proactive exception alerts. Infor ION Connect Communication and secure sharing of data across on-premise and cloud applications. ION Desk

5 APPLICATION INFOR CLOUD, INFOR APPLICATION (IO BOX), INFOR ERPLN/BAAN, SALESFORCE.COM, MICROSOFT CRM, SAP, ORACLE EBS DATABASE (JDBC CONNECTOR) SQL SERVER, ORACLE, DB2, DB2-400, (EXTENDABLE) QUEUE FILE ADAPTER WEB SERVICE CONFIGURED AND MANAGED FROM ION DESK CLEAN UP OF MESSAGES VARIABLE POLLING SETTINGS

6 BUILDS ON ION CONNECT CONSUMES THE MESSAGES THAT APPLICATIONS ARE SHARING MANAGED THROUGH ION DESK MONITORS BOD TO BE USED AND RULES TO FILE THE MONITOR WORKFLOWS WORKFLOW DEFINES A FLOW, IN AND OUT PARAMETERS TASK MESSAGES BRANCHES ACTIVATION POLICY DEFINES THE BODS AND RULES TO START THE FLOW ASSOCIATED TO A WORKFLOW

7 A PORTAL COMMON INTERFACE / INFRASTRUCTURE FOR INFOR AND NON-INFOR WEB-BASED APPLICATIONS ALLOWS EXTENSION OF CORE PRODUCT CAPABILITIES WITHOUT MODIFYING THE CORE PRODUCTS USER EXPERIENCE SINGLE SIGN ON PROVIDES BRANDED USER EXPERIENCE FOR INFOR PRODUCTS PROVIDES COMMON LOOK & FEEL ACROSS INFOR PRODUCTS PROVIDES A PLATFORM TO CREATE MASH-UPS ACROSS INFOR AND NON-INFOR PRODUCTS DOCUMENT MANAGEMENT PROVIDES CONTEXTUAL DOCUMENT MANAGEMENT FOR INFOR CORE PRODUCTS

8 BOD BUSINESS OBJECT DOCUMENT A XML DOCUMENT THAT IS A GENERIC REPRESENTATION OF A BUSINESS OBJECT A COMMON LANGUAGE USED FOR INFORMATION INTEGRATION BASED ON OPEN APPLICATIONS GROUP INTEGRATION SPECIFICATION (OAGIS) THE OAGIS DEFINITION HAS BEEN EXTENDED FOR INFOR USE

9 ENABLES COMMUNICATION FROM AN APPLICATION TO A USER SEQUENCE OF STEPS THAT COMPLETES A BUSINESS GOAL ACTIVITIES TASK SET PARAMETER NOTIFICATION EXIT POINT FLOW DECISION LOOPBACK

10

11 No Supervisor Notification Requisitioner User creates/ updates a purchase requisition with header and line items Is Supervisor & Approver1 same? Yes Requisition Approval by Approver1 Is Approved? Requisition Is Price greater Yes Yes Approval by Is Approved? Yes than Approver1 Approver(n) limits? Is Price greater than Approver(n) limits? No No Requisition Line updated with status as R in XA Reject/Resubmit Notification No No Requester notified for resubmission Yes Is price greater than 10%? Buyer Assistant Verification $$$ Purchasing No Requisition Line updated with status as A & V in XA XA ION ION Activity Deck/ Ming.le

12 Infor XA Requisition BOD ION Workflow Ming.le Requisition ID, Warehouse, Department, Request Type, Approval Status Approver Data/Limits Exit Point.NET Web service System Link Web service Requisition ID, Warehouse, Department, Request Type, Approval Status Approver Data/Limit s

13

14 TO ACTIVATE ANY BOD IN XA, PERFORM THE FOLLOWING STEPS. a) GO TO SETTINGS CARD IN POWER LINK b) SELECT SYSTEM LINK TRANSFORMATIONS. c) SEARCH FOR XA_REPLICATE_PURCHASEREQUEST_SYNCREQUISITION _BOD.XSL d) ACTIVATE BY CLICKING THE ACTIVATE BUTTON AS SHOWN.

15

16

17

18

19

20

21 EXIT POINT CAN BE USED TO GET DATA FROM XA AND SEND DATA TO XA USING WEB SERVICE. EXIT POINT PROPERTIES CONTAIN NAME, DESCRIPTION, URL AND COMMAND. URL AND COMMAND IS MANDATORY AS SHOWN BELOW.

22

23 BY SELECTING CONDITION ONLY OPTION SHALL TRIGGER THE WORKFLOW ONLY BASED ON THE CONDITION SPECIFIED.

24

25

26

27

28

29 THE APPROVAL CYCLE CONTINUES TO NEXT APPROVER IF THE REQUISITION VALUE IS HIGHER THAN THE LIMIT FOR THE PARTICULAR APPROVER ELSE GOES TO THE BUYER FOR VERIFICATION

30