Files Received

This File rule (also referred to as AsFile) allows configuration to translate incoming data and insert it directly into the database. AsFile can also be configured to selectively insert records into the database based upon the data in the inbound SOAP message.  

The configuration for each File has two sections: XMLData and XSLT. The XMLData section assigns values to attributes prior to the transformation process. The XSLT defines how the information will be transformed.    

The XMLData section can be configured using the elements and attributes described below. The XSLT section transforms data according to a stylesheet. Each Attribute defined in the XMLData section that will be needed in the XSLT stylesheet must first be declared as a parameter in the XSLT.

Functioncall can also be configured using this web service. 

Refer to the Administration Overview | Files Overview section in the Rules Palette help system for additional information on configuring File and the XSLT section.

Parameter, Attribute and Variable are interchangeable terms depending on which section you are working with. An attribute in the XMLData section is called a parameter in the XSLT section.  

If a policy number is not provided in the Soap input XML, then a plan level AutomaticPolicyNumber rule override can trigger automatic generation of the number.

Files Received Elements/Attributes

Element/Tag

Definition

Attribute

Element/Attribute Value and Description

<File>

The opening and closing tag for the rule.

 

 

<RequestType>    

Optional element

This element defines the type of request received. This is currently used to define illustration type requests for which OIPA has a specific sequence of actions that it follows.

 

Illustration

This is the only allowed value.

<AssignAttributes>    

Required element

 

 

<Attribute>     

 

 

 

 

 

 

 

 

 

 

Required element

 

 

 

 

 

 

 

 

 

 

 

 

NAME

Note: NAME=ImportName and NAME=ClassName are both required attributes.

The import name is the text of the root XML node of the AsXML.

The ClassName attribute should be defined as one of the objects that AsXML mapping is going to create.

GUID

 

XPATH

 

VALUE

 

SQL

 

SYSTEMDATE

 

SEQUENCE

 

XPATHSTRINGLIST

 

XPATHNUMBERLIST

 

SQLMAP

 

<PreInsert>     

Optional element;

PreInsert allows for functionally to be exercised prior to records being inserted into the database. Only used when there is a need to call other functionality in the application. 

 

 

<Object>          

Used to define the name of the Java class being called.

CLASS

 

<Parameters>                

Allows for passing parameters to the class.

NAME

 

<PostInsert>    

 

Optional element:

PostInsert allows for functionally after the records are being inserted into the database. Only used when there is a need to call other functionality in the application. 

 

 

<ActivityMathResponse> Optional Element: Opening element to define the MathVaribles to be included in Response Result.    
 

Optional Attribute: It can take 'Yes' ,'No' and 'Logged' as a value. If 'Yes' all the math variables for all the processed activities will be included in response result and rest all instructions that include MathVariable in response result will be ignored.

If 'No' then it will refer other instructions to decide which mathvariable to be included in response result. If attribute value is 'Logged' then all the logged math variables of all the processed activities will be included in response result. This attribute value can be used with or without Transaction specific instruction. In case both are available then distinct union of MathVariable will be available in response result. If this attribute value is used then if configured, 'Logged' attribute value for ALLMATHVARIABLES attribute of <Transaction> element will be ignored.

ALLMATHVARIABLES Yes|No|Logged
<Transaction> Optional Element: It is optional element and should be repeated for each unique transaction for all the activities defined in AsFile configuration.    
  Mandatory Attribute: Unique identifier for Transaction <TransactionGUID> Attribute with Transaction guid value
  Optional Element: It can take 'Yes' ,'No' and 'Logged' as a value. If 'Yes' all the math variables for all the processed activities will be included in response result. Default value is 'No'. If value is 'No' then it will refer the <MathVariableName> instruction (mentioned below) to decide which mathvariable to be included in response result. If attribute value is 'Logged' then all the logged math variables of processed activities associated with this specific transaction will be included in response result. This attribute value can be used with or without <MathVariableName> element. In case both are available then distinct union of MathVariable will be available in response result. ALLMATHVARIABLES Yes|No|Logged
  Optional and Repeatable Element: Name of MathVariable to be included in Response Result.   literal name of Mathvariable from Transaction configuration

<Object>            

Used to define the name of the Java class being called.

CLASS

 

<Parameters>                 

Allows for passing parameters to the class.

NAME

 

<ActivityMathResponse> Optional Element: Opening element to define the MathVaribles to be included in Response Result    
 

Optional Attribute: It can take 'Yes' ,'No' and 'Logged' as a value.

If 'Yes' is set, then all the math variables for all the processed activities will be included in response result and rest all instruction to include MathVariable in response result will be ignored.

If 'No' is set, then it will refer other instruction to decide which mathvariable to be included in response result.

If attribute value is set as 'Logged', then all the logged math variables of all the processed activities will be included in response result.

  • This attribute value can be used with or without Transaction specific instruction. In case both are available then distinct union of MathVariable will be available in response result.
  • If this attribute value is used then if configured, 'Logged' attribute value for ALLMATHVARIABLES attribute of <Transaction> element will be ignored.
