topic Re: Custom humanPerformer in Alfresco Archive

Custom humanPerformer

mir — Wed, 22 Feb 2012 13:33:25 GMT

Greetings,I came across this issue while developing a custom workflow with Activiti: there are two assignees in that workflow, first one being bpm:assignee and the second one being, say, mywf:assignee2; it is declared through an aspect in myWorkflowModel. They are in charge of a task each in the wor

Re: Custom humanPerformer

amandaluniz_z — Wed, 22 Feb 2012 14:57:23 GMT

Doesn't it say which is the unknown property?

Re: Custom humanPerformer

mir — Fri, 24 Feb 2012 05:53:51 GMT

Doesn't it say which is the unknown property?

Nope, unfortunately. I'm pretty sure its the mywf_assignee2, since replacing it with bpm_assignee removes the error; it isnt really a solution though. The error message I provided is the entirety of what I'm seeing.

Re: Custom humanPerformer

amandaluniz_z — Fri, 24 Feb 2012 09:44:36 GMT

can you post the workflow's xml file in here as well as the workflow model?

Thanks,
Adei

Re: Custom humanPerformer

mir — Fri, 24 Feb 2012 12:30:26 GMT

workflowModel: http://paste2.org/p/1914557
process: http://paste2.org/p/1914559

Aspect is cntpwf:developer, task where it gets assigned is expertRequestTask, task where it gets used - and where it fails to transition - is developerRequestTask, through flow4.

I'm nowhere nearer solving the problem than I was a couple days ago; kind of bugging me now, cant wait to find out I still missed some kind of typo through all the checks I did.

Re: Custom humanPerformer

amandaluniz_z — Fri, 24 Feb 2012 16:49:24 GMT

I guess you have already changed this, right?

From:

<formalExpression>${cntpwf_developer}</formalExpression>‍

To:

<formalExpression>${cntpwf_developer.properties.userName}</formalExpression>‍

That is in line 158

Re: Custom humanPerformer

mir — Sat, 25 Feb 2012 12:46:57 GMT

Yeah, had .properties.userName there for a while, changed it when desperately trying to make it work.

EDIT: was wrong previously. Eventually solved through adding


<activiti:taskListener event="complete" class="org.alfresco.repo.workflow.activiti.tasklistener.ScriptTaskListener">
   <activiti:field name="script">
      <activiti:string>
         execution.setVariable('mywf_assignee2', task.getVariableLocal ('mywf_assignee2'));
      </activiti:string>
   </activiti:field>
</activiti:taskListener>
‍‍‍‍‍‍‍‍‍

to the node that assigned the assignee2.

This subject somewhat freaks me out with how little consistency it has been presenting; hopefully this fixes it once and for all.