Sync for Some Users from Oracle HRMS Source Without Changing EFFECTIVE_START_DATE

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hi Developers,

I’m working with an Oracle HRMS source in SailPoint and need some guidance regarding synchronization.

We noticed that running the standard account sync updates accounts and consequently changes the EFFECTIVE_START_DATE attribute. However, in our use case we want to avoid modifying this date.

Requirement:

  • Update the Name attribute for only a subset of accounts (for example, recently created accounts).

  • Ensure that the EFFECTIVE_START_DATE in Oracle HRMS is not updated or changed to the current date during the sync.

Questions:

  1. Is there a recommended way to sync or update specific attributes for selected users without affecting the EFFECTIVE_START_DATE?

  2. Would implementing a Workflow be a viable approach for this scenario?

  3. Are there other best practices (e.g., targeted aggregation, rule-based updates, or connector configuration) to handle partial updates from Oracle HRMS without triggering an effective date change?

Context:

  • Source system: Oracle HRMS

  • Attribute in question: EFFECTIVE_START_DATE

  • Desired update: Name attribute only for some accounts (recently created users)

Any guidance or recommended approaches would be greatly appreciated.

Thanks in advance!

3 Likes
2

Hi Laxman,

Please find the screenshot below for reference. To achieve your use case, please use the Update Provisioning Policy configuration.

image
image1492×624 49 KB

{
"name": "Update Account Policy",

"description": null,

"usageType": "UPDATE",

"fields": [

    {

        "name": "EMAIL_ADDRESS",

        "transform": {

            "type": "identityAttribute",

            "attributes": {

                "name": "WorkEmail"

            }

        },

        "attributes": {},

        "isRequired": false,

        "type": "string",

        "isMultiValued": false

    },

    {

        "name": "UPDATE_MODE",

        "transform": {

            "type": "static",

            "attributes": {

                "value": "CORRECTION"

            }

        },

        "attributes": {},

        "isRequired": false,

        "type": "string",

        "isMultiValued": false

    }

]
}

Kindly review the screenshot and configure the Update provisioning policy as per reference policy. Let me know if you need any further clarification.
Thank you.

4 Likes
3

@suraj_gorle

Thank you for your response.
let me try this and check my luck.

5 Likes