XML entitlement example

The following example is an ADI XML document that might be passed to the XSL processor from the rules evaluator during the evaluation of an authorization rule.

The document contains two containers: JohnSmith and AmountReqd. The attribute value of the container JohnSmith is defined in XML. The AmountReqd container is translated to XML from an incoming string application context attribute. The container JohnSmith is an entitlement and the container AmountReqd is an item of transaction context.

The authorization rules evaluator automatically encompasses all the data under the XML top-level node declaration XMLADI when the ADI XML document is created. This top-level element was added for clarity. The XML document that is passed to the evaluation routines by the authorization rules evaluator is as follows:

<XMLADI>
  <JohnSmith>
    <CreditCard>
      <AcctNumber>0123456776543210</AcctNumber>
      <Limit>10000.00</Limit>
      <Balance>2000.00</Balance>
    </CreditCard>
    <MileagePlus>
      <MemberStatus>100k</MemberStatus>
      <CardNumber>12345678</CardNumber>
    <MileagePlus>
  <JohnSmith>
  <AmountReqd>500.00</AmountReqd>
</XMLADI>

When referencing a particular ADI item in the XMLADI document available to a rule, the XPath path specifier can begin from the container name of the XML element. For example, the name might be JohnSmith. The default template rule matches the /XMLADI element automatically. If the callers want to specify their own template match statement explicitly, they can do so.

In this example, the ADI container names are JohnSmith and AmountReqd. See Format and constraints of rules.

Parent topic: XML access decision information