-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
When a user task references a Camunda Form through one of the new form Camunda Form Ref bindings, Tasklist should be able to display the referenced form.
Tasklist performs a query against /task/id/form to check the formKey. If the formKey references a deployed form, the form is loaded via deployment query.
Since Camunda Forms using the new bindings do not have a formKey but instead provide a camundaFormRef object, Tasklist should be adjusted to support those bindings as well by treating Camunda Forms with formKey and camundaFormRef equally (i.e., perform the same request to retrieve the form).
Example payload of /task/id/form with a Camunda Form using the new binding:
{
"key":null,
"camundaFormRef":{
"key":"myform",
"binding":"deployment",
"version":null
},
"contextPath":null
}
camundaFormRef is null when the new bindings are not used. camundaFormRef.key should never be null (if new bindings are used) as it is required by the engine. camundaFormRef.binding can have the following values: deployment, latest, version. camundaFormRef.version is only set if camundaFormRef.binding is version, in which case camundaFormRef.version is mandatory and should not be null.
This is the controller panel for Smart Panels app
- is related to
-
CAM-13870 In Cockpit, on the deployment page, I can see the version number of .form files
-
- Open
-
- links to
