Performance Management - Status flow - Closed/Reject

[Chris_Thomas]

All - we are not implementing the WF Approval part of the system, but rather utilizing the status flow to manage the process. We want to allow a manager to 'close/Reject' an appraisal document if the employee transfers to a new department during the objective planning (Planning) phase.

I have checked 'Activate Approval Process' which makes Closed/Rejected status available, but when I try to add it to the status flow I get the error message that "Status Change from Objective Planning to Closed Rejected is not allowed".

How should I set up the template to provide for the scenario where the manager needs to get rid of (without deleting) an appraisal document ?

[Former Member · Accepted solution]

>

> All - we are not implementing the WF Approval part of the system, but rather utilizing the status flow to manage the process.  We want to allow a manager to 'close/Reject' an appraisal document if the employee transfers to a new department during the objective planning (Planning) phase. 
> 
> I have checked 'Activate Approval Process' which makes Closed/Rejected status available, but when I try to add it to the status flow I get the error message that "Status Change from Objective Planning to Closed Rejected is not allowed".  
> 
> How should I set up the template to provide for the scenario where the manager needs to get rid of (without deleting) an appraisal document ?

im pretty sure you can only go to from completed to closed rejected, hence the error.

i just answered a similar question yesterday, and the guy liked the suggestion.

You could create a sub-status in "Objective planning" called "Document Closed - Employee Transferred". You allow a button for the manager to move it to this status.

However, on this status configuration, you select a role other than appraiser or appraisee to be able to move it out of this status, a role not even used on the template. this way you create a limbo status, that could only be undone through PHAP_ADMIN status change. When the document is in this status you make it read-only.

the other way would be through development in some type of badi.

[Chris_Thomas · Accepted solution]

Michael, et. al.,

I followed your advice to create the substatus, "Document Closed", however I do have a question about ongoing administration.

At the end of the cycle I can see people wanting to 'sweep' these documents out of their views (Yes, I know I can do limit with the POWL query parameters) but it seems a little messy to me in leaving these documents in this state.

Do you have any suggestions for handling this ? Write code to update the status behind the scenes, meaning the edits won't be encountered (Going from Objective Planning, Document Closed to Closed Rejected for example).

Suggestions ?

thanks as always,

Chris Thomas

Duke University