-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Zeebe's user task forms #88
Comments
@saig0 Hi, will you please guide me, where to get "userTaskForm"? Now I can get "userTaskForm_id" from "customHeaders" by "io.camunda.zeebe:formKey". While in orig serverTask path, the "taskform" or "formFields" 's key and value are all lay on "customHeaders", and can handle one time by read job meta info. |
"But it order to read the form, we need to import the process record. The form is stored in the process extension zeebe:userTaskForm." I will check this path, thx. |
Custom form logic can be associated with the userTaskForm_id, and the corresponding permissions can be verified, but can not be stored in the userTaskForm |
A similar feature was implemented in the Zeebe-Play project. A contributor could adopt the relevant changes from the following PRs: |
Since Zeebe 1.0.0, user tasks and task forms are supported: https://docs.camunda.io/docs/reference/bpmn-processes/user-tasks/user-tasks#user-task-forms
The task forms are a new part of the Camunda stack and can be modeled directly in the modeler: https://docs.camunda.io/docs/product-manuals/tasklist/userguide/camunda-forms
Replace the previous task forms and form fields with the official Camunda forms. The form viewer can be integrated as described here: https://github.com/bpmn-io/form-js/tree/master/packages/form-js-viewer
The text was updated successfully, but these errors were encountered: