This interface provides the ability for ALIP to update an already submitted application. This functionality is currently available for the Non- Trad product – Deferred Annuity.
| TR ID# | Technical Requirements |
| TR1 | ACORDv2.36 shall be used to communicate with the client system. |
| TR2 | The client system will send a New Business Post Submit Update request message in the ACORD XML format to ALIP Request Queue. (TransType tc=”502” and TransSubType tc=”50204”) |
| TR3 | ALIP would first respond to the Client system with an Acknowledgement to indicate the receipt of the New Business Post Submit update request. |
| TR4 | ALIP would then process the received ACORD message to update the Pre- issue application in ALIP. |
| TR5 | Events will be published for the update of the application. |
| BR ID# | Business Requirements |
| BR1 | ALIP would receive a request for New Business Post Submit update request from external system comprising of application information for a Deferred Annuity Product. |
| BR2 | ALIP would first return an Acknowledgement to the client’s system to acknowledge the receival of the post submit update request and then it would update the pre issued application in ALIP. |
| BR3 | Any changes made by this interface, will be associated with a user called ‘Interface User’ in the ALIP database. |
The external system will post an application post-submit message to the ALIP request queue.
ALIP will receive this message, and first post an acknowledgement message in ACORD format, to the calling external system.
The message will be transformed to ALIP canonical format, and then invoke the necessary ALIP APIs to retrieve the ‘ApplicationID’ and ‘PolicyStatus’ based on ‘Case Number’ received in the input message. Using this ‘ApplicationID’, it would further retrieve the existing application information from the ALIP database.
ALIP will store the incoming application data to an explicitly designed /XML/Integration/Input path and will then synchronously invoke a workflow that will capture the change history, replace the existing application data with the incoming application data, and update the application details in the ALIP database. If any application details are missing from the input XML, which was present in ALIP earlier, it will delete these application details.
If the workflow ends without any error, ALIP will further invoke the Underwriting Workflow, to resubmit the application for underwriting in ALIP with the same contract number.
Events will be published for application post submit changes that occur in the ALIP system.
None
ALIP may receive a New Business Post Submit Update request for a single contract, more than once, by receiving unique ‘Case Number’ in the input ACORD request.
The incoming ACORD XML will always contain the entire application information, whenever it is received by ALIP from an external system. For example, if only one of the beneficiaries come as a part of the input ACORD XML, and two beneficiaries were already present in ALIP for the respective application, the beneficiary which did not come in, will be removed from ALIP application.
Application details like ApplicationStatus, CaseNumber, ApplicationID cannot be modified using this interface.
N/A
| Request Parameters | Description | Mandatory | Allowed values |
| CaseName | A tag which uniquely identifies an Application number within ALIP. | Y | String |
| Success | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | The Success acknowledgement message will be sent in the response queue | 1 | Success | Informational |
| Error | Error Scenario Description | Message Description | Message Type | Additional Comments |
| #1 | New Business – Post Submit interface was NOT successful due to technical errors. | Internal Error | Fatal | |
| #2 | New Business – Post Submit interface was NOT successful because Application Id is not present in ALIP | Application doesn’t exist | Fatal | |
| #3 | New Business – Post Submit interface was NOT successful because Application update is not allowed due to its status being already issued | Contract is already Issued | Fatal | |
| #4 | New Business – Post Submit interface was NOT successful due to any IGO validation failure. | Validation Error | Fatal | Any Validation error in below processing.IGO Validation in New Business Post-Submission Background RulesClient Details ValidationBank Details ValidationProduct Details Validations |
| #5 | New Business – Post Submit interface was NOT successful due to invalid TransType code provided in ACORD xml i.e. /XML/TransType | Invalid TransType code provided | Fatal |