Date: Fri, 29 Mar 2024 06:00:36 -0500 (CDT) Message-ID: <1281426280.39625.1711710036242@kodak01.contegix.mgmt> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_39624_1815419676.1711710036212" ------=_Part_39624_1815419676.1711710036212 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Create rule sets that automate the preparation of processed Stor=
efront files for digital printing.
You can have Prinergy automatically prepare Storefront files for digital p=
rinting, after the content files from an order are uploaded to the Prinergy=
system and processed.
Follow these steps to set up a digital production rule for each Storefront=
product:
When an order is submitted using the Storefront system, you can set up t=
he system to prepare the files manually or automatically. For example, if p=
rint buyers will use your Storefront system to upload ad hoc items (print-r=
eady files), you can set up the system to add the files and refine them aut=
omatically for previewing. You do not need to create a rule for this using =
RBA.
For information on assigning upload processing rules in Storefront, see th=
e InSite Storefront System Administration Guide, available on Part=
ner Place at https://?partnerplace.kodak.com/.
Common file processing tasks for Storefront products are shown in the foll=
owing table:
Storefront product |
Prepress workflow |
---|---|
Ad hoc items (files uploaded by print buyers)= |
Input files are added and refined, enabling p=
rint buyers and CSRs to preview them. |
Static items (items that buyers order from th= e system=E2=80=94files are not personalized) |
Input files are added. |
Variable items (items that buyers personalize= using variable templates) |
The item is composed and input files are adde=
d. |
Inventory items (such as mugs, hats, and T-sh= irts) |
The job is copied. |
Automat=
ing the digital output
After a Storefront order is moved to Production, you can automate the prep=
aration of the document for digital printing using RBA. Create a separate r=
ule set for each Storefront product.
The recommended event to start a Storefront rule set is the Job Ch=
anged To Production event, which occurs when a pre-production job =
in InSite becomes a production job. (In Prinergy, this changes a pre-job in=
to a job.)
Attach the Read XML action to the trigger event to access=
the order information. In the parameters of the action, provide the XML sc=
hema for the Storefront product.
Every Storefront product has its own XML schema definition file (.xsd) tha=
t defines the product's printing options, such as the possible quantities, =
colors, and so on. Storefront automatically creates the schema when the pro=
duct is created, and gives the schema the same name.
When a customer places an order, Storefront creates an XML file according =
to the XML schema for that product and registers it in RBA. The XML file co=
ntains the specific printing options that the customer ordered.
In Prinergy, the Read XML action interprets the XML file =
and makes that information available within the rule set. The output action=
then puts that information into a JDF file and submits the JDF file to a d=
igital printer.
The digital print engine processes the file using the output actions that =
you include in your Storefront rule.
Triggering the production rule set
The following sections give an overview of the events and actions in a typ=
ical Storefront production rule. For detailed procedures to set up a Storef=
ront production rule, see the InSite Storefront System Administration G=
uide.
The recommended event to start a Storefront production rule set is the
You can also use the Order Item Set Status event as the t=
rigger event, and set the parameter to Accepted. When an o=
rder is accepted in Storefront, the production rule starts.
Reading the order
Attach the Read XML action to the trigger event to access=
the order information. In the parameters of the action, provide the XML sc=
hema for the Storefront product.
Every Storefront product has its own XML schema definition file (.xsd) tha=
t defines the product's printing options, such as the possible quantities, =
colors, and so on. Storefront automatically creates the schema when the pro=
duct is created, and gives the schema the same name.
When a customer places an order, Storefront creates an XML file according =
to the XML schema for that product and registers it in RBA. The XML file co=
ntains the specific printing options that the customer ordered.
In Prinergy, the Read XML action interprets the XML file =
and makes that information available within the rule set. The output action=
then puts that information into a JDF file and submits the JDF file to a d=
igital printer.
Adding output actions
Add the output actions that make sense for your Storefront workflow. The o=
utput actions that you include in your Storefront rule depend on what type =
of Storefront product you are setting up: whether customers will upload the=
ir own print-ready files, order static items from a catalog, order variable=
items from a print catalog and personalize them, or order inventory items.=
For example, you might add one or more of the following actions:
You can override some of the settings with information from the Storefro= nt order. For example, you can override the job name and quantity.