on 08-04-2009 7:45 PM
Hi !
We have this scenario : one of our process lane belongs to a potential user that is an employee of an specific department of the company. This user will initiate the process by sending filling a form. Then, his/her manager should authorize that form.
Initially, the potential user and his/her department is not known, so neither is his/her manager, that should recieve a notificacion in the UWL.
Is there any standard way to specifiy in the UME how users are related (employee->manager->etc) to be able in runtime to determine who is the process initiator manager?
Thanks.
Regards,
Matias
Hi Matias,
User hierarchy is not maintained in UME so if you have department level approvals then you can use the department attribute of UME user to identify the dept and initiate the approval to the respective person.
Regards,
Arafat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
If the standard attributes from UME are not sufficient you could come up with a custom EJB function that can be used in a mapping. For example getManager(String umeUserId) : String. This could then dynamically access your org hierarchy (whereever you maintained this) and resolve the manager for the userID that is passed as argument. The positive effect is that you can directly use this function in the potential owner determination (by choosing "use expression" instead of defining a "static" list of principals).
In case the EJB function is too complex you could stll go for an automated activity that invokes an existing backend services in your org management. the output of this should be a unique ID that is also known to the UME (which is the principal management on the CE system). Using this output in combination with the built-in "getPrincipal" functions in the mapping editor will do its job.
Maybe one of those suggestions fit to your needs.
Cheers,
Martin
Hi Matias,
You can maintain the Org Structre in LDAP so if your UME is connected to LDAP and you have a structure maintained, then you can at runtime decide who is the manager and approver for a certain request.You also need to maintain the potential users that should have access to the UWL by assigning the required roles (BPEM End User Role, etc).
Regards,
Arafat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.