Hello,
Does using Provisioning Command Node in workflow still triggers the output parameter to be fetched & updated?
Or it works only when connector is invoked via AFX handler?
Hello,
Does using Provisioning Command Node in workflow still triggers the output parameter to be fetched & updated?
Or it works only when connector is invoked via AFX handler?
As far as I know, it works only when using the AFX handler.
My question is why? If you have an output parameter functionality in the connector, why do you want to use the provisioning command node?
You can get is using below variables:
${jobUserData_acm.provisioningCommandStatusMessage}
${jobUserData_acm.provisioningCommandStatusCode}
Those variables provide a status of the provisioning attempt (when using provisioning node).
How is it related to the output parameter functionality?
Those variables provide a status of the provisioning attempt (when using provisioning node).
000034403 - Provisioning node CommandStatusCode and CommandStatusMessage in RSA Identity Governance & Lifecycle
How is it related to the output parameter functionality?