Order Summary and Confirmation Services


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Search \| PDF Files \| Contact \| Glossary

WebLogic Portal Documentation \| Order Guide \| Previous Topic \| Next Topic \| Contents \| Index

Prior to submitting their order, your customers will want to review an order summary that includes information about the items they have decided to purchase, as well as other information (shipping, payment, and tax) related to their order. Following order submission, it is customary to provide your customers with a confirmation page, which customers can save and later use to check on the status of their order. The Order Summary and Confirmation Services allow you to do just that, and this topic describes how.

This topic includes the following sections:

JavaServer Pages (JSPs)

This section describes the JavaServer Pages (JSPs) used to implement the Order Summary and Confirmation Services. You can use them on your own e-commerce site, or customize them to meet your requirements.

Note: For a description of the complete set of JSPs used in the WebLogic Portal Web application and a listing of their locations in the directory structure, see the E-Commerce JSP Template Summary.

checkout.jsp Template

The checkout.jsp template (shown in Figure 7-1) provides a customer with a final look at all the details of their order, before the customer commits or cancels the order. Information displayed includes the shipping address, shipping details, a list of the items ordered (including the item name, short description, quantity, price, and subtotal), shipping and handling costs, tax costs, and total cost.

Customers must click the Complete Purchase button to commit their order. Customers wishing to return to the previous page can click the Back button instead.

Sample Browser View

Figure 7-1 shows an annotated version of the checkout.jsp template. A description of the annotated regions follow the figure.

Figure 7-1 Annotated checkout.jsp Template

The numbers in the following list refer to the numbered regions in the figure:

The Final Checkout Review region uses a combination of WebLogic Portal and Pipeline JSP tags to obtain and display the shipping address, splitting preferences, and shipping method. This provides the customer with a final look at this shipping information as it was entered on previous JSP templates.
The Order region uses a combination of WebLogic Portal and Pipeline JSP tags to obtain and display the customer's current shopping cart. This provides the customer with a final look at the contents of their shopping cart (including item name, description, quantity, price, and subtotal), and the discount, shipping, tax, and total amounts for the entire order.

Location in the WebLogic Portal Directory Structure

You can find the checkout.jsp template file at the following location, where PORTAL_HOME is the directory in which you installed WebLogic Portal:

%PORTAL_HOME%\applications\wlcsApp\wlcs\commerce\order\
checkout.jsp (Windows)
$PORTAL_HOME/applications/wlcsApp/wlcs/commerce/order/
checkout.jsp (UNIX)

Tag Library Imports

The checkout.jsp template uses existing WebLogic Server JSP tags, and WebLogic Portal's User Management and Personalization JSP tags. It also uses Pipeline JSP tags. Therefore, the template includes the following JSP tag libraries:

<%@ taglib uri="webflow.tld" prefix="webflow" %>
<%@ taglib uri="weblogic.tld" prefix="wl" %>
<%@ taglib uri="um.tld" prefix="um" %>
<%@ taglib uri="es.tld" prefix="es" %>
<%@ taglib uri="i18n.tld" prefix="i18n" %>

For more information on the WebLogic Server JSP tags or the WebLogic Portal JSP tags, see "JSP Tag Reference" in the Guide to Building Personalized Applications. For more information about the Pipeline JSP tags, see the Guide to Managing Presentation and Business Logic: Using Webflow and Pipeline.

These files reside in the lib directory within PORTAL_HOME.

Java Package Imports

The checkout.jsp template uses Java classes in the following packages and therefore includes these import statements:

<%@ page import="java.util.*" %>
<%@ page import="java.text.*" %>
<%@ page import="com.beasys.commerce.axiom.units.*" %>
<%@ page import="com.beasys.commerce.axiom.contact.*" %>
<%@ page import="examples.wlcs.sampleapp.shoppingcart.*" %>
<%@ page import="examples.wlcs.sampleapp.price.service.DiscountPresentation" %>
<%@ page import="examples.wlcs.sampleapp.price.quote.OrderAdjustment" %>
<%@ page import="examples.wlcs.sampleapp.price.quote.AdjustmentDetail" %>
<%@ page import="examples.wlcs.sampleapp.price.quote.AdjustmentType" %>

