I recently built an approval‑assignment rule that returns the correct list of approvers based on an entitlement’s extended attribute.
The rule works as expected for single‑entitlement requests. For example, I created an entitlement called ADTestDisplay183, and the request is correctly routed to its designated owner workgroup.
However, when a request contains more than one entitlement, the approver list is inaccurate because the items are grouped together and only one approval is generated. For instance, a request that includes ADTestDisplay182 (which should go to the requester’s manager) and ADTestDisplay183 (which should go to the owner workgroup) is sent only to the manager for approval.
Please make sure you are calling the approval assignment rule in the appropriate subprocess. It seems you are requesting multiple entitlements. To my knowledge, if there is a approvalSplitPoint defined, approvals will go all in as a single package to approvers before splitPoint through Pre-Split Approve. Post that, in Approve and Provision Subprocess - each item will follow its approval defined from approvalAssignment and its provisioning later.
