WEBVTT

00:00:00.000 --> 00:00:02.666
Hi. Welcome to XMPie.

00:00:02.666 --> 00:00:08.999
In this module, we look at how to manage orders of cross media products in the uStore Admin site.

00:00:09.000 --> 00:00:15.233
In uStore admin, on the Orders tab, you will notice some new queues in the drop-down list. 

00:00:15.233 --> 00:00:22.199
As you would expect, the XM Campaign queues allow you to manage orders of this new product type. 

00:00:22.200 --> 00:00:29.100
New XM Campaign orders arrive in the Pending queue where they can be Launched or Cancelled. 

00:00:29.100 --> 00:00:36.000
Once a campaign is Launched, it will appear in the Campaigns in Progress queue until the campaign is Terminated 

00:00:36.000 --> 00:00:39.133
and it appears in the Completed queue.

00:00:39.133 --> 00:00:45.599
The standard uStore triggers can be used to move products between queues automatically if desired. 

00:00:45.600 --> 00:00:52.500
There is a trigger defined out of the box, that automatically launches new XM Campaign orders. 

00:00:52.500 --> 00:00:58.700
If you don’t want to launch campaigns automatically, you can change the status to inactive, 

00:00:58.700 --> 00:01:05.766
or alternatively, you can select the specific stores and products that will use the trigger.

00:01:05.766 --> 00:01:13.499
Back in the Orders list, clicking the order Item ID will show details of the product. 

00:01:13.500 --> 00:01:23.333
The Open in Circle button will take you to Circle, automatically login, and open the correct instance of the project for this order. 

00:01:23.333 --> 00:01:29.699
In Circle, you could also open the project instance from the Open/Organize menu, 

00:01:29.700 --> 00:01:38.066
but when you have many instances of the project in Circle, the button in uStore admin will help you avoid mistakes. 

00:01:38.066 --> 00:01:44.332
For clarity, the number refers to the uStore order product id. 

00:01:44.333 --> 00:01:50.499
You will also see on the item details page, that the print job has a separate order Item ID. 

00:01:50.500 --> 00:01:58.233
In the sample campaign, I configured scheduling to automatically process the print document when the campaign is launched.

00:01:58.233 --> 00:02:03.999
So, Circle has triggered the print production, and passed the output file to uStore. 

00:02:04.000 --> 00:02:12.800
uStore will pass the job through the Prepress Workflow - if you selected one - and it will arrive in the Ready for Delivery queue.

00:02:12.800 --> 00:02:16.466
If you don’t configure Circle to schedule the print production, 

00:02:16.466 --> 00:02:22.999
you will need to process the Print Touchpoint manually in Circle before it will appear in uStore. 

00:02:23.000 --> 00:02:29.933
To do that, click the Open in Cirlce button, and process the Print Touchpoint in the usual way.

00:02:29.933 --> 00:02:36.566
In a few minutes when the job is completed, the resulting production file is passed to uStore. 

00:02:36.566 --> 00:02:46.732
If you didn't use a Prepress Workflow to send the job to a printer, you can download the output file from uStore Ready for Delivery queue, 

00:02:46.733 --> 00:02:51.166
or from the Circle Run Centre.

00:02:51.166 --> 00:02:55.599


00:02:55.600 --> 00:03:05.433
Note that because Circle is producing the print file and not uStore, it is not possible to aggregate the print job like you can for other dynamic products. 

00:03:05.433 --> 00:03:12.233
For customers who would want to aggregate to be able to sort or edit the recipient list before processing the print file, 

00:03:12.233 --> 00:03:22.266
you can go to the Circle instance, download the recipient list, sort or edit, and replace the list before processing the Print Touchpoint.