This chapter of the Claro manual is intended for system integrators and developers who want to integrate Claro in an existing workflow or with third party applications like editorial systems. A basic understanding of the Claro product and its features and options in general is a prerequisite to understanding this part. The tag descriptions are shorter than the explanation of the features in the main part of the Claro manual.
Jobtickets can be used to make channel settings more dynamic. Channel settings are overruled by the jobticket if the corresponding tag is present in the ticket. That allows you to vary certain parameters per image based on things happening outside the scope of Claro. Most commonly jobtickets are used to specify crop and size parameters per image. Output folder and file name are other good examples.
There is only one mandatory tag in a jobticket and that is the PathName tag, containing a path to the file to process. The most simple jobtickets have only that tag.
Export a channel, and you have the basic XML structure for jobtickets with almost all available tags. Almost, because jobtickets can also contain image specific actions that are not available in the normal channel settings like crop and rotation parameters.
Some channel specific settings like the channel-name and hotfolder cannot be overwritten by the jobticket.
A jobticket can be given to Claro in three ways:
- Copy it to the hot-folder of a channel;
- Use the WebServices interface (API);
- Use the generic Claro folder for jobtickets and use the “ProcessChannel” tag that specifies by which channel the image should be processed.
Check the example jobfiles that are available for download and the tag definitions available in “Claro integration options” (one level up from this page).Remarks
JobTickets are XML files and must have the extension .xml or .job.
Float values must be represented as n.n notation (where n is a numerical value).