Using the Signature Gifts Newspaper App
Custom Gateway have created a smartlink app layout which works with Signature Gifts extensive original newspaper database to allow orders to be taken for specific newspapers and gift packs.
Signatures website showing these products is available here - https://www.historic-newspapers.co.uk/original-newspapers/
This app works with only the following products in CPP
Product Name | Signature SKU | CPP Product ID |
Original Keepsake Anniversary Case | 021300000000 | 1058176 |
Original Picture Frame | 020600000000 | 1058169 |
Original Gift Box | 020100000000 | 1058164 |
Original Newspaper in a Premium Box Green | 020200000000 | 1058165 |
Tattinger Champagne & paper | 010404010401 | 1060503 |
Vintage Bordeaux wine & paper | 010104010401 | 1060506 |
Macallan Double Cask Gold Malt + newspaper | 010701010101 | 2576891 |
Personalised Prosecco & paper | 011601010402 | 1060893 |
Personalised Malt Whisky & paper | 010700010410 | 1060905 |
The link structure without any config, company ref or callback example is below
When submitting orders to the OMS for this product it is important to note that these items are submitted to the OMS as the PRODUCT STATE ITEM TYPE as they do not generate traditional print jobs because of the newspaper data we have to capture (The product_state_ref can be captured and saved from the add to cart callback). Example JSON for the item object is below :-
{ "sku": "021600000000", "description": "Original + Book in Red Gift Box",
"quantity": 1, "type": 8, "product_state_ref": "ABCDEFGHIJKLM" },
CPP NOTE - Items being used in this app must have an internal attribute with the name ":NEWS PaperCode" and no value. This is where we save the newspaper choice made inside the app
When it comes to the callback and capturing data to show in the cart
In the callback there should be a data.body.items[0].extra.state property
The paper code can be found in data.body.items[0].extra.state.attributes[0].value
The paper code is in the format YYYYMMDD followed by a 3 letter code identifying the publication (i.e. GUA = guardian). Signature will have a list of 3 letter codes
The other text values can be found in data.body.items[0].extra.state.text_areas - specifically the area_properties.name and final_text fields
Save state must be used in the link "_usePs=1" for it to fully function
Related Articles
Platform | Product Manager App Defaults
What Is App Defaults? "App Defaults" is an option found within Catalog > Product Manager and is accessible when setting up or modifying a product. The main menu is found within "Product Details" and the tab "App Defaults" which is shown below. ...Smartlink Apps | Kiosk
Introduction The following article has been written to detail how our standard Kiosk app can be set up and used for. We have also detailed all of the available options associated with Kiosk features, POS, Styling and Renderer Options menus. The Kiosk ...Smartlink Apps | Flow
Introduction The following article has been written to detail how our standard Flow app can be set up and used for. We have also detailed all of the available options associated with Flow features, styling, product info, renderer option, POS (Point ...Smartlink Apps | Stepped3
Introduction The following article has been written to detail how our standard Stepped 3 app can be set up and used for a stepped app experience. We have also detailed all of the available features associated with Stepped 3 general, features, ...Smartlink Apps | Selector 3_2
Introduction The following article has been written to detail how our standard Selector 3_2 app can be set up and used for. We have also detailed all of the available features associated with Selector 3_2 features, POS, styling, product info, ...