topic Re: workflow definition not activated in Application Development and Automation Discussions

workflow definition not activated

Former Member — Tue, 08 Jul 2008 12:12:52 GMT

Hi,

I have developed a custom workflow and transported it to QA. It was working well in Dev system but when transported to QA workflow was not started . When I checked SWUD it shows workflow definition not activated. Further Transports does not have any issues and also event linkage is active .

But there is one discrepancy in SWDD header ,version overview does not show any active version.

I tried to create an active version with the help of function module SWD_WFD_REPLICATE_FROM_9999(which is mentioned in one of the OSS message 962488) but no luck

Regards,

Sirisha

Re: workflow definition not activated

Former Member — Tue, 08 Jul 2008 12:14:45 GMT

Hi Sirisha,

Check if triggerring event is active or not in QA.... Sometimes,after transport triggerring event is not active in QA.

Regards,

Aparna Gaikwad.

Re: workflow definition not activated

Former Member — Tue, 08 Jul 2008 12:28:24 GMT

Hi Aparna,

Triggering event is active and event linkage is correct.

Regards,

Sirisha

Re: workflow definition not activated

Former Member — Mon, 11 Aug 2008 06:11:46 GMT

I faced the same problems recently. Everything is transported without problems to QAS. After careful scrutinization, we found an error. The position maintained in one of the notification tasks exists in DEV but not in QAS. The wrong assignment of recipient type has caused this problem. Perhaps you may be encountering the same problem.

Re: workflow definition not activated

Former Member — Mon, 11 Aug 2008 06:15:44 GMT

Hi,

Check the Event linkage activation in Swe2. Sometimes just generating the BOR in QA syas the error. Check this possibility also. Else check the version management tool in SWDD.

Thanks

Papiya

Re: workflow definition not activated

Former Member — Mon, 11 Aug 2008 06:17:58 GMT

hi,

First transport the workbench request .

then transport the customizing request.

every time , when u make changes and transporting the tps ,

u should send both the tps in sequence.

try this , surely it vil work.

Regards,

Sabari

Re: workflow definition not activated

Former Member — Sat, 18 Jun 2016 19:38:05 GMT

i faced a similar problem recently just as described in the question and Tze Young Teh's answer did it for me. A user was assigned to a task in DEV and but that user was not created in QAS.

Re: workflow definition not activated

former_member196651 — Mon, 20 Jun 2016 10:04:00 GMT

Hi Sirisha,

Please check all the tasks in your workflow. Check each task and evaluate its agent assignment. May be the rule, the user etc assigned may be missing in QA. Please have close analysis.

Thanks & Regards,

Abijith