Skip to content

Overview

Using the Integration capabilities on Hire2Retire you can create Record(s) on Hire2Retire IGA for various employee lifecycle changes. Read the official documentation of Hire2Retire IGA here.

Hire2Retire IGA Application on Hire2Retire

Figure 1. Hire2Retire IGA Application on Hire2Retire

Choose Action

You can select the action among the following on Hire2Retire:

  1. User Provisioning - Using Hire2Retire you can provision and deprovision users on Hire2Retire IGA.
  2. Incidents - This is used to create incidents in the Incident table.
  3. Records - This is used to create records in the selected table.
  4. Trigger Workflows - This can be used to trigger Hire2Retire IGA workflows. Create a record or incident and it will become a trigger for the Hire2Retire IGA workflows.
  5. Request Order Guide - This action can be used to order multiple related services as a single request.
  6. Assign Catalog Items - This action can be used to request one or more catalog items in a single request.

User Provisioning

Define Role Definition

Provisioning Type

Define Role(s)

You can assign a Role to any user based on their AD attributes. You can define complex conditions using AND and OR logic. You can also use the Group memberships in AD to define Roles. For example:In Figure 2, user(s) with Department "Sales" and Title "Sales Officer" will get provisioned and similarlily user(s) with Department "Audit" and Title "Manager" will get provisioned. Only users who get a Role assigned based on the conditions, will be provissioned. If the user is unassigned from a role-based on their updated profile in AD, and you have selected to deprovision using Hire2Retire, user will be deprovisioned from Hire2Retire IGA.

Hire2Retire IGA Provision rules

Figure 2. Provision users with following rule definitions

You can enable the "Do not deprovision upon change of profile or role" checkbox to prevent users from being deprovisioned on Hire2Retire IGA due to a role mismatch.

Hire2Retire IGA checkbox

Figure 3. Do not deprovision users upon change of profile or role

Process All Employees

All user(s) will be provisioned on Hire2Retire IGA.

Hire2Retire IGA Process All Employees

Figure 4. Process All Employees

Provision User

You can decide to either provision or deprovision user(s) using Hire2Retire IGA.

  • Provisioning - You can provision one or more user(s) to the Hire2Retire IGA according to the requirement. User(s) can be created, updated or reactivated in provisioning operation.

  • Deprovisioning - You can deprovision one or more user(s) according to the requirement. User accounts will be deactivated on Hire2Retire IGA upon deprovisioning.

Hire2Retire IGA Form Operations

Figure 5. Configure lifecycle operations for Hire2Retire IGA

Map attributes on Hire2Retire IGA

You can populate a user's profile in Hire2Retire IGA by mapping attributes incoming from the AD. You can also use Hire2Retire's powerful data transformation capabilities using Excel Style functions.

Hire2Retire IGA Form Attributes

Figure 6. Select Hire2Retire IGA attributes

Employee Identifier

An employee identifier is a unique code, number, or combination assigned to each employee within an organization. It is used to differentiate employees for record-keeping, payroll, tracking performance, and managing access to resources.

Employee Identifier

Figure 7. Employee Identifier

Configuring Records to be created on Hire2Retire IGA

Create Records

You can create one or more record on each employee lifecycle event. The record summary table will show you all the record(s) configured to be created along with the lifecycle operation for which they will be created. You can edit and delete them as per your need.

Hire2Retire IGA Form Operations

Figure 8. Creating multiple record(s) for Hire2Retire IGA on Hire2Retire

Conditional Service Desk

You can give specific condition(s) based on attribute(s) and group(s) membership to process integration. The ticket(s) will be processed if the user has been added or removed from the specified group(s) or if certain attribute(s) matches the given condition(s).

For example, if the employee is promoted to the position of senior software developer, then the integration ticket can be made to assign them a new MacBook Pro.

Jira Software on Hire2Retire

Figure 9. Conditional Service Desk on Hire2Retire

Choose Operation(s)

You can choose the operation(s) on which the specific record(s) are created in the Hire2Retire IGA. Following are the lifecycle operations for records that can be created on Hire2Retire IGA:

  1. Hire
  2. Onboard
  3. Update
  4. Termination
  5. Schedule Termination
  6. Termination: Account Deletion
  7. All type of Leaves ( Long Term, FMLA, Security Discipline, Legal )

Hire2Retire IGA Form Operations

Figure 10. Configure lifecycle operations for Hire2Retire IGA

Record Summary

Record Summary serves as the primary headline or title of the record, providing a snapshot of its content or issue. You can provide a summary for each record you are configuring, the summary will be visible along with the selected operations on the summary table. The Record Summary is not populated on Hire2Retire IGA.

Hire2Retire IGA Form Operations

Figure 11. Configuring the action & record summary for Hire2Retire IGA

Select Attributes

You can select the attributes of the Hire2Retire IGA record that you want to populate. You can map values from the AD to populate these attributes. You can also use Hire2Retire's powerful data transformation capabilities using Excel Style functions.

Map Value

You can select Map Value checkbox to map attributes from your Identity Management System to your Service Desk application.

Map Value Checkbox

Figure 12. Mapping attributes for Hire2Retire IGA on Hire2Retire


Note: For user-centric fields (e.g., Manager, Caller, Assigned To, Opened By, etc.), you may directly source values from your identity management system.
In contrast, fields backed by lookup tables require you to select the appropriate entry from the dropdown list.

User centric mapping

Figure 13. Mapping User centric fields using lookup table


Note: For Date/Time fields (e.g., Assigned, Due Date, Checked in, etc.), uses by default format yyyy-MM-dd HH:mm:ss. If user had configured different format they have to use that.

Examples

Explore detailed step-by-step examples for the most common Hire2Retire IGA use cases: