Job Management

In uProduce, a job is a production operation. uProduce allows you to create different types of jobs: print, proof, port, email, etc.

In the Job Center you can create jobs, view the status of all jobs that belong to a specific customer, manage these jobs (for example, abort or delete a job) and access the job output (a print output file, an email, etc.).

To access the Job Center, click the Job Center button of the navigation bar.

The Job Center page provides information on the print, email and HTML jobs sent to production, as well as ICP Port jobs, in all accounts the current user has permission to see. The page is divided into the following panes:

• Job list

• Job filters

• Job details

Job list

The jobs list shows the main job details and allows you to perform various management operations using the buttons at the top of the pane.

To create a job, click New at the top of the pane. This opens the Create Job page, where you can define a job of any type and submit it. For details, see Creating a Job.

The list provides the following options and details on each job:

• ID: The unique identifier of this job in the uProduce system.

  Note: When a job is split to batches that are processed in parallel, all batches share the same job ID and appear as a single job in the Job Center.

• Status: The job’s production status - Waiting, In Progress etc.
  For a description of the possible statuses, see Job By Status.

• Information icon: if there is any special information concerning this job, one of the following icons is displayed:

  • Indicates a message, providing useful information that does not call for an action (for example, notifies that a PDF On Demand has been generated for a specific recipient, or provides a summary of the job production notes).

  •  Indicates a warning concerning a job that was completed according to the processing policies, but has issues the user should address (for example, missing assets; or an email batch that failed for a specific recipient).

  • indicates an error, describing a problem that caused the job to fail (for example, an error in the plan file).

    Clicking the icon opens a pop-up window, listing all messages generated for this job, with the relevant message selected.

• Name: the name of the document, port or email activity used to produce this job.

• Type: The type of this production job, which may be one of the following:

  • PRINT <Output Format>: A job that generates an output file for printing (known as the print output file) in the specified output format — for example, PRINT PDF, PRINT PDF/VT-3 or PRINT PNG. For the full list of print output formats, see Production.

  • PROOF <Output Format>: A job that generates an output file for proofing in the specified output format: PDF, Interactive PDF, JPG, PNG, EPUB (Fixed Layout) or EPUB (Reflowable).

  • DOWNLOAD DOCUMENT: A job that generates a document package (DPKG).

  • DOWNLOAD CAMPAIGN: A job that generates a campaign package (CPKG).

  • PROOF SET: A job that generates a proof set.

  • BATCH: A job that produces HTML output for a batch of recipients.

  • PORT: Represents an Interactive Content Port (ICP), used to provide live recipient data to applications and websites. An ICP allows you to both receive and update recipient information. It is used to provide data for personalized websites and to uCreate Connectivity.

  • SYSTEM PORT: A port that belongs to a Circle campaign. It is the same job type as PORT, listed under a different name.

  • ON DEMAND PRINT: Represents an InDesign or XLIM document that has been placed online, and can be used by uProduce to generate HTMLs On Demand.

  • ON DEMAND <Output Format>: Represents a document that has been placed online, and can be used by uProduce to generate output On Demand. The output format is appended to the type, so an HTML or TXT document placed online appears as ON DEMAND HTML.

  • EMAIL SEND: An email batch that has been sent to the campaign recipient list (or to some recipients on this list).

  • EMAIL PREFLIGHT:An email batch that has been validated: uProduce has gone through all production steps, except for actually sending the email to the campaign recipient list (or to some recipients on this list).

  • EMAIL TEST: An email batch sent to an email address that serves testing purposes.

  • TRIGGERED EMAIL: An email triggered by an event on a website (Page Load, Self-Registration or Referral). This job is automatically created once a triggered email is sent from a website. If the email activity on which the triggered email is based has been modified or deleted, the job will be marked as completed and the next time a triggered email will be sent, a new job will be created.

  • FLAT: A job that generates a CSVX file, containing the ADOR object values for each record on the recipient List.

  • EXTERNAL: A job containing tracking information on another job that was not performed by uProduce (for example, a dynamic print job produced by uCreate Print).

  • TASK: A background task the server ran on its own, rather than a production job — for example, generating a report, or hosting or exporting a data source. A task has no campaign, so the Link to Campaign icon is not shown for it.

• Started: The date and time on which this job’s production has started.

• User:The name of the uProduce user who submitted this job.