<%@ page import="com.beasys.commerce.webflow.HttpRequestConstants" %>
<%@ page import="com.beasys.commerce.webflow.PipelineSessionConstants" %>
<%@ page import="com.bea.p13n.appflow.webflow.WebflowJSPHelper" %>

Location in Default Webflow

Customers arrive at the checkout.jsp template from the payment information page (payment.jsp). If customers choose to commit their order, they will continue to the order confirmation page (confirmorder.jsp). If customers choose to cancel, they will be sent back to the payment page (payment.jsp).

Note: For more information about the default Webflow, see Overview of Managing Purchases and Processing Orders.

Events

The checkout.jsp template presents a customer with two buttons, each of which is considered an event. These events trigger a particular response in the default Webflow that allows customers to continue. While this response can be to load another JSP, it is usually the case that an input processor or Pipeline is invoked first. Table 7-1 provides information about these events and the business logic they invoke.

Table 7-1 checkout.jsp Events

Event	Webflow Response(s)
button.back	No business logic required. Loads payment.jsp.
button.purchase	CommitOrder

Table 7-2 briefly describes each of the Pipelines from Table 7-1. For more information about individual Pipeline components, see Pipeline Components.

Table 7-2 Checkout Review Pipelines

Pipeline	Description
CommitOrder	Contains CommitOrderPC, AuthorizePaymentPC, CalculateTaxLineLevelCommitPC, and is transactional.
PurchaseTracker	Contains PurchaseTrackerPC, ResetCheckoutPC, and is not transactional.

Dynamic Data Display

The purpose of the checkout.jsp template is to display the data specific to a customer's shopping experience for their final review. This is accomplished on the checkout.jsp template using a combination of Pipeline and WebLogic Portal JSP tags and accessor methods/attributes.

First, the getProfile JSP tag is used to set the customer profile (context) for which the customer information should be retrieved, as shown in Listing 7-1.

Listing 7-1 Setting the Customer Context

<um:getProfile	profileKey="<%=request.getRemoteUser()%>"
profileType="WLCS_Customer" />

Note: For more information on the WebLogic Portal JSP tags, see "JSP Tag Reference" in the Guide to Building Personalized Applications.

Next, the getProperty JSP tag retrieves the SHIPPING_ADDRESS and SHOPPING_CART attributes from the Pipeline session. Table 7-3 provides more detailed information on these attributes.

Table 7-3 checkout.jsp Pipeline Session Attributes

Attributes	Type	Description
PipelineSessionConstants. SHIPPING_ADDRESS	com.beasys.commerce.axiom .contact.Address	The address the order is being shipped to.
PipelineSessionConstants. SHIPPING_METHOD	examples.wlcs.sampleapp .shipping.shippingMethodValue	Identifies the shipping method the customer selected.
PipelineSessionConstants. SHOPPING_CART	examples.wlcs.sampleapp .shoppingcart.ShoppingCart	The shopping cart that was ordered.
PipelineSessionConstants. SPLITTING_PREFERENCE	java.lang.String	The splitting preference the customer selected.
PipelineSessionConstants. SPECIAL_INSTRUCTIONS	java.lang.String	Any special instructions the customer specifies.
PipelineSessionConstants. ORDER_ADJUSTMENTS	examples.wlcs.sampleapp .price.quote.Quote	Adjustments to the order and order lines.
PipelineSessionConstants. PAYMENT_CREDIT_CARD	com.beasys.commerce.axiom .contact.CreditCard	The user's credit card.

Listing 7-2 illustrates how some of these attributes are retrieved from the Pipeline session.

Listing 7-2 Retrieving Check Out Attributes

<webflow:getProperty id="shippingMethodValue" property="<%=PipelineSessionConstants.SHIPPING_METHOD%>" type="examples.wlcs.sampleapp.shipping.ShippingMethodValue" scope="session" namespace="sampleapp_main" />

