on 06-10-2016 3:17 PM
Hi Sara,
If possible try to explain what you want clarified in detail. Look forward to your response.
In general words, you map certain actions to the request types, so that each request type has specific provisioning/deprovisioning characteristics assigned.
For example if you have a request "Lock User" you would assign the actions "Lock User" and "Change and Lock User". This would allow you to create a request where you lock a user ID but at the same time possibly also change user details like User Group to "Left/Locked" for admin purposes.
Just having "Lock User" as the assigned action won't allow you to do the additional request processing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sara G,
There are many request types used in ARQ like New Account. Lock Account, Change Account etc., When these request types are selected the underlying actions are triggered.
Actions can be something like Create User, Change User, Change and Lock user, Remove etc., So, these actions are mapped against the requests based on the requirement that we maintain in workflows.
Is this what you are looking for or do you need any further information?
Regards,
Rakesh Ram M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sara,
Do you want to know the actions that needs to be mapped to a specific request type?
Could you please give a brief description as your query is not clear enough.
Regards,
Manju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.