Skip to content
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

Template Processes View #456

Open
5 of 12 tasks
iaktern opened this issue Jan 28, 2025 · 0 comments
Open
5 of 12 tasks

Template Processes View #456

iaktern opened this issue Jan 28, 2025 · 0 comments

Comments

@iaktern
Copy link
Contributor

iaktern commented Jan 28, 2025

  • 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"
  • check if everything else works like for the normal process editor

From Lucas- TODOs:

  • Currently, the handling of templates and processes in the DB is not ideal, because for the requested process/template both DB tables are searched through until the requested process/template is found. It should be implemented a mechanism to known in which table to search for the requested resource.
  • Import of Templates is not implemented
  • Currently, Templates can be used even without a published version. This should be changed to only allow to use versioned templates
  • Refactoring
@iaktern iaktern moved this to In Progress in PROCEED MS New Jan 28, 2025
@LucasMGo LucasMGo linked a pull request Jan 31, 2025 that will close this issue
@iaktern iaktern moved this from In Progress to Todos: Fine-Grained in PROCEED MS New Feb 3, 2025
@OhKai OhKai removed a link to a pull request Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todos: Fine-Grained
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant