I need to invoke the specific identity collector from the fulfillment workflow. Is it possible ? if yes . How ?
What is the use case here?
You want to run identity collector after every fulfillment attempt to a specific application?
If you need to run an identity collector more than once a day, maybe a better approach will be to run the collector every 3 hours or so.
To answer your question, there are 2 options (as far as I know) to invoke the identity collector:
In the fulfillment workflow, you have a sub process node in which you can call the custom task workflow (didn't try that option)
We have been working on Vendor onboarding. For the vendors , we have one table in external DB where all vendors are migrated. And we need to provision the new vendors through RSA Via to bring back its identity into the system. The Vendor creation process is as follows,
A Global form to enter vendor information (First name , department etc).
Supervisor and other required approval.
A 8 digit unique number will be generated in Fulfillment workflow (uniqueness is being checked in PV_USERS table of Via) and will be assigned as EmployeeNumber to the vendor then will create a user record in external DB table.
Identity Collector will run to collect and create user identity in Via.
Issue : Employee ID generation –
Fulfillment workflow will check for existing vendors in PV_Users table and generate Employee ID within workflow and Provision at target.
We feel our process will break, Since we are generating employee id by checking PV_Users Via table and the latest vendors/newly provisioned users are in external oracle table and we cannot check external oracle table from workflow.
So we though of doing identity collection everytime a vendor being provisioned in external table.
Should I run unification also ? or identity collection would be enough to update PV_Users table with new identities ?
Unification need to be done for the new user to show up in PV_USERS table.
Not sure what logic you have been using to generate unique number but you should be able to keep track of numbers used to avoid collection and unification. For example by using a sequence that starts with some higher number not found in users table. Everytime, you need to assign a new ID, you can increment this and use that if it's no longer found for existing users. There could be other ways to just store what you have used to avoid repeating them instead of collecting everytime to bring them into system.
Retrieving data ...