Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
07/11/2023 01:54 PM
Hi,
We are onboarding an integration between Saviynt and SuccessFactors to manage group access in SuccessFactors.
During testing we have noticed that when an entitlement is removed through ARS request and the provisioning job is run, that the account status changes to 'Manually Provisioned'.
We were not sure why the entitlement task would update the account status, or if there is a way to prevent that. The account status corrects itself after running the account import job.
This is the Remove Access Policy:
{
"call": [
{
"name": "DynamicGroups",
"connection": "SuccessFactors",
"url": "https://api8preview.sapsf.com/odata/v2/updateStaticGroup?groupId=${entitlementValue.entitlementID}L&...}'",
"httpMethod": "GET",
"httpHeaders": {
"Accept": "application/json",
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200
]
},
"unsuccessResponses": {
"statusCode": [
400
]
}
}
]
}
Thanks
07/11/2023 09:17 PM
Is their any tasks getting created for update account and can you please share update account Json.
07/12/2023 07:29 AM
Hi Rakesh,
There is only a task created for Remove Access when requesting to remove an entitlement from ARS.
After the provisioning job runs, the task is marked complete and the entitlement is removed, but the account status becomes Manually Provisioned.
Here is the update account json:
07/14/2023 03:38 PM - edited 07/14/2023 04:05 PM
Hi @RakeshMG
I responded to your reply with the update account json.
We do not see a task created for account update, only a task for the Remove access; but it updates the account status to Manually Provisioned after the task is processed.
Let me know if you need any other information. Thanks