This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
In this article, a scenario is described where for a client event, all the named destination users in the destination set approve the activity. At the same time, a role has been specified and at least one (1) of the users from the role must approve as well.
The approval rule logic would resemble the following:
Client Activity is Approved WHEN all individual approvers approve AND at least one of role approvers approve.
The approval scenario described here, was difficult to implement in K2.net 2003 without splitting the approval process into 2 separate client activities. The same scenario can now be achieved by using the following settings in K2 blackpearl. The scenario below which has been tested to be functionally working, will demonstrate how this can be done in one activity by implementing the following settings.
- The scenario does not apply if two (2) or more users in the role are required to approve
- The scenario does apply if more roles are required to approve, so long as one (1) user in each role can approve