Question:
Workflow Folks,
I need to lock a workflow against instantiation. I believe you can do it through workflow start conditions if the workflow was event driven but this workflow is not so.
This workflow is triggered via function module sww_fi_start from a lot of program and to uncomment it from all thos programs is tedious as those are locked for other development.
I tried setting the lock flag in Additional Data->Classification screen in the workflow template change screen, but it did not create any customizing transport for this activity. ( We have 2 clients in the Dev Box. One where development and custimizing is done and other where testing is done. )
So i assumed it should be visible in the testing client but it is not and does not work.
The underlying table which stores this activity is HRP1217.
Any inputs on this would be greatly appreciated.
Thanks
Krishna.
Answer:
Hi,
Correct me if I'm wrong.
In your system you want to prevent a workflow from instantiating.
This workflow is started hard coded in a lot of programs via FM sww_fi_start ( you mean probaby SWW_WI_START)
Options:
1. In PPOM you can prevent the workflow from instantiating
2. work around, in the workflow definition, make the first step end the workflow, or check if the workflow was started via an event, if not, end it
3. Although it's tedious change the programs starting it, it's not a clean method anyway.
Regards, Rob Dielemans
Answer:
Thanks Rob. I think I will use PPOM to lock the workflow against instantiation as per your suggestion.
Krishna.