<process-definition
xmlns="urn:jbpm.org:jpdl-3.1"
name="wf:sam2">
<swimlane name="initiator">
<assignment actor-id="#{bpm_assignee.properties['cm:userName']}" />
</swimlane>
<start-state name="start">
<task name="wf:start" swimlane="initiator">
<controller>
<variable name="color" />
<variable name="size" />
</controller>
</task>
<transition name="commencer maintenant" to="relecture"></transition>
</start-state>
<end-state name="end"></end-state>
<task-node name="relecture">
<task name="wf:relecture" swimlane="initiator"></task>
<transition name="terminer maintenant" to="end"></transition>
</task-node>
</process-definition>
Ensuite pour le bpm_assignee, il faut définir ton type wf:start dans ton workflow model, ce dernier contenant le bpm_assignee: <type name="wf:start">
<parent>bpm:startTask</parent>
<properties>
<property name="wf:mailGestionnaire">
<type>d:boolean</type>
<default>true</default>
</property>
</properties>
<mandatory-aspects>
<aspect>bpm:assignee</aspect>
</mandatory-aspects>
</type>
Enfin il faut dire d'afficher ce bpm_assignee dans le web client: <config evaluator="node-type" condition="wf:start" replace="true">
<property-sheet>
<separator name="sep1" display-label-id="general" component-generator="HeaderSeparatorGenerator" />
<show-property name="bpm:workflowDescription" component-generator="TextAreaGenerator" />
<show-property name="bpm:workflowPriority" display-label-id="wf_adhoc_priority" />
<show-property name="bpm:workflowDueDate" display-label-id="wf_adhoc_due_date" />
<show-property name="wf:mailGestionnaire" />
<separator name="sep2" display-label-id="user_filter_user" component-generator="HeaderSeparatorGenerator" />
<show-association name="bpm:assignee" display-label-id="wf_adhoc_assignee" />
</property-sheet>
</config>
Voilou avec ça ça devrait marcher!!!! Pour savoir ce qu'est ce bpm_assignee, il faut aller dans bpmModel.xml. Il s'agit d'un type de la classe cmerson, donc des personnes :rolleyes:Content from pre 2016 and from language groups that have been closed.
Content is read-only.
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.