Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, a business process is created, and a cost of change value for the business process is defined. An executable process that is generated from the business process is executed, and a change request is received. It is determined whether the cost of change value is greater than a threshold value, and, when the cost of change value is not greater than the threshold value, the change request is initiated.

Abstract: A method of pausing a plurality of service-oriented application (SOA) instances may include receiving, from an instance of an SOA entering a pause state, an initiation message. The initiation message may include an exit criterion that identifies a business condition that must be satisfied before the instance of the SOA exits the pause state. The method may also include receiving a notification from an event producer, the notification comprising a status of a business event and determining whether the status of the business event satisfies the business condition of the exit criterion. The method may additionally include sending, in response to a determination that the status of the business event satisfies the business condition of the exit criterion, an indication to the instance of the SOA that the business condition has been satisfied such that the instance of the SOA can exit the pause state.

Abstract: A distributed order orchestration system provides a plurality of representations of a product, such as a sales-centric representation of a product and a fulfillment-centric representation of a product. The distributed order orchestration system captures an order associated with the product, and creates a sales order based on the sales-centric representation of the product. The distributed order orchestration system then transform the sales order into a fulfillment order, where the fulfillment order is based on the fulfillment-centric representation of the product. As part of the transformation, product information that is associated with the sales order is transformed into product information that is associated with the fulfillment order, using one or more product transformation rules.

Abstract: A generic wait service for facilitating the pausing of service-oriented applications. In one set of embodiments, the generic wait service receives, from a paused instance of an application, an initiation message comprising a set of key attributes and an exit criterion. The key attributes uniquely identify the paused instance, and the exit criterion identifies a condition that should be satisfied before the paused instance is allowed to proceed. The generic wait service then receives, from one or more event producers, notification messages comprising status information (e.g., statuses of business events) and information correlating the notification messages to particular instances. If a notification message is determined to be correlated to the paused instance, the generic wait service evaluates the exit criterion based on the status information included in the message. If the exit criterion is satisfied, the paused instance is notified of the status information and is allowed to proceed.

Abstract: A method of pausing a plurality of service-oriented application (SOA) instances may include receiving, from an instance of an SOA entering a pause state, an initiation message. The initiation message may include an exit criterion that identifies a business condition that must be satisfied before the instance of the SOA exits the pause state. The method may also include receiving a notification from an event producer, the notification comprising a status of a business event and determining whether the status of the business event satisfies the business condition of the exit criterion. The method may additionally include sending, in response to a determination that the status of the business event satisfies the business condition of the exit criterion, an indication to the instance of the SOA that the business condition has been satisfied such that the instance of the SOA can exit the pause state.

Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, a new order header object and an original order header object that share a source order number are selected, and one or more new order line objects based on the new order header object are also selected. One or more original order line objects based on the original order header object are selected and the one or more new order line objects and the one or more original order line objects are compared. Where a new order line object and an original order line object match, a reference identity of the new order line object is set to an identity of an original order line object.

Abstract: A distributed order orchestration system publishes one or more newly generated artifacts that are generated as a result of generating one or more extensible flex fields to a rule dictionary. The distributed order orchestration system then imports the one or more newly generated artifacts within the rule dictionary as one or more facts. The distributed order orchestration system then creates one or more rules for the rule dictionary that references the one or more facts.

Abstract: A distributed order orchestration system provides a plurality of representations of a product, such as a sales-centric representation of a product and a fulfillment-centric representation of a product. The distributed order orchestration system captures an order associated with the product, and creates a sales order based on the sales-centric representation of the product. The distributed order orchestration system then transform the sales order into a fulfillment order, where the fulfillment order is based on the fulfillment-centric representation of the product. As part of the transformation, product information that is associated with the sales order is transformed into product information that is associated with the fulfillment order, using one or more product transformation rules.

Abstract: A distributed order orchestration system publishes one or more newly generated artifacts that are generated as a result of generating one or more extensible flex fields to a rule dictionary. The distributed order orchestration system then imports the one or more newly generated artifacts within the rule dictionary as one or more facts. The distributed order orchestration system then creates one or more rules for the rule dictionary that references the one or more facts.

Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, a new order header object and an original order header object that share a source order number are selected, and one or more new order line objects based on the new order header object are also selected. One or more original order line objects based on the original order header object are selected and the one or more new order line objects and the one or more original order line objects are compared. Where a new order line object and an original order line object match, a reference identity of the new order line object is set to an identity of an original order line object.

Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, a business process is created, and a cost of change value for the business process is defined. An executable process that is generated from the business process is executed, and a change request is received. It is determined whether the cost of change value is greater than a threshold value, and, when the cost of change value is not greater than the threshold value, the change request is initiated.

Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, a task layer service pattern is created, and a task layer service is created from the task layer service pattern. The task layer service is assigned to a step of an executable process, and the step of the executable process is executed. The task layer service is executed in order to invoke a fulfillment service.

Abstract: A generic wait service for facilitating the pausing of service-oriented applications. In one set of embodiments, the generic wait service receives, from a paused instance of an application, an initiation message comprising a set of key attributes and an exit criterion. The key attributes uniquely identify the paused instance, and the exit criterion identifies a condition that should be satisfied before the paused instance is allowed to proceed. The generic wait service then receives, from one or more event producers, notification messages comprising status information (e.g., statuses of business events) and information correlating the notification messages to particular instances. If a notification message is determined to be correlated to the paused instance, the generic wait service evaluates the exit criterion based on the status information included in the message. If the exit criterion is satisfied, the paused instance is notified of the status information and is allowed to proceed.