cancel
Showing results for 
Search instead for 
Did you mean: 

Automatic deletion of Workitem - Workflow Substitution

ravi_sirigiri
Participant
0 Kudos

Hello,

We have maintained substitution of user in leave workflow.

For ex:

User B is a Substitute for User A.

User B receives the workitem and approves the leave request.

But the leave request is not getting deleted in User A inbox.

Could you please let me know the missing configuration/step in Workflow.

Thanks,

Ravi

Accepted Solutions (0)

Answers (3)

Answers (3)

ravi_sirigiri
Participant
0 Kudos

Hi Pavan,

PTREQ_ACTOR table will store the ACTOR_ID and Person details. It is not related to any leave request.

Normally when a workflow workitem is executed, the workitem should be deleted right. But in the above case it is not getting deleted. Could you please let me know why?

Thanks,

Ravi

bpawanchand
Active Contributor
0 Kudos

Hi ,

I completely agree with you that the table stores the actor Id's however, how many entries are stored in the table. The whole means of referring this table or header table is to identify whether the work item is sent parallelly with different work item Ids or the same work item sent to multiple users.

Thanks, Pavan

bpawanchand
Active Contributor
0 Kudos

Hi ,

The actors of the leave request are stored in the PTREQ_ACTORS table. I guess even you might find the status of the leave request in this table. So based on your scenario get the GUID of leave request from PTREQ_HEADER and check how many actors are available in PTREQ_ACTORS. The take appropriate actions. I guess you can find standard classes which can help you to do this merging of actions. Search where user list for this actors table. I remember we handle this kind case but it was more of merging the actions from multiple users.

Thanks, Pavan

bpawanchand
Active Contributor
0 Kudos

Hi ,

The actors of the leave request are stored in the PTREQ_ACTORS table. I guess even you might find the status of the leave request in this table. So based on your scenario get the GUID of leave request from PTREQ_HEADER and check how many actors are available in PTREQ_ACTORS. The take appropriate actions. I guess you can find standard classes which can help you to do this merging of actions. Search where user list for this actors table. I remember we handle this kind case but it was more of merging the actions from multiple users.

Thanks, Pavan