Any resource approver "reject" rejects entire workflow.

I was working on a custom "Update User" workflow, but have discovered that this occurs with the native workflow in the environment I am working in.

When any resource approver rejects, provisioning is never called even if other resource approvers have approved.

Chapter 4 of the admin guide suggests that a resource approver should be able to reject individually, but it is not explained in detail.

Any inspiration would be appreciated.

[460 byte] By [seanpower] at [2007-11-26 8:30:40]
# 1
FYI, I resolved this by iterating over waveset.resources and spawning a new approval thread for each resource, and subtracting it from waveset.resources if the data owner rejects it, so that why it comes time to provision, only approved resources remain.
seanpower at 2007-7-6 21:51:30 > top of Java-index,Web & Directory Servers,Directory Servers...