- Drop node 12 support
- fix(types): add missing
moddleContext
option
- Bump
[email protected]
with support for bound non-interrupting repeating timeCycle
- Engine is prototyped, can still be invoked without new
- Bump
[email protected]
with support for bpmn:CallActivity (#97) - Bump
[email protected]
- fix for removing wrong listener on error by @allain
- fix: set the correct
Logger
type inBpmnEngineOptions
by @leon19
- Slimmer state from
bpmn-elements@6
. In most cases it should be safe to update, unless you inspect the broker states for some reason
- Prettify and actualize ts types
Update package.json to reflect what was stated in v12.0.3.
- And add tests for issue #142
- Bump
[email protected]
with support for bpmn:Property (#139) - Bump
smqp@5
- Bump
[email protected]
- Bump
smqp@4
- Bump
[email protected]
with "support" for bpmn:Group and Category. Kinda bugfix for the engine to be honest.
- Something about loop characteristics in
[email protected]
. Not sure that a major was necessary, but semver is semver. In most cases it should be safe to update, unless you have used parallel loops without collection or cardinality (∞)?
- Bump
[email protected]
- Add badge
- Patch
[email protected]
- Patch
[email protected]
- Expose execution api on property
engine.execution
since it is basically the same as when returned on events
- Bump
[email protected]
- Add tests for issue #125
- Engine.resume returns Promise that resolves BpmnEngineExecutionApi by @mdwheele
- Pick recovered definition source from passed sources if not present on definition state
- Bump
[email protected]
to version with timer tracking - Add the above timers, i.e.
setTimeout
andclearTimeout
, to inline script context - Clear all timers when execution is stopped
[email protected]
bpmn-moddle
patch
- Major bump of
bpmn-elements@4
. No apparent breaking change to engine except that gives more power to a custom script handler
All conditional flows from bpmn-elements@3
.
- Outbound sequence flow with script condition requires
next(err, result)
to be called where result decides if it should be taken or discarded
- Outbound sequence flow conditions are evaluated for all activities, as well as default flow
- Process now also have
cancelActivity
function for facilitation
Type definitions courtesy of @saeedtabrizi.
- Some type fix and add engine broker types
- Add type definition to package.json
- Bump bpmn-elements to 2.1, adding support for Transaction and CancelEventDefinition see change log
Untangle issue #105 which resulted in refactoring outbound sequence flow handling.
- Bump bpmn-elements from 1.6 to 2, see change log
- No more
flow.pre-flight
events from sequence flows, not sure that anyone used them, but still - Activities now publish (or emit)
activity.leave
when all outbound flows have been taken/discarded
- Bump bpmn-elements from 1.2 to 1.6, see change log
- Support adding definition source with
addSource
function
- Bump bpmn-elements to version with ability to signal waiting start event from definition
- Bump bpmn-elements to version with shake activity functionality
- Bump [email protected] with scripts and timers
- Add engine option
sourceContext
to hold pre-serialized context
- Add signal function to engine execution api
- Bump bpmn-elements to v1.0.0 with some breaking changes regarding MessageEventDefinition and SignalEventDefinition
- Bump bpmn-moddle, bpmn-elements, and smqp to latest
- Add typescript declaration file (Saeed Tabrizi)
- Bump [email protected]
- Bump [email protected] with new ability to use process extensions
- Bump [email protected] to support compensation
- Bump [email protected] that expose sequence flow name
- Bump [email protected] and moddle-context-serializer to support StandardLoopCharacteristics
- Bump [email protected] to support LinkEventDefinition
- Bump bpmn-elements to v0.6.0 with refactored MessageEventDefinition, ReceiveTask, and some bug fixes from @TallaInc
- Recover takes optional options that completely overrides environment and passes it along to the recovered definitions
- Bump bpmn-elements to v0.5.0
Bump bpmn-elements and bpmn-moddle (which now has a node dist :).
- Implementation of ErrorEventDefinition is now closer to the BPMN 2.0 spec
- Start sub-process' sub-process if sub-process throws an error
- Expose the name of the element that emitted event
- Bump bpmn-elements and serializer and thereby add support for ConditionalEventDefinition
- Expose humanPerformer and potentialOwner
Use bpmn-elements to execute elements.
Behind the scenes the entire definition execution is replaced with bpmn-elements
- Node version >= 10 is required
- Events are not emitted with name of the activity, i.e. no more
enter-task_a8dje7
emits - Most events are emitted with the type of element as prefix, e.g.
activity.start
, one exception iswait
wich is still emitted aswait
getPendingActivities()
is renamed togetPostponed()
- Change license to MIT
- Engine
execute
callback is called when execution completes - Node version >= 8.9 is supported
SendTask
message requires outputParallelGateway
emitsstart
on first taken inbound, i.e. discarded inbound are just registered- Extensions have been moved to separate project bpmn-engine-extensions
- Support for parallell task loop
- Parallel gateway
getState()
returns pending inbound and/or pending outbound, so old states are not supported
- Add support for Manual task
- Support camunda input/output for Exclusive Gateways, input is passed to conditional flows
- Support camunda errorCodeVariable and errorMessageVariable for Error Events
- Add support for SendTask and ReceiveTask
- A start event with form key will also emit wait
- The
Engine
now handles definitions instead of processes, hence:execute(callback)
returns executed definition in callback instead of processgetState()
returns executing definition instead of processes
- Engine
getState()
andresume(state)
does no longer return or need the actual definition source. They work with moddle contexts. Transformer
is now calledtransformer
since it is not called withnew
- Engine instance
resume()
is now a "static" function on engine, i.e.Engine.resume
Definition
is exposed and can be executed with moddle context and options, see documentationvalidation
is exposed and harbours functions for validating moddle context and execute options- Support camunda input forms for user task and start event
- Output from tasks with defined
camunda:inputOutput
now updates context variables. The previous behavior was to save result tovariables.taskInput
. That will still happen if no output is defined.
- Support service connector (#4)
- Support map and list input/output types from modeller (#5)