# 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](<https://developer.sailpoint.com/docs/api/authentication/>) and [REST API - Update Source (Partial)](<https://developer.sailpoint.com/docs/api/update-source-v-1>).

> [!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:

```json
{
"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`.