Two questions related to the pools.
1. A Pool (participant) can depict a Partner Entity (Org. unit) according to BPMN allocation diagram method. But it can't depics a System, Module or Block (Application System Type) or any other thing that a pool can represent. My question is:
(To SAG people) What was the reason for such limited implementation? And of no, is it in the pipeline?
(To the community) Any ideas of workaround?
2. Participants behave quite like a library object. An ARIS user would expect to have a participant definition with occurence in many collaboration diagrams. Well, not in cases when Participant represents a process but when it's clearly an organisational unit. However, this shouldn't be done. At least in the current BPMN implementation in ARIS. If occurrences are used, then a participant which is multiple in one collaboration will appear as such in all, including those that it is single in reality. The same applies for "process"-attributes that are maintained as poll attributes.
On the other hand having one and the same participant as definition copy in every collaboration limits many of the ARIS advantages. You can't even see in the relations and occurrences tab, what other things this Participant does in other situations.
That could be partially solved via BPMN allocation diagram and some nested queries. But I don't find it an elegant way. Other ideas, thoughts?
