Hi,
We have a webservice connector used for target application provisioning & deprovisioning. The configuration has a set of create Account, Update Account and Disable Account Operations set.
We have a requirement from termination workflow to call the 2 sequential ‘Disable Account’ operation. So a provisioning plan like below with Disable operation is being created and the project is run within the rule. When this plan is compiled, the connector triggers the 3 update operation and then moves to the 2 disable account. Could someone help to understand why the connector is calling the update account first.
<ProvisioningPlan>
<AccountRequest application="App_name" nativeIdentity="ONXXXX" op="Disable">
<AttributeRequest name="groups" op="Remove" value="{"displayName":"COXXXXX","id":"pc:6934","type":"Group","uri":"/admin/v1/groups/pc:6934"}"/>
<AttributeRequest name="groups" op="Remove" value="{"displayName":"CONXXXX","id":"pc:6935","type":"Group","uri":"/admin/v1/groups/pc:6935"}"/>
</AccountRequest>
</ProvisioningPlan>