[opencms-dev] Release workflow issues in OpenCMS 16

[AnsonYF Cheung]

Hi all experienced users and developers,

My Test environment:

  *   OpenCMS 16 on Docker running Tomcat & MariaDB

I would like to use the workflow function to perform a 2-level approval of content management required by the user. Thus, I enable the workflow function by using the following steps.
http://www.slideshare.net/AlkaconOpenCms/opencms-days-2015-hidden-features-of-opencms      (Slide 35-41)

With the following config added in opencms-system.xml
              <workflow class="org.opencms.workflow.CmsExtendedWorkflowManager">
                      <parameters>
                             <param name="workflowProjectManagerGroup">Administrators</param>
                             <param name="workflowProjectUserGroup">Users</param>
                      </parameters>
              </workflow>

Test users (come with the OpenCMS initial config):

  *   Editor/Author (under "Users" user group)
  *   Admin (under "Administrators" user group)

My Test steps:

  1.  Login by Editor (or Author) and edit two content sections on a page (e.g. the first two content sections under /mercury-demo/index.html)
[cid:image001.png at 01DAF7C0.AFBCABD0]
[cid:image002.png at 01DAF7C0.AFBCABD0]
[cid:image003.png at 01DAF7C0.AFBCABD0]

  1.  Click "Publish" icon on header and choose "Release" in workflow; Then, click the bottom "Release" button
[cid:image004.png at 01DAF7C0.AFBCABD0]

  1.  An email with a list of modified contents would be received by the Admin

[cid:image005.png at 01DAF7C0.AFBCABD0]



  1.  Login by Admin and click "Publish" icon on header; select the release shown in the email; select all the resources; Then, click the bottom "Publish" button (enabled after contents selected)
[cid:image006.png at 01DAF7C0.AFBCABD0]

  1.  Checked the contents are published properly.

However, I encountered the following 2 issues:

  1.  When login by Editor (or Author), the "Publish" option in workflow dropdown can still be selected and the bottom "Publish" button can still be clicked. it seems there is no way to disabling the "Publish" operation in access control. It would be a loophole that Editor (or Author) can bypass the approval workflow required by the organization.

[cid:image007.png at 01DAF7C0.AFBCABD0]

  1.  When the modified objects (e.g. content sections) is under the release workflow (pending for release), the content could still be edited by the Editor again and even other editors. If doing so, the content under review would be de-coupled from the existing release workflow (see the below screen). (in this example, 00042.html is being modified by Editor again and warning icon about the object releasing in progress would disappear)
[cid:image008.png at 01DAF7C0.AFBCABD0]
If the Administrators publish the release after that, these de-coupled contents would be missing. (in this example, 00042.xml)
[cid:image009.png at 01DAF7C0.AFBCABD0]

I would be grateful if someone could help. Thanks!

Regards,
Anson



________________________________

Think before you print.

Disclaimer: This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Computer And Technologies Holdings Limited and her wholly owned subsidiaries. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone.  Please contact the sender if you believe you have received this email in error.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 112650 bytes
Desc: image001.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 105023 bytes
Desc: image002.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 547020 bytes
Desc: image003.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 275150 bytes
Desc: image004.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 69269 bytes
Desc: image005.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 193997 bytes
Desc: image006.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 131374 bytes
Desc: image007.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 143151 bytes
Desc: image008.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 218889 bytes
Desc: image009.png
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240826/0b94615f/attachment-0017.png>