[opencms-dev] Release workflow issues in OpenCMS 16
Michael Emmerich
m.emmerich at alkacon.com
Tue Aug 27 11:01:14 CEST 2024
Hello Anson,
the workflow feature was build into OpenCms according to some
specifications of a customer many years ago. Therefore it works as the
customer once had specified.
Regarding your questions:
You are testing the workflow with the "Author" and "Editor" users. Both
users are in the "Users" group. This group is the "ProjectManager" group
of the Offline project and therefore every user who is in this group is
allowed to publish, even if the workflow is enabled.
When the feature was developed and my presentation was made many years
ago, the "ProjectManager" group of the offline project was a different
one, therefore users in the "Users" group were not allowed to publish at
all.
There are now two ways how to solve this:
1) Create a new group, lets call them "ProjectManagers" and assign this
group as the ProjectManager group to the offline project. Then, everyone
who should be allowed to publish in the offline project must either be
in this group or an Administrator. All other users can use the "Release"
function in the publish dialog.
2) If you do not want to modify the Offline project, there is another
way: Create a new group lets call it "Restricted release". Create a new
user and assign it to the "Restricted release" group. Make sure that the
user is NOT part of the Users group. Now set a permission on the site
folder for the group "Restricted release" allowing it to read (R), view
(V) and write (W). Users of this group will not be able to edit and
save content, but not to publish it, they can only use the release
function of the workflow. Users who will be in the normal "Users" group
will be able to publish as usual.
To me, solution 1) would be the easier to do.
The other observation, when you re-edit a content that is in workflow,
it will be removed form it, this is correct and there is no workaround
for it. This is based on the initial requirements as mentioned above.
Kind regards,
Michael
Am 26.08.24 um 08:17 schrieb AnsonYF Cheung via opencms-dev:
>
> 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)
>
> 2. Click “Publish” icon on header and choose “Release” in workflow;
> Then, click the bottom “Release” button
>
> 3. An email with a list of modified contents would be received by the
> Admin
>
> 4. 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)
>
> 5. 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.
>
> 2. 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)
>
> If the Administrators publish the release after that, these de-coupled
> contents would be missing. (in this example, 00042.xml)
>
> 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.
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> https://lists.opencms.org/mailman/listinfo/opencms-dev
>
>
>
--
Michael Emmerich
Alkacon Software GmbH & Co. KG - The OpenCms Experts
http://www.alkacon.com -http://www.opencms.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 112650 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 105023 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 547020 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 275150 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 69269 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 193997 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 131374 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 143151 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 218889 bytes
Desc: not available
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20240827/0885a403/attachment-0017.png>
More information about the opencms-dev
mailing list