Assign Workflow

Hey there! Thank you for the great job so far, I am really impressed of what I see so far :)

I have currently a requirement to create a workflow where different users (or user groups) have to work on one object (of a specific entity type) by adding some more data via form and after they have finished their part assign it to the next. As far as I can see the workflows are currently configured via yml only and there is no acl or permission handling or role assignment or whatever in the current implementation.

Is it planned to provide such a feature in the future? In the roadmap it says “advanced workflows” for version 1… Or do you have any suggestions how to hook into the current implementation (via events/listeners or so) to add some more dynamic logic to a workflow than “just” serializable configuration via yml?

Thanks in advance,
Andes

Topic

[andeskParticipant]

Ah, maybe this could be done with a custom condition service? Like custom actions documented here: https://github.com/orocrm/platform/blob/master/src/Oro/Bundle/WorkflowBundle/Resources/doc/reference/workflow-entities/transition-actions.md#add-custom-action ?

[andeskParticipant]

I got it to work, somehow… Built a custom condition as explained for actions above, configured it as a service with security context as argument and then checking inside if access is granted. But it does not feel that comformtable. So are there any plans to introduce permissions into workflow transitions?

[Dima SorokaKeymaster]

Hi andesk

Yes, we are planning to implement permissions management per transition per role with support of access scope.

[andeskParticipant]

Thank you for your reply!

Does this get into version 1 or later?

[Dima SorokaKeymaster]

Most likely will be included into version 1

[andeskParticipant]

That is great news! :)

[andeskParticipant]

Hey there!

Because of http://oroinc.com/orocrm/qa/64/share-use-cases-for-custom-workflow-you-have-built I remembered this topic and checked the documentation of WorkflowBundle. Did not find any words about the access scope. Did I miss it or is it still work in progress?

Thanks for answer :)

[Yevhen ShyshkinParticipant]

Hi, andesk.

Did you check this topic http://oroinc.com/orocrm/forums/topic/workflow-acl#post-4166? If you have some questions related to it – feel free to ask them here.

For now we don’t have ability to select transition availability based on ACL scopes because transitions have no owner, but we have this improvement in our backlog.

[andeskParticipant]

Thanks for the link!

Is this “acl_resource” a “real” acl setting in database or could we implement specific voter classes to handle permissions dynamically?

[Yevhen ShyshkinParticipant]

Actually, both. :)

“acl_resource” is a system level ACL that simply checks whether is allowed for current user. If you don’t like the way it works – you can override condition “acl_granted”.

As for voter you can always implement your own and handle permissions dynamically. We already have voter that restricts access to entities depends on step.

[Author]

Replies