SuiteApprovals Considerations
Take note of the following considerations when using SuiteApprovals:
Approval Routing
-
Transaction records aren’t routed for approval in the following cases:
-
The transaction is created before the approval rule's start date.
-
The transaction is created through CSV import, script deployment, web service, or RESTlet.
-
The transaction is created using a role that sets the Set By column (under the System Notes subtab) to System. For example, a transaction created using the FSM Mobile role.
-
-
If you created recurring journal entries using memorized transactions before enabling the Approval Routing feature, SuiteApprovals won't process those transactions.
If you want SuiteApprovals to process these journal entries, you must recreate each transaction record.
Approval Matrix Management
-
If there's a pending approval transaction using the approval matrix, you can't delete that approval matrix from the approval rule.
Email Approvals
-
The Email Approvals feature doesn't support Engineering Change Orders.
Journal Entries
-
Journals that are approved for posting or pending approval can't be edited.
Record Update Failed Error Banner
-
For accounts that don't have Final Approvers, you should do one of the following:
-
Set up a Final Approver for each supported record type. For more information, see Setting Up Final Approvers.
-
If you don't plan to assign a Final Approver, you can ignore the error banner. However, affected transactions will stay in pending approval status.
-
-
You can't turn off the error banner regardless of your Final Approver setup.
-
Transactions may be affected because of one of the following reasons:
-
Transactions are stuck in pending approval.
-
The values of the following fields don't match the latest entry in the Approval History subtab:
-
Approval Status
-
Next Approver
-
-
-
The error banner will appear if the transaction has duplicate serial numbers. To update the transaction, do the following:
-
Edit the affected transaction and update the serial number. For more information, see Received or Purchased Serialized Items.
-
After you update the serial number, the Final Approver must click Update Approval Information. For more information, see Updating the Approval Information of a Record.
-
-
Transactions created before version 7.02.9.a are still checked by the SuiteApp. If you view an old transaction and the approval information update fails, the Final Approver gets an email notification.
-
Final Approvers may get multiple email notifications, depending on how many affected transactions are viewed.
Each email notification is sent one time only and is unique to each affected transaction.
Final Approvers can create a saved search to list all transactions that require attention. For more information, see List All Record Update Failed Emails Using Saved Search.
-
Bulk processing of affected transactions isn't currently supported.
Roles and Permissions
-
The Administrator role isn't available in approval matrices.
-
A record submitter can’t be an approver.
-
Approvers with Core Administration Permissions roles aren’t supported.
Script Deployments
-
The Mirror Approval record is a custom record in SuiteApprovals. Only the SAS Mirror Approval UE script should be deployed to this record.
Deploying other scripts to this record can cause errors in the approval workflow. You should review script deployments for all records in your account.
Voided Transactions
-
Voided transactions aren't supported. When a transaction is voided, the SuiteApp does the following:
-
If an approver approves or rejects a voided transaction through email, the approver will receive the Approval Action Denied email notification.
-
If a transaction in Pending Approval is voided, it'll stay in Pending Approval.
-
The Approve and Reject buttons are removed from the transaction record.
-