Camunda (1): Camunda Platform and Modeler create workflow

Camunda (1): Camunda Platform and Modeler create workflow

Foreword: Because the company has a project that requires the use of a workflow engine, it inspected various workflow engines on the market, compared their advantages and disadvantages, and finally chose the Camunda workflow engine. I didn't know much about the Camunda workflow engine before, so I recorded the process of learning the Camunda workflow engine and integrating the use of the Camunda workflow engine in the springboot project. This article does not involve any code, but simply creates a workflow from the tools officially provided by Camunda, observes the flow of the process, and makes a simple preliminary understanding of the flow review of the workflow.

insert image description here

1. Camunda Platform and Modeler

1.1 Download Camunda Platform and Modeler

Camunda Platform: At present, the official website provides a free trial of Camunda Platform 8 SaaS, and the only way to download and install Camunda Platform 8 Self-Managed is docker. Camunda Platform Run is a pre-packaged distribution of Camunda Platform, including Camunda webapps (Cockpit, Tasklist, Admin), which has the features of our local test, so here we choose to download Camunda Platform Run.

Camunda Platform Run download link: https://downloads.camunda.cloud/release/camunda-bpm/run/

Camunda Modeler download address: https://camunda.com/download/modeler/

1.2 Unzip and start Platform Run

To start, double-click start.bat (Windows system), (Linux or Mac) click start.sh to start
insert image description here

After successful startup, visit Platform Run:
http://localhost:8080/camunda/app/welcome/default/#!/login

Camunda's default account password is demo / demo, which is configured in the configuration file.

Entering the Camunda management platform provides a web management interface. The main functions of the management interface include:

Cockpit - manage process process and process instances process instances
Tasklist - manage specific tasks in the process process (navigate to specific tasks, provide form input, repair process instances, etc.)
Admin - manage users, organization groups, authorizations

Enter the Admin module to create a user, which is used for the review of the workflow created later

insert image description here

insert image description here

insert image description here

  1. 3 Unzip and start Platform Modeler, and create a workflow test.

insert image description here

insert image description here
insert image description here

After completing the settings of each node, the workflow has a History cleanup attribute that is required

P90D: Indicates that historical data will be cleaned up within 90 days

In addition, select the corresponding platform version in the lower left corner to deploy the workflow. One thing to note here is that I didn’t pay attention to version deployment before. When running workflow tasks on the platform, I found that the user of the corresponding workflow audit node has no agency tasks and cannot audit the flow. So it is recommended to choose to install the same platform version yourself.

insert image description here

1.4 Check whether the deployment is successful

Here, because I have deployed other workflows before, here is 2. If no workflow has been deployed before, then it will be 1 after the new workflow is successfully deployed.

insert image description here

2. Camunda Platform runs the created workflow

2.1 Start the workflow process

The demo user enters the Tasklist module of the Platform to start the process.

insert image description here

insert image description here

Create a name for the process, then add some variables to say who asked for leave to start the process.

insert image description here

2.2 Go to the corresponding user for review

Because the user of the first audit node set before this process is demo, we can see this audit pending under the demo user
insert image description here

Before the demo user is audited, the user to be audited by the next node is user1, and then log in to user1 for auditing. And so on until all nodes are audited

insert image description here

Guess you like

Origin blog.csdn.net/qq798867485/article/details/131439688