Scenario Background:
An existing employee has moved to a new job in a different department.
Scenario Narrative:
- Job information is updated in the institution's HR system. The employee's former job is given an end date, and the new job is entered.
- An institutionally defined process invokes Person Registration and Update either via REST API call (synchronous method) or by placing a Person Update message in the Person Update queue (asynchronous method). The payload of this message contains both the end-dated former job and the new job, as well as the source system identifier for the employee.
- Person Registration will invoke Person Search service to find the proper person for this update, based on the source system identifier supplied.
- Person Registration will update the job information in the Master Person Store.
- Person Registration will invoke Group Update through a REST API (synchronous method) or by placing a Person Update message in the Person Update queue (asynchronous method).
- Groups Service will evaluate dynamic group memberships for the employee, removing them from groups relating to the former job and adding them to groups relating to the new job.
- Groups Service will invoke Provisioning Service via REST API (synchronous method) or by placing a Group Update message in the Group Update queue (asynchronous method).
- Provisioning Service will dynamically deprovision services relating to the former job and provision services relating to the current job.
- Services that are provisioned to 'all employees' will not be deprovisioned, as the employee will remain in this group.
- Services that are provisioned by specific characteristics of a job (title, employing department, etc) can be deprovisioned according to institutional policy
- Services that were requested by the employee under the former job can be deprovisioned according to institutional policy