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.

Multiple single assignne isn't possible ?

cloe_durdux

Hello,

I try to develop a customized "sequential" workflow. And I want to choose only one person for each step (my example have 2 steps).
Is it possible ?
Because when I initiate my customized workflow I can filled up the firts level, but for the second one nothing appears.

I have a simple workflow with a succession of review base on the workflowModel.xml.

Like the bpm:assignee, I added to the bpmModel.xml my 2 aspect bpm:assigneeL1 and bpm:assigneeL2 :

<!–                       –>
        <!–  Single Task Assignee Level 1  –>
        <!–                       –>
        
        <aspect name="bpm:assigneeL1">
            <associations>
                <association name="bpm:assigneeL1">
                    <source>
                        <mandatory>false</mandatory>
                        <many>false</many>
                    </source>
                    <target>
                        <class>cm:person</class>
                        <mandatory>true</mandatory>
                        <many>false</many>
                    </target>
                </association>
            </associations>
        </aspect>
        
        <!–                       –>
        <!–  Single Task Assignee Level 2 - Association not found–>
        <!–                       –>
        
        <aspect name="bpm:assigneeL2">   
            <associations>
                <association name="bpm:assigneeL2">
                    <source>
                        <mandatory>false</mandatory>
                        <many>false</many>
                    </source>
                    <target>
                        <class>cm:person</class>
                        <mandatory>true</mandatory>
                        <many>false</many>
                    </target>
                </association>
            </associations>
        </aspect>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

In the web-client-config-properties.xml, I added

<config evaluator="node-type" condition="wf:submitReviewTaskL1" 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_review_priority" />
         <show-property name="bpm:workflowDueDate" display-label-id="wf_review_due_date" />
         <separator name="sep2" display-label-id="users_level_1" component-generator="HeaderSeparatorGenerator" />
         <show-association name="bpm:assigneeL1" display-label-id="wf_reviewerL1" />
         <separator name="sep3" display-label-id="users_level_2" component-generator="HeaderSeparatorGenerator" />
         <show-association name="bpm:assigneeL2" display-label-id="wf_reviewerL2" />
      </property-sheet>                    
   </config>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Everything is OK except the last line "show-association name="bpm:assigneeL2" display-label-id="wf_reviewerL2" />"
And in the log file :
09:01:46,955 User:admin WARN [component.property.UIAssociation] Failed to find association definition for association 'bpm:assigneeL2'

I've tried to switch my variable assigneeL1 and L2, but the result is nearly the same with the name of the bpm:assigneeL1 instead of bpm:assignneL2.

Thanks by advance.
Cloé

Find more posts tagged with

Comments

cjimenez2581

I have the same problem… I need to create something like that… have single asignee in diferent task….. Do you know how I can model it?

granddams

Hi,

for your custom workflow, i advise you to create your own files, and not tu change the existing one. Withou it, If you upgrade your version of alfresco, you'll lost your custo.
So in alfresco/tomcat/shared/classes/alfresco/extension

create a file myWorkflow-model.xml where you'll create your two associations and say that in your "wf:submitReviewTaskL1" you'll need these associations
create a file myWorkflow-process-definition.xml with, if you want, the same content that your old review-process-definition.xml
create a "web-client-config-custom.xml" file with your config

I don't know why your assigneeL1 works cause you've to change too this aspect's name in the file alfresco/tomcat/webapps/alfresco/web-inf/calsses/alfresco/workflow/workflowModel.xml?

With what i suggest you, you'll have to add

<types>
      <type name="your_wf_namespace:submitReviewTaskL1">
         <parent>bpm:startTask</parent>
         <mandatory-aspects>
            <aspect>your_wf_namespace:assigneeL1</aspect>
         </mandatory-aspects>
         <mandatory-aspects>
            <aspect>your_wf_namespace:assigneeL2</aspect>
         </mandatory-aspects>
      </type>
</types>

<aspects>
    <aspect name="your_wf_namespace:assigneeL1">
            <associations>
                <association name="your_wf_namespace:assigneeL1">
                    <source>
                        <mandatory>false</mandatory>
                        <many>false</many>
                    </source>
                    <target>
                        <class>cm:person</class>
                        <mandatory>true</mandatory>
                        <many>false</many>
                    </target>
                </association>
            </associations>
        </aspect>
        <aspect name="your_wf_namespace:assigneeL2">   
            <associations>
                <association name="your_wf_namespace:assigneeL2">
                    <source>
                        <mandatory>false</mandatory>
                        <many>false</many>
                    </source>
                    <target>
                        <class>cm:person</class>
                        <mandatory>true</mandatory>
                        <many>false</many>
                    </target>
                </association>
            </associations>
        </aspect>
</aspects>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

in your file myWorkflow-model.xml
You your two associations, and you use it in your task submitReviewTaskL1.

I think it could work.

cjimenez2581

Grand Dams, I cant resolve the problem… I did what you suggested but still does not work… I dont know what could be wrong…

can you check this topic, please? http://forums.alfresco.com/en/viewtopic.php?f=34&t=39796