Overview:

Schemas are a grouping of Workflow rules that affect the nominated Document Type. Workflows must be enabled in Control Parameters before documents can be submitted to a Workflow. You can adjust each schema to affect the desired Entities, providing potential for detailed application across various areas of your company.

Workflows allow for a broad range of situations and processes, and while this guide cannot cover them all, it will go through how to build a Workflow for your company's needs.

The Permissions “Workflow Reviewer” and “Workflow Approver” are useful for validating workflow functions. They are granted to global ‘General’ Role by default to limit disruption to Purchase Requisition workflows. Remove them from General if required for vouchers, but then they should be granted to the respective PR roles.
The default workflow behaviour is to assign a reviewer or approver that is different to the prior step to avoid actioning by the same person.
Voucher Credits are a separate Document Type and requires their own Workflow.

Screen Guide:

Workflow Schema List

The initial screen lists all existing Schemas. The Workflow Schema field serves as a link to open the editing window.

+ New Workflow Schema. button is used to create a new schema.
View history button allows you to view the record of all modifications made.

Create/Edit Schema

We will use a Purchase Order Workflow for our example. Each section is detailed below:

The Header section is where we determine the Document Type. Once you choose the Document Type, give the Workflow a Description. Description can only contain "a-z, A-Z, 0-9, <underscore>, or spaces", and cannot start with a number or an underscore. Workflow Type is an optional field that can be associated with this Workflow. The Value Review Type gives the choice between the following: Multiple Value allows for a sequential review up to the document's value. The workflow would begin with the indicated user with the lowest review mandate, then once they review it, the document is passed to the user with the next highest review mandate until the value of the document has been reached. Remember, this only affects the review step and does not allow for multiple approvals. Multiple Value Review Example Reviewer/Approver Setup: Reviewer 1 - $1K Reviewer 2 - $20K Reviewer 3 - $100K Approver 1 - $1K Approver 2 - $20K Approver 3 - $1M For a $30K PO the Workflow would follow these steps: Reviewer 1=> Reviewer 2=> Reviewer 3=>Approver 3 For a $15K PO the following steps would apply: Reviewer 1=> Reviewer 2=> Approver 2 Single Value requires review from only the person with the minimum required mandate, and the option exists to select another person with a sufficient mandate. Single Value Review Example Reviewer/Approver Setup: Reviewer 1 - $1K Reviewer 2 - $20K Reviewer 3 - $100K Approver 1 - $1K Approver 2 - $20K Approver 3 - $1M For a $30K PO the Workflow would follow these steps: Reviewer 3=>Approver 3 For a $15K PO the following steps would apply: Reviewer 2=> Approver 2 Technical Review Type is used solely for Purchase Requisition Workflows and is used as a parallel review process outside of purely cost-related review such as Engineering, OH&S, etc. When selected, additional options appear: It does not consider Authority Limits and will go through all the defined Technical Reviewers in the list to complete the review process. Technical Review is the first Review step in the process before it goes to the Value Review (if any defined in the Value Schema) and Approval (which is a mandatory step). The Technical Review Group can be added to in Lookups under the "TechnicalReviewGroup" type. You can tick the box to make Technical Review Optional. Optional means that the Technical Review and the Value Review/Approval can happen in parallel, and the document can be approved eventhough the Technical review process hasen’t finished. Once the document is approved, no further technical review is required and the document is removed from the Technical Reviewers’ list of documents to review.