<webflow:getProperty id="shippingAddress" property="<%=PipelineSessionConstants.SHIPPING_ADDRESS%>" type="com.beasys.commerce.axiom.contact.Address" scope="session" namespace="sampleapp_main" />

<webflow:getProperty id="shoppingCart" property="<%=PipelineSessionConstants.SHOPPING_CART%>" type="examples.wlcs.sampleapp.shoppingcart.ShoppingCart" scope="session" namespace="sampleapp_main" />

Note: For more information on the getProperty JSP tag, see the Guide to Managing Presentation and Business Logic: Using Webflow and Pipeline.

For the data stored in the customer profile and retrieved using the getProfile JSP tag, use the getPropertyAsString JSP tag to display the customer information, as shown in Listing 7-3.

Listing 7-3 Displaying Data Stored in the Customer's Profile

<div class="tabletext">

  <um:getPropertyAsString propertySet="CustomerProperties" propertyName="firstName"/> <um:getPropertyAsString propertySet="CustomerProperties" propertyName="lastName"/><br>

    <%=shippingAddress.getStreet1()%><br>

    <!-- implent street2 using es -->

    <% if( shippingAddress.getStreet2().length() != 0 ) { %>

    <%=shippingAddress.getStreet2()%><br>

    <% } %>

    <%=shippingAddress.getCity()%><br>

    <%String stateZip  = shippingAddress.getState()+ "-" + shippingAddress.getPostalCode();%>

    <%=stateZip%><br>

    <%= shippingAddress.getCountry() %><br>

</div>

Note: For more information on the WebLogic Portal JSP tags, see "JSP Tag Reference" in the Guide to Building Personalized Applications.

The data stored within the Pipeline session attributes (retrieved using the getProperty JSP tag) is displayed by using accessor methods/attributes within Java scriptlets. Table 7-4 provides more detailed information on these methods/attributes for Address, ShoppingCart, and ShoppingCartLine.

Table 7-4 Address Accessor Methods/Attributes

Method/Attribute	Description
getStreet1()	The first line in the customer's street address.
getStreet2()	The second line in the customer's street address.
getCity()	The city in the customer's address.
getState()	The state in the customer's address.
getPostalCode()	The zip/postal code in the customer's address.
getCountry()	The country in the customer's address.

Table 7-5 ShoppingCart Accessor Methods/Attributes

Method/Attribute	Description
getShoppingCartLineCollection()	The individual lines in the shopping cart (that is, ShoppingCartLine).
getTotal(int totalType)	The total amount specified by the totalType parameter. The relevant parameter is: ShoppingCartConstants.LINE_TAX Note: The getTotal() method also allows you to combine different total types. For more information, see the Javadoc.

Because the getShoppingCartLineCollection() method allows you to retrieve a collection of the individual lines within a shopping cart, there are also accessor methods/attributes you can use to break apart the information contained within each line. Table 7-6 provides information about these methods/attributes.

Table 7-6 ShoppingCartLine Accessor Methods/Attributes

Method/Attribute	Description
getQuantity()	The quantity of the item.
getProductItem()	The product item in the shopping cart line.
getUnitPrice()	The current price for the item at the time it was added to the shopping cart. May be different from MSRP.
getBaseTotal()	The total before discounts.
getDiscountPresentations()	Returns an array list of DiscountPresentation objects.

Listing 7-4 illustrates how these accessor methods/attributes are used within Java scriptlets.

Listing 7-4 Using Accessor Methods/Attributes Within checkout.jsp Java Scriptlets

