Ticket items are available at order level and at job level. At order level, the items define the commercial information. For example the order name, the delivery address, the billing information, etc. A ticket item can be used at order level or at job level, but not at both levels.
You can edit the ticket items both at order level and at job level.
Ticket items are available at order level and at job level. At job level, the items contain the requested print settings and any remarks of the customer. A ticket item can be used at order level or at job level, but not at both levels.
You can edit the ticket items both at order level and at job level.
A product defines which items are available in the job ticket and order ticket. It can also define which files can or cannot be added to a job. The system administrator configures the product in the [Product and order editor].
The order manager can access the [Order view] and the [Job view].
You can manage and process the orders in the order view.
The order view displays the list of orders on the left. Select an order to display list of jobs belonging to that order, the workflow steps and the order details.
You can add, edit and remove jobs from an order, on behalf of the customer, as long as the order is not accepted and the payment is not yet completed. You can cancel an order on behalf of the customer, as long as the order is not accepted.
The operator can access the [Order view] and the [Job view].
You can manage and print the jobs in the job view.
The job view displays the list of jobs. The jobs are displayed without reference to the orders they belong to. Select a job to display the files and the job details.
You can add or remove files from a job, on behalf of the customer, as long as the order is not accepted and the payment is not yet completed. You can prepare the job. For example, you can preflight and page program the merged document. And finally, you can print the job.
Displays the state of the job according to the workflow. The steps of the workflow are defined by buttons in the order details.
Displays the state of the job according to actions performed on the job. For example, action [Preflight] can result in [Internal job state] = [Preflighted] or in [Internal job state] = [Preflight error].
The operator of the print room is responsible for preparing and printing the jobs.
The order manager communicates with the customer, manages the orders, and assigns orders to operators.
The approver is responsible for the budget. The approver can approve or reject an order based on the quotation.
Some ticket items are used by the page program application when you page program the document. For example, [Orientation and binding edge]. These job ticket items are marked with a blue dot in the job ticket. Some ticket items are used by the printer when you print the document. For example, [1-sided or 2-sided]. These job ticket items are marked with a blue square. Some job ticket items are only valid for specific printers.
The system administrator defines which ticket items can be used by the page program application and/or the printer.
The preflight operation checks if any rules are violated in the PDF file(s). The set of rules is fixed. Some of the rules can be configured in the [Configuration].
If enabled, the automatic preflight operation is applied when a customer submits an order. The automatic preflight operation allows you to fix the violations according to the configured rules or cancel the operation with that document.
A preflight report and an annotated file are generated. The preflight report shows a summary of the problems that have been found. The annotated file shows the complete document with the location of any found problems and fixes. The manual preflight operation automatically fixes the violations according to the configured rules. Some problems are detected by the preflight operation, but cannot be fixed automatically. It is recommended that you fix these problems manually before you print the job.
The preflight report for the files of the job is also available for the customer in the web shop.
For repetitive jobs it is possible to select one or more templates with pre-defined settings. They will prepare a job using PRISMAprepare in the background. These templates are called automation templates. They can be applied manually or automatically. The benefits of the automation templates are:
Saving time and minimizing errors as the layout is standardized and preparation is done in the background.
Consistent layout in a multiple operator environment.