topic Re: Issue with Multi-Instance variables and extensionElements in Alfresco Archive

Issue with Multi-Instance variables and extensionElements

wilco — Tue, 19 Nov 2013 09:18:25 GMT

First of all, thanks for this great framework!In my project I'm switching from Activit 5.11 to 5.14. I'm using a bpmn serviceTask like this: <serviceTask id="dicomsort" name="dicomsort" activiti:delegateExpression="${dicomSortIOActivity}">

Re: Issue with Multi-Instance variables and extensionElements

wilco — Tue, 19 Nov 2013 10:21:17 GMT

I did some more investigation:

For me it seems, that the MultiInstanceActivityBehavior is executed AFTER the ExecutionListener. Maybe this is the desired behavior but in my case, the loop variables are not yet set when the executionlistener is fired.

Any idea how to modify this behavior?

Wilco

Re: Issue with Multi-Instance variables and extensionElements

trademak — Tue, 19 Nov 2013 11:06:10 GMT

I don't understand why you switched from using activiti:field variables to the extension elements. To my knowledge we didn't change anything since 5.11 that prevents you from using activiti:field elements. Can you elaborate a bit more on that?

Best regards,

Re: Issue with Multi-Instance variables and extensionElements

trademak — Tue, 19 Nov 2013 11:07:31 GMT

Okay, did you try to use an embedded sub process with the multi instance definition and a service task with the execution listener in the embedded sub process?

Best regards,

Re: Issue with Multi-Instance variables and extensionElements

wilco — Tue, 19 Nov 2013 12:19:09 GMT

Regarding my refactoring when migrating from 5.11 to 5.14:
In 5.11 I was using Activiti:field members to store custom configuration options. The values of those options were captured via ParseListener and ExecutionListener and stored in a seperate Java object which can be accessed in the serviceTasks. But since 5.14 I have no access to Activiti:field fields using the BpmnParseHandler handler. The BpmnParse.getExtensionElements() doesn't return activiti:field fields. It only returns other custom extension fields (like the one in my first post above). But at the end I like the idea of having a custom section in the extensionElement.

Regarding the sub process:
No, this is not a subprocess. It's just a regular ServiceTask in a multi instance loop.

As I said, the main issue for me seems to be that the ExecutionListener is executed before the Multi Instance behavior is executed. So that's why the loop variables are not available.

In the meantime i tried to implement a custom ActivityBehavior which should do the job of the ExecutionListener. But this did not yet work out very well. Or is there another way?

Wilco

Re: Issue with Multi-Instance variables and extensionElements

trademak — Wed, 20 Nov 2013 15:18:21 GMT

I know it's not a sub process, but you could implement it like I explained. That should work I think.

You should be able to get the field definitions from the ServiceTask instance using the getFieldExtensions method. Did you try that?

Best regards,