topic Exception when assign workflow to assignees in Alfresco Archive

Exception when assign workflow to assignees

zengqingyi12 — Thu, 30 Apr 2009 12:42:50 GMT

right now I am working on alfresco share preview 2.there is no build in workflow that can assign multiple assignees, so i should do it by myself, there is such code in assign_workflow.post.json.js// Get the workflow definitionvar workflowDefinition = workflow.getDefinitionByName(workflowName);// Cre

Re: Exception when assign workflow to assignees

mikeh — Thu, 30 Apr 2009 15:27:18 GMT

Hi

Although I've not tested it, the following line in the original code looks a bit odd:

#57:       assignees[i] = [people.getPerson(assignees[i])];‍

I suspect you need to remove the array brackets around the right-hand side.

Thanks,
Mike

Re: Exception when assign workflow to assignees

zengqingyi12 — Thu, 30 Apr 2009 16:03:37 GMT

yes, you are right, when i debug the code the original code will form such a array[[],[],[]] , and I think the jpdm need a [ , ] array.
but when i remove the bracket, it still can not assign adhoc to multiple assignees,
could you please help me ?
Regards,
Dennis

Re: Exception when assign workflow to assignees

mikeh — Thu, 30 Apr 2009 21:09:09 GMT

What's the new exception after the code change? Same one..?

Mike

Re: Exception when assign workflow to assignees

zengqingyi12 — Fri, 01 May 2009 00:10:28 GMT

It seems that the adhoc model has cached or other reasons, i still cann't find the problem.

There is another exception: bpm:assignee is not defined.
What a strange problem! I do never change the bpmmodel's definition!

could you please tell me how alfresco communicate with jboss workflow ? just use jpdl ?

Re: Exception when assign workflow to assignees

mikeh — Fri, 01 May 2009 07:16:10 GMT

Did you redeploy the workflow? Note that in-flight workflows won't be updated.

See the wiki notes on the Workflow Console and Workflow Administration

Thanks,
Mike

Re: Exception when assign workflow to assignees

zengqingyi12 — Mon, 04 May 2009 04:42:32 GMT

Thanks so much, that's exactly where the problem is.