Skip to main content

Business Process Instance

About​

A business process instance in a Flux BPM is a specific execution of a business process. It represents the practical application of a business process model to a particular set of circumstances or data. Each instance is a unique enactment, carrying out the steps, decisions, and activities as outlined in the process model.

Business Process Instance

How a Business Process Instance is Created ?​

  • Triggering: A business process instance is created when a trigger occurs. This trigger can be manual (like a user starting the process), automated (based on system events), or time-based (initiated at a specific time or interval).

  • Initialization: Upon triggering, Flux BPM initializes a new instance. It assigns unique identifiers and allocates resources necessary for the process.

  • Context and Data: Each instance operates within its context, meaning it handles specific data or situations. For example, in a customer service process, each complaint or query would create a new instance, each dealing with different customer data and issues.

How They Differ from the Business Process​

  • Business Process: This is the blueprint or template that defines the sequence of activities, decision points, and paths that should be followed. It's a general framework outlining how a type of operation should be conducted.

  • Business Process Instance: This is the actual execution of that model in a real-world scenario. While the process model remains the same, each instance of it can vary based on the specific data, decisions made, and paths taken.

Example: Handling purchase orders​

Consider a process model for handling purchase orders. The process model lays out the steps for processing any purchase order. However, when a specific purchase order comes in, a process instance is created. This instance deals with the particular details of that order, such as the items purchased, the supplier details, and the payment terms.

Each new purchase order results in a new process instance, each following the same process model but dealing with different data and potentially making different decisions along the way.

Handling purchase orders

Receipt of Purchase Order: The process starts when a purchase order is received. This could be through an electronic system, email, or a physical document.

Verification of Order Details: The details of the order are verified. This includes checking the items ordered, quantities, prices, and supplier information.

Approval of Purchase Order: Depending on the company's policy, the purchase order may require approval from a manager or relevant authority. This step ensures that the order is necessary and within budget.

Confirmation with Supplier: Once approved, the order is confirmed with the supplier. This might involve sending a confirmation email or updating the status in a supplier management system.

Sending Goods: Once the supplier confirm, the goods are sent to the customer.

Receiving Goods: Upon delivery, the goods are received and checked against the purchase order to ensure that the correct items and quantities have been delivered.

Payment to Supplier: Once the goods are received, payment is made to the supplier according to the agreed-upon payment terms.