Account Attribute to be sent in JDBC Provisioning policy Disable

[chandramohan27 (Chandra Mohan S)]

Hi,

We have a JDBC source account attribute which is auto populated during account creation and aggregated into Sailpoint.

Now, I’m trying to send the same account attribute of a JDBC source to my disable provisioning policy attribute request.

I tried using transform to get account attribute, but that doesn’t work… Is there any alternate approach / suggestion.

[JackSparrow (Theja C)]

Hi @chandramohan27 ,

Hope in account schema you have that attribute defined. In this case you should be able to get that account attribute using transform Account Attribute | SailPoint Developer Community.

Also, you can get the attribute in JDBC provisioning rule. getAttributeRequestValue(account, “attributename”));

[KRM7 (Krishna Mummadi)]

Did you set that attribute as Account ID (Native Identity) ?

[chandramohan27 (Chandra Mohan S)]

No, we have different native identity.

I tried with this below disable policy to send the attribute in disable provisioning… But whenever I trigger disable operation. I don’t see the attribute in attributeRequests.

{
“name”: “Account”,
“description”: null,
“usageType”: “DISABLE”,
“fields”: [

            {
                "name": "PERIOD_OF_SERVICE_ID",
                "transform": {
                    "attributes": {
                        "sourceName": "Oracle EBS Employee Source - New",
                        "attributeName": "PERIOD_OF_SERVICE_ID"
                    },
                    "type": "accountAttribute"
                },
                "attributes": {},
                "isRequired": false,
                "type": "string",
                "isMultiValued": false
            }
     
]

}

[KRM7 (Krishna Mummadi)]

Whenever you have an attribute in Provisioning Policy form, if the attribute value is not changed, then it will be filtered and not included in the Plan.

Add some text to this Transform along with account attribute, then it will be different from what account has already.

In your JDBC Provisioning Rule, remove the text you added.

[chandramohan27 (Chandra Mohan S)]

Thanks @KRM7 It worked.