nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Task Model Permissions vs. Attachment Permissions

srobinson

I have a client requirement that wants the attachment of the workflow to be read only to all reviewers as its moving through the review process. The issue that I am having is that when I set the permissions on the attachment to Consumer for the reviewers, they are not able to add comments or edit any fields on the task model. When I increase the permissions to Editor, the task model fields are editable. Is there a way to achieve such separation of permissions between the task model and attachment permissions? I want to be able to edit the task model form fields without setting edit permissions on the workflow attachment.

Any help on this is greatly appreciated. This is a critical issue for my client.

Thanks,

- Shannon

Find more posts tagged with

Comments

ronald_van_kuij

Isn't this more a question for an Alfresco forum?

frederikherema1

Is indeed more Alfresco-related. I will try to answer, nevertheless:

A task can only be edited by the person that is assigned OR by the process initiator. This has nothing to do with permissions on the models, more of a service/ui constraint. The content-model uses for tasks describes the task, however, the task is NOT an Alfresco-cm:content but just a task in activity, having no Alfresco ACL's capabilities.

A solution should be to:
- Create a multi-instance (as parallel-review) that has a task for EACH reviewer assigned to him/her explicit ally.
- Add a service-task before the tasks, setting READ_CONTENT permission to all selected assignees
- Add a end-task-listener to the review-task, that revokes (if needed) the READ_CONTENT permissions from the document again

Or am I getting your use case wrong?

srobinson

Thanks for your input. It does help in the understanding of the integration. Sometimes it is difficult to know what things were put into place from an Alfresco end and what is Activiti.

My use case however would actually call for the assignee to have READ access on the attachment and edit access on the task. My process actually does something similar to what you have mentioned, but the task UI in Alfresco remains read-only following the access on the content. It does seem that there is something in the Alfresco UI that is preventing this and not anything that can be controlled in Activiti.

Thanks again for your response.

- Shannon