BPMN execution using Camunda 8.8 (self-managed)

Hi,

I built several case studies using Camunda 8.8 (self-managed) because I felt that the online doc. isn’t sometimes up-to-date with careless code errors, for example: TypeScript SDK | Camunda 8 Docs

So, please find ready-to-use fully-packaged downloadable (case studies) projects (BPMN/DMN files + appropriate config. & code files) for your users:

https://livebpmn.com/Camunda/BCMS_Camunda_8.html [Keywords: BPMN, Collaboration Diagram, Camunda 8, TypeScript, Node.js, Message Event, Signal Event, Ad hoc subprocess, Job worker, Execution listener]
https://livebpmn.com/Camunda/Barcode_Camunda_8.html [Keywords: BPMN, DMN, Camunda 8, TypeScript, Node.js, Business rule task, Service Task Task, REST outbound connector, Error Event, Escalation Event, Job worker, Execution listener]
https://livebpmn.com/Camunda/Custom_connector_Camunda_8.html [Keywords: BPMN, Camunda 8, Java, Spring Boot, Custom connector, Script connector, SQL connector]
https://livebpmn.com/Camunda/Service_activator_Camunda_8.html [Keywords: BPMN, Camunda 8, FEEL, Java, Spring Boot, Call Activity, Error Event, Escalation Event, Event subprocess, REST outbound connector, Connector secret, Job worker, Execution listener]
In French only:
https://livebpmn.com/Camunda/Clinique_Camunda_8.html [Keywords: BPMN, Collaboration Diagram, Camunda 8, FEEL, Java, Spring Boot, Message Event, Timer Event, User Task, Job worker, Execution listener]

Don’t hesitate to provide comments, even questions!
Beforehand, BPMN files may in particular be (pre-)executed through LiveBPMN.com (new 1.0.9 ver.).

Regards.

1 Like

Hi @Bab64 - could you share a bit more about what errors are on the Typescript SDK page? I took quick look but didn’t see anything obvious. I’d love to get the errors corrected if there are any!

Hi Nathan. For example, at the beginning, const clientFactory = new Camunda8();. Below, the next line is const camunda = **camunda**.getOrchestrationClusterApiClient();.
Where camunda var. in bold comes from? It’s totally unclear… Is the correction const camunda = **clientFactory**.getOrchestrationClusterApiClient();? Maybe I’m wrong, but anyway reader has great difficulty to understand…
Some lines below a zeebe var. appears from nowhere in the code? Again, it hard to follow the tutorial. Sum up: trying to reproduce the code in reader’s own environment isn’t “fluid”. Regards.

1 Like

Hi @Bab64

Yes, I believe this ia a typo which needs to be corrected

const camunda = clientFactory.getOrchestrationClusterApiClient();

1 Like

Hi @Bab64 and @hassang - thanks for the feedback, I just submitted a PR to update these typos: docs(sdk): fix incorrect variable names in code examples by nloding · Pull Request #7503 · camunda/camunda-docs · GitHub