You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Maintenance Work Order Approval based on Position Hierarchy

in Maintenance

Summary:

Maintenance Work Order deferred approval (WorkOrderDeferredApproval), works successfully when the list builder is used as 'Approval Group' & 'Resource', and the work order progresses from Pending Approval to Released after approval. However, both Position and Supervisory list builders fail to resolve approvers, even though the same users, employee assignments, positions, position hierarchy, and supervisory relationships are valid. For the same Employee - Position setup, it works successfully in case of Purchase Requisition approval.

We tested static position IDs, hard-coded Fusion usernames,Task.creator, getManager() and getPrincipal() expressions, simplified level settings, and isolated single-rule scenarios, but hierarchy-based routing still does not trigger. This indicates a likely issue with hierarchy resolution specifically within the

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!