RE: Transfer docs from one db to another Oscar W. Henneken 28.May.09 04:42 PM a Web browser Lotus Workflow Engine 3.0.1All Platforms
You could change the processos by changing the process when calling the DWFJobInitiate, right?
If this is done correctly, you would not need the reroute api call at all.
The DWFBinderAddDocument is needed only if you have some process running in the target application, which uses the binder from the source application as separate additional binder documents. Since you told me you were also transfering the cover documents, i assumed you needed them as a separate binder document. If not, just transfer the main document and use it as input for a new process using DWFJobInitiate.
If you need the coverdocument and you cannot get it to work,
you might just have to transfer that coverdocument in a different way, because it may interfere with the LWF engine in the target database. If that proves to be true, i would transfer the coverdocument while renaming all the os-fields on the back end document to os_bak fields and then add that coverdocument to the binder with DWFBinderAddDocument.
If you cannot get it to work within the same scope of DWFUtilSetApplication, i would firstly transfer the binder without job initiate. Then i would use another agent in the target application , outside of the scope of DWFUtilSetApplication, and have that agent perform the reroute and if needed the DWFBinderAddDocument.
Alternatively you could transfer the documents in pure Domino style, also renaming all the os-fields to os-bak fields, so that the LWF engine in the target application will not recognize the binder as an LWF binder and will not interfere. Then use an agent in the target application to initiate jobs based on your transfered document, e.g. using form-based initiation. To get that to work you will have to restore some fields to be compliant with form based initiation.
Hope this helps you out ....
Cynapps Workflow Solutions,