Decision Driven Business Processes Using Red Hat BPM Suite 6.4
Business Processes as defined by the BPMN 2.0 specifications are usually structured and rigid. This is great for well-defined end-state business logic. In another words things don't change much. In the real world business requirements change often and many times drastically. Making such changes in rigid business processes can be both risky and time consuming. The Red Hat BPM Suite 6.x allows for top-level ad-hoc processes that can be driven by signals. This gives us a flexibility rigid process do not. In this article I will outline a pattern using ad-hoc processes that can be driven by business decisions encoded in business rules. This flexibility allows for quick changes without modifying the business processes. Example Business Case To show the decision driven business process pattern we will use a simple business case of ordering supplies through the company procurement department. We have four different actors: the employee (requester) who makes the supplies reques
