Vault Custom Job for function 'Roll Back Lifecycle State' of a File

[kefer_kb]

It should be possible to configure a vault custom job when the
reset of a file's lifecycle status is executed.

Background: When a change to the lifecycle status is executed, e. g. new status 'WIP', a vault job makes changes to the part in our ERP system. (ERP part is 'WIP' too, not released)

If the user resets the change to the lifecycle status, the changes in our ERP system are not reset to the old values. A status roll back is also a status change, so a custom job should also be configurable!

[RajSchmidt]

Excellent Idea, I would love that!

However, as I understand it, the roll back does just revert to the previous state of the document. No matter which states, categories, or lifecycles are involved. Jobs, on the other hand, are attached to specific changes (from state 1 to state 2 in a certain lifecycle).

You would have to solve this with an extra setting within the lifecycle definition. Same way as you trigger a job for a change from state 1 to state 2, you would have to define a job for that specific roll back.

[kefer_kb]

@RajSchmidt

Basically, you are right. But our jobs are not geared toward the initial state; only the target lifecycle is considered. We have configured several jobs for each status change. One job for dataexport, one for publishing in definedn formats, ... and exactly one job is responsible for data synchronization with the ERP system. This job checks the current status (WIP, released, etc.) and performs the necessary steps. Therefore, the following lifecycle configuration menue item would suffice for us:

Jobs after resetting the lifecycle: Jobname1, Jobname2, etc.

[RajSchmidt]

Yes, that is exactly what I was talking about. We need a possibility to define, what jobs are triggered on roll back.