The interface provides the technical, functional requirement for CCL interface. The interface is used to call ALIP product rules used for validation/calculation. The third party applications like portal or eApp can use this interface to validate application data for certain product validations like age check, minimum and maximum amount range check etc. These validations can be called by passing application data to the ALIP system. This interface provides the capability to call these rules which can invoked by the third party applications.
ALIP rule engine functions are set up in product rules can be found at below menu. Product Rules -> Custom functions.
To view the functions you can login to ALIP system. Click Product Rules -> Custom functions as shown below.
Select ID and then click search function
You can see list of functions
Use can also test functions by passing expression as FunctionName alongwith parameters
This interface exposes same functionality wrapped in interface which can be called on over SOAP/REST/JMS protocol.
| TR ID# | Technical Requirements |
| TR1 | ACORD version 2.36 shall be used to send request transaction. |
| TR2 | CCL Interface request should contain “integrationPoint=GET_CCL_EXPRESSION” for executing interface |
| TR3 | Interface must always return an error code and desc in the event of a rule engine processing failure while executing validation or calculation function in addition to HTTP response code. |
| TR4 | For a sucessful execution of rule engine transaction a return code of 200 is returned. |
| BR ID# | Business Requirements |
| BR1 | The Rule engine validation/calculation function should be present within the ALIP system. |
| BR2 | The input request’s processing instruction block & OLifE element data will be used to pass data to rule engine validation/calculation function present in ALIP |
| BR3 | In case of a successful execution of a rule engine function, success code will be returned by the interface. |
| BR4 | In case of an failure to find a match for function, an error message with suitable description and code will be returned by the interface. |
ALIP will receive a new request to call CCL function, on the ALIP Request Queue.
The ALIP process server will pick up the message, and validates request to check if inuput is correct. If there are any issues in the input, an Integration Failure would be created and stored in ALIP and error response is returned.
After successful validation of input, ALIP will transform the ACORD message to ALIP format, and call the CCL APIs to get function definition.
After receiving the function definition, incoming data is passed in CCL expression alongwith function definition to CCL APIs to execute the function.
Once the response is received from CCL function exection, the information would be transformed back to ACORD format and sent back to the calling system.
None
ALIP rule engine calculation/validation function mapped against processing instruction should be present within the ALIP system.
The mapping for processing instruction name against ALIP Calculation/validation function to be called and context data to be used should be available within the XSL.
The data required for executing the ALIP rule engine calculation/validation function should be available within the incoming Request’s OLifE block. XSD check will only check generic ACORD structure of message and will not check specific fields required by calculcation expression. It is responsibility of calling applications to pass all required data.
Only ALIP rules which are self contained meaning which can do business logic check or calculation based on data passed in paramters passed to it; can be exposed through this interface.
N/A
| Success | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | The CCL interface call was successful | 1 | Success | Informational | TXLife/TXLifeResponse/TransResult/ResultCode/@tc =1 |
| #2 | The CCL interface call failed as data required by CCL function was not available in input and hence not passed to CCL function. | 5 | Failure | Error | TXLife/TXLifeResponse/TransResult/ResultCode/@tc =5 |
| #3 | The CCL interface call failed with XSD/System error. | 5 | Failure | Error | TXLife/TXLifeResponse/TransResult/ResultCode/@tc =5 |