<wl:repeat set="<%=shoppingCart.getShoppingCartLineCollection().iterator()%>" id="shoppingCartLine" type="ShoppingCartLine" count="100000">

  <tr>

    <td colspan="8" bgcolor="#899ABC"><img src="<webflow:createResourceURL resource="/commerce/images/shim.gif" />" width="62" height="1"></td>

  </tr>

  <tr>

    <td nowrap valign="top">

      <div class="tabletext"><%= shoppingCartLine.getProductItem().getKey().getIdentifier() %>

      </div>

    </td>

    <td valign="top" bgcolor="#CCCCFF">

      <div class="tabletext"><%= shoppingCartLine.getProductItem().getName() %>

      </div>

    </td>

	  

    <td align="center" valign="top">

      <div class="tabletext"><%= WebflowJSPHelper.quantityFormat( shoppingCartLine.getQuantity()) %>

      </div>

    </td>

    <td align="right" valign="top" bgcolor="#CCCCFF" nowrap>

      <div class="tabletext">

      <%-- The i18n tag allows the "currency.properties" file to substitute a display --%>

      <%-- currency value (e.g "$") for the returned 3 letter ISO4217 code (e.g. "USD").  --%>

      <i18n:getMessage bundleName="/commerce/currency" messageName="<%= shoppingCartLine.getUnitPrice().getCurrency() %>"/>&nbsp;<%= WebflowJSPHelper.priceFormat( shoppingCartLine.getUnitPrice().getValue() ) %>

      </div>

    </td>

    <td align="right" valign="top" nowrap><div class="tabletext" nowrap>

      <% // Calculate the Subtotal

      //double lineTotal = (shoppingCartLine.getQuantity() * shoppingCartLine.getUnitPrice().getValue());

%>

      <i18n:getMessage bundleName="/commerce/currency" messageName="<%= shoppingCartLine.getBaseTotal().getCurrency() %>"/>&nbsp;<%= WebflowJSPHelper.priceFormat( shoppingCartLine.getBaseTotal().getValue() ) %>

      </div>

    </td>

  </tr>
...
</wl>

Form Field Specification

The checkout.jsp template does not make use of any form fields.

confirmorder.jsp Template

The confirmorder.jsp template (shown in Figure 7-2) displays the information about the customer's order after they have committed it. This information is the same as that shown in the checkout.jsp template, but also includes an order confirmation number customers can use to access information about the order in the future. The confirmorder.jsp template also provides the customer with a Continue Shopping button that will bring the customer back to the product catalog.

Sample Browser View

Figure 7-2 shows an annotated version of the confirmorder.jsp template. A description of the annotated regions follow the figure.

Figure 7-2 Annotated confirmorder.jsp Template

The numbers in the following list refer to the numbered regions in the figure:

This region contains the dynamically generated order confirmation number, which customers can use on subsequent visits to check the status of their order. It is displayed using Pipeline JSP tags and accessor methods/attributes.
This region uses a combination of WebLogic Portal and Pipeline JSP tags to obtain and display the shipping address, splitting preferences, and shipping method. Together with the information in region 4 and region 6, this provides the customer with a record of the shipping information as it was entered on previous JSP templates.
This region uses a combination of WebLogic Portal and Pipeline JSP tags to obtain and display the customer's shopping cart. Together with the information in region 4 and region 5, this provides the customer with a record of their shopping cart (including item name, description, quantity, price, and subtotal), and the shipping, tax, and total amounts for the order.

Location in the WebLogic Portal Directory Structure

You can find the confirmorder.jsp template file at the following location, where PORTAL_HOME is the directory in which you installed WebLogic Portal:

%PORTAL_HOME%\applications\wlcsApp\wlcs\commerce\order\
confirmorder.jsp (Windows)
$PORTAL_HOME/applications/wlcsApp/wlcs/commerce/order/
confirmorder.jsp (UNIX)

Tag Library Imports

The confirmorder.jsp template uses existing WebLogic Server and WebLogic Portal's User Management and Personalization JSP tags. It also uses Pipeline JSP tags. Therefore, the template includes the following JSP tag libraries:

<%@ taglib uri="webflow.tld" prefix="webflow" %>
<%@ taglib uri="weblogic.tld" prefix="wl" %>
<%@ taglib uri="um.tld" prefix="um" %>
<%@ taglib uri="es.tld" prefix="es" %>
<%@ taglib uri="i18n.tld" prefix="i18n" %>

