Manual Update V

Transcription

1 Manual Update V This document contains the latest information about PRISMAproduction, which has not been integrated into the handbooks so far or which we want to emphasize as changes. Dieses Dokument NICHT mit OpenOffice bearbeiten! Die Formatierungen sind zu komplex!!! Das verantwortliche Labor wird durch die Hervorheben Funktion gekennzeichnet. Zum Ausdrucken bitte unter Menü "Extras - Optionen - Ansicht" Hervorhebung deaktivieren (auch diese Info wird dann unsichtbar). Farbcodes in der Reihenfolge der Labore: SWD21 SWD22 SWD23 GSf SWD11 SWD12 SWD13 Mixed Open / To be done Manual_Update40204.doc Page 1/14

2 Contents CONTENTS INSTALLATION OF THE SYSTEM ADD-ON FUJITSU_HW_OBSERVER AFP PREFLIGHT AND COLOR MAKE READY VIEWER AND VIEWER RIP SERVER VRS Installation Viewer Configuration VRS Status Messages PRISMA - COMMON INFORMATION ACCOUNTING Accounting administration General Consumables configuration TICKETRULES ENHANCEMENTS Parameter Search feature Command line scripts ticketrulesreload ticketrulestest Notification of rule changes PRISMA - POD MODULES PROFESSIONAL DOCUMENT COMPOSER Generalization of position logic for identical copies Support of monochrome appearance (PEC) Particularity when using pre-rasterized data (PPO) CIS INDEX LENGTH CALCULATION Manual_Update40204.doc Page 2/14

3 Installation of the System 1 Installation of the System 1.1 Add-On Fujitsu_HW_observer Using a Fujitsu or FSC server it is possible to install the PRISMAproduction Add-On software Fujitsu_HW_observer. 1.2 AFP Preflight and Color Make Ready Two new actions have been introduced: Change RGB grays to highlight grays that replaces near by gray RGB colors with highlight colors using only black toner to avoid rich black resulting from color management; Optimize internal medium maps that moves all internal medium maps into the FORMDEF and eliminates duplicate medium maps. For details please see the User Guide. Page 3/14

4 Installation of the System 1.3 Viewer and Viewer RIP Server VRS Installation The new PRISMAproduction Viewer will be used for APA, POD and LCDS jobs targeted to IPDS printers by installation default. The VRS can be attached to any PRISMAproduction network card. Note: After installation of PRISMAproduction the new PRISMAproduction Viewer is the default viewer in the All Jobs list for APA, POD and LCDS jobs targeted to IPDS printers and in the PJM for files of type AFP Format in APA tickets. Make sure to install the Viewer RIP Server and configure the respective Viewer Host IP address in Configuration / System / System and Job Parameter. Otherwise, viewing in the All Jobs list or in the PJM is not possible with the Standard Viewer and an error message Viewer RIP Server is not online will be displayed. However, viewing in the ALL Jobs list is still possible using View Job in PDV button or context menu. Page 4/14

5 Installation of the System Viewer Configuration The Viewer configuration option Preferred Viewer to choose between Standard Viewer or PDV for the All Jobs List has been removed from the PRISMAproduction Configuration, System, System and Job Parameter: Page 5/14

6 Installation of the System Instead, it is now possible in the All Jobs List to select the Viewer or the PDV for each job either by the Viewer Button or by the context menu: Page 6/14

7 1.3.3 VRS Status Messages The current status of the VRS will be logged in the messages: 2 List the installed SCSI boards including the attached devices: Use the LINUX control center, choose 'Information', sub menu 'SCSI', or execute the command line "cat /proc/scsi/scsi". 2.1 Accounting Accounting administration General The structure of the database is available at the moment only by special requests from the service department. Page 7/14

8 2.1.2 Consumables configuration A new Consumable type Paper Roll + Stack has been introduced on a separate Consumables Table. 2.2 TicketRules enhancements Parameter Search feature The TicketRule configuration supports parameter search with adding or editing of conditions, settings and messages. The former Paste-To-Value feature is therefore omitted. See the following example for editing a condition. To change the parameter, click on the Find button on the right of the parameter text box. This would open following window: Hier wird ein neuer screenshot nötig, wenn die Description nicht mehr Paste To Value enthält. Page 8/14

9 In the left bottom window all parameters can be found in form of a tree with section names as branches and the corresponding key names as leaves. In the right bottom window the description of the currently selected parameter is shown. Page 9/14

