This section describes scenarios that confirm order placement and shipment.
OrderShipped
The OrderShipped
scenario, located in /store/orders
, looks like this:
The OrderShipped
scenario sends a confirmation e-mail after a customer’s order has been shipped. This scenario listens for the atg.commerce.fulfillment.scenario.ShippingGroupModified
event message that indicates that a shipping group has been shipped. These messages are sent by the /atg/commerce/fulfillment/OrderChangeHandler
component. When the OrderShipped
scenario detects a ShippingGroupModified
event message that indicates a shipping group has been shipped, it does one of the following:
If the customer’s e-mail address is blank, the scenario ends without sending e-mail.
If the customer’s e-mail address is undefined, the scenario ends without sending e-mail.
For all other cases,
OrderShipped
sends a confirmation e-mail to the address stored in the customer’s profile, using thestore.war/emailtemplates/orderShipped.jsp
template. TheOrderShipped
scenario passes the order’s site ID toorderShipped.jsp
, so that the e-mail it generates is site-specific.
Note: For more information on the ShippingGroupModified
event message, see the ATG Commerce Guide to Setting Up a Store. For more information on the OrderChangeHandler
component, see the ATG Commerce Programming Guide.
ordersubmit
The ordersubmit
scenario, located in /store/orders
, confirms a customer’s order. It looks like this:
The ordersubmit
scenario sends a confirmation e-mail after a customer has submitted an order. This scenario listens for the atg.commerce.fullfillment.SubmitOrder
event message that is generated each time a customer submits an order. When it detects a SubmitOrder
message, the scenario does one of the following:
If the customer’s e-mail address is blank, the scenario ends without sending e-mail.
If the customer’s e-mail address is undefined, the scenario ends without sending e-mail.
For all other cases,
ordersubmit
sends a confirmation e-mail to the address stored in the customer’s profile, using thestore.war/emailtemplates/orderConfirmation.jsp
template. Theordersubmit
scenario passes the order’s site ID toorderConfirmation.jsp
, so that the e-mail it generates is site-specific. If the order is split over multiple shipping groups, an e-mail is sent for each shipping group.