OnlineSessionType

This includes all the parameters necessary to request and identify a session between two applications.  Information within this component includes information like the userid, account, usergroup, URLs to which the reply/ cart should be redirected and so on.

This also includes the ReturnURL tag to identify the result URL that is returned by the target system as a result of processing the Request.

See http://www.openapplications.org/oagis/9.

Complex type information

Content

• Sequence [1..1]
  1. SessionID [0..1]    The SessionId uniquely identifies the session that makes the Request
  2. User [0..1]    Identifies the user of a given system.
  3. RequestDateTime [0..1]    This is the DateTime at which the Request for the OnlineSession is initiated by the Requesting application
  4. ResponseDateTime [0..1]    This is the DateTime at which the Response for the OnlineSession is generated by the Target application
  5. ReplyURL [0..1]    The ReplyURL is used to specify a URL that can be used by the provider to post any information collected by the requester in the session. An example of usage of this is to post the contents of a cart created by a buying application user from an external catalog.
  6. RedirectURL [0..1]    The RedirectURL can be used to indicate a URL to which the Requesting application can be re-directed once the session initiated by this connection is completed. The session completion event is not recorded in this transaction.
  7. ReturnURL [0..1]    The ReturnURL element is specified in the Show ECatalogURL by the target application. It contains a URL reference to which the requesting application is pointed. This will not have a value in the Request (Get) Message
  8. RequestLanguageCode [0..1]    The RequestLanguage element can be used by the requesting system to indicate the desired language of the catalog or application to which session will be initiated upon receipt of the Show URL transaction. For instance, application A wishes to ‘punch out’ to external system B’s online Dutch-language catalog. System B supports numerous languages, but will validate the value of the 'RequestLanguage' element and return the appropriate URL to direct application A to the Dutch site
  from group FreeFormTextGroup
  Sequence [0..1]
  1. Description [0..*]    
  2. Note [0..*]    
  9. OriginatorParty [0..1]    Identifies the party that originated the purchase of the goods, service or payment.
  10. RecipientParty [0..1]    Identifies the recipient of the goods or services.
  11. CatalogParty [0..*]    Identifies the party whose catalog is used to purchase the goods or services.
  12. SearchTerm [0..*]    The SEARCHTERM data type contains information that can be used to perform an initial search on the destination’s application. For example, a requester might wish to view a supplier’s catalog but restrict the result set for only ‘ballpoint pens’. The requester would use this data type to perform this initial query.
  13. 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 by

• Element OnlineSession