10 Entering text into the Filter text field at the top would filter the parameter tree. Only parameters that contain the string in the Filter text field in the section or in the key name are shown any longer. The filter works case insensitive. Separate the section and key in the Filter text box by a dot. It is also possible to filter for all parameters that contain the filter string in the description or in both, parameter name and description, by selecting the appropriate check boxes. Page 10/14

11 If at least one variable is defined, it is also possible to list all defined variables. If the condition, setting or message resides in a foreach loop, then also the references to the headers of the appropriate value table can be listed. The filtering can be done over the names of parameters, variables, headers of value tables and their descriptions. If finally one entry is selected, the Ok button is enabled. Clicking on it would close the window and enter the selected entry in the parameter field. If the Find button right of the value text field is clicked, the same Find parameter window opens. After clicking the Ok button the selected entry is added to the value text field at the current cursor position. If the cursor was not positioned in the value text field before the Find parameter window was opened, then the selected entry is always added at the end of the text. The former Past-To-Value feature has become obsolete and is omitted. Page 11/14

12 2.2.2 Command line scripts Two new command line scripts were added in /u/prismapro/bin ticketrulesreload Syntax: ticketrulesreload <rules.xml> [<ticketparameter.dat>] [<valuetable.csv>... ] With this script a new set of ticketrules can be loaded. A set of ticketrules consists at least of an xml file that contains all rules definitions. If own defined parameters are used, also the appropriate ticketparameter.dat file has to be loaded. And if value tables are referred in the rules, also these value tables have to be loaded. Note: Any formerly saved rules are overwritten by this command ticketrulestest With the other new command a specific existing rule can be tested for a specified ticket. Syntax: ticketrulestest <rulename> <inticket> <outticket> <jobid> The script requires a rule and a test ticket (<inticket>) on which the rule shall be executed. It also requires a path for the resulting ticket (<outticket>) and a jobid. The jobid will be shown in all messages produced by the execution of the rule Notification of rule changes If the currently saved setting of rules is changed by another user or by the command line interface, following window will automatically pop up in all open TicketRules configuration windows. By selecting No it is possible to save the currently done changes on the server and to overwrite the last loaded rules. Hier werden evtl. noch die Antworten zu Save, Discard, Cancel geändert, so dass ein neuer screenshot nötig wird. Page 12/14

13 PRISMA - POD Modules 3 PRISMA - POD Modules 3.1 Professional Document Composer Generalization of position logic for identical copies By a generalization of the position logic in the new PDC differences to the old PDC can occur in mode Identical Copies and 2Up&Identical Copies. In theses cases the user is asked by a message to check the positioning Support of monochrome appearance (PEC) In version V4.02 converter supports a functionality which allows to print colored pages black/white. This information is captured from input document by new PDC and transferred to print sheets. If impositioning is used each logical page of a print sheet is scanned and then monochrome appearance of the sheet is calculated. In this connection the rule is valid that a print sheet can be printed only black/white if all logical pages of the sheet have the monochrome appearance attribute. In all other cases the print sheet must be printed in normal mode Particularity when using pre-rasterized data (PPO) Another feature of the converter in V4.02 is the pre-rasterization of data in printer. This feature offers a better printer performance. However it implicates some side effects. In opposite to objects generated in versions before the new pre-rasterized objects are encapsulated opaque objects. These cover images below them. To guarantee a reasonable functionality PDC places those objects at first on a page and then places transparent objects. Due to that fact the resulting print image can differ to the same application with not prerasterized data. Especially when using pre-rasterized overlays this must be considered (normal overlays are placed on a page in the end of the process). Page 13/14

14 CIS 4 CIS The parameter CASECTRL has a new option 4:: = at first the resource name and the extensions are read in upper case and afterwards in lower case and at last "AsIs" (combination of "0", 1 and "2"). Index length calculation 1. There has been introduced the ability to pick the length of a field from the data (Merlin CR ). This is can be used to create TLE based on a variable length field from MODCA file. (Die Merlin-Nummer natürlich nicht ins Handbuch!) Parameter FIELD: extension of FIELD parameter in case of searchstring possibility to determine the indexlength using data and calculate it considering a variable FIELD (fieldname, { record, column, length } { literal value [, LIT ] } { x literal value [, LIT ] } { _variablename [, VAR ] } { attributename, ATT } { x attributename, ATT } { searchstring x searchstring, offset, indexlength (offslen,sizelen,calcval) }) offslen: signed number of the offset of the searchstring position where CIS should take the indexlength sizelen: absolute number of the number of bytes CIS should take as indexlength calcval: signed value which CIS should use to calculate the indexlength Page 14/14