Wrap try-catch block around zbc.deployWorkflow and trigger node.error

more info: https://nodered.org/docs/creating-nodes/status

Depends on #26 and #27

In zeebe-node the oAuth token cache directory is now configurable via the ZBClient constructor parameter oAuth.cacheDir. This should be added to /src/nodes/zeebe.js

see https://github.com/creditsenseau/zeebe-client-node-js/releases/tag/v0.22.0-alpha.4

It should be possible to configure a worker (i.e. maxActiveJobs or imeout). See https://www.npmjs.com/package/zeebe-node#create-a-task-worker for more info.

See https://github.com/creditsenseau/zeebe-client-node-js#start-a-workflow-instance-of-a-specific-version-of-a-workflow-definition

I think there are 3 options to make that work:

• extend "create wfi" node to output the outcome of the workflow when it has finished
• create an additional "create wfi w/ result" node which only outputs when the workflow has finished
• create a "workflow completed" node, which outputs each time any workflow finishes

More info: https://zeebe.io/blog/2019/10/0.22-awaitable-outcomes/

Hi there,

I just tried to implement a zeebe worker over node-red:

• added a worker node to my flow (listening to "echo" tasks)
• connected the output to a debug node
• connected the output to a complete node

The output of the debug node:

{"payload":{"job":{"key":"2251799813769806","type":"echo","workflowInstanceKey":"2251799813769794","bpmnProcessId":"ECHO","workflowDefinitionVersion":1,"workflowKey":"2251799813728423","elementId":"ServiceTask_0phglip","elementInstanceKey":"2251799813769803","customHeaders":{},"worker":"08adfae5-82b8-4e27-bd53-325282bc9958","retries":3,"deadline":"1569336118974","variables":{}},"complete":{}},"_msgid":"cbe132e.57828d"}

The complete node keep saying: "complete is not a function"

So I tried several tricks to set complete to a function but I'm failing. Can someone explain how to set complete to a function so the job is successfully completed in zeebe ? I just want to output variables at first.

Perhaps it can be helpful to document some examples in the README ?

Dockerfile:
`FROM nodered/node-red

COPY package.json .
RUN npm install --only=production

COPY settings.js /data/settings.js
COPY flows.json /data/flows.json

CMD ["npm", "start"]`

docker-compose:
`version: "3.7"

services:
node-red:
container_name: node-red
build: .
environment:
- TZ=America/Sao_Paulo
ports:
- "1880:1880"
networks:
- operate_zeebe_network
external_links:
- zeebe:zeebe
volumes:
- node-red-data
volumes:
node-red-data:

networks:
operate_zeebe_network:
external: true`

package.json dependences:
"dependencies": { "node-red": "1.0.6", "node-red-contrib-zeebe": "0.6.3", "node-red-contrib-aws": "0.5.0", "node-red-dashboard": "~2.22.1" },

On exec 'docker-compose up --build'
Output:
node-red | 30 May 13:05:56 - [info] Node-RED version: v1.0.6 node-red | 30 May 13:05:56 - [info] Node.js version: v10.20.1 node-red | 30 May 13:05:56 - [info] Linux 4.14.177-107.254.amzn1.x86_64 x64 LE node-red | 30 May 13:05:56 - [info] Loading palette nodes node-red exited with code 0

Without node-red-contrib-zeebe, is successfull.

Tks,

Hi,

"add support for complete.error" in 8663c8d commit not contain in 0.6.3 version ?

see here: https://www.npmjs.com/package/zeebe-node#deploy-a-workflow

we should ensure, this node works with Node-RED's storage nodes (file, ...).

Problem

One of two integration tests fails from time to time, due to the 25 seconds jest timeout. Presumably one test is completing tasks of the other tests, if they're executed in parallel.

Proposal

Either make sure to use a different task type or run them sequentially.

• onConnectionError is not properly passed to zbc.createWorker
• node.error is not called

Currently a zeebe config node connects to Zeebe, even if this config is not used by any other node (eg. worker node). It should connect only, if it is not in use.

The docker-compose file should bootstrap a dockerized development environment containing a Node-RED instance, a single node Zeebe broker and Operate.

• The Node-RED instance should come with pre-installed node-red-contrib-zeebe nodes pre-configured to point to the local Zeebe broker.

• Everything should be documented

Create a new node that gets the topology of a broker. See https://www.npmjs.com/package/zeebe-node#get-broker-topology

This node should output a json object, when triggered.