Note: For more information on the WebLogic Server JSP tags or the WebLogic Portal JSP tags, see "JSP Tag Reference" in the Guide to Building Personalized Applications. For more information about the Pipeline JSP tags, see the Guide to Managing Presentation and Business Logic: Using Webflow and Pipeline.

These files reside in the lib directory within PORTAL_HOME.

Java Package Imports

The confirmorder.jsp template uses Java classes in the following packages and therefore includes these import statements:

<%@ page import="java.util.*" %>

<%@ page import="java.text.*" %>

<%@ page import="com.beasys.commerce.axiom.units.*" %>

<%@ page import="com.beasys.commerce.axiom.contact.*" %>

<%@ page import="com.beasys.commerce.axiom.util.helper.*;" %>

<%@ page import="examples.wlcs.sampleapp.order.*" %>

<%@ page import="examples.wlcs.sampleapp.catalog.*" %>

<%@ page import="examples.wlcs.sampleapp.shipping.*" %>

<%@ page import="com.beasys.commerce.util.*; " %>

<%@ page import="com.beasys.commerce.webflow.HttpRequestConstants" %>

<%@ page import="com.beasys.commerce.webflow.PipelineSessionConstants" %>

<%@ page import="com.bea.p13n.appflow.webflow.WebflowJSPHelper" %>

Location in Default Webflow

Customers arrive at confirmorder.jsp template from the final checkout page (checkout.jsp). The default Webflow does not define a subsequent JSP template.

The template is in the sampleapp_order namespace.

Note: For more information about the default Webflow, see Overview of Managing Purchases and Processing Orders.

Events

There are no events associated with the confirmorder.jsp template.

Dynamic Data Display

The purpose of the confirmorder.jsp template is to display the data specific to a customer's shopping experience along with a unique order confirmation number. This is accomplished on the confirmorder.jsp template using a combination of Pipeline and WebLogic Portal JSP tags and accessor methods/attributes.

First, the getProfile JSP tag is used to set the customer profile (context) for which the customer information should be retrieved, as shown in Listing 7-5.

Listing 7-5 Setting the Customer Context

<um:getProfile
  profileKey="<%=request.getRemoteUser()%>"
  profileType="WLCS_Customer" />

Note: For more information on the WebLogic Portal JSP tags, see "JSP Tag Reference" in the Guide to Building Personalized Applications.

Next, the getProperty JSP tag retrieves the ORDER_VALUE and SHIPPING_METHOD attributes from the Pipeline session. Table 7-7 provides more detailed information about these attributes.

Table 7-7 confirmorder.jsp Pipeline Session Attributes

Attribute	Type	Description
PipelineSessionConstants.ORDER_VALUE	List of com.beasys.commerce .ebusiness.order.OrderValue	List of the orders available for the customer.
PipelineSessionConstants.SHIPPING_METHOD	examples.wlcs.sampleapp .shipping.ShippingMethodValue	The method being used to ship the order.
PipelineSessionConstants.CREDIT_CARD_KEY	java.lang.String	The key of the credit card.

Listing 7-6 illustrates how these attributes are retrieved from the Pipeline session.

Listing 7-6 Retrieving Order Confirmation Attributes

<webflow:getProperty id="orderValue" property="<%=PipelineSessionConstants.ORDER_VALUE%>" type="OrderValue" scope="request" namespace="sampleapp_main" />

<webflow:getProperty id="creditCard" property="<%=PipelineSessionConstants.CREDITCARD_KEY%>" type="java.lang.String" scope="session" namespace="sampleapp_main" />

<webflow:getProperty id="shippingMethodValue" property="<%=PipelineSessionConstants.ORDER_SHIPPING_METHOD%>" type="examples.wlcs.sampleapp.shipping.ShippingMethodValue" scope="request" namespace="sampleapp_main" />

Note: For more information on the getProperty JSP tag, see the Guide to Managing Presentation and Business Logic: Using Webflow and Pipeline.

