Automatic state transition on new document approval

Question

Hi everyone, 
 we store documents in our vault automatically converting files into multi-docs upon approval (as a pdf is also generated). Files have Issue and Revision metadata. When a new version of the document is needed we do a "make copy" of the multidoc, update the Issue and Revision data, get rid of the pdf and covert the document back to single file for editing. 
 Now it is requested to add to the workflow an "Obsolete" state that should be triggered on the original multidoc as soon as the new version is approved. Is there any easy way to automatically trigger the transition? 
 Thanks in advance for any help! 
 Best, Max

Marcio · Accepted Answer

From what I understand, it makes a copy of the original object, in this copy the updates are made. You can use a vault event depending on when you want to change the state of the original object. Example: If everything occurs in the copy, use the event: BeforeCreateNewObjectFinalize If it is at another time, you need to see which event fits best. 
 But in any case, you need to fetch the original object, put it in check-out, add it to the obsolete state, set the check-in. But this will be done via development, I suggest accessing the link: developer.m-files.com/.../