This tab is where you can enter the Workflow steps. Sequence is the numerical order that the steps should be completed. Review/Approval gives you the choice between whether the step should be a Review, Approval, or Unapproval step. Person allows you to nominate a particular User that should be doing the step. Function gives you more contextual options for the step. The options will change depending on the Document Type: Me – The user performing the previous action, i.e. Submit or Review PO Purchaser – The user listed as the purchaser of the PO PO Approver – The user who approved the PO PO Purchaser if Unreceipted - If the PO is unreceipted or all receipted quantity has been vouchered then route to PO Purchaser, else go to the next WF step. PO Entered By else Send Back - Route to the PO Entered By if valid else Send Back; but if PO Entered By has insufficient limit then go to next WF step. Job Manager - based on the job referenced in the first line of the document Job Account Manager - based on the job referenced in the first line of the document Subcontract Administrator - the user listed in Subcontract Settings as the administrator on the respective subcontract; the reassign list is any active person with a login. Subcontract Administrator Only - the user listed in Subcontract Settings as the administrator on the respective subcontract; the reassign list is any active person with a login and assigned as a subcontract administrator. All Voucher Users - Lists all people with a valid voucher limit, filtered by the first line Job Profit Centre. Note this function only works for Single Value workflow schema to support a manual allocation workflow. Profit Centre Manager: Document JobCode → Jobs. ProfitCentreCode → ProfitCentres. Manager. For documents without a Job at the header, the first line’s Job Code will be used. Location Manager: Document JobCode → Jobs. ProfitCentreCode → ProfitCentres. LocationCode → LocationManager. For documents without a Job at the header, the first line’s Job Code will be used. Job Person Roles may also be reference in the same way, refer Using Job Roles in Workflows Derive Limit resets the Limit to 0 and derives the user's normal approval limit from their User's Settings, depending on the Document Type. Additionally, voucher also supported review-specific limits via the ‘AP Voucher Use Review Limits’ control parameter. This enables workflow review steps with Derive limits to refer to the ‘Voucher Reviewers Limit’ setting rather than the standard ‘AP invoice Approvers Limit’ setting. Limit is the document's value limitation that the step can review or approve. Note, specifying a step limit takes precedence over any Derived limits specified for the related users on that step. For example, selecting "All Voucher Users" with a specified step limit will display all active users with a login and applies the step limit. Decline Allowed indicates that the user can reject the document, preventing it from being resubmitted (this should not be allowed unless the user has authority to do so - the option to Send Back is otherwise available).

Since the Workflows Schemas are defined to approve documents within the specific context, the Auto Approval setup is within the same context i.e. applied based on the document type and defined WF Entity matching criteria. In the absence of any specific approval method the evaluation will fall back on the standard manual WF process. Sequence is the order of method evaluation. Method specifies approval rule to apply. Several are available and may be added as relevant to this WF Schema. Description provides a brief of the method with Param Description as details on the parameter. Comment is available to make relevant notes regarding the configuration in use. P1 - P5 provides setup supports for one or more parameters to set the method tolerances. Although blank will be interpreted as N/A there must be at least one parameter specified. Enable allows each method to be enabled/disabled if required. For further detail refer Using Auto Approval Methods below.

Buttons

The image above is compiled to display the applicable buttons for illustrative purposes rather than what it would look like during normal use.

Assign

The Assign is available before submission into the Workflow and allows for ad-hoc assignment, typically for coding of lines.
The User settings ‘AP/AR/PO/Voucher Assigned Email’ determine if a notification email is sent to users with this setting.

Submit

The Submit button begins the Workflow process for the document and places it into the applicable Workflow based on matching Entity and Workflow Type.
Once submitted, there can be no deviation from the schema used.

Review

Review is available to the assigned reviewer (or a Voucher Admin) and indicates the document has been reviewed by the user.
This review process may be for coding of lines, ensuring receipt of goods, or as a preliminary approval step where more than one approval is required (a document can only have one final approval).

Send Back

Send Back will return the document to the requester (the person who submitted to document), or in case of an auto submit, the requester as defined by the Setting "AP Voucher Auto Requester."
The document may be re-submitted.

Decline

Rejects the submission with a ‘Declined’ status, and the document is disabled from further updates.
An email notification is sent to the requester, and the document may NOT be re-submitted.

Cancel

Marks the submission with a ‘Cancelled’ status, and the voucher is disabled from further updates.
An email notification is sent to the requester, and the document may NOT be re-submitted unless uncancelled.

Uncancel

Uncancel reverts the voucher status to New and allows reprocessing of a document.

WFlow | Msg

Displays a trail of the workflow progress.
Also supports the display of prior workflows if the document was re-submitted.
It also allows ad-hoc messaging with an audit of previous messages sent in the Messages tab.

Valid Workflow Description
Workflow Schema Description cannot start with a number or contain spaces or special characters. Naming rules:

Description can only contain "a-z, A-Z, 0-9, <underscore>, or spaces", and cannot start with a number or an underscore

Using Job Roles in Workflows

This functionality allows Job Roles to be leveraged in Workflows Schemas. The key points are:

improved formality on the list of “valid” Roles for people on a Job
visibility of invalid Roles
ability to leverage defined people with defined Roles on a Job context
equivalent in concept to the base Workflow functions already available

A. Lookup Type - defines valid roles

The Lookup of Type ‘JobPersonRole’ is added to define valid roles appropriately to avoid duplication or variations like ‘QS’ or ‘Q.S.’ or ‘Surveyor’.
Two default roles are available -‘Supervisor/Foreman’ and ‘Project Engineer’, but the roles can be client managed and are not fixed.
Validation are in place to prevent deletion of referenced roles, and addition of exact duplicates.

