topic How to specify activiti:collection variables? in Alfresco Archive

How to specify activiti:collection variables?

rby — Tue, 06 Sep 2016 16:27:16 GMT

Greetings!I'd like to know how to work with multi-instance type SubProcesses.Process consist of 3 transactional subProcesses:Garden,Tree,Fance //as exampleTree subProcess should be done multiple times.Here is bpmn20.xml process template:<?xml version="1.0" encoding="UTF-8"?><definitions xml

Re: How to specify activiti:collection variables?

trademak — Wed, 07 Sep 2016 09:29:18 GMT

Is there a specific reason for using the transaction sub process?
Because I don't see any compensation events in the process definition, so you could use a standard subProcess element.
The trees collection is expected to be a variable in the process instance context. And in the code provided, I only see the garden variable being used to start the process instance.

Best regards,

Re: How to specify activiti:collection variables?

warper — Wed, 07 Sep 2016 09:45:12 GMT

You need process variable trees defined/evaluated in process or supplied to it in vars map on process start. Currently you only put 1 variable - garden

Re: How to specify activiti:collection variables?

rby — Wed, 07 Sep 2016 10:15:23 GMT

At the moment i don't need to use transactions,I may use them in a scale,thank you!

So do i need to specify trees collection before starting and use it to start the process?

I try to integrate with openstack ,so mine task is to create Tenant (Garden), multiple Networks (Trees) and they should form VM (Fance). I can not specify their variables right before starting the Tenant sub process. The result of Tenant sub process should provide some information for Networks ,in the end Networks provide the information for creating VM.

Re: How to specify activiti:collection variables?

jbarrez — Thu, 08 Sep 2016 09:36:52 GMT

you need to provide that collection when the execution arrives at that step in the process instance.
Either by an API call or by it is being set by a JavaDelegate.

Alternatively, you can have a bean (for example with Spring) that uses an expression like ${myBean.determineTrees(execution)}. That bean will be consulted when needed at runtime.