This is the overview explanation of the process project. Explain the purpose of the project.
Version | Build | Date (yyyy-mm-dd) |
---|---|---|
Camunda 7.7 | Tomcat | 2017-06-07 |
Person | Contact Info | Responsibility |
---|---|---|
John Dishman | john@example.com 555-555-5555 |
Project Manager |
Jane Horseshoe | hjane@example.com | Developer |
Bob Umbrella | Business Analyst |
Explain what is the purpose of each process and process related file in the project.
Click to see file details:
Explanation of how to deploy this specific project goes here.
For further deployment templates and options see: Deployment Documentation
Method | Trigger |
---|---|
Jenkins | On creation of a Production Release. Deployed to production server |
Jenkins | On commit to branch with pattern build/development . Deployed to development server |
Store details about the releases of your project in the Change Log
Explanation of other details about the project that may not have been included in the Overview.
Examples:
/docs
folder.See the following for additional support documentation related to building and managing process projects:
A list of terms used by this project.
Term | Acronym | Definition |
---|---|---|
Requestor | ||
Initiator | Another term used for requestor. | |
Business Unit | ||
Manager | ||
Citizen | ||
Permit | ||
Purchase Order | PO | The first official offer issued by a buyer to a seller, indicating types, quantities, and agreed prices for products or services. |
Legacy System Archer D27 | LSAD27 | An example of a legacy system and a acronym. |