Business Rules Orchestration Scenarios Describe scenarios for integrating business rules within an orchestration. Common Orchestration Scenarios Instead of having to code and recode constantly changing business policies and logic within your complex business processes, you can incorporate a call to the Business Rule Engine and thus allow information workers to update the rules as needed. Overview You can integrate business rules into your orchestrations to support a variety of scenarios: You can use to determine whether another business process needs to be executed. For example, after successfully placing a customer order, you might want to call a second orchestration that handles the shipping of orders. You can use rules to evaluate business logic and to determine when a business process requires a variable delay. For example, you might set up a loop to check on the status of an item to see if the item is in stock. After initially checking the stock of an item that is not available, the rule delay would be one minute. The next time, the rule would wait five minutes before executing, the following time, the rule would wait 30 minutes before executing, and so on. You can use rules to determine the execution path for a business process, basing the determination on the results of the rule execution. For example, if the customer submitting the purchase order does not exist in the database, you could route the document to another business process to add the customer to the database before continuing to process the purchase order.
Business Rules Orchestration Scenarios Describe scenarios for integrating business rules within an orchestration. Common Orchestration Scenarios Instead of having to code and recode constantly changing business policies and logic within your complex business processes, you can incorporate a call to the Business Rule Engine and thus allow information workers to update the rules as needed. Overview You can integrate business rules into your orchestrations to support a variety of scenarios: You can use to determine whether another business process needs to be executed. For example, after successfully placing a customer order, you might want to call a second orchestration that handles the shipping of orders. You can use rules to evaluate business logic and to determine when a business process requires a variable delay. For example, you might set up a loop to check on the status of an item to see if the item is in stock. After initially checking the stock of an item that is not available, the rule delay would be one minute. The next time, the rule would wait five minutes before executing, the following time, the rule would wait 30 minutes before executing, and so on. You can use rules to determine the execution path for a business process, basing the determination on the results of the rule execution. For example, if the customer submitting the purchase order does not exist in the database, you could route the document to another business process to add the customer to the database before continuing to process the purchase order.
BT10D_11.docx