Migrating Workflows while doing a parallel upgrade

[Stelex]

For awhile here we were wondering how to keep the workflow status updated when doing a parallel upgrade from 9.2 SP1 to 9.5 SP1. We needed to keep two versions running in parallel for a few months.

Document objects and such can be handled by the Object Importer/Exporter modules - but how would one manage the Workflow Status and audit records? We had a highly customized workflow in 9.2 SP1 that wouldn't migrate to 9.5 SP1, so we re-wrote it using more or less standard functionality. But then we were wondering how we would keep the two status' in sync - while we wouldn't necessarily be working on a 9.2 initiated workflow in the 9.5 environment, we would still need to keep the workflow status, audit trail and and any documents in the workflow attachment volume updated.

I think this might be able to be scripted through SQL - anyone care to hazard a guess as to what the SQL might look like?

 

[appnair]

You can port any workflow information from 9.2 to 9.5
by using oscript or lapi as static pages,if that is what you are asking.If the 9.2 workflow did not get upgraded to 9.5,I would refrain from bringing database records of the workflow schema from one to another thinking that it may work.If you have the 9.2 system up and running all you have to program is a query limiting all or the particular workflows a that you are looking for,then look at the work package of each one,it will have the attachments,attribute data and what not you may want to capture and write an oscript routine.The workflow schema is well documented so is the workflow data structure and its development.Jeff Lang who wrote most of the opentext workflow sees this forum and you can contact him at

http://globalcents.com

to see if you can use one of his importers for this purpose as well.If anybody ought to know how it could be done efficiently Jeff should.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937