You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation is working but is not intuitive enough:
Permissions for workflow package are in task models.
Permissions for files in the package are in beans properties in context.
We need to keep these options for backward compatibility, but we also need better permissions configurations (most probably, everything should be configured from the model).
Two special use cases from the related ticket ALV-705:
It would be great if I could set also a custom role I created, not only the standard Alfresco roles. Example: Let's say I have a custom role, which provides edit permission to change properties, but only read access for the content. This cannot be covered by a standard Alfresco role.
If I understand correctly, now the customizing is workflow specific - better said workflow instance specific - so the user has access rights to the documents regarding the concrete workflow instance (Process ID). Would it be possible to enhance it as task-specific? So you will be able to define 2 tasks in the same WF definition with different behavior, e.g. factual approval with read-write permission, and after this another task for a different user for business approval with read-only access. As far as I know this cannot be achieved now in the same WF definition.
Current implementation is working but is not intuitive enough:
We need to keep these options for backward compatibility, but we also need better permissions configurations (most probably, everything should be configured from the model).
Two special use cases from the related ticket ALV-705:
P.S. Migrated from http://issues.itdhq.com/browse/ALV-727
The text was updated successfully, but these errors were encountered: