Version Management in workflow..

[Former Member]

Hi ,

How to do Version Management in workflow ?

I am working on an issue of workflow where there is difference in the workflow version and the FM  in Rule Definition in Quality and development.

Kindly tell me the method to do the version management for the Workflow so that I can make Quality and Development in sync.

Thanks,

Mrinal Pradhan

[Former Member]

Hi Mrinal,

Yes, the version numbers will be different for each clients.

If you want to synchronize your workflow in all the clients, create a new TR in Dev and move till Production.

Function module in the Rule is also like a normal function module and you can do the version comparison at SE37.

Thanks,

Viji.

[ronen_weisz]

I also agree with Modak about the workflow template version management. workflow object and FM based rules can be compared as any other program/function module via SE39 (the objects program can be compared)

[Former Member]

Hi Mrinal,

As stated by Modak, the workflow version numbers can be different in different systems even though it is the same workflow logical version.

You can check with the Changed by, Date and Time stamps on the workflow versions and then manually sync them.

~Ali~

[I042439]

Hi Mrinal

The Version Management in WF does not works like that of ABAP code, say a function module.

When you create a new workflow in DEV system, it gets created with a version 0000. When you change in DEV, it overwrites the same version (unless, development system has a separate client for testing and there is a running instance).

How system determines a version - if an instance of workflow is running during activation, it creates a new version, (so that already running instances can still use the old version in which they were started); Any new workflow started after the activation would run with the latest version.

When you transport to QA or PRD, same check happens.

So if you change a workflow in DEV, activation may not result in version increment as there may not be a running instance in DEV. But when you transport to QA, the version may or may not increment based on a running instance at the time of import. Same applies for PRD.

Hence, the workflow version number may not be same in DEV, QA and PRD even though it's the same logical version.

To summarize, you have to manually check for differences in the workflow definition.

Regards,

Modak