• (Resubmit job): Runs the job again. Clicking the icon opens the Create Job page, populated with the job's properties, where you can make changes before resubmitting the job. For details, see Creating a Job.

  Note that in case of a sub-job created from a split job submission, the resubmit will use the range of the sub-job and not of the original job range.

  This icon appears only for jobs that can be resubmitted: PRINT, PROOF, PROOF SET, FLAT, EMAIL SEND, EMAIL TEST and EMAIL PREFLIGHT jobs. It is not shown for other job types, such as PORT or DOWNLOAD CAMPAIGN.

• (Link to Campaign): Click the icon to go to the campaign for which this job was produced (by default, this link shows the documents page).

  This icon is not shown for a job that has no campaign, such as a report task, or for a job that belongs to a Circle campaign.

Notes:

• To download the job output, click its status icon . The download window opens for every completed job, and tells you when the job produced nothing to download.

• To stop the production of a selected job, click Abort.

• To remove jobs, select them using the checkboxes at the left of the list and click Delete. This deletes the jobs together with their output files, and cannot be undone.

Job filters

The following image provides a closer look at the Job Filters pane of the Job Center.

You can filter the Jobs List by status or account.

Job by status

Select All Jobs to list every job you have permission to see. This is the default. To narrow the list, select one of the following job statuses instead:

• Waiting : a job that is currently in the waiting queue, and will be processed based on its priority.

• In Progress : a job whose production is currently in progress.

• Suspended : a job whose status is online and whose type is either PORT or ON DEMAND PRINT, which a user has put temporarily on hold. Jobs are suspended in order to depute the campaign or to prevent access to a website.

• Online : the status of one of the following job types, as long as they are available: PORT, and ON DEMAND PRINT and ON DEMAND HTML.

• Completed : a job that was produced successfully.

• Failed : a job whose production has failed.

• Aborted : a job whose production has been canceled by the user.

Note: If a job is associated with other jobs, the job’s status icon includes a plus sign. For example, if you produce an EMAIL SEND job, whose body includes a link to a PDF, the each job’s status icon will have a plus sign:

• The status of a completed EMAIL SEND job will appear as follows:  

• The status of an ON DEMAND PRINT job will appear as follows:

Job by account

You can filter the display by showing only jobs that belong to a specific uProduce account. To apply the filter, click the name of the relevant account.

Job details

The Job Details pane at the bottom of the Job Center presents the full job ticket — every setting the job actually ran with. To open it, click a job’s name in the jobs list.

The details are organized into sections. A section appears only when it applies to the job, so most jobs show a handful of the sections rather than all of them. Individual values behave the same way — they are listed only when they have something to report. A job that ran without a job ticket, such as a background task, shows only Status, Production Metrics, Overview, Additional Info and Export.

Sections

