SuiteApprovals Considerations
Take note of the following considerations when using SuiteApprovals:
-
If you created recurring journal entries using memorized transactions before enabling the Approval Routing feature, SuiteApprovals will not process these transactions. If you want SuiteApprovals to process these journal entries, you must recreate each transaction record.
-
The Administrator role is not available in approval matrices.
-
The Mirror Approval record is a SuiteApprovals custom record. Only the SAS Mirror Approval UE script must be deployed to the record.
Deploying other scripts to the record can cause errors in the approval workflow. You must review script deployments to all records in your account.
-
A record submitter cannot be an approver.
-
Transaction records are not routed for approval under the following conditions:
-
The transaction is created before the approval rule's start date.
-
The transaction is created through CSV import, script deployment, web service, or RESTlet.
-
-
If you are using SuiteApprovals for purchase orders or expense reports, the approval hierarchy follows that of the Employee field of the record. If there is no employee specified on the record, the rule uses the submitter’s hierarchy.
-
If there is a Pending Approval transaction that is using the approval matrix, you cannot delete that approval matrix of the approval rule.
-
Approvers using roles with Core Administration Permissions are not supported.
-
Journals that are approved for posting or pending approval cannot be edited.
-
The Email Approvals feature does not support Engineering Change Orders.
-
Voided transactions are not supported. When a transaction is voided, the SuiteApp will do the following:
-
When an approver approves or rejects a voided transaction through email, the approver will receive the Approval Action Denied email notification.
-
When a transaction in Pending Approval is voided, it will remain in Pending Approval.
-
The Approve and Reject buttons are removed from the transaction record.
-