Multiple Group Entitlements with Pre-existing Source

For pre-existing Oracle ERP Siebel sources, perform the following steps to start using the Multiple Group Entitlements with your current sources.

Use the createSchema API to create new group schema for your source. The following is an example for API body content for adding Responsibilities to an existing source:

Here, id refers to the actual source ID.

{
    "id": "2c91808429864c0180279a6340ba7",
    "name": "Responsibility",
    "nativeObjectType": "responsibility",
    "identityAttribute": "Name",
    "displayAttribute": "Name",
    "features": [
        "PROVISIONING"
    ],
    "attributes": [
        {
            "name": "Id",
            "type": "STRING",
            "schema": null,
            "description": "Unique Identifier for Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Name",
            "type": "STRING",
            "schema": null,
            "description": "Name of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Description",
            "type": "STRING",
            "schema": null,
            "description": "Description for Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Organization",
            "type": "STRING",
            "schema": null,
            "description": "Organization of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Primary Organization",
            "type": "STRING",
            "schema": null,
            "description": "Primary Organization of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Primary Organization Id",
            "type": "STRING",
            "schema": null,
            "description": "Primary organization ID of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Primary Organization.DS Updated",
            "type": "STRING",
            "schema": null,
            "description": "Primary Organization.DS Updated of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Mod Id",
            "type": "STRING",
            "schema": null,
            "description": "Mod ID of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Access Type",
            "type": "STRING",
            "schema": null,
            "description": "Access type of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Created",
            "type": "STRING",
            "schema": null,
            "description": "Created date of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Created By",
            "type": "STRING",
            "schema": null,
            "description": "Responsibility created by",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        },
        {
            "name": "Updated",
            "type": "STRING",
            "schema": null,
            "description": "Updated date of Responsibility",
            "isMulti": false,
            "isEntitlement": false,
            "isGroup": false
        }
    ]
}

Update the account schema with the following steps:
1. Get the account schema using getSchema API.
2. Copy the schema to a file and search for the attribute corresponding to the group schema that is added in the previous step.
3. Add or update the following two properties for the attribute found in the previous step.
```
"isGroup": true,
"isEntitlement": true,
"schema":
{
    "type": "CONNECTOR_SCHEMA",
    "id": "<Schema_ID_From_Step1>",
    "name": "<Name_Of_Schema_Created_In_Step1>"
}
```
4. Add the schema modified in the previous step to the payload to update the account schema in the source using replaceSchema API.

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.