Dynamically pick entitlementtype during REST based calls (in add access JSON)

[rohan32]

Hello,

We have a requirement where we have 90+ entitlement types for a REST based application and we need to pull the entitlement type dynamically during REST based calls (add access JSON) -  highlighted below :

Tried using ${entitlementValue?.entitlementtypekey?.entitlementName} or ${entitlementName} but none of the expression are working

Ex : 

{
"name": "Argentina",
"connection": "acctAuth",
"url": "<app URL>",
"httpMethod": "POST",
"httpContentType": "text/xml",
"httpParams": "<?xml version=\"1.0\" encoding=\"utf-8\"?> <soap:Envelope xmlns:wsa=\"http://schemas.xmlsoap.org/ws/2004/08/addressing\" xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"><soap:Header><wsa:Action>Configure</wsa:Action><wsa:MessageID>urn:uuid:04765906-5469-4a79-a85a-2c9cc3a15040</wsa:MessageID><wsa:To>https://mcffrcsjyrj1cl3cgq5-96gnk041.soap.marketingcloudapis.com/Service.asmx</wsa:To><fueloauth xmlns=\"http://exacttarget.com\">${access_token}</fueloauth></soap:Header><soap:Body><ConfigureRequestMsg xmlns=\"http://exacttarget.com/wsdl/partnerAPI\"><Action>assign</Action><Configurations><Configuration xsi:type=\"Role\"><ObjectID>${entitlementValue.customproperty5}</ObjectID><AssignmentConfigurations><AssignmentConfiguration><AccountUserId>${account.accountID}</AccountUserId>${(arsTasks.assignedFromRole.customproperty8!=null)?'<BusinessUnitId>'+arsTasks.assignedFromRole.customproperty8+'</BusinessUnitId>'+'<AssignmentConfigureType>'+'RoleUserBusinessUnit'+'</AssignmentConfigureType>':''}<IsDelete>false</IsDelete></AssignmentConfiguration></AssignmentConfigurations></Configuration></Configurations></ConfigureRequestMsg></soap:Body></soap:Envelope>",

"httpHeaders": {
"Content-Type": "text/xml"
},
"successResponses": {
"statusCode": [
200,
201
],
"status": [
"success"
]
},
"unsuccessResponses": {
"statusCode": [400, 401, 404, 405, 500]
}
}

[rushikeshvartak]

You can't add Entitlement Type dynamically

[rohan32]

So there is no way REST connector provides a way to provision 90+ entitlement types? And we need to hardcode all the calls separately?

[rushikeshvartak]

Yes. That’s bad design from application side check if they can merge into one & use dynamic attribute for filtering. Request form will be too much complex and long 

[rohan32]

Actually from application side we just have two entitlement type , but the use case is as follow -

We have two entitlement types - Role and Business Unit(Market)

For ex : Content Approver is the role and we need to provision it to Argentina Market (Business Unit).

From application, Content Approver is getting reconciled only once under role entitlement type but I need to provision it specific to each market. So if Saviynt provisions it once in a particular market , next time i try to provision it in some other market , it says "No Action Required" . 

So for that we have created 90 entitlement types via Saviynt DB import and importing these specific roles under each entitlement type so that each role can be provisioned to each market (business unit)

So, while provisioning I need to call different entitlement types in REST call

Please suggest if you know any other way to handle this scenario

[rushikeshvartak]

What is request option for market

[rohan32]

Dynamic variable in ARS form single drop down

[rushikeshvartak]

its one time activity you need to write 90+ times

[rohan32]

maintenance is difficult for this solution 

[rushikeshvartak]

Better ask to change application team to change api if possible