Search

Help

Page 39 of 215. Showing 2,144 results (0.177 seconds)

  1. Prinergy Document Screen Manager

    screening was being specified in PostScript applications that calculated angles based on 0 at 3 o'clock and measured counter-clockwise. Prinergy, on the other hand … was being specified in PostScript applications that calculated angles based on 0 at 3 o'clock and measured counter-clockwise. Prinergy, on the other hand, has always
    Prinergy Tools 2.6Feb 26, 2026
  2. Prinergy Document Screen Manager

    screening was being specified in PostScript applications that calculated angles based on 0 at 3 o'clock and measured counter-clockwise. Prinergy, on the other hand … was being specified in PostScript applications that calculated angles based on 0 at 3 o'clock and measured counter-clockwise. Prinergy, on the other hand, has always
    Prinergy Tools 2.1Feb 26, 2026
  3. Output From PDF 1

    adjustments. Auto distribute evenly positions pages in a grid within each axis of the defined media. It creates variable gutter widths on the fly, based on the size … for the gutters, but variable height, that can be configured. This also means that it can be used with Roll fed layouts. Auto distribute can be used with N-up or Auto
    Evo 11Mar 23, 2026
  4. What you need to know

    In this activity, you will create and use temporary variables. For more information about variables, see the Variables chapter in the Prinergy Connect Workflow 6.1 Rules-Based Automation User Guide. What is a variable? Variables allow for the storage and later retrieval of data within rule sets. Types of variables
    Prinergy TrainingFeb 26, 2026
  5. Type and concurrency

    Access to variables is always serialized so no explicit synchronization is needed by the user as long as a variable of the appropriate type is used for the situation. Each variables type will determine the concurrency semantics in a given situation. For example, if a global variable is used to store a string
  6. Type and concurrency

    Access to variables is always serialized so no explicit synchronization is needed by the user as long as a variable of the appropriate type is used for the situation. Each variables type will determine the concurrency semantics in a given situation. For example, if a global variable is used to store a string
  7. Type and concurrency

    Access to variables is always serialized so no explicit synchronization is needed by the user as long as a variable of the appropriate type is used for the situation. Each variables type will determine the concurrency semantics in a given situation. For example, if a global variable is used to store a string
  8. Including the rule set name when reporting exceptions

    not be obvious which rule set an exception is originating in. With the introduction of rule set variables it is now possible to create a string rule set variable that contains the name of the rule set. The name of the rule set can then be included in the logging of the exception by referencing the rule set variable. To create
  9. Including the rule set name when reporting exceptions

    not be obvious which rule set an exception is originating in. With the introduction of rule set variables it is now possible to create a string rule set variable that contains the name of the rule set. The name of the rule set can then be included in the logging of the exception by referencing the rule set variable. To create
  10. Including the rule set name when reporting exceptions

    not be obvious which rule set an exception is originating in. With the introduction of rule set variables it is now possible to create a string rule set variable that contains the name of the rule set. The name of the rule set can then be included in the logging of the exception by referencing the rule set variable. To create