For the data stored in the customer profile and retrieved using the getProfile JSP tag, use the getPropertyAsString JSP tag to display the customer information, as shown in Listing 7-7.

Listing 7-7 Displaying Data Stored in the Customer's Profile

<um:getPropertyAsString propertySet="CustomerProperties" propertyName="firstName" />&nbsp;

<um:getPropertyAsString propertySet="CustomerProperties" propertyName="lastName" /><br>

Note: For more information on the WebLogic Portal JSP tags, see "JSP Tag Reference" in the Guide to Building Personalized Applications.

The data stored within the Pipeline session attributes (retrieved using the getProperty JSP tag) is displayed by using accessor methods/attributes within Java scriptlets. Table 7-8 through Table 7-11 provide more detailed information on these methods/attributes for Address, ShippingMethodValue, OrderValue, and Orderline.

Table 7-8 Address Accessor Methods/Attributes

Method/Attribute	Description
getStreet1()	The first line in the customer's street address.
getStreet2()	The second line in the customer's street address.
getCity()	The city in the customer's address.
getState()	The state in the customer's address.
getPostalCode()	The zip/postal code in the customer's address.
getCountry()	The country in the customer's address.

Table 7-9 ShippingMethodValue Accessor Methods/Attributes

Method/Attribute	Description
description	A description of the shipping method.
identifier	Key in the database for the shipping method.

Table 7-10 OrderValue Accessor Methods/Attributes

Method/Attribute	Description
createdDate	The date the customer's order was created.
identifier	Key in the database for the order.
getTotal(int totalType)	The total amount specified by the totalType parameter. The relevant parameter is OrderConstants.LINE_TAX Note: The getTotal() method also allows you to combine different total types. For more information, see the Javadoc.
orderLines	A collection of the lines in the shopping cart that make up the customer's order.
price	The total price as a money object.

Because the orderLines attribute allows you to retrieve the individual lines within an order, it also has accessor methods/attributes you can use to display the information contained within each line. These methods/attributes are listed in Table 7-11.

Table 7-11 OrderLine Accessor Methods/Attributes

Method/Attribute	Description
getProductIdentifier()	The name (identifier) for the shopping cart item.
getDescription()	A description of the shopping cart item.
getQuantity()	The quantity of the shopping cart item.
getUnitPrice()	The unit price for the shopping cart item.

Listing 7-8 illustrates how these accessor methods/attributes are used within Java scriptlets.

Listing 7-8 Using Accessor Methods Within confirmorder.jsp Java Scriptlets

<%--Iterate through order to get all order lines --%>

<wl:repeat set="<%=orderValue.orderLines.iterator()%>" id="orderLine" type="OrderLine" count="100000">

  <tr>

    <td valign="top" align="left" nowrap>

      <div class="tabletext"><%= orderLine.getProductIdentifier() %></div>

    </td>

	  

    <td valign="top" align="left">

      <div class="tabletext"><%= orderLine.getDescription() %></div>

    </td>

	  

    <td align="center" valign="top">

      <div class="tabletext"><%= WebflowJSPHelper.quantityFormat( orderLine.getQuantity()) %></div>

    </td>

	  

    <td align="right" valign="top" nowrap>

      <div class="tabletext">

      <i18n:getMessage bundleName="/commerce/currency" messageName="<%= orderLine.getUnitPrice().getCurrency() %>"/>&nbsp;<%= WebflowJSPHelper.priceFormat( orderLine.getUnitPrice().getValue() ) %>

      </div>

      </td>

	  

      <td align="right" valign="top" nowrap>

<%

			// Calculate the line subtotal without adjustments/discounts

			double orderLineTotal = (orderLine.getQuantity() * orderLine.getUnitPrice().getValue());

%>

        <div class="tabletext">

			<i18n:getMessage bundleName="/commerce/currency" messageName="<%= orderLine.getUnitPrice().getCurrency() %>"/>&nbsp;<%= WebflowJSPHelper.priceFormat( orderLineTotal ) %>

		</div>

      </td>

    </tr>

