We are currently working on provisioning in web service for two different entitlement types but are encountering an issue. Note: Both ADD HTTP operations use the same context URL, but the request bodies are different. We are attempting to provision these entitlements through an Access Profile, but the process fails when trying to add both entitlements simultaneously. However, if we request a single entitlement, the provisioning works as expected.
We would appreciate any guidance or suggestions on resolving this issue.
This will allow multiple request to trigger to target if add or remove entitlement has multiple items in it to trigger differently.
2. Create a before operation rule on “ADD” operartion to iterate through the entitlement triquest and update the requestEndpoint with the desired body based on the input values you are getting from plan (like name etc).
I have tried the above steps but its not working .
In provisioning plan we are getting both entitlements types paln from one HTTP operation we are adding companies from another HTTP operation we are adding entitlements.
I heard that some of my peers also had encountered similar issue and they have used before provisioning rule to do a external API calls through the before operation rules