Steps to reproduce:
1. Create event with default workflow
2. Leave Cutting and Review config options checked
Actual Results:
The Cutting operation is skipped
Expected Results:
The workflow pauses for Cutting and Review
Workaround (if any):
in ng-partial-publish the editor operation has the config option "interactive" set to "false"
Hi James,
I am not sure I completely understand. The workflow panel has two options (cut and review) that basically mark the recording as "needs cutting", "needs review". Whether the recording is published before that or is holding, is subject to the "Publish right away" setting. So I am not sure if we are actually looking at a bug here? (other than a documentation bug, maybe)?
Thanks,
Tobias
Ok, so I see that the Cutting and Review options do nothing other than add comments that the Video needs cutting and review.
However these options are checked by default and if the recording needs needs Cutting and Review then surely it should not be Published before there has been and opportunity to actual cut and review it! In my mind selecting Cutting and/or Review implies Hold.
From what I understood it correctly, the idea of a hold state has completely been removed in 2.0. Even when I use the old admin ui in 2.0 sending something to the video editor, the hold state is just skipped and the workflow runs through without waiting for user input.
Again Ok, but selecting Cutting and Review still implies that files shouldn't be published until Cutting and Review!
I huess that is correct. A better wording could be “Add review notification”, “Add edit notification”? That would make it clearer that only a comment is added that the event should be reviewed and “hold” needs to be selected if it should not automatically be published.