When you are modeling business processes with business process diagrams, you may find that although the business processes are different and yield different goals, many of them are indeed sharing the same set of workflow. For example, both the process of ordering and returning goods share the same packaging and delivery processes. These common workflow share the same behaviors and activities, so it is wise to “draw once and re-use everywhere”, not just to save time, but to ensure the consistency of business process by keeping one and only one copy of unique workflow. Business Process Model and Notation (BPMN) supports grouping related process flow to sub-process. With BPMN sub-process, you can easily re-use the common process flows in different business processes by incorporating the sub-process shape, which contains the common workflows, into those business process diagrams.
Complex workflow design makes it difficult for readers to get into the process flow. If flow elements in process diagram can be categorized into meaningful activity groups, you may want to group them as sub-processes and show their detail at lower-level process diagrams. Besides, by moving detailed flow to sub-diagram also helps maintain a consistent leveling of context a business process diagram try to present. In this article, you will see how to group several BPMN tasks into a sub-process. To help you understand the principle easier, a simple example will be used.
In business improvement, business users’ feedback is important to help improve the quality of process design. That’s why analysts have to meet with the users from time to time to present the latest process design and ask them for feedback. Unfortunately, traditional ways of presentation, such as slideshow failed to work well for presenting process designs. In this article, we will see what the problems are and how Windows tablets can make business process presentation more effective.
When one shape is nested inside another, such as sub-process, its content (shapes) inside would show along with what’s outside in diagram at the same time. For example, if a sub-process is not composed of any other sub-processes, it will appear in business process diagram, with the shapes (e.g. tasks) that make it up inside itself. However, the viewing works up to one level of nesting only by default.