on 05-30-2011 8:30 AM
Hello,
We have configured PCRs (Promotion & Change in position) using standard worflow WS 50000041. For Approver, standard Work flow, WS 50000033 and TS 50000075. In this Task, we have assign a Standard rule "50000133 - Approver(PCR): Superior Manager".
The scenario works perfectly fine when, the Chief/Head of an Org. unit raises a PCR for employees under that org. unit. It goes to the next org. unit level's chief for approval.
Org Level 1 (OrgHead_1)
- - - - - - - - Org Level 2 (OrgHead_2)
- - - - - - - -- - - - - - - - - Emp_1, Emp_2
When OrgHead_2 raises request for Emp_1 it goes to OrgHead_1 and this works perfectly fine.
======================================================================================
Now, Question/Issue:
The scenario is, Emp_1 reports to Emp_2 and Emp_2 should raise request for Emp_1 which should be approved by OrgHead_2.
For this, we have changed the "Define Rules for Object Selection" for rule "MSS_PCR_RULE1" where we have changed the evaluation path. So now, Emp_2 is able to raise request for Emp_1, *but here, the request is going to OrgHead1 for approval.*_
We believe, this is due to the rule. "50000133 - Approver(PCR): Superior Manager".
If yes, do we have a standard Rule which can return us the immediate Chief/Head of the Managers/Employee's department. (in our case, OrgHead_2).
If No, Please suggest suitable solution.
Note: We will not like to do any custom changes in neither the Workflow nor the rules.
Thanks
you need to use a different rule, if this doesnt meet your requirement
You can use 0168 rule for manager. here you need to verify how does the rule work and how does your organisation
structure is constructed
check your tasks at PFAC and org at ppose etc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Siddharth, thanks for your response,
We tried to use couple of standard rules available for PCRs but they were not useful. Then we tried rule 168, while simulating (passing S as Object Type) it was returning correct agents, so we changed our rule in TS 50000075 from rule 50000133 (earlier used) to 00000168 (as said).
But still, the request raised by emp_2 is going to OrgHead_1 as per earlier behaviour.
Org Level 1 (OrgHead_1)
- - - - - - - - Org Level 2 (OrgHead_2)
- - - - - - - -- - - - - - - - - Emp_1, Emp_2
So, since we have changed the rule for Task 50000075, why still it is going to OrgHead_1 for approval and not to OrgHead_2.
Note:
i. Emp_1 reports to (A,B /002) Emp_2
ii. Emp_2 report to OrgHead_2 .....also, OrgHead_2 is the Chief of Org Level 2
iii. OrgHead_2 report to OrgHead_1...also, OrgHead_1 is the Chief of Org Level 1
Hello Siddharth,
When we test our rule with PFAC transaction...it returns OrgHead_2...which is what we actually expect.
The rule 168 which you suggested works fine there.
But when we associate that rule with our PCR scenario.....it returns OrgHead_1.......
So, the rule is right as we can test it from PFAC.....but with PCR it is not working for us.....
Hi Siddarth,
First of all, appreciate your help and inputs in exploring this process.
We succeeded in resolving this issue.
Analysis: As standard settings, it was found that, in WF 50000033, under Activity "Approve Personnel Change Request (Web)" (000004), rule 50000134 was mentioned in "Agents".
Solution: We changed this to Rule 00000168.
Earlier when it was not working correctly, initially, we had assigned rule 00000168 in the TS 50000075 as default rules.
Thanks for all the support again.
User | Count |
---|---|
100 | |
11 | |
11 | |
6 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.