Set - Unset e-Statement Options

Overview

The e-Statements is a functionality that allows Customers to enable or disable e-statements, meaning email statements for the transaction done at the Contract Level. The existing Correspondence Override setting which generate Confirms will be used to enable of disable e-statements option.

The Customer will be able to view the selections of e-statements on all his contracts in the Summary Information of the customer. Also, each Contract information will include the selection of e-statements option.

When a customer checks/selects(3-Email for Check and 4-Regular Mail for uncheck) the e-Statements option, the backend system searches for all the Active contracts of the customer and updates the Mailing Type of the particular Correspondence Override to Email.

When a customer unchecks the e-Statements option or wants to unsubscribe from the E-Statements, the Mailing type is reverted to the previous setting that was persisted earlier.

Technical Requirements

Business Requirements for e-Statements

Process Flow

The external system would fire the REST URL with the JSON message containing input parameters on the request queue.

ALIP webadapters would pick up, process the message, convert it into XML format, and posts it onto the ALIP request queue.

ALIP process server will pick up the message, convert from ACORD to the canonical format, perform the necessary XSD validations, and other basic validations on the completeness of the correspondence information, existence of the CRM id/External agent ID in ALIP.

Post the necessary validations, it would invoke the necessary ALIP APIs/workflows to update or retrieve the necessary correspondence information from the database.

The licensing information in case of a “GET” request, would be generated in XML format, converted to ACORD format, and sent back to the REST layer.

Here, it would be further converted back into the final JSON output format and returned back to the external system.

Impact on ALIP system for e-Statements(applicable for get operations)

This interface provides the ability for viewing if the customer has any correspondence settings available for the Conract.

Upon receiving the request,based on the CRMID, ALIP system checks for the list of contracts where correspondence is set to role specified fo the role and provides the Mailing Type for the contract.

If the validations are successful the the request is forwarded to appropriate API/workflow which converts the response to ACCORD and then into the JSON format.

If the validations fail the appropriate error messages will be displayed on ALIP system next to the licensing request. The status of licensing will reflect the same as in “Error”.

Impact on ALIP system for e-Statements(applicable for post Operations)

This interface provides the ability to set the Mailing Type to Email or any previous setting for a Contract of the customer.

Upon receiving the request,based on the CRMid, ALIP system gets the contracts for a customer. On receiving the list of contracts, the system changes Mailing Type of the existing Correspondences to Email if e-statements is to be enabled or to the previous setting if e-statements is to be disabled.

If the validations are successful the the request is forwarded to appropriate API/workflow which converts the response to ACCORD and then into the JSON format.

If the validations fail the appropriate error messages will be displayed on ALIP system next to the appointments request. The status of licensing will reflect the same as in “Error”.

Assumptions

N/A

Dependencies

N/A

Request Data Elements

Response Data Elements

NA

Success/ Error Handling