Migrate to Zeebe 1.x

[saig0]

Currently, the project uses a Zeebe client 0.26.x. In order to support the new Zeebe/Camunda Cloud versions >= 1.0, we need to update the Zeebe client.

Similar projects are already migrated, for example, camunda-community-hub/zeebe-simple-monitor#250.

[tbfly]

Hello, I'm trying to dig this problem.
Now, in 1.x+, we need HazelcastService to read all jobrecord? While in 0.26 we have UserTaskJobHandler to add "taskForm" and "Variables".
Will you please, guide me where to start？@saig0
Now，I can read task/job info from ZeebeHazelcast, but I can't find a method to read "taskForm".
Do I need to check zeebe-simple-monitor path, use ZeebeImportService to get process/instance resource, then get "taskForm" to show?
Thx!

[tbfly]

I get some clues from: https://github.com/camunda-community-hub/zeebe-simple-tasklist/blob/master/src/test/resources/custom-task-form.html
and:
https://github.com/camunda-community-hub/zeebe-simple-tasklist/blob/master/src/test/java/io/zeebe/tasklist/Demo.java

Thx.

[saig0]

@tbfly awesome that you want to contribute 🚀

Now, in 1.x+, we need HazelcastService to read all jobrecord?

No. We can still use the job worker to read the tasks. The formKey is stored as io.camunda.zeebe:formKey in the task headers.

But it order to read the form, we need to import the process record. The form is stored in the process extension zeebe:userTaskForm.

[tbfly]

@tbfly awesome that you want to contribute 🚀

Now, in 1.x+, we need HazelcastService to read all jobrecord?

No. We can still use the job worker to read the tasks. The formKey is stored as io.camunda.zeebe:formKey in the task headers.

@saig0 Thx, I will check this path. Now, I just use HazelcastService to load the exist taskinfo in jobrecord.
By now, #87
this issue: 87 is sloved.

But it order to read the form, we need to import the process record. The form is stored in the process extension zeebe:userTaskForm.

Exactly! I found this way too. "UserTaskJobHandler" still useful for import userService job, "taskForm" and "formFields" info.

I just found the Demo.java code useful to test for load taskForm and formFields.
#90 (comment)

[tbfly]

@tbfly awesome that you want to contribute 🚀

Now, in 1.x+, we need HazelcastService to read all jobrecord?

No. We can still use the job worker to read the tasks. The formKey is stored as io.camunda.zeebe:formKey in the task headers.

@saig0 Thx, I will check this path. Now, I just use HazelcastService to load the exist taskinfo in jobrecord. By now, #87 this issue: 87 is sloved.

But it order to read the form, we need to import the process record. The form is stored in the process extension zeebe:userTaskForm.

Exactly! I found this way too. "UserTaskJobHandler" still useful for import userService job, "taskForm" and "formFields" info.

I just found the Demo.java code useful to test for load taskForm and formFields. #90 (comment)

#88

Some update by using [io.camunda.zeebe:formKey].

[saig0]

Done by #91 🚀