Skip to content

Provisioning

The Oracle HRMS connector supports provisioning, allowing you to create and manage accounts and entitlements in Oracle HRMS directly from SailPoint.

Prerequisite: Your system is configured for provisioning.

When SailPoint provisions new accounts to the source, it uses the attributes on the Create Account page as instructions or a template for what to include in the account. This page is also referred to as the provisioning policy.

When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment.

For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account.

Important

This section describes the default Create Account configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail.

Default Create Account Attributes

Note

Mandatory attributes are marked with an asterisk (*).

Account Attribute Description
FIRST_NAME* The first name of the employee.
LAST_NAME* The last name of the employee.
GENDER* The gender of an employee. For example, M- male, F-female
PERSON_TYPE* The type of the employee/person defined for an organization.
JOB* The job details of an employee.
KNOWN_AS This is what an employee is known as. For example, this can be a nick name.
MIDDLE_NAMES The middle name of the employee.
EMAIL_ADDRESS The email address of the employee.
WORK_TELEPHONE The work telephone number of the employee.
DATE_OF_BIRTH The date of birth of the employee in DD-MM-YYYY format.
TITLE The title of the employee. For example, MR., MRS., or MISS.

Create an employee record with a Create Profile form using the REST API. Refer to Best Practices: REST API Authentication and REST API - Update Source (Partial).

Note

For existing sources, set the useEnhancedAggregation attribute to true, using the REST API:

POST <url>/api/source/update/<sourceID>

  • <url> is the URL for the customer's SailPoint instance
  • <sourceID> is the Source ID (number) obtained through the UI

In the body of the POST, use form-data as follows:

  • key: connecor_useEnhancedAggregation
  • value: true

Method: Post

URL: https://{url}/api/accountProfile/update/<source_id>?usage=Create

Content-Type: application/json

Body:

{
"description": null,
"fields": [
{
"attributes": {
"cloudRequired": "true"
},
"isRequired": false,
"name": "FIRST_NAME",
"transform": {
"attributes": {
"name": "FIRST_NAME"
},
"type": "identityAttribute"
},
"type": "string"
},
{
"attributes": {
"cloudRequired": "true"
},
"isRequired": false,
"name": "LAST_NAME",
"transform": {
"attributes": {
"name": "LAST_NAME"
},
"type": "identityAttribute"
},
"type": "string"
},

{
"attributes": {
"cloudRequired": "true"
},
"isRequired": false,
"name": "GENDER",
"transform": {
"attributes": {
"name": "GENDER"
},
"type": "identityAttribute"
},
"type": "string"
},
{
"attributes": {
"cloudRequired": "true"
},
"isRequired": false,
"name": "JOB",
"transform": {
"attributes": {
"name": "JOB"
},
"type": "identityAttribute"
},
"type": "string"
},

{
"attributes": {},
"isRequired": false,
"name": "PERSON_TYPE",
"transform": {
"attributes": {
"value": "Employee"
},
"type": "static"
},
"type": "string"
}

],
"name": "Account",
"usage": "Create",
"validPolicy": true
}

Update Operation of Employee Records in the Oracle HRMS System

  • EMAIL_ADDRESS

For updating, the email address default can be UPDATE / CORRECTION / UPDATE_CHANGE_INSERT applicable in the following scenarios:

Condition Mode Configurable
EFFECTIVE_START_DATE equals Today's date CORRECTION NO
EFFECTIVE_START_DATE < Today's date UPDATE / CORRECTION YES
EFFECTIVE_START_DATE > Today's date UPDATE_CHANGE_INSERT NO

To configure, add UPDATE_MODE field in update policy.

  • WORK_TELEPHONE

For updating phone number of type Work, the default mode is Correction.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.