Approval Chain Import

Overview

The Approval chains Import process reads files from ./Incoming/ApprovalChains/ in the SFTP. These files will be moved to the archive folder located at ./Incoming/Archive/ApprovalChains/ before being processed in alphanumeric order.

Keys & Validations

Approval Chain Name and Approval Chain Type are the keys to update an existing approval chain. Both these keys are needed in order to perform an update. You cannot update the type of an existing approval chain.

You cannot create Orders and Requisitions approval chains with the same name. Loading an approval name for orders with the same name of an existing one for requisitions through the bulk loader will cause the Approval Chain Type to change from "requisition" to "order" (it's also true vice versa).

Currently supported conditions and operations:

  • Accounts (equals, contains)

  • Commodity (equals, contains, not contains)

  • Item (equals, contains, not contains)

  • Requester (equals, contains, not contains)

Approval chains created through the loader follow the same validations as those created through the UI.

Note: Priority cannot be 50 because 50 is the management hierarchy. This means that a chain that's less than 50 fires before management hierarchy while a chain that's greater than 50 fires after management hierarchy.

Approval Chain

Field NameRequired FieldUnique?Field TypeField DescriptionPossible Values
Approval Chain NameNoNoUnique Approval Chain Name
StatusNoNoActive or Inactive
Approval Chain TypeNoNoSome possible values: requisition requisition-submission-blocking requisition-approval-blocking requisition-hierarchy expense invoice invoice-submission-blocking invoice-submission-warning invoice-approval-blocking invoice-hierarchy contract-hierarchy contract contract-submission-blocking contract-submission-warning easy-form-user contract-round worker-assignment worker-assignment-hierarchy worker-assignment-submission-blocking worker-assignment-submission-warning worker-assignment-exception-handling worker-assignment-change-request worker-assignment-change-request-hierarchy worker-assignment-change-request-submission-blocking worker-assignment-change-request-submission-warning worker-assignment-change-request-exception-handling
PriorityNoNoOrder in which to evaluate approval chain. Number from 1 to 49 and 51 to 99
Skip ApproversNoNoSkip Approvers prior to self if on approval chain
Skip Management HierarchyNoNoSkip Management Hierarchy if this chain matches
Skip Further ApproversNoNoSkip Further Approvers if this chain matches
Auto Approve SelfNoNoAuto Approve Self if added to approval chain
Dedupe OBO User and Auto ApproveNoNoOverride On Behalf Of user, keep the approval chain approver and auto approve the approval
Always EvaluateNoNoAlways Evaluate
ParallelNoNoParallel approvals supported
Total ComparatorNoNoThe total comparator
Minimum Total AmountNoNoMinimum allowed approval total
Maximum Total AmountNoNoMaximum allowed approval total
Total CurrencyNoNoCurrency Code for total currency
Minimum Approval LimitNoNoMinimum Approval Limit
Maximum Approval Limit AmountNoNoMaximum Approval Limit Amount
Maximum Approval Limit CurrencyNoNoMaximum Approval Limit Currency
Maximum Approval LimitNoNoMaximum Approval Limit
OperatorNoNoThe conditions operator
Condition 1NoNoCondition 1 - Colon : seperated list of val:field:condition
Condition 2NoNoCondition 2
Condition 3NoNoCondition 3
Condition 4NoNoCondition 4
Condition 5NoNoCondition 5
Condition 6NoNoCondition 6
Condition 7NoNoCondition 7
Condition 8NoNoCondition 8
Condition 9NoNoCondition 9
Condition 10NoNoCondition 10
DescriptionNoNoSet custom notification text for the condition(s) you have set above. If you leave this field blank, the system will use the name of the configuration you set as the default text.
Approver 1NoNoApprover 1 - Colon : seperated value consisting of user_login;amount;currency_code
Approver 2NoNoApprover 2
Approver 3NoNoApprover 3
Approver 4NoNoApprover 4
Approver 5NoNoApprover 5
Approver 6NoNoApprover 6
Approver 7NoNoApprover 7
Approver 8NoNoApprover 8
Approver 9NoNoApprover 9
Approver 10NoNoApprover 10
Watcher 1NoNoWatcher 1 - User Login to add as watcher
Watcher 2NoNoWatcher 2
Watcher 3NoNoWatcher 3
Watcher 4NoNoWatcher 4
Watcher 5NoNoWatcher 5
Approver ParamsNoNosemi-colon ; seperated list of parameters. Each parameter begins with an identifier than any needed values seperated by a colon : Example identifiers are first_approver, middle_approvers and last_approver. sample values for these are skip, watcher, or approver. Other examples are escalation:User:<UserLogin>, escalation:ApprovalGroup:<GroupName> where the bracketed values should be replaced by the actual Login or Name.
Validation MessageNoNoApproval Chain Message / Description
Signatory 1NoNoSignatory 1 - User Login to as signatory
Signatory 2NoNoSignatory 2
Signatory 3NoNoSignatory 3
Signatory 4NoNoSignatory 4
Signatory 5NoNoSignatory 5
Applies to SupplierNoNoApplies to Supplier

Approval Group

Field NameRequired FieldUnique?Field TypeField DescriptionPossible Values
NameYesYesstring(255)Name
IdNoNointegerUnique identifier Coupa assigns when a new record is created. It can’t be modified, but can be used to update the record.
ActiveNoNobooleanWhether this Project or Group is currently Active.
OwnerNoNoOwner group receives notifications on Approval Group errors. Field is called Parent Group in the UI.
Users By LoginNoNoA semi-colon seperated list of Logins for all users of this project or group.
Users By Employee NumberNoNoA semi-colon seperated list of Employee Numbers for all users of this project or group.
DescriptionNoNoDescription