This document summarizes a presentation about Infor Process Automation (IPA). It discusses using IPA for transaction approval workflows with email notifications and inbasket approvals. It also covers using IPA for interfacing with other systems, automating user account provisioning and jobs. The document cautions that variables may not persist after user actions and provides workarounds for common issues. It emphasizes preparing the Landmark environment before implementing IPA and migrating from ProcessFlow to IPA.

1. Infor Process Automation
Presenter: Richard Leigh Stout
Copyright © 2015 RPI Consultants, LLC. All rights reserved.
August 20, 2015

2. Infor Process Automation

3. About RPI
Founded in 1999
in Baltimore, MD
50+ consultants
nationwide with
certifications
across the
spectrum of Infor
Lawson products

4. • IPA for Approval
• IPA for Interfaces
• Architecture
• Favs / Gotchas
• PFI IPA Migration
On Today’s Agenda

5. IPA for Transaction Approval

7. Email Notification

8. Approve via Email

9. Inbasket

10. Requisition Approved!

11. Flow Design
Simplified example

12. Flow Design
Real world example

13. Enable Email Approval
User action node properties, notify tab, edit message

14. Approval Matrix
Options
• HR Org Chart
• RQ02
• Integrate with another
system
• IPA Tasks & Filter
Categories

15. IPA Tasks and Filter Categori

16. Tip: Loop over a single User Action node for all approval levels

17. WorkflowTriggers

18. Common Transactions Routed for Approval with IPA
• Procurement: Requisitions
o Supplies – Specials and Nonstocks
o Capital, Services, Implants, etc
• HR: Personnel Actions – MSS
• Finance: Journal Entries

19. Approver Security Requirements
LSF
• Logan WF tables
• RM: WFUser = 1
• Inquiry access to see
transaction details
Landmark
• InbasketUser_ST role
• Email address on Actor
record
• User record in IPA
Tip: Program your flow to check security and make corrections

20. IPA for Interfaces

21. Nodes for Inbound
Interfaces• Lawson
Transaction
(AGS)
• Landmark
Transaction
• RM Update • Web Run

22. Nodes for Reaching Out

23. Triggering an Interface Flow
By Time
• Scheduler with many
options for recurring
flows
By Incoming File
• File Channels monitor
a directory for incoming
files
• Auto archiving

24. IPA for Lawson User Account Automation
• Provision user accounts for new hires
o Works with Active Directory bind
• Update groups or roles on position
change
• Disable or delete account on termination

25. IPA for Job Automation
• Update job parameters, such as date
• Submit jobs
• Collect print files and parse output

26. Landmark Architecture

27. Landmark Platforms
or
Hardware requirements are significant

28. Grid
IPA
IPA
WebSphere
Inbasket,
IPA
Admin
Rich
Client UI
Web UI
Landmark
Components
AD Bind SSO
Data
base

29. IPAFavorites

30. Configuration Sets

31. Configuration Set Properties

32. Configuration Sets

33. Configuration Sets
• How many do you need?
o Out of the box: main and system
o You can create as many as you’d like
o One per suite is a good idea
• A configuration set points to one product
line only

34. Error Handling
Options
• Send Email
• Custom Log Entry
• Divert Flow

35. Divert Flow Execution on Error
The Old Way The New Way

36. Monitoring Flows in IPA

37. WorkunitLogs

38. IPA
Admin
Website

39. Workunit Messaging

40. Action Override
• Admins can override workunits pending
User Action
o Workunit > Take Action > “Approve”
o Workunit > User Actions > Routing

41. Workunit Cancel and Restart
• Cancel a flow and start from
beginning
• Can change process version
• Caution: Log is not cleared and
variables may not reset

42. Avoid
PITFALL!

43. JavaScript Expression Gotcha
• Variables set with JavaScript don’t save
after a User Action node
Workaround: Set variable value to itself
with a regular assignment

44. Long String Variable Gotcha
• Message builder and string variables are
truncated to about a thousand
characters after User Action node
Workaround: Rebuild string after User
Action

45. AP Invoice Approval
• AP32 throws error if payment cycle in
process
Workaround: Use a Wait node and retry

46. Landmark on Windows – local lawson user
• Installing or updating Landmark on
Windows while logged in as the domain
lawson user creates duplicate identity
Workaround: delete duplicate actor
identity record after install/update
Workaround: create a local lawson
account in Windows

47. Implementing IPA
Build environments and
product lines to match LSF
Landmark is no charge for
ProcessFlow owners

48. They
go
togethe
r like…
Keep in mind when implementing Landmark
Landmark 10.1.1.29
6
Landmark 10.1.0.40

49. Get Ready for Landmark & IPA
• LSF Environment
update
• LSF Java update
• Refresh Test
environment
including security
• Contact CAE for
license
• Identify current
ProcessFlow use
• Clean up LDAP to
prepare for ISS
sync

50. Consider this when
implementing Infor Security
Services…
Update
LSF and
LDAP
schema
LSA
Desktop
Client
Training
Security
Admin
N-1 or
N-2 ESP
&
Stabilize IS
S

51. IPA
Considerations
 Converting flows
and migrating
data
 Logan tables
 Training admins
and developers

52. ProcessFlow to IPA Migration
Things that convert
• Flows
• User, Task, and
Category data
Things that don’t
• Crystal Reports
• Active Workunits
Trigger cutover is all or nothing

53. How RPI Consultants Can Help
• Project Leadership
• Landmark Implementation
• PFI to IPA Migration
o Flow conversion
o Reporting
• Custom Training

54. Questions?