This interface provides functionality to perform Case Assignment of an Application.This provides the Primary Writing Agent to an external system which determines the case assignment (e.g., ‘”group and individual” or “group”) for the corresponding application. This is handled via a real time web service call to the external system with primary writing agent details and contract information as input to do Case Assignment for an Application.
The call to the external Case Assignment system is currently available, for the below mentioned trigger points:
• Trigger 1 - ALIP New Business Submission for Deferred Annuity, Universal Life and Term Life Applications
The Case Assignment will only be applicable to the Primary Writing Agent.
When invoked from the New Businses application processing scenario, the response from interface can be leveraged by ALIP business configuration.
| No. | Trigger Point | Case Assignment rule group Call |
| 1 | Any App Submission flow | INT - Case Assignment service |
| TR ID# | Technical Requirements |
| TR1 | The interface will receive ALIP format XML from the above listed trigger points configured for agent case assignment. This ALIP XML will be converted to ACORD 22850 format, and sent by the interface to the external system. |
| TR2 | ALIP will call the external validation service with all the primary writing agent details mentioned in Request Data Elements. |
| TR3 | External case assignment service will return back the response with fields mentioned in Response Data Elements. |
| TR4 | The response from external service, will be in ACORD format. This will be converted into ALIP XML and returned by the interface to the trigger point that invoked this interface. |
| TR5 | The expected response time from the external system is 3 seconds or less. If there is no response received in that time, ALIP will retry 3 times before it considers this as an integration failure. |
| TR6 | ALIP can connect to external service using REST. For REST, support is provided for OAuth2 authentication |
| TR7 | If the case assignment service of the external system is unreachable or any exception is thrown while invoking the service, the interface will log an Integration Failure in the ALIP database. |
| BR ID# | Business Requirements |
| BR1 | Case Assignment Interface will be called from various trigger points on the basis of business rules. This interface will invoke the case assignment service provided by the external system, to do case assignment of the Application. |
| BR2 | The response received from the external system is translated and sent back to the invoking trigger point by the interface. Business rules will further interpret this response, to perform the case assignment when the trigger is during application submit. |
a. ALIP system sends a Case Assignment request to the ALIP request queue, from the configured trigger points.
b. /XML/Trigger/InvokeIntegration/AdditionalProcessingIndicator tag can be leveraged to check if there are any mandatory fields or additional business validations required to be performed before invoking the external service.
c. If “AdditionalProcessingIndicator” tag is set to ‘Y”, integration will call the rulegroup (i.e., “INT-Case Assignment Validation Rule”). Currently, this rule is used to check if the mandatory fields are available. This enables the interface to be generic across multiple external systems, while giving business configuration the capability to check for the mandatory fields or any other validations.
d. If “AdditionalProcessingIndicator” tag is set to ‘N”, integration will not perform any additional validations and will proceed with the available information.
e. Message from the request queue is routed to the appropriate interface, which translates the message to ACORD 22850 format and invokes external service.
f. The response message returned by the external service, is translated to ALIP format and sent to the invoking trigger point.
g. Business configuration will help further translate the response to error messages/requirements, based on the trigger point.
None
a. This interface is currently enabled and maintained for the below combination(s):
• REST without namespace with Oauth and POST.
This can be further enhanced to work with other combinations, based on client’s requirement.
b. This interface will not perform any validation of the Group Assignee and Assignee returned in the response.
Connectivity details to the external systems are highlighted below.
• The connection type for REST is configurable for Accenture Dev team, and will be a one time setting. Allowed value is REST. Connection Type is set as below:
CaseAssignment.ExternalServiceType=REST
• REST connection supports OAauth2 authentication as well, if it is not required it can be turned off. If required token generation details will be required as below.
Oauth2Token.AuthParams=dfsfdhhkkj:gygyuujjlkkj (ClientSecretID:Pwd)
Oauth2Token.Url= http://ml-ix-dk01.alipacn.com:51006/token
(Sample URL, needs to be replaced with client token generation url)
Token Generation Currently supports only application/json format. Also Url and credentials will be shared across all the interfaces for a client.
• The generated token can be cached for certain duration as per client’s requirement. Default Property setting for it will be 0 ms. This can be changed to for example 7200ms
tokenTimeToLive=0
• REST connection supports both XML and JSON content type with POST request. REST connection details are defined as below. IntegrationPoint.REST.{RequiredDetails}.
CaseAssignment.REST.AuthReqd=Yes
CaseAssignment.REST.AuthType=OAuth
CaseAssignment.REST.ContentType=XML (or) JSON
CaseAssignment.REST.Url=<
CaseAssignment.REST.RequestType=POST or GET
• In case connection to the external REST service fails, API will automatically retry to connect to service. This setting is also configurable as below. Default setting will be 3 retries. These properties will be shared across all the interfaces.
RESTConfigurableRetryCount=3
RESTConfigurableBackOffPeriod=0
• API provides the ability to connect to extetrnal system using namespace in the payload. If namespace is required to connect to external system below setting is required. If this setting is provided API will apply it to the external service request and remove the same once the external service response is received before passing it for further processing.
CaseAssignment.Namespace=http://ACORD.org/Standards/Life/2
Please refer to spreadsheet above for the Response Data elements.
| Success | Success Scenario Description | Message Code | Message Description | Message Type | Additional Comments |
| #1 | Case Assignment Interface executed successfully. | 1 | Success | Informational | The call to the external webservice is successful.Success entry will be logged on the integration history page. |
| Error | Error Scenario Description | Message Description | Message Type | Additional Comments |
| #1 | Case Assignment Interface was not successful due to validation failure of the response received from the external validating webservice. | Internal Error | Fatal | |
| #2 | Case Assignment Interface was not successful due to the webservice being down or timing out | Internal Error | NA | |
| #3 | Case Assignment Service was not successful due to the token generation failing for cases where the external system’s webservice uses REST OAuth2 due to below reasonsToken Generation Url is not validClient Credentials are not validRequest body (if mandatory) is not provided. | Internal Error | NA |
An average response time of 3 seconds (i.e. client external system needs to provide a response within this timeframe) is assumed for this interface.