Professional Documents
Culture Documents
Chapter 3: Workflow Actions and Reporting: Objectives
Chapter 3: Workflow Actions and Reporting: Objectives
Introduction
A workflow approval process involves two main groups of participants: Originators Approvers
An approval workflow is the routing of a document to one or more individuals for approval. When the originator clicks the Submit for approval button the document is saved and submitted to workflow. Workflow then checks the conditions of the first level to determine if the document should go through the workflow approval process and who is required to approve it.
3-1
Security, accessibility, and functional requirements ultimately determine which software application your firm will use.
Microsoft Dynamics GP
With Microsoft Dynamics GP, approvers can act on documents and batches using entry windows and lists. Approvers can use entry windows to act on a specific document or batch. For example, an approver can approve a specific purchase order using the Purchase Order Entry window. Approvers can use lists to act on several documents or batches at one time. For example, an approver can approve multiple purchase orders at one time using the All Purchasing Transactions list.
3-2
3-3
NOTE: To act on a workflow (approve, reject, etc.) through an e-mail the user must be using Microsoft Office 2007 or later.
Workflow Tasks
A task represents a document or batch assigned to a user for approval. When a user submits a document or batch for approval, the Workflow system evaluates the first step in the workflow to determine if approval is required there. If the Workflow system determines that approval is required, a task is created for that approver.
3-4
Assume that Frank approves the purchase order. The Workflow system then evaluates step 2 to determine if the purchase order meets the condition specified. Because the purchase order is more than $5,000, Sue's approval is required. The Workflow system creates a task for Sue. After Sue approves the purchase order, the purchase order is given Approved status. The purchase order can now be printed and shipments can be received.
3-5
Due Dates
Each task has a due date. The due date indicates the date by which the approver must respond to the task-that is, approve or reject the document or batch the task represents. Default due dates When configuring a workflow step, you specify how many days the approver has to respond to the task. For example, the following workflow shows the number of days each approver has to act on assigned tasks. Overriding default due dates Approvers can override the default due dates. For example, using the previous workflow illustration, suppose Sam submits a purchase order for $18,000. When Frank approves the purchase order, he can specify how many days Sue will have to approve or reject the purchase order. Similarly, when Sue approves the purchase order, she can specify how many days Ann will have to approve or reject the purchase order. When a task is overdue When an approver fails to act on a task by the task's due date, the task is considered overdue, or escalated. When configuring a workflow, you must specify what will happen to overdue tasks. The following options are available. If you select this option Take no action Delegate to next approver Delegate to Have system automatically This will occur The task remains assigned to the current approver. The system automatically assigns the task to the next approver in the workflow. The system automatically assigns the task to the user you specify. The system automatically approves or rejects the task, depending on the action you choose.
3-6
Originator Actions
The originator starts the workflow approval process by submitting a document or batch for approval. The originator does this in Microsoft Dynamics GP. For example, to submit a purchase order, the originator will use the Purchase Order Entry window. Use the Batch Entry window to submit a General Ledger batch. These windows have buttons that enable originators to submit the document or batch, or save it.
3-7
Challenge Yourself
Enter a purchase order for eight conference call phones (Item number 08539) from vendor Advanced Office Systems to be shipped to the warehouse. Submit the order for workflow approval.
Step by Step
1. Login to Microsoft Dynamics GP as Alicia Stevens. 2. Click Transactions, point to Purchasing, and then click Purchase Order Entry. 3. Enter a Standard type purchase order using the vendor Advanced Office Systems. 4. Enter item number 08539 (Conference Call Phone), and enter a quantity of 8. 5. Click the Submit for Approval button. 6. Enter the following comment in the Add Comment box Conference phones for the new offices. 7. Click the exclamation point symbol to set this document for high priority. 8. Click submit.
3-8
Approver Actions
When a document or batch is assigned to an approver, the approver can take one of the following actions. NOTE: The following information applies to workflow steps that have a single approver.
Approve
When an approver approves a document or batch, the document or batch is assigned to the next approver in the workflow, if required. If no additional approval is required, the document or batch is given the status of Approved and the workflow approval process is complete. For example, suppose Sam submits a purchase order for $6,000. In this scenario, the purchase order must be approved by Frank and Sue. When Frank approves the purchase order, it is assigned to Sue for approval. When Sue approves the purchase order, it is given the status of Approved, and the workflow process is complete.
Reject
When an approver rejects a document or batch, the document or batch is assigned the status of Rejected and the workflow process is complete. For example, using the workflow previously shown, suppose that Sam has submitted a purchase order for $12,000 and that it is assigned to Sue. When Sue rejects the purchase order, it is given the status of Rejected and the workflow process is complete. Sam can resubmit the purchase order, with or without changes. If Sam resubmits the purchase order, a new workflow process starts at the first step.
3-9
Request Change
When an approver requests a change to a document or batch, the document or batch is given the status of Pending Changes and the workflow process is complete. The originator, however, can make changes and resubmit the document or batch for approval. For example, using the workflow previously shown, suppose that Sam has submitted a purchase order for $12,000 and that it is assigned to Sue. When Sue requests a change, the purchase order is assigned the status of Pending Changes and the workflow process is complete. Sam can resubmit the purchase order, with or without changes. If Sam resubmits the purchase order, a new workflow process starts at step one.
3-10
Challenge Yourself
Phyllis decides that only seven conference phones are necessary. Request a change to the purchase order to reduce the quantity ordered to seven.
Step by Step
1. In Microsoft Dynamics GP click the Purchasing series button, then click Purchase Order Transactions on the navigation pane menu. 2. Select purchase order PO2112, and click the Edit button on the action pane. 3. In the Purchase Order Entry window click the Request Change button on the workflow wrapper. 4. In the Add Comment box enter the following comment We only acquired seven new offices, please reduce the order to 7 phones. 5. Click the Requst Change button.
3-11
Status
A document or batch in workflow has one of the following statuses. Status Workflow Not Activated Not Submitted No Approval Needed Description The document or batch was created before a workflow was activated. The document or batch has been saved, but not yet submitted for approval. The document or batch has been submitted for approval, and does not require approval. The workflow approval process is complete. The document or batch has been submitted for approval, but the web server-running Office SharePoint Server and the Workflow server components has not responded yet. The document or batch is awaiting approval. An approver has requested that the originator make changes to the document or batch and resubmit it. The workflow approval process is complete. The document or batch is approved. The workflow approval process is complete. The document or batch is rejected. The workflow approval process is complete. The Workflow administrator or manager deactivated the workflow this document or batch was using. The workflow approval process is complete.
Submitted
3-12
The user assigned to the document may edit the priority of the document at any time. The priority of the document will be displayed on workflow tasks and notifications related to the approval of the document. HINT: If the document priority is updated, after the document is submitted, existing tasks and notifications will not be updated with the new priority. The originator or the assigned approver(s) may select/edit the priority of the document. If more than one approver is assigned to the approval routing, the latest approver will update the priority.
Reporting
The following sections explain how to view documents and batches that have been submitted to the Workflow system, and their workflow history. In addition the details of several reports are discussed. All the reports displayed in this lesson are accessible via the Workflow web site.
Document Views
It is possible to view documents and batches submitted to the Workflow system in several areas of Microsoft Dynamics GP. For example, you can view a submitted purchase order in the Purchase Order Entry window or in purchase order lists. It is also possible to view documents and batches submitted to the Workflow system on the Workflow web site. Use the following steps to view submitted documents and batches on the Workflow web site. 1. Go to the Workflow web site. 2. Click Documents on the Quick Launch.
3-13
View History
The workflow history of a document or batch can be seen by viewing the workflow history pane in certain Microsoft Dynamics GP windows. For example, to view the workflow history of a purchase order, open the Purchase Order Entry window in Microsoft Dynamics GP and view the workflow history pane. The workflow history of a document or batch may also be viewed on the Workflow web site. Use the following steps to view workflow history information on the Workflow web site. 1. Go to the Workflow web site. 2. Click Documents on the Quick Launch. 3. In the Workflow Documents page click a workflow type. The documents or batches that you submitted and are pending approval are listed. 4. From the View menu, click All Items. All documents or batches submitted to this workflow are listed, regardless of who submitted them or their approval status. 5. From the View menu, click Modify this View. The Edit View: <Workflow Type> page is displayed. 6. In the Columns area of the page, select the Approval Status check box. 7. Click OK. 8. An Approval Status column now appears on the page. To view the workflow history of a specific document or batch, click the status of that document or batch. The Workflow Status: Approval Status page is displayed. Workflow history information is shown at the bottom of the page.
3-14
3-15
Summary
Approvers have several options when acting on workflow tasks. Many reports are available through the Workflow web site that may appeal to various workflow participants. The workflow status assigned to a document or batch is imported when determining what actions can be performed.
3-16
Approver Actions
2. If an approver requests a change to a document or batch which of the following best describes the originators options? ( ) The originator must appeal to the workflow manager for approval or start a new document or batch ( ) The originator can resubmit the document or batch, and it will return directly to the approver that requested the change ( ) The originator can resubmit the document or batch, but it will have to restart the workflow at the first step ( ) The originator cannot resubmit the document or batch, they must start over with a new document or batch
3-17
4. When a document or batch is submitted through workflow it is assigned a priority. Which of the following would indicate a normal priority document or batch? ( ) Downward pointing arrow ( ) Exclamation mark ( ) No indicator ( ) Red flag
3-18
2.
3.
3-19
Solutions
Test Your Knowledge
Methods for Action
1. Which of the following are valid interfaces for interacting with the Workflow system? Mark all that apply. () Microsoft Outlook ( ) Microsoft PerformancePoint Server () Microsoft SharePoint Server () Microsoft Dynamics GP
Approver Actions
2. If an approver requests a change to a document or batch which of the following best describes the originators options? ( ) The originator must appeal to the workflow manager for approval or start a new document or batch ( ) The originator can resubmit the document or batch, and it will return directly to the approver that requested the change () The originator can resubmit the document or batch, but it will have to restart the workflow at the first step ( ) The originator cannot resubmit the document or batch, they must start over with a new document or batch
3-20
e 1: An approver has requested that the originator make changes to the document or batch and resubmit it. b 2: The Workflow administrator or manager deactivated the workflow this document or batch was using. a 3: The document or batch was created before a workflow was activated. f 4: The document or batch has been submitted for approval, and the Workflow system has determined that the document or batch does not require approval. c 5: The document or batch has been saved, but not yet submitted for approval. d 6: The document or batch is awaiting approval. g 7: The document or batch has been submitted for approval, but the web server - running Office SharePoint Server and the Workflow server components - has not responded yet.
4. When a document or batch is submitted through workflow it is assigned a priority. Which of the following would indicate a normal priority document or batch? ( ) Downward pointing arrow ( ) Exclamation mark () No indicator ( ) Red flag
3-21
3-22