Process Templates

[sanjacornelius]

Issue & Reproduction Steps

This PR includes a ‘create from template’ feature for new processes, where users can select from a list of available templates to use as a base to work from in developing their new process.

Current Functionality:

• Ability to publish a process as a template
• View published templates in the Templates tab on the Process Designer page
• Search for templates in the Templates tab
• Configuration of process templates with a name, description, and category
• Export and Import process templates
• Set template permissions
• View, search, and select a process template from the Create Process button

Known Issues:

• When publishing a template with a name that already exists, the 'Update' button produces an error.
• When publishing a template and selecting 'Save process modal only', the process assets are still imported.
• When publishing a template and the selected process to be converted is blank, an 'SVG not found' error is displayed when viewing the template in the 'Create Process' modal.
• When creating a process from a template and selecting 'Cancel' after selecting 'Use Template', the Create Process modal is not pre-filled with the template information upon selecting a template again.

Missing Features:

• Edit Process Template in Modeler
• View Process Template Documentation via the Process Documenter package
• Deleting a Process Template
• When creating a process from a template, the process defaults to the 'uncategorized' category and does not inherit the template's category.

How to Test

Describe how to test that this solution works.

Related Tickets & Packages

- Process Templates PRD

• Ticket FOUR-7375

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.
  .