Hi 
The documentation refers to “single velocity operation”. Can this be explained some more? I associate it to apache velocity, which for example exists in email templates of ISC. Is this using the same “velocity”, or is this something else?
To show my usecase, I want to achieve the following in this source (And I have many similar sources where I stumble on something similar).
For the operation update account, the application has no PATCH operation, only a PUT operation. So if we want to update the firstname, we also need to pass the lastname and vice versa. So we have two operations for update account. One to get the latest data from the application and then we want to update the account with the following body:
{
"firstName": #if($$plan.firstName$$)"$$plan.firstName$$"#else"$$response.firstName$$"#end
"lastName": #if($$plan.lastName$$)"$$plan.lastName$$"#else"$$response.lastName$$"#end
}
This way, if attribute sync triggers both values to be changed, they will both appear in the plan and should both be used, but if only firstname will be changed and thus visible in the provisioning policy, we would need to refer to the lastName that is currently visible in the application.
Can the documentation show how we can achieve a usecase like this using this connector, perhaps through apache velocity if this is indeed supported?