Here is the idea for implementing the use case .
The following is an example response of provisioning completed trigger :
[
{
"accountId": "talker3",
"accountOperation": "Modify",
"attributeRequests": [
{
"attributeName" : "detectedRoles" ,
"attributeValue": "Accounts Payable [AccessProfile-1709866079244]",
"operation" : "Add"
}
],
"provisioningResult": "IdentityNow Task",
"provisioningTarget": "IdentityNow",
"source": {"id": "IdentityNow", "name": "IdentityNow", "type": "SOURCE"},
"ticketId": "..."
},
{
"accountId": "CN=whiters walkers,OU=Demo,DC=seri,DC=sailpointdemo,DC=com",
"accountOperation": "Create",
"attributeRequests": [
{
"attributeName": "memberOf",
"attributeValue": "CN=AccountsPayable,OU=Groups,OU=Demo,DC=seri,DC=sailpointdemo,DC=com",
"operation": "Add"
},
{
"attributeName" : "ObjectType",
"attributeValue": "User" ,
"operation" : "Add"
},
{
"attributeName" : "sAMAccountName" ,
"attributeValue": "whiters.walkers",
"operation" : "Add"
},
{
"attributeName" : "displayName",
"attributeValue": "talker3" ,
"operation" : "Add"
},
{
"attributeName": "manager",
"attributeValue": "CN=Nagur Shaik,OU=Demo,DC=seri,DC=sailpointdemo,DC=com",
"operation": "Add"
},
{
"attributeName" : "mail" ,
"attributeValue": "[email protected]",
"operation" : "Add"
},
{
"attributeName" : "givenName",
"attributeValue": "whiters" ,
"operation" : "Add"
},
{"attributeName": "sn", "attributeValue": "walkers", "operation": "Add"},
{
"attributeName" : "pwdLastSet",
"attributeValue": "false" ,
"operation" : "Add"
},
{
"attributeName" : "IIQDisabled",
"attributeValue": "false" ,
"operation" : "Add"
}
],
"provisioningResult": "committed",
"provisioningTarget": "Active Directory",
"source": {
"id" : "f5cedeea49164e3f9ce1d1bd883b02b4",
"name": "Active Directory" ,
"type": "SOURCE"
},
"ticketId": "..."
}
]
Refer to Constructing and Building Event Trigger Filters , which gives you idea on what filters you need to compose in string compare operators .
The below is the workflow image :
Hope this will help.
Thanks