XML document attributes

Document attributes identify specific content in the documents when they pass through the network. This specific content in the document may be of your interest in the document. For example, a purchase order number or the account number of a purchaser. You can write specific logic to process a document with a certain purchase order after you extract the attributes of your interest in the document.

The following points are a few reasons to extract document attributes:

• To use extracted attributes as a criterion for using a particular processing rule. For example, if you want to use one processing rule if the sender is Partner A and another processing rule if the sender is Partner B, you would extract the system attribute SenderID. Or if you want to use a particular processing rule when the receiver is Partner C and the total order amount is greater than $10,000, you will extract the system attribute ReceiverID and the custom attribute Total_Order_Amount.
• To perform certain processing actions that require extracted attributes. For example, if you want to deliver a document to the receiver partner, you would extract the system attribute ReceiverID. If you want to verify the digital signature of an XML document, you would extract the system attributes SignedBody and Signature.
• If you want to pass extracted attributes for specific type of analysis. For example, if you want to generate a report on the purchase order quantity for a particular sender from a particular receiver, and classify them as platinum, gold, and silver partners, you would extract the custom attribute PO_Quantity and the system attributes SenderID and ReceiverID and write a business logic to further categorize them.

RNIF attribute behaviors

When you receive an HTTP header with the prefix x-RN- for an inbound RNIF message, webMethods B2B creates a document attribute. You can view this RNIF-specific attribute in the attribute tab of the Transactions page. The RNIF-specific custom attribute is case-sensitive.