Presented by Mark DiGiovanni September 12, 2002 - PowerPoint PPT Presentation

About This Presentation
Title:

Presented by Mark DiGiovanni September 12, 2002

Description:

Happy Birthday / Anniversary! Inbasket Functionality. Work Requires User Interaction ... Build Messages. Category Filtering. Perform a form action using AGS ... – PowerPoint PPT presentation

Number of Views:53
Avg rating:3.0/5.0
Slides: 27
Provided by: Sum564
Category:

less

Transcript and Presenter's Notes

Title: Presented by Mark DiGiovanni September 12, 2002


1
Lawson ProcessFlow Overview and Actual
ProcessFlow Solutions
Presented by Mark DiGiovanni September 12, 2002
2
Agenda
  • Introduction
  • ProcessFlow Overview
  • - What is ProcessFlow?
  • - What can ProcessFlow do for you?
  • - How does it work?
  • ProcessFlow in Action (Examples)
  • - Requisition Approval
  • - Rush Order Processing
  • Questions

3
What is ProcessFlow?
  • ProcessFlow is a powerful Lawson product allowing
    customers to automate business processes
  • ProcessFlow is Workflow
  • Same Concept New Product
  • ProcessFlow can be used to perform tasks from
    simple email notification to the complex routing
    of work
  • Easy to implement, use, and develop

4
Types of Work
  • ProcessFlow allows users to automate two
    primary types of work
  • 1. Notification (inbox)
  • 2. Routed (inbasket)
  • as well as the capability to perform
  • multiple other functions.

5
Inbox Functionality
  • A business event triggers the creation of an
    email to notify users of the event
  • Usually a single step process
  • Examples
  • EE Status Change Reports
  • Buyer Messaging
  • Happy Birthday / Anniversary!

6
Inbasket Functionality
  • Work Requires User Interaction
  • May be a multi-stepped process
  • Approve, Reject, etc.
  • Examples
  • JE Requires Approval
  • Requisition Approval
  • Personnel Action Approval
  • Data Validation

7
ProcessFlow Features
  • Requires no 3rd Party Software or additional
    hardware
  • Execution occurs on Lawson Server
  • Integrated with Lawson Applications
  • Uses Lawson and Web Server Security
  • Multiple trigger types
  • Inbasket available for Portal and Browser
  • Metrics

8
ProcessFlow Maintenance
  • Requires no special set-up
  • Distributed with a design utility allowing users
    to graphically create or modify processes (drag
    and drop)
  • Designer also allows for development of more
    complex ProcessFlows if necessary
  • Provides for user desktop maintenance,
    administration, and the tracking of work

9
Standard and Professional
  • There are 2 editions of ProcessFlow
  • ProcessFlow Standard
  • - Free!
  • - Inbox, Designer, Tools, Applications
  • ProcessFlow Professional
  • - Purchased separately
  • - Full Product Functionality
  • - Standard Inbasket (User Action and HR User
  • Action) Work Object

10
Triggers
  • Automatic
  • - Requisition is released
  • Manual (On Demand)
  • - User submits a job
  • Scheduled
  • - 3rd Tuesday of month at 9 AM

11
Simple Flow Design
12
Designer Functionality
  • Query the Lawson DB using DME
  • Send Email (inbox)
  • Prompt a user for Action (inbasket)
  • Create a new process
  • Build Messages
  • Category Filtering
  • Perform a form action using AGS
  • Execute Jobs (Lawson and Non-Lawson)
  • Branches, Conditions
  • Assign Values to Variables
  • Flow Simulation

13
Delivered Functionality
  • Several triggers are delivered with the base
    Lawson product
  • Templates for the HTML and Portal Inbasket are
    also delivered for several common functions (PA
    Approval, Requisition Approval, etc)
  • Several ProcessFlow templates (services) are also
    delivered
  • Delivered templates allow for the easy
    development of ProcessFlows

14
Some Delivered Triggers
  • Activity Additions / Changes
  • Personnel Action Approval
  • Journal Entry Approval
  • Requisition Approval
  • Invoice Approval
  • Cost Discrepancies
  • Customer Changes
  • Shipment Backordered
  • Requested Item Received
  • Unmatch Invoice

15
ProcessFlow in Action
  • Two Real World Solutions Using ProcessFlow
  • 1. Requisition Approval
  • 2. Rush (Stat) Orders
  • Note These concepts can be applied to numerous
    other business scenarios

16
Requisition Approval Process
  • Concepts to be demonstrated
  • Trigger (automatic)
  • Inbasket / User Action
  • Branch Conditions
  • Email Notification
  • Routing
  • AGS Updates
  • Category Filtering

17
Requisition Approval Process
Signature Authorization
Finance Approval
Purchasing Approval
ED Approval
Account Verification
Level 3 gt7500 Approval
gt25,000
AED Approval
Level 2 gt100 lt7500
gt10,000
Director Approval
Level 1 lt 100 Approval
gt1,000
Manager Approval
gt500
Requisition with Special Item(s) is released
Supervisor Approval
Requisition is not approved
Requisition is approved
18
More Complex Requirements
  • There are three director levels, but only one
    director level approval is required to release
    the requisition.
  • For signature authorization, the approver cannot
    be the same person as the requester.
  • When a requisition is not approved, a message
    should be generated for the requester telling
    them why it was rejected.
  • If a user has a requisition in their Inbasket, an
    email should be generated telling the user that
    they have a requisition to approve.
  • If a req. sits unapproved for 3 days, the
    requester should be notified

19
ProcessFlow Development
20
Inbasket Display
21
New Requisition Scenario
  • A requisition with a special item is released
    totaling 350
  • Requisition set to needs approval status and
    req. is routed to supervisor for approval
  • Supervisor approves requisition
  • Since lt500 goes to Finance for Approval (based
    on Acct Unit on Req.)
  • Finance approves requisition

22
New Req. Scenario (contd)
  • Requisition is routed to Buyer 2
  • Buyer 2 rejects requisition and enters why they
    have rejected requisition
  • Requisition is updated in based Lawson to
    Unreleased status.
  • Email is generated for purchaser
  • Process Ends

23
Rush (Stat) Orders
Requisition is approved through AGS on RQ13
WH130 Job is created for requisition being
processed.
Several Fields on RQ10 are updated through AGS
calls.
Stat order is released
WH130 Job is submitted
WH130 Pick Ticket Routed Directly to Printer
RQ111 Job is created for requisition being
processed.
RQ111 Job is submitted
Patient charges are created using AGS on PC20
END
RQ111 Output Routed Directly to Printer
24
Rush Orders Scenario
  • Requisitions with Priority 1 should be treated
    as a Rush Order
  • Rush orders should automatically be approved
  • Pick Tickets should be printed
  • Delivery information should be printed
  • Patient Charges should be created

25
Rush Order Flow Development
26
Questions?
E-Business on Solid Ground
Write a Comment
User Comments (0)
About PowerShow.com