You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Template Editor writes into a new "TemplateProcess" table, same columns as in Process table (a new table is faster for search and managing instead of a new column in the Process table)
add a column "basedOnTemplateId" and "basedOnTemplateVersion" in "Process" AND "TemplateProcess" tables referring to the id of the Template
add column "templateProcessId" in Version table and link the "TemplateProcess" table
Create View for Templates (normal list/icon view like in the Editor view)
Change "Create Process" modal: 1. add a string prop for the component that the modal uses to show what is created in the text title and input labels, e.g. "Create Process" or "Create Template". Default: "Process". 2. use this modal for creating Templates (prop = "Template") 3. Add an input field where you can select a Template which the new Process/Template is based on (yes, also Templates can be based on other Templates). Only Templates should be selectable, which have a defined Version
Add fields in the BPMN editors property panel about the "Based on Template: " (show Name not Id) and "Based on Template Version:"
add in the BPMN XML inside the definitions element as attributes: proceed:basedOnTemplateId="_5t...a4ht3"proceed:basedOnTemplateVersionId="_df89...ht43" like defined in our BPMN schema
implement Import and Export of Templates: there should be nothing different compared to import/export of normal processes. If exported, there should be no marker/attribute that the BPMN was a Template - it is just a normal BPMN process. The only difference: if imported inside the Template view of the MS, a process is stored internally as a template
check if everything else works like for the normal process editor
definitionselement as attributes:proceed:basedOnTemplateId="_5t...a4ht3"proceed:basedOnTemplateVersionId="_df89...ht43"like defined in our BPMN schema