08 Jul 2010
10 Nov 2011
Link to this post
We are using a workflow that utilizes 2 levels of approval before publishing. We have recently upgraded our test environment to 4.2 SP1 and then 4.3 once it was released. During testing, I'm getting an error screen when the following steps are taken:
1. An author (our Course Author role) accesses a page to begin the workflow, and adds content to the page.
2. The same author chooses to Save as Draft rather than advancing the page through the workflow.
3. The same user then attempts to Edit any of the widgets added to the page = error in attached SS
I have verified that this same error is generated on a fresh local 4.3 project.
I noticed that the first stage of the workflow (pre level 1 approval... IE when the page is first created and content added to it) does NOT behave in the same manner as the later stages of workflow in terms of saving the page without workflow progression. In the later stages, users in the appropriate roles can perform the analogous actions (Save as Awaiting Approval or Save as Awaiting Publishing), but it does NOT keep them on the page - it automatically re-directs them back to /pages. Is this the desired behavior for ALL stages of the workflow? If so, why does the first stage not re-direct as the others do? I would argue that, similar to most other applications, you should be able to save your work and continue to make changes un-interrupted, as frequently as you want to.
SS of error attached.