Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 18 529618-002
HistoryRecord
The HistoryRecord class identifies a single record to be inserted into another table every
time that the parent record is inserted or replaced. The purpose of a HistoryRecord is to
track changes in the parent record; later in this document, you’ll see an example of
HistoryRecord used to track schedule changes for line items in an order. (See “Metadata
Excerpts: An IDoc Definition.”)
Because the whole point of a HistoryRecord is to be preserved over time, a
HistoryRecord is not deleted as part of a delsert operation. (See “Update Options,” below,
for a description of what a delsert is.)
HistoryRecord is a subclass of RelatedRecords, so you can put a HistoryRecord into an
array of RelatedRecords.
HistoryRecord must have at least one parameter, which specifies either the name of the
table where the history record must be inserted (tableName) or an enriched record. You
may also specify an enrichment.
For HistoryRecord constructors, see the Javadoc for HistoryRecord.
Update and Query Options for Document Definitions
The generalized syntax for the call to the superclass, in a document definition, is
super(documentRecord(), " DOCUMENTNAME ", " update-options ", " query-
options ");
where
DOCUMENTNAME is the name of the document type.
update-options is a blank-separated list of options that apply to insert or update
transactions.
query-options is a blank-separated list of options that apply to queries.
Update Options
The possible update options for document definitions are
AUDIT_INBOUND. Causes the Director to create an audit record whenever a document
of this type is loaded into the data store. The inbound document itself is included as an
audit detail. For more information, see the document called RTID Security and Auditing.
AUDIT_OUTBOUND. Causes the Director create an audit record whenever a document
of this type is loaded into the data store. The outbound document (consisting of any