Legacy platform

View order summary

After capturing payments, the store associate must be able to view the order summary and print the receipt.

Order summary

After the payment is successfully processed, a confirmation is displayed. From the capture payment screen, when the store associate clicks View Order Summary, the following logic is executed to display the Order Summary screen:
  • The getCompleteOrderDetails API is called to get the order details.
  • The getCompleteOrderLineList API is called to get the order line details.
The Order Summary screen provides a summary of the order that the customer places, including the product, the delivery method, and the price. From the Order Summary screen, the store associate can print a receipt and email the receipt.
Note: Since the application does not support bundle products and services, if an order created through a different channel is searched in store, in the Order Summary screen, these order lines cannot be visually differentiated as such and there is no handling for such order lines.

Notes

The store associate can click Add Notes from the View Cart screen for a draft order and from theOrder Summary screen for a confirmed order. A pop-up window is displayed with the total number of notes and the existing comments which include both user logged and automatically logged events. The getNoteList API is called to retrieve the comments saved to the order. The store associate can enter a new comment in the text box and click Add. The changeOrder API is called to save the notes to the order.

Print receipts

A store associate can print a receipt for the customer. The StoreOrderSummary_94 print service is called to print the receipt. The following logic is executed in the service:
  • The getItemUOMMasterList API is called to retrieve the unit of measure.
  • The getRuleDetails API is called to get the unit of measure rule value. If the unit of measure rule value is not set to H, then the unit of measure is shown. If the unit of measure rule is set to H, then the unit of measure is not shown.
  • The getShipNodeList API is called to get the details of the current store.
  • The getCompleteOrderDetails API is called to get all order details for the receipt.
  • The getCurrencyList API is called to get the order currency type.
  • The getOrganizationHierarchy API is called to get the organization information to be used in the receipt.
The outputs of these APIs are passed to the custom API YCDGetModifiedOutputForOrder, which consolidates the outputs into a single output and then the output is converted into HTML format for printing.
The store associate can print by using a desktop or a mobile device.
  • Printing from a desktop browser
    • In Google Chrome and Mozilla Firefox browsers, the HTML content is appended into an iFrame and the print command is executed.
    • In Internet Explorer, the HTML content is appended into a new pop-up window and the command is executed.
  • Printing from a mobile browser
    • In iOS and Android devices, the HTML content is appended into a new pop-up window and the store associate must use the device options to execute the print.
    • In Windows™ Mobile Internet Explorer, the HTML content is appended into an iFrame and the current content is hidden to show the iFrame. The store associate must use the device options to execute the print.

Email receipts

The customer might want the order receipt to be sent to an e-mail address. The YCD_StoreOrder_Email service is invoked to get the order details and send the email.

You must configure this service for your email-server appropriately in the Applications Manager. The YCD_StoreOrder_Email service uses StoreOrderEmail_95_1_multiApi.xsl.sample and StoreOrderEmail_GenerateData_95_1_multiApi.xsl.sample templates. In the service definition, set the E-mail Server field to point to your mail server. The Subject and From fields have certain default values as part of the service, which can also be customized as required.