We are creating some jobs for the Vault Job Processor.
The jobs are fired if the state of an item is changed to a released state. Je jobs will be executed on the files.
We have added the job to a the transition from Review to Released with the LifeCycle Event Editor, where we log in as JobProcessor user, which has all rights on items, even in released state (and can make changes to the item).
The job itself will also log in as this JobProcessor user.
We are able to queue this job manually (richt mouse click) and by changing the state to Released.
But in both situations, the job is submitted by the active Vault user and not by the JobProcessor user. The problem is, that the active user is an engineer and her has no modify rights on items which are in released state.
How can we control the user which will execute the job?
I saw in the job queue, that you can take "ownership" on a job. Do we have to do something like that within our job code?
