Is there a description of how to configure a Provisioning Command in a custom task wf?
I want to update one attribute in an AD for a group of users.
What is the exact difference between Update an account and Update an account attribute?
I see the Account Name as an attribute. I suppose this one is needed as a unique identifier. But how do I add other attributes I want to update? I've tried right clicking, left clicking, dragging.
This was certainly helpful. I was able to configure the node.
But somehow I don't see the AD being updated so I do need some error checking logic.
The thing is I need to do it for a group a users so it is done in a loop. I can email a picture of the wf if needed. But as the article says the status fields are overwritten and there is not much I can see.
What I want to achieve is to populate the company attribute in the AD. This was only recently added to the AFX connector so for many accounts in the AD it is not present. And I would like to use for filtering in the collection.
And I am still curious to know the difference between Update Account and Update Account Attribute.
Glad it helped
As a starting point, have you tried just updating a single account? With regards to the error checking, you could write these to the admin error log:
RSA IGL Services 101: Explaining Workflow Nodes - "Create Admin Error"
Where/what is the source of the company attribute? I obviously don't know all that much about your implementation but I wonder if Attribute Sync could be of help here? Feel free to share a screenshot of the workflow, it all helps
Apologies, I wasn't sure exactly where you were seeing Update Account and Update Account Attribute?
Cheers,
Clive
Hi Bas,
The Provisioning Node reflects what is configured within the AFX connector. The connector must first be associated to a business source in order for it to be configured within the Provisioning Node.
In the below, you can see that the Parameters added to the specific capability are then visible within the Provisioning Node:
What is the exact use case you're trying to achieve and is the use of a Custom Workflow the best approach? You mention the need to update a 'group' of users which will require loop logic within the workflow.
If you do go with this approach, I'd also recommend adding error handling by capturing the status code:
000034403 - Provisioning node CommandStatusCode and CommandStatusMessage in RSA Identity Governance & Lifecycle
Thanks,
Clive