OriginalApplicationArea

A copy of the ApplicationArea for the original BOD that was processed. Present either as additional reference information, or for use in identifying the BOD in situations where a BODReference is not known.

See http://www.openapplications.org/platform/1.

Element information

Content

• Sequence [1..1]
  1. Sender [0..1]    Identifies characteristics and control identifiers that relate to the application that created the Business Object Document. The sender area can indicate the logical location of the application and/or database server, the application, and the task that was processing to create the BOD.
  2. Receiver [0..*]    Identifies the intended receiver of the given BOD instance.
  3. CreationDateTime [1..1]    is the date time stamp that the given instance of the Business Object Document was created. This date must not be modified during the life of the Business Object Document.
  4. Signature [0..1]    If the BOD is to be signed the signature element is included, otherwise it is not. Signature supports any digital signature that maybe used by an implementation of OAGIS. The qualifyingAgency identifies the agency that provided the format for the signature. This element supports any digital signature specification that is available today and in the future. This is accomplished by not actually defining the content but by allowing the implementation to specify the digital signature to be used via an external XML Schema namespace declaration. The Signature element is defined to have any content from any other namespace. This allows the user to carry a digital signature in the xml instance of a BOD. The choice of which digital signature to use is left up to the user and their integration needs.
  5. BODID [0..1]    The BODId provides a place to carry a Globally Unique Identifier (GUID) that will make each Business Object Document instance uniquely identifiable. This is a critical success factor to enable software developers to use the Globally Unique Identifier (GUID) to build the following services or capabilities: 1. Legally binding transactions, 2. Transaction logging, 3. Exception handling, 4. Re-sending, 5. Reporting, 6. Confirmations, 7. Security.
  6. UserArea [0..1]    Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS.This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document through the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline.

Attributes

None

Used in

• Type ResponseVerbType
• Type BODType (Element BOD)
• Type AcknowledgeType via extension of ResponseVerbType (Element Acknowledge)
• Type ConfirmType via extension of ResponseVerbType (Element Confirm)
• Type ListType via extension of ResponseVerbType (Element List)
• Type RespondType via extension of ResponseVerbType (Element Respond)
• Type ShowType via extension of ResponseVerbType (Element Show)

Sample instance

<OriginalApplicationArea>
   <Sender>
      <LogicalID>normalizedString</LogicalID>
      <ComponentID>normalizedString</ComponentID>
      <TaskID>normalizedString</TaskID>
      <ReferenceID>normalizedString</ReferenceID>
      <ConfirmationCode>Always</ConfirmationCode>
      <AuthorizationID>normalizedString</AuthorizationID>
   </Sender>
   <Receiver>
      <LogicalID>normalizedString</LogicalID>
      <ComponentID>normalizedString</ComponentID>
      <ID>normalizedString</ID>
   </Receiver>
   <CreationDateTime>2000-01-01</CreationDateTime>
   <Signature>
      <!--any element-->
   </Signature>
   <BODID>normalizedString</BODID>
   <UserArea>
      <!--any element-->
   </UserArea>
</OriginalApplicationArea>