B. Job Details - defines a person’s role on a job

The Role on People tab of Job Details uses the new Lookup list but any existing data mismatched data will display as highlighted.
Highlighted / invalid roles cannot be referenced in workflow schemas.

C. Workflow Schema - can reference a Person via their Role on a Job

The Function picker on the Steps tab is updated to include all defined Job Person Roles, and identified as Role to identify the context.
As per base workflow functions the Job Roles support Workflow Step limits and Derived limits based on the resolved person.

D. Workflow Process - explains resolution of Job Roles in Workflows

As per base workflow functions the Job Person Role and Job context resolve to the specific person.
For a valid resolution the person must be Active and Has Login, and an applicable Workflow Step limit or Derived limit.
A resolution failure will escalates to the next workflow step, for example if the Person Role is not defined on the context Job or the person is Inactive.
The Reassign list of people are filtered based on the assigned Person Role, and must be Active and Has Login with an applicable Workflow Step limit or Derived limit.

Using Auto Approval Methods

The auto approval methods applied for a workflow are setup in the Approval Rules tab (AP Voucher only) of the WF Schema popup.

Evaluation - On Submit

If there are auto approval methods enabled on the WF Schema then the evaluation process is:

Perform general pre-validations for
- Header values match line totals
- Payment Due date specified
- Every line coded to Job, Activity and Work Centre
- Every line has a GST Type
Iterate the enabled Method set in sequence and execute each method on specified parameters
An evaluation method may assess the document in total or on a per line basis, or both.
The evaluation process will short-circuit at the first FAIL as:
- at least one FAIL, or
- after all method evaluations there are only SKIPs i.e. so no valid parameters were given

Evaluation Result

On completion of auto approval evaluation, a banner displays the overall result.

A. The overall result of auto approval evaluation will be displayed in a banner that is retained even if the popup is reopened to that it can inform the next person.
B. Any specific lines that triggered a FAIL or SKIP displays an icon that links to their relevant auto approval evaluation audit.
C. The ‘Auto Approval History’ tab of the WF / Msg popup displays the full history of the latest evaluation:
- PASS: the document or line passes the evaluation method criteria
- FAIL : the document or line fails the evaluation method criteria
- SKIP : the document or line skipped the evaluation as no parameters were given
- NA: line was beyond the method scope, so ignored in assessing PASS/FAIL but audited
D. The overall result is also recorded in the WF audit trail
E. If the auto approval fails, then the voucher falls to the standard manual WF process

Evaluation Methods

Auto Approval Methods are available for AP Voucher only. These are:

TotalMaxValues - The AP voucher incl. Total value and its elements must be below or equal the set value parameter if specified. Refers to max allowed for the voucher and by line type. Line totals are Excl. Tax. Blank = not checked; set at least one:

P1 Voucher total (Incl. Tax)
P2 PO lines
P3 Stock location job lines
P4 Docket lines
P5 Manual lines

LineRateToPoLineRate - The Qty and Value of the voucher line rate must be within the tolerances of the matched PO line rate. Line rate (Value ÷ Qty) vs PO unit cost, compared per unit. Blank = not checked; set at least one. Skips lines with no PO line, and bulk lines: no qty, or sharing a PO line with another line:

P1 Max $ variance
P2 Max % variance

LineRateToCatalogueRate - The Rate of the voucher line must be within the tolerances of the matched Catalogue line rate. Line rate (Value ÷ Qty) vs Catalogue cost rate, compared per unit. Blank = not checked; set at least one. Skips lines with no Catalogue line, and bulk lines: no qty, or sharing a Catalogue line with another line:

P1 Max $ variance
P2 Max % variance

LineRateToDocketScheduleRate - The Rate of the voucher line must be within the tolerances of the matched Docket Schedule line rate. Line rate (Value ÷ Qty) vs Docket schedule rate, compared per unit. . Blank = not checked; set at least one. Skips non docket lines, and bulk lines: no qty, or sharing a docket with another line:

P1 Max $ variance
P2 Max % variance

AllVouchersToTotalPO - The Total Value of this and previous vouchers must be within the tolerances of the matched PO value. This and previous vouchers vs PO value. Blank = not checked; set at least one. A part vouchered PO always passes:

P1 Max total $ over
P2 Max total % over

Next Steps:

Once you have set up a new Workflow, be sure to test it to ensure the steps progress as intended. Ensure all users who will be part of the Workflow understand their role and the actions they can take.

Related Pages:

Workflow

FAQs:

Process Flow:

Workflow Schemas