Not sure if what you are encountering is true or non understanding of livelink workflow.in essence this is how livelink workflows work.
You create a repeatable process .You paint this in a MAP.this is a special subtype in DTREE.This is just like a document with versions et al.
When somebody initiates this OBJID livelink makes a temporary copy of that instance version(objid) and copies it into a database table in wmap.
The assignments and all user interactions are based on the copy of the map let me call it localcopy.When you suspend the map and repaint the map you are only affecting this local instance and the changes are made on your local copy.
If you cahnge anything on the original map definition that has no effect on this local copy.
If you delete the form step unless the local copy logic is aware of the change,did you delete it before or after livelink assigned the work,then that would be dependent on that.If not as you say it is a bug that requires OT intervention
Changing the dtree map has no repercussions on any running instance that was initiated prior to the dtree map change.That is what I am saying
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
