Workflow state on document move

RE: Workflow state on document move

Jeff Burrill — Tue, 19 Aug 2014 06:07:20 GMT

My solution takes care of the current version as well as old versions. The methods used to preserve state of old versions is the part that goes beyond the normal API function that handles the current version. But the basis for all of it is in hooks.

The API provides the ability to add a "hook" into different points of event chains. In my solution, the hook gets registered and runs whenever a document move operation is detected in ProjectWise Explorer. Using information available to the hook about the document being processed at that time, you can use API methods to manipulate the document, such as set the workflow state.

There are some good examples that demonstrate hook usage in the SDK samples.

RE: Workflow state on document move

Leif Frederiksen — Tue, 19 Aug 2014 05:37:57 GMT

Hi Jeff,

Thanks for your answer.

So what you are saying is, that you created a solution to keep the correct state on the current version, but not on the older versions (the ones that are also hardest to fix afterwards)?

I do not have experience with the SDK (yet) - can you enlighten me a bit on how you accomplished this?

/Leif

RE: Workflow state on document move

Jeff Burrill — Mon, 18 Aug 2014 17:28:15 GMT

There is no out-of-the box setting to force preservation of workflow state when moving between folders, even if they share the same workflow. Though some times it might appear they are being preserved, that is purely coincidental; e.g. the state applied after the move (dependent on what your datasource settings are for "Creation in workflow") just happens to match what it was before the move.

Prior versions cannot be modified in any way, and this includes workflow state. Given that rationale, I do not understand why workflow states aren't automatically preserved on the older versions when a document with versions is moved - at least between folders with the same workflow, but I digress...

I put in a CR for these very issues a while ago (sorry, can't recall the CR#) but to date, they haven't been addressed. In the meantime, I came up with my own workarounds. Using the SDK, I was able to solve state preservation for current versions using a hook. I also engineered my own SDK solution to modifying state of prior versions, but that one goes beyond the native capabilities of the SDK and would not be supported by Bentley.