Scenarios allow business users to define the set of actions to be performed when certain events or conditions occur. A detailed discussion of how scenarios are created and used can be found in the Personalization Guide for Business Users.
The fulfillment process uses the scenario engine to provide features including e-mail notifications to customers. These e-mails can indicate that a shipping group has shipped, an item was backordered/preordered or whether the order is complete.
The scenario engine listens for the three different classes of messages described in the Order Fulfillment Events section. The default Core Commerce implementation uses several of these messages as the events that trigger e-mail.
The following list describes the Fulfillment and ReceiveOrder scenarios included with Core Commerce. These scenarios are located in the Scenarios section of the ATG Control Center (ACC) in the DCS folder. For a description of the events, see the previous section. By default, this scenario is disabled. Enable this scenario using the ACC.
Fulfillment scenario:
OrderFinished: When anOrderModifiedevent with asubTypeofOrderFinishedis received, send an e-mail to the owner of the order (the Profile that is included in the message). The e-mail uses the e-mail template found atdynamo/commerce/en/email_templates/jsp/OrderFinished.jsp. It notifies the customer that their order has shipped and payment has been made.ShippingGroupShipped: When anShippingGroupModifiedevent with asubTypeofShippingGroupShippedis received, send an e-mail to the owner of the order. The e-mail uses the e-mail template found atdynamo/commerce/en/email_templates/jsp/ShippingGroupShipped.jsp. It notifies the customer that a shipping group in their order has been shipped.UnavailableItems: When anOrderModifiedevent with asubTypeofOrderHasUnavailableItemsis received, send an e-mail to the owner of the order. The e-mail uses the e-mail template found atdynamo/commerce/en/email_templates/jsp/OrderHasUnavailableItems.jsp. It notifies the customer that their order cannot be completed yet.OrderCancelled: When anOrderModifiedevent with a subtype ofOrderWasRemovedis received, then send an e-mail to the owner of the order. The e-mail uses the template found atdynamo/commerce/en/email_templates/jsp/OrderCancelled.jsp. It notifies the customer that their order has been cancelled.ItemRemoved: When anItemRemovedFromOrdermessage is received and the order’s state is 0, send an e-mail to the send an e-mail to the owner of the order. The e-mail uses the e-mail template found atdynamo/commerce/en/email_templates/jsp/ItemRemovedFomOrder.jsp. It notifies the customer that the item has been removed from the order.PaymentGroupChanged: When aPaymentGroupModifiedmessage is received, send an e-mail to the send an e-mail to the owner of the order. The e-mail uses the e-mail template found atdynamo/commerce/en/email_templates/jsp/PaymentGroupChanged.jsp. It notifies the customer that their payment information has been updated.
ReceiveOrder scenario:
SubmitOrder: When aSubmitOrdermessage is received, send an e-mail to the owner of the order. The e-mail uses the e-mail template found atdynamo/commerce/en/email_templates/jsp/SubmitOrderReceived.jsp. It notifies the customer that their order has been received.
