You may have noticed that, using the QC for Base System’s connector, a provisioning/deprovisioning step may affect objects/accounts even though they are out of scope of the Workflow. The following behaviours have been recorded in the QC Base Systems connector’s release notes:
You may experience any of the following issues when running the provisioning or deprovisioning
- Quick Connect may unexpectedly provision an object that has already been provisioned earlier.
- Quick Connect may unexpectedly deprovision objects that do not meet the deprovisioning
This is by design. These issues show up if you have, within the workflow steps, a configured attribute updating rules for any attributes that uniquely identify an object in the connected system.
Either remove the updating rules which reference the unique identifying attributes from the existing workflow. Or move the provisioning/deprovisioning step to a separate workflow (which won't contain any updating rules).