Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Setup Checklist

Insert excerpt
Set-up Checklist
Set-up Checklist
nopaneltrue

1. POS Tasks

  • Configure Product Header Codes or DCIs for scanning by native POS scanners.

    Status
    colourRed
    titleRequired

    1. For Siriusware, set up the product as a “Regular Item” that creates an access record.

    2. For RTP|One, set up the Product Header as an access product.

Status
colourYellow
titlePrerequisite

2. Infrastructure Tasks

  • Ensure scanners are configured for both test and production and test this functionality end to end.

    Status
    colourRed
    titleRequired

Status
colourYellow
titlePrerequisite

3. Commerce Tasks

  • Assign ‘Send Print-at-Home Notification’ product classification to the product.

    Status
    colourRed
    titleRequired

  • Configure the ‘OrderPlaced.PrintAtHomeCustomerNotification’ email template through Content Management>Message Templates.

    Status
    colourRed
    titlerequired

Status
colourYellow
titlePrerequisite

  • Configure 'ordersettings.orderidprefix.' The value here must match the value that is configured for the Order Processor Order ID.

    Status
    colourYellow
    titlerequired

  • SIRIUSWARE ONLY: Set "OrderProcessing.SendExternalPrintAtHomeNotification" to TRUE

    Status
    colourRed
    titlerequired

Status
colourYellow
titlePrerequisite

  • Assign Print at Home Notification to product.

    Status
    colourRed
    titleRequired

  • Ensure product has been set to ber auto fulfilled in Aspenware Commerce.

    Status
    colourRed
    titlerequired

Status
colourGreen
titleDetailed Setup

Prerequisite Tasks

Insert excerpt
Prerequisites Tasks Excerpt
Prerequisites Tasks Excerpt
nopaneltrue

...

  • Configure the Product Header Codes(s) or DCI in your resort POS according to the rules that make this product eligible for scanning by the native POS scanners.

    1. In Siriusware consider setting up your item as a ‘Regular Item’ that ‘creates an Access record,' like the example below.

      Image Modified

Info

NOTE: Any Siriusware product sold as “Print At Home” must be correctly configured as a “validation” product, rather than a “redemption” product**. In other words, the QR code generated by the Siriusware product should be configured in such a way that it will scan on a Siriusware-programmed hand scanner, and validate appropriately in the Siriusware system. The Configuration below manages the process by which the code generated by Siriusware is converted to a readable QR Code, and delivered to the guest. Little validation or configuration of the product is discussed in this guide, as that happens in Siriusware

(**Validation vs. Redemption: A validation product allows the guest access to a gate, venue, lane, etc. when they present their QR code for scanning. A redemption product requires the guest to present their code and receive a separate piece of media – lift ticket, RFID Card, etc. to gain access.)

...

  • There is a new product classification called ‘Send Print-at-Home Notification’. When assigned to a product, this is meant to trigger sending a follow-up email if the product is purchased with a QR code for the Axess Access Code of the Ticket. This uses a new OrderPlaced.PrintAtHomeCustomerNotification message template that includes a %Order.Barcodes% message token. If you wish to use print at home functionality, contact your Aspenware representative to ensure these items are all in place for your test and production sites.

  • To configure the print at home email template go to Content Management>Message Templates and Edit to edit the ‘OrderPlaced.PrintAtHomeCustomerNotification’ email template. 

    • To edit the email HTML, go to Tools>Source Code and adjust the HTML from there in the Source code window. In the body portion of the email template, paste the following code and customize as desired. Do not remove the %Order.Barcodes% message token.

      Code Block
      <p style="margin: 0;">Hello %Order.CustomerFullName%,</p>
      
      <p>Below is the voucher for your RESORT ticket.</p>
      
      <p>Add details on redemption.</p>
      
      <div class="”block”" style="text-align: center;">%Order.Barcodes%</div>
      
      <p>Order Number: PK%Order.OrderNumber% <br /> Date Ordered: %Order.CreatedOn% <br /><br /> %Order.Product(s)%<br /> <br /> Terms of print at home tickets here.</p>
      
      </td>
      
  • Additional styling can be applied to information within the %Order.Barcodes% table using email CSS, using the following div classes.

  • For more details on email configuration, refer to https://hub.aspenware.net/main/Configuration:-Emails.1251868693.html

...

Insert excerpt
Setting, Language String and/or HTML Widgets for this feature
Setting, Language String and/or HTML Widgets for this feature
nopaneltrue

Settings

  • Go to Configuration > Settings > All Settings and search for 'ordersettings.orderidprefix.' The value here must match the value that is configured for the Order Processor Order ID. Ask your Aspenware Representative what your Order Processor Order ID is if you are unsure.

  • SIRIUSWARE ONLY: In Aspenware Commerce, under Configuration> Settings> All Settings, locate  "OrderProcessing.SendExternalPrintAtHomeNotification"

    1. If this is set and the value is TRUE, then the print at home email will be sent from the Status function and not the Order Processor. This should be true for Siriusware resorts.

Note

IMPORTANT: The OrderProcessing.SendExternalPrintAtHomeNotification setting is a Siriusware only setting, and it should not be set or it should be FALSE for RTP|One resorts.

EXPLANATION:

Current print at home functionality works by the order processor calling an endpoint "api/orderprocessing/ordercleanup/{orderId:int}" which checks reservations for a print a home classification and sends accordingly.

For Siriusware this will not work because when the order processor runs, Siriusware hasn't finished processing the order on its end and we do not yet have a "sale_no" which is required to generate the print at home email. To get around this issue the Status Function calls a new endpoint named "api/orderprocessing/sendprintathomenotification/{orderId:int}" that will send the email using the now ready "sale_no." There is a new setting that needs to be set to TRUE for Siriusware environments so that the order processor doesn't attempt to send these emails, since the "sale_no" isn't available at that time. This setting is called OrderProcessing.SendExternalPrintAtHomeNotification and will be defaulted to FALSE.

...

1. Assign Send Print at Home Notification

  • From Plugins>Product Classifications>Add Assignment, select the desired category and product.

  • If print at home functionality is only desired for a particular attribute combination, check the desired product attribute values that are associated to print at home products. If the entire product should be set up as a Print-at-Home product, do not check any of the attribute options.

...

  • In the Classification table, click the Assign checkbox for the Send Print at Home Notification classification.

  • Click Add.

  • Make sure you have your product set to be auto fulfilled in the Aspenware Commerce using the guide in httpsOverview: //hub.aspenware.net/main/Overview:-Autofulfill%2FFinalize-Sale.1181155452.html

...

...