Reviewers

Topics:

Many reviewers are available to assist you in reviewing messages. Some common ones are described in this section.

EvalWalk

Class name: XDEvalReviewer

Implements the iWay Active Document within an agent.

The exit evaluates each attribute and entity value in the document, executing all iWay functions. For example, a node:

<node1/ATR1="_ISERROR()">SREG(ip)</node1>

might become:

<node1/ATR1="false">123.45.678.910</node1>

Parsing

Class name: XDFlateToXMLReviewer

Parses a flat document into XML. This reviewer is usually needed only in a flat channel, as in XML [non-flat] channels such parsing is automatic before the first reviewer is executed.

QA

Class name: XDQAReviewer

Emits a flattened copy of the input document to a file named in the init() parameters. The business agent outputs the document (XML or flat) either in QA mode or always, depending upon the setting of a parameter. If the QA mode is not on (set in the Diagnostic System Properties Console Configuration Page) and the always parameter is not set, this business agent acts as a move business agent. This business agent is designed to work as a chained business agent during debugging. The document and all special registers are included in the output.

Registers

Class name: XDSregReviewer

Sets or deletes one or more special registers under program control. The registers can be set to any of the supported scopes (message, flow, or thread) and can be of any defined category (hdr [header], user, or doc). Normally, registers cannot be set above the Message scope. The value to be assigned to any register can be an iFL expression which is evaluated when the service is executed.

The order of register assignment is undefined. You cannot, for example, assume that the following two assignments:

first

10

second

sreg (first) +1

will be executed such that first is assigned before second. The results of such a setting strategy is unpredictable. If such a setting is required, you must use two copies of the register agent.