nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Designer vs. Patterns

santa1

Hello, just wanted to ask if the Designer contains or has implemented following patterns and primitives:

ProcessFlow
- Process Flow Refinement
- Process Flow Steps
- Macroflow Model
- Microflow Model
- Macro-Microflow Refinement
Flow Automation
- Automated Macroflow Steps
- Automated Microflow Steps
Service Invocation
- Synchronous Service Invocation
- Asynchronous Service Invocation
- Fire and Forget Invocation
- One Reply Asynchronous Invocation
- Multiple Reply Asynchronous Invocation
- Process Control Data Driven Invocation
Component and Connector
- Callback
- Indirection
- Grouping
- Layering
- Aggregation Cascade
- Composition Cascade
- Shield
- Typing
- Virtual Connector

thanks

Find more posts tagged with

Comments

trademak

Hi,

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.

Best regards,

santa1

Hi,

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.

This might get you in the picture:

http://www.infosys.tuwien.ac.at/Staff/sd/papers/Shark%202008%20U.Zdun.pdf

Best Regards

meyerd

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.

Read http://docs.jboss.com/jbpm/pvm/article/. It draws a clear line between what a process engine is responsible for and what not.