Incoming Documents

Incoming messages can be written in several formats. The raw content can be written as a stand-alone file or the content can be wrapped in XML as described in the previous section.

To control the format of the incoming message, use the Incoming Content Format menu and select Two-action only in the RNIF Host: RosettaNet tab. See RNIF Host: RosettaNet Tab. If Two-action only is selected, then all one-action PIPs will be written in the Original format and the two-action PIPs will follow the Incoming Content Format selection. If Two-action only is not selected, then both one-action and two-action PIPs follow the Incoming Content Format selection. If Original is selected in the Incoming Content Format pull-down menu, then the content is written in separate stand-alone files. If the pull-down selection is Wrapped XML, then the content is wrapped as specified in the previous section, with the content written as an inline XML fragment. If the selection is Wrapped CDATA, the content is saved as text within a CDATA section within the wrapper. If the selection is Wrapped BASE64, then the content is encoded as Base64 data.

For a wrapped incoming message, the following attributes are added to the root <pip> element for your convenience:

Element Description Attribute Description
<pip> Required.

Root element.

test This attribute is set to true for a test message and false for a production message.
    host The alias of the receiving VersaLex host.
    mailbox The alias of the receiving VersaLex mailbox.