Parent Endpoint

The Parent Endpoint tab displays for aggregation operations. For more information, refer to Aggregation or Account, Entitlement, or Get Object Aggregation.


This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/webservices/help/integrating_webservices/parent_endpoint.html

Can we get some more documentation here to allow us to understand when to use a parent endpoint and when not?

Suppose we want to create an account, but the response body does not contain the account attributes allowing us to perform response mapping. Can we then add a second HTTP operation with operation type Get Object that has this create account as parent endpoint to ensure that we get all the expected account attribute values?

Suppose we want to disable an account, and the account has an account attribute version that gets incremented on each account update (regardless of whether it was done by ISC or not). Suppose that whenever we want to update the account (update country, disable account, add entitlement) we need to pass the current version value in the body. We then need to get the latest information of the account because the data we have in ISC might be outdated after external changes occurred. Is it possible to define an HTTP operation with operation Disable account that does a GET to fetch the latest version number and define another HTTP operation with operation Disable account as well that does a PATCH to disable the account. If so, do we need to setup parent child relationships between these operations? Note that ‘needing the version number’ is just one example, there are different cases for Web Services that we need to perform GET requests prior to performing POST/PUT/PATCH requests.

Kind regards,
Angelo

Hi Angelo! Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-4071

Any updates here? The Parent Endpoint documentation is still really confusing and doesn’t really explain much.

Why can I select “Create Account” operations from the Parent Endpoint drop-down if they can’t be Parent endpoints?

If I have a child endpoint for Full Account Aggregations to pull the user’s entitlement data, how can I also do that for Single Account Aggregations? Do I make both the parent and the child Get-Object operations? Should the child be a Get-Object-group type instead?

Hi @benjaminoriold we don’t have any updates at this time. Once we’ve made the updates to the topic we’ll post a comment here.