Example: Leave of Absence - Offboarding and Onboarding
A leave of absence can be applied to staff who will be on extended leave, such as sabbaticals, study, parental, and medical leave. A manager will request a leave of absence on behalf of a user and set start and return dates. A scheduled task will run to trigger the leave of absence and disable the user’s accounts.
Since leaves of absence are intended to be reversible, accounts are not deleted, and group memberships are not revoked – the only actions are to disable and later re-enable accounts and user profiles.
This example shows how to install the component that controls corporate leave of absence policies, lists the pre-defined requests that will need customization to your environment, and walks you through a leave of absence request.
Requirements
This example assumes that:
Bravura Identity and Connector Pack are installed.
An Active Directory target system has been added as a source of profiles
Deploy Leave of Absence
To deploy the leave-of-absence component:
Install
Scenario.im_corp_loa
.Click Manage external data store to verify the following tables are available and configured for the environment:
HID_GLOBAL_CONFIGURATION to set targets that are a source of profile ID
HID_POLICY_ATTRVAL_DEFAULT to set relative default values
HID_POLICY_ATTRVAL_VALIDATION to set input validation
IM_LEAVE_OF_ABSENCE to set leave of absence configurations
IM_POLICY_AUTHORIZATION to set authorizations for the requests
Configure the membership of the LOA-AUTHORIZERS user class.
Configure the following pre-defined requests:
LOA-EFFECTIVE
LOA-REQUEST
LOA-RETURN
LOA-RETURNED
As a manager, request a leave of absence using the pre-defined leave of absence request
To test this feature, request a leave of absence:
Log in to Bravura Security Fabric as a manager.
Click View and update profile under Other users .
Select the user to request a leave of absence for.
Click Leave of absence.
Fill out and submit the request.
If required, log in to Bravura Security Fabric as an authorizer and approve the request.
Allow the start date to pass so that LOA-EFFECTIVE can trigger the event.
Verify that the user has been modified as follows:
The user’s status should be set to on leave.
The user’s profile and account should be disabled.
See also:
Pre-defined requests for more information about configuring pre-defined requests and user classes.
Installing components for information about installing components.