Approval-Related Operations
Use the Submit
(XML API) or submit()
(SOAP API) command to submit transactions of a supported type for approval.
Use the Approve
(XML API) or approve()
(SOAP API) command to approve transactions that were submitted for approval.
Use the Reject
(XML API) or reject()
(SOAP API) command to reject transactions that were submitted for approval.
Use the Unapprove
(XML API) or unapprove()
(SOAP API) command to unapprove transactions that were previously approved.
A submit, approve, reject or unapprove command passes the following parameters and arguments:
-
type
— (XML API only) You must specify the type of object you want to submit, approve, reject or unapprove. For information about supported object types, see Object Types Supporting Approval-Related Operations. -
Objects — All command must include the object(s) to be submitted, approved, rejected or unapproved as argument and an approval action information [
Approval
] object. Object properties must include the object internal ID [id
]. -
Attributes — You can use the following attribute to submit the transaction for approval even if there are warnings concerning the transaction.
Object Types Supporting Approval-Related Operations
The following table lists the object types for which the XML API and SOAP API support approval-related operations.
Approval routing is available for other transaction object types in the OpenAir UI. Some transaction approvals are available as standard if the transaction type is available, other transaction approvals are optional. For example, account administrators optional transaction approvals for invoices in the OpenAir UI (Administration > Global Settings > Organization > Approval Options). See Approval Routing.
Transaction Type |
Object Type |
Notes |
Submit |
Approve |
Reject |
Unapprove |
---|---|---|---|---|---|---|
Booking |
Mutually exclusive with booking request approvals |
|
|
|
|
|
Expense report |
— |
|
|
|
|
|
Invoice Credit invoice Rebill invoice |
Optional |
|
|
|
|
|
Receipt |
Reject operation only. Other operations are supported indirectly as part of an |
|
|
|
|
|
Time entry |
Reject operation only. Other operations are supported indirectly as part of an |
|
|
|
|
|
Time off request |
— |
— |
— |
— |
|
|
Timesheet |
— |
|
|
|
|