Section	What it shows
Status	The job’s production status and, while it is still running, what it is doing; the highest message severity it produced; when it was submitted, started and ended; how long it took; and which machine and InDesign instance processed it.
Production Metrics	The record range produced, the estimated and processed record counts, generated pages, click charge, output size and total file count. Records per minute is added for completed jobs of more than 100 records. A job that was split into batches also shows the split and turbo ranges alongside the original range. Output Size and Total File Count are fetched after the rest of the pane, so they may read Loading for a moment.
Overview	The job ID and name, its type and output format, the account, campaign, campaign type, creator, document, email template and hot folder it ran for, its place in a job hierarchy, and any comments submitted with it. A job submitted through the uProduce REST API can also carry a container ID, which is listed here.
Job Execution	The priority the job ran at, its turbo production setting, whether a completion email was triggered, the URLs the job reported its progress to, and its auto purge time. A job submitted through the uProduce REST API also shows the request ID the caller sent with it.
Job Metadata	Custom job metadata submitted with the job ticket. Nested metadata is listed as Group / Value.
Job Tracking	The touchpoint the job was associated with, and what was tracked: events, content object values and link clicks.
Data Recipients	Which recipients were produced: the input type, the port, and each recipient data source with its filter, sorting, range and field mapping, and whether the data source is deleted when the job ends. How the job was split into batches is listed at the end. A port that reads and writes single records also shows the four queries it uses to do so. These queries can only be set through the uProduce REST API.
Data Schemas	The data source bound to each schema the plan draws on, and whether that data source is deleted when the job ends.
Data Field Customizations	Recipient field values that were overridden for this job.
Data Campaign Recipient Fields	Campaign recipient fields submitted with the job ticket, with their values.
Data Assets	How assets were resolved: the resolving mode, and the asset sources used. A port job also shows the prefix given to the assets’ web URLs and the target media. A job that asked uProduce Connectivity to fetch its assets on demand shows that too; this can only be set through the uProduce REST API.
Data Friendly URL	The domain, folder and landing page used for the personalized URLs, whether the recipient ID was added as a prefix, and whether a redirect was used.
Data IDs Filter	A file of recipient IDs used to include or exclude recipients. This filter can only be set through the uProduce REST API.
Data Online Documents	The documents placed online for this job. Each links to the job that hosts it.
Logic Plan	The plan the job used, whether it ran in trivial mode, and any content object filters applied.
Logic Customizations	Content objects, variables and user views whose expression was overridden for this job.
Logic CAN-SPAM Content Objects	The CAN-SPAM values applied to an email job.
Template Design	The document that was composed, its type, its web resources path and resources folder, and whether campaign fonts or a custom fonts folder were used.
Template Email Context	Whether the message was transactional, its subject, and the subject’s character set.
Template Email Sender	The sender display name and address, and the reply-to addresses.
Template Email Recipients	The To, CC and BCC addresses the message was sent to.
Template Email Content	The documents used as the message body and alternate body, and their character sets.
Output Files Specification	How the output file was named and whether the job ID was appended to it, the number of copies, whether a separate file was produced for each recipient, whether assets were included, whether the output was packaged, and whether a recipients data file was produced and with which delimiter.
Output Format Options	The settings that go with the output format, which is named in the section heading — for example Output Format Options (PDF). The PDF family shows the job options, compatibility level, standards compliance, interactive elements and transparency handling; JPEG and PNG show the resolution and grayscale; VPS, VIPP, PPML, VDX and PostScript show embedded assets and resources, the cross-job cache mode and the document set per recipient. Interactive PDF also shows the document language passed to screen readers.
Output PDFVT Recipient Attributes	The PDF/VT Recipient Attributes configured for the job. Each attribute is listed as Category / Field with its fixed value or its source content object.
Output PDF Security	Whether an open password or a permissions password was applied, and which actions were disallowed. The passwords themselves are never shown.
Output Liquid Layout	The page width and height the liquid layout was applied at.
Output Bleed & Marks	Whether the document’s own bleed definition was used, or the bleed values that were applied instead; which printer marks were added, and their offset and weight.
Output InDesign Scripting	The initialization, per-record and final scripts, and any user data, passed to InDesign. These scripts can only be set through the uProduce REST API.
Output Production Policies	What the job was told to do about missing fonts, missing assets, missing styles and text overflow, and about the output file size limit when that policy was changed from Ignore.
Output Delivery Provider	The delivery provider that sent an email job.
Output Delivery Validation	How thoroughly the message was checked, whether a preflight pass ran, and the thresholds that would have stopped it.
Post-composition	Every post composition operation the job ran, in the order it ran them, with the operation type in brackets. An operation defined in Settings links to its settings page; one defined in the job ticket itself lists its properties instead.
Legacy Options - Filler Pages	The filler page action and method, and where the pages were inserted.
Legacy Options - Imposition	The imposition applied through the deprecated Imposition section of the Process page.
Legacy Options - JDF	Shown when a JDF file was created through the deprecated Legacy JDF section of the Process page.
Legacy Options - Destinations	The copy, FTP and print destinations set in the deprecated Legacy Operations section of the Process page.
Legacy Options - Metadata per record	Shown when every readable content object of the plan was written into each recipient’s metadata.
Additional Info	Further information reported by the production engine, shown as plain text or as formatted XML.
Export	Links to download the job ticket. See Download the job ticket.
Output Files	Each file the job produced, with its size. Click a file name to download it. A file produced in a subfolder is listed as subfolder/filename. The section lists 50 files at a time; click More to list the next 50. It is shown last, and only for a completed job that produced output files.

Download the job ticket

The Export section provides four links:

• Download JSON

• Download Full JSON

• Download XML

• Download Full XML

All four download the same job ticket, in the requested format. The Full downloads also include the messages the job produced and the list of files it wrote. This is useful when you need to capture or share the exact settings a job ran with, for example when reporting a problem to support.

The downloads are also the reliable way to see the structure that post composition operations read from. The XML is what the Create Job Definition File (JDF) operation’s XSLT transforms, and the JSON shows the paths you can use as output naming tokens in the other operations.