ALLMATHVARIABLES Yes / No / Logged
<Transaction> Optional Element: It is an optional element and should be repeated for each unique transaction for all the activities defined in AsFile configuration.    
  Mandatory Attribute: Unique identifier for Transaction <TransactionGUID> Attribute with Transaction guid value
 

Optional Element: It can take 'Yes' ,'No' and 'Logged' as a value.

If value is 'Yes', then all the math variables for all the processed activities will be included in response result.

Default value is 'No'. If value is 'No' then it will refer the <MathVariableName> instruction (mentioned below) to decide which mathvariable to be included in response result.

If attribute value is 'Logged' then all the logged math variables of processed activities associated with this specific transaction will be included in response result.

  • This attribute value can be used with or without <MathVariableName> element.
  • In case both are available then distinct union of MathVariable will be available in response result.
ALLMATHVARIABLES Yes / No / Logged
MathVariableName Optional and Repeatable Element: Name of MathVariable to be included in Response Result.   Literal name of Mathvariable from Transaction configuration.

XML Schema

<File>
<AssignAttributes>
</AssignAttributes>
<PostInsert>
<Object CLASS="<ClassName>"></Object>
<ActivityMathResponse ALLMATHVARIBLES="Yes|No|Logged" >
<Transaction TransactionGUID="{Defined Attribute Name from the AssignAttributes element with Transaction guid value}" ALLMATHVARIBLES="Yes|No|Logged">
<MathVariableName>MVName1</MathVariableName>
<MathVariableName>MVName2</MathVariableName>
</Transaction>
</ActivityMathResponse>
</PostInsert>
</File>

XML Example 1

<File>
<RequestType>Illustration</RequestType>
<AssignAttributes>     
<Attribute NAME="ImportMapName" TYPE="VALUE">AsXml</Attribute>            
<Attribute NAME="ClassName" TYPE="VALUE">com.adminserver.utl.JibxListUtl</Attribute>             
</AssignAttributes>     
<PreInsert>     
<Object CLASS="com.adminserver.pas.webservice.bll.AsFilePostInsertIndividualActivityProcessorBll">            
<Parameters>                  
<Parameter NAME="ActivityClientNumber">ActivityClientNumber</Parameter>                         
</Parameters>                  
</Object>           
</PreInsert>      
</File>
 

XML Example 2

<File>
<AssignAttributes>
<!-- Required in all AsFile interfaces -->
<Attribute NAME="ImportMapName" TYPE="VALUE">AsXml</Attribute>
<Attribute NAME="ClassName" TYPE="VALUE">com.adminserver.utl.JibxListUtl</Attribute>
<!-- Additional AsFile -->
<Attribute NAME="PlanGUID" TYPE="XPATH">/TXLife/TXLifeRequest/OLifE/Holding/Policy/ProductCode</Attribute>
<Attribute NAME="FundGUID" TYPE="XPATH">/TXLife/TXLifeRequest/OlifE/Holding/Investment/SubAccount/ProductCode</Attribute>
<Attribute NAME="PolicyGUID" TYPE="GUID"/>
<Attribute NAME="ParentCompanyGUID" TYPE="SQL">SELECT CompanyGUID FROM AsCompany WHERE CompanyName='Prototype Child Company'</Attribute>
<Attribute NAME="ChildCompanyGUID" TYPE="SQL">SELECT CompanyGUID FROM AsCompany WHERE CompanyName='Primary Company 1'</Attribute>
<Attribute NAME="TransactionGUID" TYPE="SQL">SELECT TransactionGUID FROM AsTransaction WHERE PlanGUID = '[PlanGUID]' AND TransactionName = 'CoverageCalculation'</Attribute>
<Attribute NAME="ProcessingOrder" TYPE="SQL">SELECT ProcessingOrder FROM AsTransaction WHERE TransactionGUID = '[TransactionGUID]'</Attribute>
<Attribute NAME="ActivityClientNumber" TYPE="VALUE">devikar</Attribute>
<Attribute NAME="ComputationID" TYPE="VALUE">IllustrationReturn</Attribute>
<!--Attribute NAME="PolicyNumber" TYPE="POLICYNUMBER" PLANGUID="PlanGUID" POLICYGUID="PolicyGUID" COMPANYGUID="CompanyGUID">PolicyNumber</Attribute-->
<Attribute NAME="PolicyNumber" TYPE="SEQUENCE">PolicyNumber</Attribute>
</AssignAttributes>
<PostInsert>
<Object CLASS="com.adminserver.pas.webservice.bll.AsFilePostInsertIndividualActivityProcessorBll">
<Parameters>
<Parameter NAME="ActivityClientNumber">ActivityClientNumber</Parameter>
</Parameters>
</Object>
<Object CLASS="<ClassName>"></Object>
<ActivityMathResponse ALLMATHVARIBLES="Yes|No|Logged">
<Transaction TransactionGUID="{Defined Attribute Name from the AssignAttributes element with Transaction guid value}" ALLMATHVARIBLES="Yes|No|Logged">
<MathVariableName>MVName1</MathVariableName>
<MathVariableName>MVName2</MathVariableName>
</Transaction>
</ActivityMathResponse>
</PostInsert>
</File>

 

 

 

 

 

Oracle Insurance Logo Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us