on 10-18-2012 8:40 PM
We have a problem that our users don't delete a leave request when it is rejected. After a year, they don't see the request any more in portal, but we see it in PTARQ - document status REJECTED, WF status STARTED.
What we have done so far, is to cancel the WF so we don't have so many open WF in system.
But we have not deleted the request itself.
Will this approach cause any problems?
(We let our 2nd line support cancel the WF, but we would rather not give them access to delete requests, as this to us is a more drastic action).
/Kirsten
It is recommended to use report RPTARQSTOPWF, scheduled monthly to clear out these items
Leave Requests: Complete Current Workflows
You can use this program to end workflows for rejected leave requests that have not been processed for a long time. Any leave requests ended by this program can no longer be processed by your employees.
We dont recommend deletion and given any other access to employees
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Siddharth.
I didn't know about this report.
I see that it cancels WF and sets status for request to STOPPED.
Some extra questions:
I really appreciate you sharing your knowledge here!
Kirsten
/Kirsten
Status would be set as Withdrawan
! The Leave record status is "STOPPED", you can check via rptarqdbview
Workflow status is "CANCELLED" and Work Item status is "LOGICALLY
DELETED" after executing the report.
You can use Rptarqdbdel to delete requests too if leave requests are nomore to be accessed again
Now coming to the frequency of the report RPTARQSTOPWF
Do you want employees to amend rejected leave request status?
If not, then you can schedule it everyday once
if you allow changes to leave request rejected status, then keep this in biweekly
however you can always change the settings in the report ie for old requests
Relative to Current Date
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.