As part of this interface, ALIP IX provides the capabilityto receive an UpdatePolicyCustomAttributes request, perform necessary validations and insert/update theCustomAttributes for the Policy, in the ALIP database. Post the update, ALIP will send an appropriate response based on the processing status to the external system, via the response queues.
Below are the input parameters,that this interface will accept as input:
Contract Number
Policy CustomAttributes
This interface has been currently built to support the following custom attributes.
ContractDeliveryReceiptDate
This interface is extensible to any further need for custom attributes update by making minor changes to the configuration.
| TR ID# | Technical Requirements |
| TR1 | ACORDv2.36 shall be used to communicate between ALIP and external system. |
| TR2 | The externalsystem will place anUpdatePolicyCustomAttributesrequest message in the ACORD XML format, to the ALIP Request Queue. (TransTypetc=”502”, and TransSubTypetc=”2147483647”) |
| TR3 | ALIP’s Process Server would receive the message and validate the incoming request. This will include XSD validations, existence check for the contract in ALIP and any other business validations based on the corresponding business requirement. |
| TR4 | If there are any issues with validation, it will be returned as a failure response and will also be stored as an Integration Failure in the ALIP system. |
| TR5 | After successful validation, the Integration interface would save the CustomAttributes in ALIP’s Contract tables. |
| BR ID# | Business Requirements |
| BR1 | The external systemwould sendan UpdatePolicyCustomAttributesRequest in ACORD format to ALIP. |
| BR2 | The incoming request should be processed only if the incoming Contract exists in ALIP. |
| BR3 | Any failure or error should be sent as an error response by ALIP to the client system. |
| BR4 | On successful processing, a success response message would be sent by ALIP to the client system. |
| BR5 | Data audit should be performed on the policy level attributes to be updated. |
| BR6 | For contract delivery date update, a check should be performed to verify that it is not be greater than the current date or less than the contract effective date. |
ALIP will receive a new UpdatePolicyCustomAttributes request, on the Alip Request Queue.
The ALIP process server will pick up the message, validate the request against the XSD and also perform necessary validations on the contract and the other policy attributes. If there are any issues finding the contract or with the CustomAttributes to be update, an Integration Failure would be created and stored in ALIP.
In case there is no failure, the request will be processed and the CustomAttributes will be saved against the contract, in the ALIP database.
The success or failuremessage, would be transformed back to ACORD format and sent back to the calling system.
None
N/A
N/A
An average response time of under 5 seconds is expected for this interface.
| Request Parameters | Description | Mandatory | Allowed values |
| Contract Number | A number which uniquely identifies a Contract within ALIP. | Y | |
| Policy CustomAttributes | CustomAttributes to be updated on Contract | Conditional |
| Success | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | The Update Policy CustomAttributes call was successful. | 1 | Success | Informational |
| Error | Error Scenario Description | Message Description | Message Type | Additional Comments |
| #1 | The Update Policy CustomAttributes call was NOT successful due to technical errors. | Internal Error | Fatal | |
| #2 | The Update PolicyCustomAttributes request was not successful, due to XSD was failure. | Failure | Error | |
| #3 | The Update Policy CustomAttributes not successful, where contract does not exist in ALIP | Failure | Error | |
| #4 | TheUpdatePolicyCustomAttributes request was NOT successful, due to contract not in Issued status. | Failure | Error | |
| #5 | The UpdatePolicyCustomAttributes request was NOT successful, due to Contract Delivery Date greater than the current date or less than the contract effective date. | Failure | Error |