...

</wl>

For a code example of the ShoppingCart and ShoppingCartLine accessor methods/attributes, see Shopping Cart Management Services.

Form Field Specification

The confirmorder.jsp template does not make use of any form fields.

Input Processors

No input processors are used in the Order Summary and Confirmation Services JSP template(s).

Pipeline Components

This section provides a brief description of each Pipeline component associated with the Order Summary and Confirmation Services JSP template(s).

Note: Some Pipeline components extend other, base Pipeline components. For more information on the base classes, see the Javadoc.

CommitOrderPC

Class Name	examples.wlcs.sampleapp.order.pipeline.CommitOrderPC
Description	Reads all the information about a customer's order from the Pipeline session and creates an Order entity bean. This is committed to the database in the WLCS_ORDER and WLCS_ORDER_LINE tables. The OrderValue object for the order is then stored in the Pipeline session.
Required Pipeline Session Attributes	PipelineSessionConstants.USER_NAME PipelineSessionConstants.SHOPPING_CART PipelineSessionConstants.SPLITTING_PREFERENCE PipelineSessionConstants.SPECIAL_INSTRUCTIONS PipelineSessionConstants.ORDER_CONFIRMATION_NUMBER PipelineSessionConstants.SHIPPING_ADDRESS PipelineSessionConstants.ORDER_ADJUSTMENTS PipelineSessionConstants.SHIPPING_METHOD PipelineSessionConstants.DISCOUNT_IDS PipelineSessionConstants.GLOBAL_DISCOUNTS_IDS
Updated Pipeline Session Attributes	PipelineSessionConstants.ORDER_HANDLE (Request scope) PipelineSessionConstants.ORDER_VALUE (Request scope) PipelineSessionConstants.ORDER_SHIPPING_METHOD (Request scope) PipelineSessionConstants.PAYMENT_AUTHORIZATION_ACCOUNT
Removed Pipeline Session Attributes	PipelineSessionConstants.SHIPPING_METHOD
Type	Java object
JNDI Name	None
Exceptions	PipelineException, thrown when the required Pipeline session attributes are not available or if the shopping cart is empty.

ResetCheckoutPC

Class Name	examples.wlcs.sampleapp.order.pipeline. ResetCheckoutPC
Description	Removes all Pipeline session attributes relating to the customer's checkout process.
Required Pipeline Session Attributes	None
Updated Pipeline Session Attributes	None
Removed Pipeline Session Attributes	PipelineSessionConstants.SHOPPING_CART PipelineSessionConstants.SHIPPING_ADDRESS PipelineSessionConstants.SPLITTING_PREFERENCE PipelineSessionConstants.SHIPPING_METHOD PipelineSessionConstants.SPECIAL_INSTRUCTIONS PipelineSessionConstants.PAYMENT_AUTHORIZATION_AMOUNT PipelineSessionConstants.VERAZIP_SHIPPING_ADDRESS PipelineSessionConstants.PAYMENT_CREDIT_CARD
Type	Java object
JNDI Name	None
Exceptions	None

PurchaseTrackerPC

Class Name	examples.wlcs.sampleapp.tracking.pipeline.PurchaseTrackerPC
Description	Fires events: first, a PurchaseCartEvent for the entire order that is being placed; second, one BuyEvent per Order Line (SKU) that is being purchased. For more information about this event, see Event Details in the Guide to Events and Behavior Tracking.
Required Pipeline Session Attributes	PipelineSessionConstants.ORDER_VALUE PipelineSessionConstants.HTTP_SESSION_ID PipelineSessionConstants.USER_NAME PipelineSessionConstants.CATALOG_CATEGORY PipelineSessionConstants.STOREFRONT PipelineSessionConstants.CUSTOM_REQUEST
Updated Pipeline Session Attributes	None
Removed Pipeline Session Attributes	None
Type	Java Object
JNDI Name	None
Exceptions	None