Modeling Objects

Model your Process in an easy-to-use graphical BPMN 2.0 compliant editor.


ProcessMaker Platform follows Business Process Modeling Notation (BPMN) 2.0 specification. However, it does not describe the BPMN 2.0 principles on which Process modeling is based. For more information about BPMN 2.0 see the BPMN specification.

Designing Process models using the BPMN 2.0 specification involves several guidelines and best practices:

  • Understand BPMN elements: Familiarize yourself with the basic BPMN elements such as Tasks, Gateways, Events, and Flow indicators, as well as more advanced constructs like Sub Processes and Pools.

  • Start with high-level views: Begin by creating a high-level view of your Process. Use Pools to represent different participants or departments involved in the Process, and Lanes to represent roles or responsibilities within each Pool.

  • Use descriptive names: Assign clear and descriptive names to Tasks, Events, Gateways, and other elements to ensure the Process's intent is easily understood.

  • Consistent styling: Maintain a consistent style throughout your Process models, including shapes, colors, and annotations.

  • Embrace Simplicity: Keep your Process models as simple and straightforward as possible. Avoid unnecessary complexity that might confuse stakeholders.

  • Flow direction: Maintain the correct flow direction (left to right) for the Process. Sequence Flows should connect activities in a logical order.

  • Message flow: When modeling interactions between Pools, use Message Flows to show the exchange of messages between participants.

  • Use Gateways appropriately: Choose the right type of Gateway (Exclusive, Inclusive, Parallel, or Event-Based) based on the decision logic required in your Process.

    • Parallel vs. Inclusive Gateways: Understand the difference between Parallel and Inclusive Gateways: use Parallel Gateways when multiple Tasks should execute simultaneously, and use Inclusive Gateways when multiple Tasks could be triggered.

    • Event-Based Gateways: Use Event-Based Gateways to represent conditional branching based on events rather than explicit decisions.

  • Boundary events: Apply Boundary-type events to Tasks and other element types to represent interrupting events that affect that Task's execution.

  • Sub Processes: Use Sub Processes to encapsulate related activities, improving the overall clarity of the Process. Decide between embedded and reusable Sub Processes based on reusability.

  • Artifacts: Use artifacts like Data Objects and Annotations to provide additional information about the Process or its elements.

  • Data Associations: Clearly define Data Associations to show input/output relationships between Tasks and Data Objects.

  • Validation and testing: Regularly validate your Process models to ensure they accurately represent the intended business logic. Test them with stakeholders to gather feedback.

  • Collaboration: Involve relevant stakeholders when designing Process models to ensure accuracy and alignment with business requirements.

  • Version control: Implement version control mechanisms to track changes and iterations of your Process models.

  • Documentation: Create documentation that explains the purpose, logic, and flow of the Process model. This aids in understanding and maintaining the model.

  • Training: Provide training to individuals who will be working with or contributing to the Process models. This promotes consistent modeling practices.

  • Continuous improvement: Regularly review and refine your Process models based on feedback, changing requirements, and performance metrics.

Process Modeling Object Descriptions

Edit Process Model Information

Configure Task Objects

Last updated

© Copyright 2000-2024 ProcessMaker Inc. All rights reserved.