Activating and Testing PDF Rendering on a Trigger

You can define a trigger so that when a promote event occurs, a PDF version of the file is automatically rendered.

See the Business Process Services Administrator's Guide for details on working with eService Trigger Program Parameters objects.

This task shows you how to:

Activate PDF Rendering on a Trigger

You can activate PDF renderingin on a trigger so that when an event occurs, a PDF file is automatically rendered.

  1. Create a properly named eService Trigger Program Parameters object.

    For example, to activate PDF Rendering prior to the promote event on WIP state in the Controlled Production Release Rev2 policy, create the object as follows:

    Name: PolicyControlledProductionReleaseRev2StateWIPPromoteCheck

    Rev: PDF Rendering.

    eService Method Name: mxMain

    eService Program Argument 1: ${OBJECTID}

    eService Program Argument 2: ${OBJECTID}

    eService Program Name: emxRNDEnqueue

  2. Promote the object to the active state.

    For example, in the Controlled Production Release Rev2 policy on WIP state, specify emxTriggerManager as the trigger program and PolicyControlledProductionReleaseRev2StateWIPPromoteCheck as the input.

Test the Activation

After activating PDF rendering on the trigger, you need to test it.

  1. Log in as any user who can view/promote documents.

  2. Select a document in WIP state and view its tree.

  3. Select the Lifecycle category. Use the green arrow to promote the document to Review state.

    The Rendering job is submitted in the background and the PDF file should be visible in the files list of the document after a while. The system load and the number of print/rendering jobs submitted will affect the wait time before you see the PDF file in the file list.