HTTP Operations

Feedback Documentation Feedback Connectivity Documentation Feedback
1

In HTTP Operations, you can add, edit, delete, and reorder HTTP operations.

The following operations are supported:

This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/saas/web_services/help/saas_connectivity/web_services/http_operations.html
2

I am having a lot of issues with the templating here and I am a bit frustrated with the entirety of this documentation:

For the Web Services source, you can configure the native identity in the provisioning plan using a placeholder such as $plan.planNativeIdentity$.

$plan.plan? First time seeing this. Isn’t it $plan.NativeIdentity$?

Below are the few keywords that will be used in the Context URL along with the placeholder $:
plan
response
application
getobject
authenticate

Very good information, but what are they? What do they contain and when should they be used? Are they all strings?

To configure the Context URL as a velocity operation, wrap the operation with $$. For example:
/2/team/members/list/$$response.data.length$$

What does this mean? Can I use the Velocity language within strings if I wrap the code within $$[CODE]$$? If the variable is referenced within Velocity is $response shouldn’t the example be /2/team/members/list/$$$response.data.length$$. All my attempts at this just removes the $$ and prints the inside of it as text. Can I build loops and use functions in Velocity here, or something else?

If the body contains a placeholder that is not present in the provisioning plan, response, or source, the source removes the key value from the JSON payload.

Are you sure this works? I am having no success at this, and if I can’t programmatically build the payload with Veolcity, then this needs to work. If not it is just sending empty value to the API and removing values it is not supposed to update.

Also: the $plan is supposed to have all the account schema attributes it is trying to update, but if the account schema contains spaces it will not work. You will have to recreate the schema without spaces. Took me a long time to figure this out.