Design business process platform based on WF _ multiple statuses of the same process

Design business process platform based on WF _ multiple statuses of the same process

 

 

A status chart is a design chart that is frequently used in workflow design,

 

When talking to me about the status chart, many process designers often say that they are familiar with the legends of the status chart in UML, but every time they draw a status chart of the business process, I always feel that the painting is not easy.

 

In fact, when drawing a state chart of a business process, many people make a mistake and want to use a state chart to show the state of the process.

 

In practical application, the same process uses multiple sets of States. In the same process and different participants, the states of the process are different.

 

Here is an example:

 

Let's talk about the scenario:

 

Company A (A commercial company) should hold A commercial activity, which should be proposed by the [marketing department], approved by the [management], planned by the [Planning Department], and implemented by the [Implementation Department ].

 

 

Let's take a look at the panoramic process.

 

 

This is the most common process

 

This process is an official process involving multiple departments and multiple functions.

This process shows

1. Business upgrade: [intention]-> [requirement]-> [solution]-> [Implementation Plan]-> [implementation]
2. External functions,
3. Rotate and hand over the new business in the lead department [marketing department]

And other standard features.

 

This is a common model in traditional enterprise management. This business process model is very similar to the Business Process in flat management mode. the biggest feature is that the table is not transparent (I will introduce it in later articles)

 

Of course, opacity does not mean that it is not good. In many cases, the business needs to be closed out within a certain range for confidentiality and other reasons. Therefore, the Process status varies with participants.

 

In this example, participants are:

• Marketing Department. Business personnel
• Marketing Department. Supervisor
• Management. Business Manager
• Planning Department. Planners
• Planning Department. Customer Service staff
• Planning Department. Supervisor
• Implementation Department Head
• Implementation Department. Scheduler
• Implementation Department. Implementers

 

The Process status in the eyes of each participant is as follows:

 

Marketing Department. Business personnel
Marketing Department. Supervisor
Management. Business Manager
Planning Department. Planners	Omitted
Planning Department. Customer Service staff	Omitted
Planning Department. Supervisor	Omitted
Implementation Department Head	Omitted
Implementation Department. Scheduler	Omitted
Implementation Department. Implementers	Omitted

 

From the preceding state chart, we can see that the status of the same process varies with the participants in the implementation process.

This is what I am talking about in the same process: multiple groups of States.

 

Each participant has only one-sided understanding of the process. If the process maker builds the process based on a participant's description of the process, problems may occur.

"I don't know the true colors of the mountains, but I am here ."

 

This is just an overview article.

 

How to set different statuses for different participants, stakeholders, managers, supervisors, and reviewers will be explained in [process transparency]

 

I will also introduce the principles of transparency in the following processes in future articles.

• Upstream Process
• Process
• Parallel Flow
• Public-to-public process
• Private-to-public process
• Public-to-private process
• Flat management process
• Procedures for various divisions
• Loose collaborative process
• Process of Lead Association

 

 

In this example, the status of [completing correction] and [returning redo] between nodes is not involved,

[Designing a business process platform based on WF _ special issues and troubles], [Designing a business process platform based on WF _ businesses cannot be rolled back], two articles will talk about this part.

 

In addition, in my examples, multi-state process design support has been provided, but the web interface of the WF client does not implement graphical display. I will add