Alfresco permission of deployed custom workflow

Question

How can i set the permission of a custom worflow?

I deployed a BPMN 2.0 workflow, by placing the bpmn20.xml in /alfresco/extension and also using the following workflow-context.xml

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>
<beans>
    <bean id="acme.workflowBootstrap" parent="workflowDeployer">
    <property name="workflowDefinitions">
      <list>
        <props>
          <prop key="engineId">activiti</prop>
          <prop key="location">alfresco/extension/workflows/activiti/superflow.bpmn20.xml</prop>
          <prop key="mimetype">text/xml</prop>
          <prop key="redeploy">false</prop>         
        </props>
      </list>
    </property>
    </bean>
</beans>

The workflow can by found in the Worfkflow console and can be run.

The problem remaing is, that I can only see this worfklow as admin in alfresco share. Not as admin@acme .

How can I set permission to use this workflow as different user than admin?

Answer 1

There is an alfresco extension project available to achieve workflow permissions https://addons.alfresco.com/addons/workflow-permissions

Configuration is done in your share custom config, using the elelement "permission-workflows" like this :

  <config evaluator="string-compare" condition="Workflow"> <!-- A list of workflow definitions that are NOT displayed <hidden-workflows> <!-- Hide all WCM related workflows --> <workflow name="jbpm$wcmwf:*" /> <workflow name="jbpm$wf:*" /> <workflow name="activiti$activiti*" /> <workflow name="activiti$quickStart*" /> </hidden-workflows> <!-- A list of workflow tasks that are NOT displayed inShare --> <hidden-tasks> <!-- Hide all WCM related tasks --> <task type="wcmwf:*" /> </hidden-tasks> <permission-workflows default="allow"> <permission-workflow name="activiti$epubcreate"> <authorities> <authority type="group">GROUP_ALFRESCO_ADMINISTRATORS</authority> </authorities> </permission-workflow> </permission-workflows> </config> 

Answer 2

I cannot really speak to how much of the Activiti engine that is bundled with Alfresco is actually exposed. But in the stand alone Activiti product you can assign "candidate starters" to any process.

http://www.activiti.org/userguide/#_add_a_candidate_starter_to_a_process_definition

This uses the identityLinks mechanism that is also available for tasks, instances and executions.