This section describes the business logic used in the Resource Kit when a termination occurs. The Resource Kit is kept very generic and flexible so that it can be quickly reused in many different environments.
A termination date is entered into PeopleSoft.
This request adds a termination start date to the user object.
As soon as the termination start date exists, a work order is created with a termination date. The termination date can be set in the future. The work order keeps checking the termination date until it reaches the current time.
As soon as the termination date is the current time, the entitlement for the user is revoked. This is an automated process done by a workflow.
As soon as the entitlement is revoked, the process trigger (job), the business logic driver, and the state machine driver work together and compare the termination date versus the last working day. They do not need to be the same day. When they have the termination date and the last working day, the drivers and the job are able to complete the termination process.
For more information about the termination process, see Section 5.6, Termination Process.
When the termination process reaches the ready to terminate state, another work order sets the employee status to terminated and the login disabled attribute to true.
The termination process reaches the terminated state, the employee is terminated, and disabled. All access to resources has been revoked by the entitlements.
A termination date is entered into PeopleSoft.
This request adds a termination start date to the user object.
A workflow is created and sent for approval. This could be to a manager, an HR person, or anyone else who must approve terminating an employee.
When the termination is confirmed, a work order is created with a termination date. This termination date can be set in the future. The work order keeps checking the termination date until it reaches the current time.
As soon as the termination date is the current time, a workflow is started and sent to the manager to grant approval for the user’s entitlements to be revoked. This is an automated process done by the workflow. The manager can either approve or deny that the entitlements are revoked.
As soon as the termination start date exists, a work order is created with a termination date. The termination date can be set in the future. The work order keeps checking the termination date until it reaches the current time. This also sets the last working day for the employee.
As soon as the entitlement is revoked, the process trigger (job), the business logic driver, and the state machine driver work together and compare the termination date versus the last working day. They do not need to be the same day. When they have the termination date and the last working day, the drivers and the job are able to complete the termination process.
For more information about the termination process, see Section 5.6, Termination Process.
When the termination process reaches the ready to terminate state, another work order sets the employee status to terminated and the login disabled attribute to True.
The termination process reaches the terminated state, the employee is terminated, and access is disabled. All access to resources has been revoked by the entitlements.