yape

Yape, like in "yet another process engine" or "your adaptable process engine" is a JavaScript BPMN workflow execution engine.

Goals

• [ ] Everything needs to be extensible. (Plugins)
• [ ] Vendor independent. (Understands various modeler's properties through plugins)
• [ ] Run in the browser and in node. (Browserify)
• [ ] Every variable value can also be a function which when executed returns 'the value' to use.
• [ ] Needs to be able to execute a BPMN 2.0 workflow. (BPMN conformance)
• [ ] Be safe.
• [ ] Try to be fast.
• [ ] Optionally spawn child processes (on node) or workers (in the browser) to optimize the execution of the flow. (not sure yet)

Install and use

First, install using npm or yarn

$ npm install @yape/engine --save

Then use yape in your Node.JS or in the browser.

To start a processInstance

const Yape = require('@yape/engine');

// Instantiate an engine
const yape = new Yape();

// Create a new process instance, specify a valid bpmn definition (returns a token)
const token = await yape
  .createProcessInstance({
    workflowDefinition: 'valid bpmn'
  }).catch(console.error);

// Tell the initial token to continue execution
await token.exec().catch(console.error);

To continue execution of a processInstance (by token)

// At some later point in time, in a different part of
// your app (e.g. when a User task is handled as complete by your own app)
const token = await yape.continueTokenInstance({
  tokenId: '<id of the token you want to execute>',
  // set the payload you want to merge into the existing payload
  payload: {}
});

await token.exec().catch(console.error);

Currently supported flow objects

Events:

• [x] Start
• [x] End
• [ ] IntermediateThrow
• [ ] MessageIntermediateThrow
• [ ] MessageIntermediateCatch
• [ ] MessageEnd
• [ ] TimerIntermediateCatch
• [ ] EscalationIntermediateThrow
• [ ] EscalationEnd
• [ ] ErrorEnd
• [ ] ConditionalIntermediateThrow
• [ ] LinkIntermediateCatch
• [ ] LinkIntermediateThrow
• [ ] CompensationIntermediateThrow
• [ ] CompensationEnd
• [ ] SignalIntermediateThrow
• [ ] SignalIntermediateCatch
• [ ] MessageStart
• [ ] TimerStart
• [ ] ConditionalStart
• [ ] SignalStart
• [ ] SignalEnd
• [ ] TerminateEnd

Activities:

• [x] Task
• [x] Service
• [x] User
• [x] Manual
• [ ] Send
• [ ] Receive
• [ ] BusinessRule
• [ ] Script

Gateways:

• [x] Exclusive
• [x] Inclusive
• [x] Parallel
• [ ] EventBased
• [ ] Complex

Other:

• [x] Swimlanes
• [ ] CallActivity
• [x] SubProcess
• [x] Loop
• [x] ParallelMultiInstance
• [ ] SequentialMultiInstance

Develop Yape

...

Develop plugins

Currently you can develop plugins for the following elements:

• Element
• FlowObject
• Activity
• UserTask
• ServiceTask

You create plugins by extending from one of the above classes and instantiating a class into the plugins array when creating the engine.

const Yape = require('@yape/engine');

class History extends Yape.Plugins.Element {
  constructor({ store = [] } = {}) {
    super();
    this.store = store;
  }

  onReady = definition => {
    this.store.push({ state: 'ready', elementId: definition.id });
  };
  onActive = definition => {
    this.store.push({ state: 'active', elementId: definition.id });
  };
  onComplete = definition => {
    this.store.push({ state: 'complete', elementId: definition.id });
  };
}

const history = new History();

const yape = new Yape({ plugins: [history] });

The above plugin will push executed elements' id's into an array, which serves as some kind of log.

Plugin methods

Every plugin can make use of three methods which will be called in order of execution, onReady, onActive and onComplete.

Method arguments

Methods receive the definition (as a moddle reference) of the current activity and the processInstance (including its .payload) as arguments. Read more about creating plugins here (... link missing...).