Workflow trigering generates duplicate tasks

[Former Member]

Hi,

we are facing a problem whenever the workflow is trigered we are having duplicated task.

Our workflow is builted using an extension of the object DRAW and the standard event "Change" conditioned by the primary status of the DMS (i.e IF DMS status = Z1 ).

This workflow was working propely until now. I have already do some verifications as:

- SWETYPV - verify the event's linkages to my workflow. Only the supose event is linkek and active

- SWEL - only one entry associated to the raise event and the workflow

- i have already desactivated the "Change" event on workflow to verify if even so the workflow was trigered. Result the workflow wasn't trigered.

I'm without ideas how could i find or resolve this question, could you give me some orientation.

Thanks

Please do not use words like "Gurus", "Experts", etc in the forums. Be specific and clear about the issue before you post it for discussion.Thanks alot ,

Edited by: Saujanya GN on Apr 28, 2008 10:03 AM

[martin_nooteboom · Accepted solution]

Did you look at the workflow log to see if there is anything there which could help you?

Regards,

Martin

[Former Member · Accepted solution]

hi Martin thanks for the reply.

Unfortunaly the log of the workflow don't say nothing that wasn't suposed. it shows us that the first task of the wf are working fine. We think the issue is before, during the trigering.

[martin_nooteboom · Accepted solution]

Just to be sure there is only one event in the event trace?

Regards,

Martin

[Former Member · Accepted solution]

Hi,

i had implement the note:1035333 to try to solve this problem.

Despite the number of duplicate task reduced it stil continue duplicating.

Any idea???

regards,

renato pedro

[sudhahar_ramachandran · Accepted solution]

check the correcsponding task's triggering event is On. if so the workflow will be created once and the task itself will be created again independent of the workflow. but in this case you'll see it in the event trace.

[Former Member · Accepted solution]

Hello Sudhahar tks for quick reply.

I don't know if i understand clearly your explication, i verify in tcode: pftc the task where the event "changed" is assigned and is on/active.

Is that verification that you propuse?? Could you give me more detailed steps if it isn't so?

[Former Member · Accepted solution]

Please check whether the User, DocumentStatus and DocumentStatus_old container element are different for the duplicate events. I think this will be different and hence the event are getting triggered.

Thanks

Arghadip

[Former Member · Accepted solution]

Hi Arghadip,

you have rigth the duplicated task have a diferent user. The initial/orginal task is generated by user A and the duplicated task is generated by "workflow system".

[sudhahar_ramachandran · Accepted solution]

let me explain in more detail.

you have created a workflow which contains several tasks.

In Tcode PFTC we can switch on/off the event linkage. and I think you've activated the event linkage.

so whenever the event is triggered, the workflow is called. the workflow has several steps and one of the step has a task which you see duplicating.

my doubt is, whether you've activated the tasks' own triggering event. this triggering event should be inactive. otherwise there will be a duplicate work item created by the task itself. make sure that you deactivated all the triggering events for the specified task.

Thanks & regards,

Sudhahar R

[Former Member · Accepted solution]

In this case it is not Duplicate task for 1 triggering event but 1 task for each triggering event. It is just like RELEASESTEPCREATED event of BUS2012 used in WS20000075. This is standard and that is its behaviour.

Thanks

Arghadip

[Former Member · Accepted solution]

Thank you both for the help.

Sudhahar, i don't how to verify what you sugest. If i deactivate the event "Changed" the workflow is not triggered and i don't have any new workitem. Could I conclude that only my event is responsible for trigger the workflow?