We have configured a webservice connector for one of the source. In that we are able to run the account via account aggregation and we can see the account in the accounts section.
When it comes to Entitlement via entitlements aggregation it’s not getting scanned, it only says the success message. We have configured the group aggregation as operation type.
Hi @saikrishnal
Can you check the payload details of the operation which aggregates the entitlement?
If you can, post it here. I suspect an issue with the payload which fetches the entitlements
From the above payload we only get the “unique_id”: “1f58cb9f-dfc5-478e-993c-4346360320fc”
Hence we are using the above unique_id as the payload for fetching the entitlements in hte group aggregation operation.
If you are able to get the entitlement details there how are you passing ?
Correct me if I understood it properly,
You have two operations to perform the entitlement aggregation, from one you are getting the unique_id by the above mentioned payload and passing the unique_id to the 2nd Group Aggregation Operation so that you get all the entitlements?
As per the below snippet we have total of six roles and group inside that the entitlement’s are present in an array. But as the final result we need to read all the entitlement’s which are present in the different arrays as a role and group.
Can you let me know what to provide exactly in the attribute path for the response mapping??.