Workflow getting initiated twice!

sharmavikrant
Kilo Expert

We have different workflow associated with our Change requests and each workflow has a different set of group approvals arranged in serial order. However, there is a strange activity which is taking place, If the change is in the first stage of approval and if someone updates the Change and approvals remains as it is. The change request repeats the same approvals that are associated with the first set of group approvals. However if the approvals reach the second stage of approval, the change request behaves normally . I have tried to investigate this and only been able to get to a conclusion that the workflow is initiated again, and no OOB business script is taking part in inserting the approval again.

 

Has anyone seen this behavior before? Or there is any OOB script that i should be aware of?

1 ACCEPTED SOLUTION

I don't think that is possible .. if the tables are mentioned , it will not get copied for everything .. are you sure that the workflows for requests were copied from clone and not newly created when something was updated on the request? check the created dates for the workflow instances and cross check those with the parent instance from which you are cloning ...


View solution in original post

10 REPLIES 10

workflow contexts dont get copied by default after the clone .. this is the expected behavior ..


the tables excluded from clone can be referred from



System Clone > Exclude Tables


And if you find any responses as helpful or you got your answer, please mark and reward the appropriate responses


Thanks Kalai, but why there was not change with the workflow context of Requests?


did you look at this?



System Clone > Exclude Tables




is the table wf_context present in the list ? it holds the workflow instance attached to each ticket ...


Yes the tables was there, but as I mentioned below, the workflow are in tact with Requestes and not with the Change requests. I am not shure if that is suppose to happen.