Approvals February '23 Release Notes

Approval request records created with an ad-hoc process are not displayed under the approvals related list on an agreement record.

Customers can include comments when submitting an object for approval.

Approving a quote or proposal via email results in a System.LimitException: Regex too complicated error and user cannot approve quote.

On taking ownership of a queue, the user must load the My Approvals tab twice before seeing the correct approval process.

In the Approval Rule Assignee object, customer is hitting the Assignee Value field’s maximum character limit.

Increased the Assignee Value field for the ApprovalRuleAssignee__c object from 255 to 2048 characters.

If Recall Comments Enabled on the approval process is set to TRUE, the system cannot recall that the user has clicked the Recall Approvals button on the OOTB page (CartApprovals).

“Approve / Reject” and “Add Comment” hyperlinks work inconsistently for Apttus_Proposal__Proposal__c and Apttus__APTS_Agreement__c objects.

Customer receives Too Many Queueables error when APTS_QueueableSubmitChunkSize = 100 with Autocomplete Step set.

rejectRequestsBulk API only marks first approval request as rejected, leaving remainder marked as assigned.

On a greater-than-30% discount, the system does not create approval requests as configured. When the async submit job fails with an Apttus_Approval: Too many DML statements: 151 error, the async action info object record still shows "Processing" and no email is sent to the submitter.

When submitting an agreement record with an attachment for approval, selecting the attachment with a version number returns an Attempt to de-reference a null object error.

The approval request creation DML logic must be optimized.

rejectRequestsBulk API only marks the first approval request as rejected leaving remainder marked as assigned.

Under certain conditions, the system does not approve all consolidated approval requests affirmed by email approval.

Having upgraded to Sep 21, a customer (using approvals on a Proposal object and OOB approval actions on an Approvalrequest object) clicking Approve/Reject or AddComment receives the error:
SObject row was retrieved via SOQL without querying the requested field: Apttus_Approval__Approval_Request__c.Apttus_Approval__Approval_Process__c

Having upgraded to Sep 21, a customer (using approvals on a Proposal object and OOB approval actions on an Approvalrequest object) clicking Approve/Reject or AddComment receives the error:
SObject row was retrieved via SOQL without querying the requested field: Apttus_Approval__Approval_Request__c.Apttus_Approval__Approval_Process__c

When updating a quote to “Draft” status and submitting it for approval while the approval request status is in “On Hold”, Approvals responds with a null email body error: SendEmail failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Email body is required.

When the user sets the Assignee Escalation to Type field in the Auto Escalation setup to “User” the system throws an SObject row was retrieved via SOQL without querying the requested field: User.Profile error.

Clicking the product configuration tab produces the error:

message.Apttus_Approval:Too many query rows: 50001

Error is in expression '{!ctxObjType}' in component <cnga:filtercardcomponent> in component cnga:filtercardcomponent

When the customer adds a custom validation error to an agreement term exception page, the error message is displayed twice.

Adding the user and saving an ad hoc process produces an Attempt to de-reference a null object error.

When trying to create a backup approver, user receives a Backup user has an active backup approver in the system error if the effective and expiration dates do not overlap.

Attachments to an approval request are duplicated when the approval request is reassigned.