9.0

with attachments in such projects. If the automation profile makes changes to a box that
has an attachment, the attachment is detached in the new revision, unless the Automation
Profile includes a QPSEntityModel mapping component for the attached article. If the
automation profile produces a new project rather than a new revision of an existing project,
all attached articles are detached unless they have corresponding QPSEntityModel mapping
components.
XML to QuarkXPress using XSLT
The XML to QuarkXPress using XSLT workflow lets you transform content from
QuarkXPress projects, QuarkCopyDesk articles, and XML sources into QuarkXPress layouts
with a QuarkXPress template and an XSL transform.
The output of the XSLT must be valid Modifier XML.
• Template: Choose a QuarkXPress project template.
• Transformation: Choose a transformation to be executed prior to the XSLT. You can use
the metadata inputs and outputs to handle any metadata that is involved. The other output
must be something that can be fed to the XSLT.
• Image Folder Paths: Specify the path(s) where any images required by the workflow can
be found. When the automation profile executes, the software searches these paths for
any images referenced in the transformation's XML output, attaches them to the layout,
and checks them into QPS (if necessary). Note that if you specify a path in the file system,
you must use a valid UNC path to which the Automation Services server has read access.
If Automation Services cannot locate a picture file, it substitutes a default picture with the
same name as the missing picture. The default picture can be found at [deployment
directory]\AutomationServices_Data\Resources\ProfileManagement\FallbackImage.jpg.
• XSL Transform: Specify the location of the XSLT file you want to use. When the
automation profile executes, the software executes this XSLT file on the output from the
transformation before rendering it as a QuarkXPress project.
This workflow currently supports only XSLT 1.0.
• Save Location: Specify where you want the final file to be put. If you check the file into
QPS, the transformation must supply the corresponding metadata in a QPSEntityModel
output. Note that if you specify a path in the file system, you must use a valid UNC path
to which the Automation Services server has write access, and the path must include the
name of the output project. Pictures are stored in a "Pictures" folder at the same level as
the output project.
If a transformation in an automation profile makes changes to an existing project and
then checks it in as a new revision, you need to be aware of how Automation Services deals
with attachments in such projects. If the automation profile makes changes to a box that
has an attachment, the attachment is detached in the new revision, unless the Automation
AUTOMATION SERVICES 9.0 WORKFLOW REFERENCE | 9
WORKFLOWS