Webservice Connector triggering Update Operation when called for Disable Account Operation


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.

  <AccountRequest application="App_name" nativeIdentity="ONXXXX" op="Disable">
    <AttributeRequest name="groups" op="Remove" value="{&quot;displayName&quot;:&quot;COXXXXX&quot;,&quot;id&quot;:&quot;pc:6934&quot;,&quot;type&quot;:&quot;Group&quot;,&quot;uri&quot;:&quot;/admin/v1/groups/pc:6934&quot;}"/>
    <AttributeRequest name="groups" op="Remove" value="{&quot;displayName&quot;:&quot;CONXXXX&quot;,&quot;id&quot;:&quot;pc:6935&quot;,&quot;type&quot;:&quot;Group&quot;,&quot;uri&quot;:&quot;/admin/v1/groups/pc:6935&quot;}"/>

Hi @prajna_poojari

I am assuming that it is because of the Attribute Requests in the plan. Can you try triggering the plan without attribute request.
Disable Endpoint is usually for only Disabling the account not for Removing the Entitlement/Updating the account. That could be the reason for triggering Update along with Disable.

Thanks @Jarin_James

I modified the plan to include only the account request and get the groups inside the Before Rule of Disable Operation. The update operation is not being called anymore.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.