Remove Entitlement on webservices is not working

Hi,

can some one help me on the remove entitlement issue on webservices, as access request is getting successfull and in the events I dont see any error, but the entitlement is not getting removed from user account on target, in IDN, entitlement is working fine

when I pass static its working, but not with dynamic values.

Any leads appreciate.

Thanks
Prashanth

Hi
Few steps to check as you mentioned that the dynamic value is not working.
The entitlement ID/name whatever is required in API call, can you confirm if that is being evaluated properly. This can be tested via a Before Operation rule.Make sure that the dynamic value is what you wanted.

Next in the HTTP operation P.S that the success code is set properly.

This can help debug the issue if there is something wrong with the BODY or the evaluation of the variable. If possible can you share the body u r using?

Hello @PrashRV
Good day !

Please check that the entitlement value is being passed appropriately to body if you are using a rule to remove entitlement, or please check that the remove entitlement API through Postman is working.

Thank you

1 Like

Hi @PrashRV
Please verify the URL and body parameters being used for the remove entitlement process. Additionally, check the values that ISC is passing in the plan from the search for the dynamic entitlement values.

Hi @gourab ,

thanks for the reply, i have configured two endpoints for removal purpose
one for fetching user object from target and use that details in second endpoint to perform remove entitlement on user on target
image

Note : response attributes, parentendpoint is configured

pls let me know anything am I missing, the accessrequest is getting successful but entitlement is not getting removed from user profile on target.

Thanks
Prashanth

Hi @PrashRV ,
I can notice you have not added parent endpoint on child operation “Remove ent from user”

Hi @PrashRV

Can you please let us know in which operation you have configured parent endpoint.

1 Like

Hi Gourab,

i have added in the remove entitlement - from user operation

thanks
Prashanth

@PrashRV I don’t think that updating the parentEndpointName directly will work. As far as i remember, the parent endpoint is available for Account Aggregation/GetObject/ Entitlement Agg. operation only.
Hence, once the Remove entitlement is being used, it is not going to the second Remove ent. operation and not evaluating the variables that were received from the previous remove ent. call.

1 Like