Page tree

Open a rule set in Rule Debugger to select a specific execution of the rule set and to view details of the execution to determine where and why a problem occurred.

  1. Open the rule set whose execution history you want to view.
    Select the desired rule set in the Rule Set Library list or the Enabled Rule Sets list, and select File > Debug or click Debug .
    Note: You can start Rule Debugger only by opening a rule set.
  2. In the Rule Set Execution History pane, select the execution whose events and actions you want to view in detail.
    The Execution Path pane lists each rule in the rule set that started during the selected execution.
  3. Perform either of the following actions:
    • In the Execution Path pane, select the rule whose event and action information you want to view. The corresponding action is highlighted in the workspace with a green square so that you can see exactly where in the rule set the action occurred.
      Tip: Press the up or down arrow key to change the selection in the Execution Path pane. The corresponding selection in the workspace is automatically updated.
    • In the workspace, click the action whose details you want to view. The corresponding rule is selected in the Execution Path pane.

    Tip: If the rule set includes a loop (for example, to create 10 new jobs), the same action may be listed multiple times in the Execution Path pane, with a different number in the Repetition column for each time the loop started. As well, if you click a flow that occurred multiple times (in a loop) in the workspace, a menu appears, prompting you to select a specific repetition. In either case, select a specific repetition of the action to view the properties and values for that particular repetition. When you select one repetition of an action, it is highlighted in dark blue in the Execution Path pane, and all other repetitions of the same action are highlighted in light blue. Press Ctrl+down arrow or press Ctrl+up arrow to change the selection in the Execution Path pane to the next or previous repetition. (You can also right-click a repetition and select Jump To Previous Execution or Jump To Next Execution.)

    The Event and Action tabs at the bottom of Rule Debugger display information about the selected instance of the action and the event that triggered it—that is, the evaluated data for the selected instance of the event/action pair. For example, for a Refine Input File action, the Input Files > Name property will have a different value (that is, a different input file name) for each execution. Information on the Action tab is for the selected action. Information on the Event tab is for the event that triggered the action (either a root event or an event resulting from a previous action).

  4. View the evaluated data for the action to analyze this instance of the action.
    For example, you might select the last action that was started in the rule set and view its values to determine why the action did not complete successfully.
    Rule Debugger cannot tell you why an action did not complete successfully. Instead, Rule Debugger displays information about the actions that occurred in a given execution of a rule set and the values that were assigned to each action's properties, for each execution of the rule set. You must interpret the values to determine why a problem occurred.
    For example, suppose that a particular execution of an Import Imposition action failed. You might notice for that execution that the action's Imposition File > Path Name property has an evaluated value that specifies a particular .pjtf file. You might then check the path to ensure that the file exists in the specified location and that there is no problem with the file.
  5. If you can diagnose the reason for the problem, open and fix the rule set. If you are unable to diagnose the reason for the problem, export the rule set's execution history to a Kodak service representative for analysis.
  • No labels