I don't know how you come up with this list and what every pattern/primitive means. The Designer supports the BPMN 2.0 elements that you can deploy on the Activiti Engine. In addition, it supports Activiti specific functionality like async continuations and Java service task classes.
So sorry for my previous post, i doesnt know if i choose the right topic. The list of the patterns and primitives i mentioned before is from this publication and i need to know if the macroflow engine has this possibilities.
Activiti as a process engine supports a subset of BPMN. For example you have the possibility to invoke a service. How this invocation works precisely is something you can/have to realize yourself. For example if you want an asynchronous, reliable invocation you might want to put a message in a reliable, transactional queue (like JMS). But there might be different ways to do that in your environment that make more sense (as you might not have a JMS Queue ready).
The point is: "patterns" like that need to be provided by both the process engine and the surrounding infrastructure collaboratively. As an embeddable process engine activiti does not provide things like asynchronous, reliable invocation "off the shelf" but allows you to realize it in your own infrastructure.