How the Actual Approving Person is Selected

When the user finished specification of a request by clicking the 'Forward Request to Processing' button (or when the approval person restarted approvals), then Valuemation checks each request item and generates internal approval tasks ('SRM Configurable Task Result' objects) in status 'To Do'. It assigns the tasks to persons (until a person is found) using the following sequence of priorities:

For approval defined by a condition:

1. default person in general - as defined in SRM Configurable Task
2. random member of default group in general - as defined in SRM Configurable Task
3. if a person is still not available, the task is not generated

For approval defined for Item:

1. default responsible person - defined for Item Responsibility
2. random member of responsible group - defined for Item Responsibility
3. random member of default group in general - as defined in SRM Configurable Task
4. default person in general - as defined in SRM Configurable Task
5. if a person is still not available, task is not generated

Special: approval as Project Leader defined with 'Assignment = Dynamic':

1. leader of Project assigned to Request
2. default person in general - as defined on SRM Configurable Task
3. if a person is still not available, task is not generated

Special: approval as Organization Manager defined with 'Assignment = Dynamic':

1. approver linked to the request by the requestor or by default
2. first leader derived from the request using settings on the 'Request Approval' tab of 'Settings - Requesting & Procurement'
3. default person in general - as defined in SRM Configurable Task
4. if a person is still not available, task is not generated