OpenCore version: 1.5.11.95
self hosted
Hi Allan,
“on success, push to” does not save on updateing a queue.
It also does not set any value in the database, so its not only visual.
Setting it manually in the database works so.
Greetings Marvin
OpenCore version: 1.5.11.95
self hosted
Hi Allan,
“on success, push to” does not save on updateing a queue.
Setting it manually in the database works so.
Greetings Marvin
Oh, that is a mistake, it was not supposed to be something you can change. I will get that fixed.
And please, please do not change it directly in the database … it will mess up a lot of things if the work item has files associated with it (if not, then you can still do it, but sometime in the future I may add features that will break if you do it, so I would highly recommend you do not do that).
If you need to have copies of a work item, you can set a “success” queue on either the work item queue itself or “ad hoc” for work item doing update work item. This will make opencore safely create a copy of the work item and put it in the next queue, when an item shifts status from “processing” to “successful”, this will also handle files correctly (without making a copy of the files).
you can set a “success” queue on either the work item queue itself
That is exactly what i want to do? I open the work item queue setting and try to set this setting. There is no other setting in the Work Item Queue that say anything about success.
Christ ! .. sorry, i completely misread your post …
Thank you ! … and yes, i will get this fixed as soon as possible
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.