Details
-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
User Story (Required on creation):
When using the new form builder in the modeler, the linking between process and form happens with the form key, defined as embedded:form:<resource name>. This always references a form within the same deployment. This prevents users from deploying a new version of the form independent of the process. It should therefore be possible to reference forms in other deployments.
Functional Requirements (Required before implementation):
- For a form key on a user task, it is possible to reference the latest deployed version of a form with the specified resource name
- It is also still possible to reference a form from the same deployment
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (Optional):
- Implementation directions
- Forms become first-class API citizens (e.g. with dedicated database table, and query API, etc.), similar to process and decision definitions
- No dedicated form entity, but versioning is implemented for deployment resources