POINT IN Agency Link 5.0 iSolutions 5.0 Guide to Agency ...ELECTRONIC EDITION USER INFORMATION...

© 2005 Computer Sciences Corporation. El Segundo, California. All rights reserved. No part of this publication may be reproduced by any means without written permission from Computer Sciences Corporation. Printed in U.S.A. All questions regarding this documentation should be routed through customer assistance, Blythewood,SC, 803-333-6200 or email [email protected].

POINT IN Agency Link 5.0

iSolutions 5.0

Guide to Agency Link

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Electronic Edition

This document describes how to use the Agency Link Electronic Edi-tion interface. Both the Agency Link standard architecture and the Designer/Builder architecture are addressed, from their shared busi-ness messages to the architecture-specific differences in the pro-cessing steps.

Revision date — November 15, 2005

Preface

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preface

Product NamesThe CSC Companion Products take on combined names when installed with other CSC products. The table below indicates the var-ious names that refer to the same product, and how the product will be referred to throughout this document.

For More AssistancePlease direct any questions or suggestions regarding this material to CSC P&C Client Support by telephone at (International Access Code U.S.A.) 803.333.6200 or email [email protected].

Product Is Named When In Documentation

iSolutions POINT IN Agency Link Installed with POINT IN Agency Link

iSolutions Installed separately or with any system other than POINT IN

Agency Link

Designer/Builder (formerly called iSolutions:Tools)

POINT IN Designer/Builder

Installed with POINT IN Designer/Builder

iSolutions Designer/Builder

Installed separately or with any system other than POINT IN

Designer/Builder

2 Agency Link 5.0 – Guide to Agency Link Electronic Edition ©Copyright 2005 CSC. All Rights Reserved.

. . .

. .TA B LE OF CO N T E N T S

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents

Preface ..............................................................................................2Product Names...............................................................................2For More Assistance........................................................................2

Electronic Edition User Information.....................................5Overview............................................................................................5Response Options Depend on XML Request .............................................6Getting Started...................................................................................7Testing Agency Link Electronic Edition..................................................8

Electronic Edition Technical Information ........................... 12Requests Are Sent Via XML Messages ................................................... 12Responses May Take Several Forms...................................................... 12Implementation Considerations .......................................................... 13

Standard Architecture .................................................................. 13Designer/Builder Architecture ....................................................... 13

Subsystems and Lines of Business Currently Supported ......................... 13New Business............................................................................... 13Notice of Loss .............................................................................. 14

Business Logic and Data Flow ............................................................. 14Logic and Flow for Designer/Builder Architecture ............................ 14

Security ........................................................................................... 15System Processing............................................................................. 15Standard Architecture – Electronic Edition Objects................................ 16

ASPX Object – EELaunch.aspx – XMLGateway Object ......................... 16Application Object – XMLX ............................................................ 16

Business Messages Currently Supported....................................... 16Example Files ........................................................................... 18Quote Processing Steps.............................................................. 18Add (Issue) Processing Steps...................................................... 19Notice of Loss Processing Steps .................................................. 20XMLX Functionality .................................................................. 20

Designer/Builder Architecture – Electronic Edition Objects .................... 21ASPX Object – EELaunch.aspx – XMLGateway.ASP Object .................. 21Component – XMLGateway.DLL ...................................................... 21Application Object – XMLX.dll ....................................................... 23Component – InterfaceVPMS.dll ..................................................... 24Processing Edits ........................................................................... 25Errors/Error Handling................................................................... 25Row Processing/Layout................................................................. 25

©Copyright 2005 CSC. All Rights Reserved. Agency Link 5.0 – Guide to Agency Link Electronic Edition 3

TA B L E OF C O N T E N T S

Appendix A: Electronic Edition Flow (Standard Architecture) ...................................................... 26

Appendix B: Electronic Edition Data Flow(Designer/Builder Architecture) .......................................... 27

Appendix C: Electronic Edition Process Flow(Designer/Builder Architecture) .......................................... 29


. . .

. .E L E C T RO N I C E D I T I O N US E R I N FO R M A T I O N

Overview

Electronic Edition User . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Information

This chapter summarizes the functions of the Agency Link Elec-tronic Edition interface at a high level. The primary audience is business analysts and users with a non-technical background.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Overview

The Agency Link Electronic Edition interface allows you to send pol-icy data between Agency Link and your existing enterprise or agency management system in order to get a quote, submit (issue) a new business policy to Agency Link, or populate the Agency Link Notice of Loss (NOL) database with claims data.

Electronic Edition sends the data in form of a request via an Exten-sible Markup Language (XML) file using the Association for Coopera-tive Operations Research and Development (ACORD) format.

The data within the request will be imported into the Agency Link database1, and Agency Link will return a response based on a parameter within the request.

Each installation of Agency Link Electronic Edition is unique. The immediate launching point from your existing enterprise system or agency management system to the Agency Link system will be cus-tomized by your technical staff. The description that follows is nec-essarily high-level, containing only those elements that are common to all installations. The response XML will most always be sent back to the requester using an application, not the browser. Submitting the request XML via the browser is just a test mecha-nism, and the normal process will be the use of an application.

1. Standard architecture uses the New Business database (or NOL data-base for claims-related data). Designer/Builder architecture uses the XML Transactions database.


E L E C T RO N I C E D I T I O N US E R I NFO R M A T I O N

Response Options Depend on XML Request

Electronic Edition makes it easier to implement processing any ACORD business message. Custom code is not required for each ACORD business message. The XMLGateway is generic and can pro-cess any XML document, but the XMLX component will require mod-ification to recognize a new message. Lastly, it allows a common approach for processing XML business messages for all development.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Response Options Depend on XML Request

The response may take one of the three following forms, dependent upon the request and which response option is selected at the time of configuration:

1 Import and generation of XML response, which the user will see dis-played in a browser window.

a For quote or issue, the policy data is imported into the Agency Link database, the policy rates (or rates and issues), and a “response view” of the XML with the premium amount returns to the browser window.

b For NOL entry, the data is imported into the Agency Link NOL database and a response such as a confirmation or error message is returned to the calling application.

2 Initiation of Agency Link with navigation to the appropriate data entry page. With this option, the policy data is imported into the Agency Link database.

a For Quote, the policy also rates. The system responds by opening the New Business Applicant Information page populated with the applicant data imported from the XML file. You can review the data, make necessary changes, and re-rate the policy, just as if you had logged-on to Agency Link. However, Agency Link Inquiry and Notice of Loss subsystems are not available with this option.

If Request Is Then Response May Be Configured As

Return XML Launch Agency Link Open Agency Link Sign-On

Quote Y Y Y

Issue (Add) Y Y

NOL entry Y Y Y


. . .


Getting Started

b For NOL, the entry page that corresponds to the loss type (Liability, Property, Automobile, or Workers’ Compensation) opens and is populated with the data imported from the XML file. You can review the data, make changes, save the NOL in a pending status, or submit it as complete. However, you may not enter any other Agency Link subsystem once you finished your NOL processing.

3 Navigation to the Agency Link system sign-on page.

a For Quote or Issue: This option begins the process by importing the XML data into the Agency Link database. Then the policy rates (or rates and issues), but the rated policy and the XML do not display in the browser. Instead, the Agency Link Login page displays so that you can enter and use Agency Link with its full system capabilities (unlike option 2 above).

b For NOL: This option imports the XML data into the Agency Link NOL database and opens the Agency Link Login page. Once you sign in with your Agency Link user ID, you have all your normal entitlements in Agency Link, unlike the Initiate Agency Link option (option 2), which only allows access to the NOL subsystem.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Getting Started

To begin, you must have access to an ACORD formatted XML file.

• This XML file is the result of a separate process that creates the XML file by extracting the appropriate data from an existing enterprise system or agency management system.

• Upon creation of the XML file, the client process should validate the format of the XML file using the DTD (Document Type Defini-tion) provided by CSC.2

• The XML file is sent using HTTPS, which ensures secure process-ing.

You also must have a valid Agency Link user ID and password regis-tered in the Agency Link Security subsystem. The XML file contain-ing your user ID and password is authenticated by Agency Link Security so that processing can continue.

2. CSC uses the ACORD 1.0 base, plus service provider extensions.



Testing Agency Link Electronic Edition

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Testing Agency Link Electronic Edition

Electronic Edition is a headless process that will receive an XML post from another server. In order to simulate this post for testing pur-poses a test page is provided.

1 In your browser enter the following URL:

http://<server>/EELaunch/EELaunch.aspx

where server is the name or IP address of your Web server.

N

Figure 1. The Agency Link test page

2 Type the name of your XML file in the text field, or click Browse to locate the file on your computer or network.

3 Then select an option from the Response drop-down. (See Response Options Depend on XML Request on page 6.)

4 Your User ID and password are authenticated, allowing data to be imported into Agency Link. The XML file is validated using the DTD to verify correctness of format. If the XML file cannot be validated, a message returns specifying the problem. If your user ID and pass-word cannot be authenticated, response XML is returned with the specific error in the SignonRs/Status element.

5 Evaluate the Response.


. . .



Option 1 – Example of ResponseChoose the Return XML option. The XML data is imported into the New Business database, the policy is quoted or issued, and the response is displayed in the browser. The policy number assigned by Agency Link and the premium amount (FullTermAmount) are located in the PolicySummaryInfo section at the end of the XML stream, unless there is a problem such as incorrect data that causes rating errors. If an error exists, the error code and description is located in the XML response MsgStatus element.

Figure 2. Option 1 (for Quote, Issue, or NOL entry) — Generation of XML response

Option 2 – Examples of ResponseOption 2 launches Agency Link and navigates you to the appropri-ate data entry page. In addition, the policy data is imported into the Agency Link database.

a For Quote: The system responds by opening the New Business Applicant page populated with the applicant data imported from the XML file. (See Figure 3.) The policy has been quoted. You can review the data, and export the policy information back into your existing system, just as if a log-on to Agency Link has taken place. You may make necessary changes and re-rate the policy.




› Because your user ID and password were initially authenti-cated, you have the same entitlements for New Business in Agency Link just as if you had logged on normally. How-ever, Inquiry and Notice of Loss Agency Link functions are not available in this mode.

figure 3

Figure 3. Option 2 (for Quote) — Initiation of Agency Link

b For NOL: The entry page that corresponds to the loss type (Liability, Property, Automobile, or Workers’ Compensation) opens and is populated with the data imported from the XML file. (See Figure 4.) You can review the data, make changes, save the NOL in a pending status, or submit it as complete.

› With this option, your entitlements are limited to the Notice of Loss subsystem. You may not go into New Busi-ness or Inquiry.

Figure 4. Option 2 (for NOL entry) — Initiation of NOL subsystem (partial image)


. . .



› For details on how to use the Agency Link Notice of Loss subsystem, refer to Notice of Loss Information in the Agency Link library.

Option 3 – Example of Response

a For Quote or Issue: Selecting this option imports the XML data into the Agency Link database, and the policy is then quoted or issued. Once the XML is imported into the Agency Link database, the policy and the XML do not display in the browser. Instead, the Agency Link Log-on page displays. You then sign in with your Agency Link user ID. This option gives you broader system capabilities in Agency Link (that is, all the entitlements assigned to your user ID), unlike the Initiate Agency Link option (option 2), which only allows access to New Business.

b For NOL: Selecting this option imports the XML data into the Agency Link NOL database and the Agency Link Log-on page displays. You then sign in with your Agency Link user ID. This option gives you broader system capabilities in Agency Link (that is, all the entitlements your user ID has), unlike the Initiate Agency Link option (option 2), which only allows access to the NOL subsystem.

Figure 5. Option 3 — Navigation to the Agency Link log-on page


E L E C T RO N I C E D I T I O N TE C H N I C A L I N FO R M A T I O N

Requests Are Sent Via XML Messages

Electronic Edition Technical . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Requests Are Sent Via XML Messages

The Agency Link Electronic Edition interface passes XML data between Agency Link and CSC enterprise systems, other insurance processing systems, or agency management systems.

• See Electronic Edition Data Flow (Designer/Builder Architecture) on page 27 and Electronic Edition Process Flow (Designer/Builder Archi-tecture) on page 29.

• See flow diagram Electronic Edition Flow (Standard Architecture) on page 26.

The interface allows users with access to the Internet to send data between the systems via Extensible Markup Language (XML) files. The XML files use the ACORD XML format so they are capable of interacting with the Agency Link system. The data is imported into the Agency Link database, and from there the user may perform other actions in Agency Link depending on which XML request was sent. (See Overview on page 5 and Testing Agency Link Electronic Edi-tion on page 8 for available options.)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Responses May Take Several Forms

Once the data is loaded into the appropriate Agency Link database, the response information can be returned to users in one of three ways. See Response Options Depend on XML Request on page 6.


. . .

. .E L E C T RO N I C E D I T I O N TE C H N I C A L I N FO R M A T I O N

Implementation Considerations

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Implementation Considerations

Standard ArchitectureThere are no special considerations for implementing Electronic Edi-tion with Agency Link standard architecture.

Designer/Builder ArchitectureThe XML business message request needs to have the version ele-ment updated with the following code to direct the XMLGateway component to invoke Agency Link (Designer/Builder architecture).

<Version>XML_Transactions</Version>

Subsystems and Lines of Business Currently

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Supported

Agency Link Electronic Edition works with the following systems and lines of business.

New BusinessHost LOB Architecture

POINT BOP Standard

POINT Commercial Automobile Standard

POINT Homeowners Standard

POINT Personal Automobile Standard

POINT Workers’ Compensation Standard

Series II Commercial Automobile Standard

Series II Personal Automobile Standard

Series II Workers’ Compensation Standard

Other (unspecified) Personal Automobile Agency Designer/Builder



Business Logic and Data Flow

Notice of Loss

The ACORD XML Business Message Specification for P & C Insurance and Surety, Version 1.0.0 and its corresponding codes list are the foundation for the Agency Link XML business messages.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Business Logic and Data Flow

An XML document is built from the user's data source and sent in a data stream through the Internet to the Agency Link Electronic Edi-tion active server page (ASPX). The XML Gateway Object is then instantiated. The XML Gateway Object validates the XML file con-tained in the data stream and authenticates the user. If the XML cannot be validated or the user authenticated, a response is sent to the user with notification of the problem. If the XML is validated and the user authenticated, the XML data is passed to the XML pro-cessing object, which imports the data from the XML file into the Agency Link database. Then it calls the function denoted by the business message, such as quote or issue.

Once processing of the XML data is complete, a response is sent to the user. (See Response Options Depend on XML Request on page 6.)

Logic and Flow for Designer/Builder ArchitectureXML messages are customized for Agency Link (Designer/Builder architecture) through the addition of a tag. The Agency Link XML request will contain a parameter or tag that specifies that data from the XML message should be stored in the Agency Link XML transac-tions database instead of the Applications New Business database.

Agency Link (Designer/Builder architecture) shares the XMLGateway and XMLX modules with Agency Link (standard architecture). (ImportXML.bll is no longer used.)

Type of NOL

Automobile

Liability

Property

Workers’ Compensation


. . .


Security

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Security

XML data containing the user ID and password is transmitted via HTTPS. The XML Gateway Object parses the user ID and password from the XML and calls Agency Link Security object to authenticate the user. If the user ID exists and the password matches, processing continues. If not, an XML response message returns to the user with an appropriate error message in the Signon/Status element.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .System Processing

An ASPX object initiates the process of request and response XML. This object posts the XML document to the XML Gateway object. The XML Gateway object loads in the XML file, validates the XML, authenticates the user, and calls the XML processing object on the Application server. Response XML is then sent back to the XML Gateway Object. Upon receiving the response XML, the XML Gateway Object performs the appropriate response option. (See Response Options Depend on XML Request on page 6.)

The response action is controlled by a property in the XML Gateway object (RequestParm) set by the calling ASPX application. If the RequestParm property is not set by the calling application, the default is response XML.

For response XML, the original request elements and data are sent back in the response XML stream along with results from the quot-ing, issue, or NOL process. The request XML is converted into response XML to preserve all information that was sent from the requester. A response XML is built with data extracted from the database and merged with the response built from the request, and the end result will be response XML containing all the data sent from the requestor plus the generated data from Agency Link, such as premiums or a status of “Success” or “Error.”



Standard Architecture – Electronic Edition Objects

Standard Architecture – Electronic Edition

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Objects

ASPX Object – EELaunch.aspx – XMLGateway ObjectThis object handles all the XML requests for all lines of business. The XML Gateway Object ASPX, EELaunch.aspx, is called by a post from a form within an ASPX page or an HTTP post. The data stream posted to the ASPX contains the XML data. When instantiated, the XML Gateway Object examines the data stream to get the XML stream and the processing parameter (RequestParm). The processing parameter dictates the type of response processing being requested.

• LOG for the Agency Link Log-on page.

• APP for display of the Agency Link Applicant Information page or the Notice of Loss entry page.

• XML returns the response XML stream.

• If no parameter is provided, XML is assumed.

The XML is loaded as an XML document and is validated against the Document Type Definition (DTD). If the XML load detects a valida-tion error, a message is returned to the user. If the XML is validated, the XML Gateway Object obtains the user ID and password from the XML data and calls the Agency Link Security object to authenticate the user. If the user ID is not valid, or the user ID is valid but the password is not, an XML response message with appropriate errors is sent to the user.

The XML Gateway Object calls XMLX, passing the request XML, and receives back the response XML.

Application Object – XMLXThis component is used by the Agency Link for all XML processing. The XMLX component centralizes the retrieval and updating of ACORD XML messages to and from the database and interfacing to common business functions, and it contains a separate class for Electronic Edition.

Business Messages Currently SupportedEach line of business has unique AddRq and QuoteInqRq business messages. An AddRq business message is used for adding a policy and a QuoteInqRq is used for requesting a quote. The desired form


. . .



of system response (response option 1, 2, or 3) is also an input to the system. The business messages can be customized as needed by a technician during system configuration.

XMLX supports 30 ACORD XML business messages for Electronic Edi-tion, including Requests and Responses for these transactions.

Standard Architecture• PersPolicyQuoteInqRq/Rs

• HomePolicyQuoteInqRq/Rs

• BOPQuoteInqRq/Rs

• CommlAutoPolicyQuoteInqRq/Rs

• WorkCompPolicyQuoteInqRq/Rs

• PersPolicyAddRq/Rs

• HomePolicyAddRq/Rs

• BOPPolicyAddRq/Rs

• CommlAutoPolicyAddRq/Rs

• WorkCompPolicyAddRq/Rs

• ClaimNotificationAddRq/Rs

Designer/Builder Architecture• com.csc_CommlPkgPolicyAddRq/Rs

• com.csc_CommlPkgPolicyQuoteInqRq/Rs

• PersAutoPolicyAddRq/Rs

• PersAutoPolicyQuoteInqRq/Rs




Example FilesSome sample XML request and response messages are included on the Agency Link Release CD.

Figure 6. Sample XML messages are provided on the Agency Link Release CD.

Quote Processing StepsA Quote request would be processed with these steps.

a Quote XML is received from the XMLGateway.

b The data from the XML is loaded into the NB database using SQLXML, a call is made to PersistXMLData, and the XML is passed to the ACORDXMLInsert stored procedure, which populates the database.

c Method ConvertRQtoRS is called to convert the request XML to response XML format.

d The data is retrieved from the NB database using SQLXML, a call is made to the GetACORDMessage method, which invokes the ACORDXMLRetrieve stored procedure. This in turn creates the Request Quote XML.

e A call is made to CFWPost, sending the Quote Request XML and receiving back the Quote Response XML.

f Error checking is done and if errors exist, the response XML containing the errors is sent back to the XMLGateway.


. . .



g A call to AssociateXMLs combines the converted Rq to Rs XML with the return XML from CFW.

h Post processing is done, such as database update.

i Response XML is returned to the XMLGateway.

Add (Issue) Processing StepsAn Add request would be processed with these steps.

a The Add XML is received from the XMLGateway.

b The data from the XML is loaded into the NB database using SQLXML, a call is made to PersistXMLData, and the XML is passed to the ACORDXMLInsert stored procedure, which in turn populates the database.


d The data is retrieved from the NB database using SQLXML, a call is made to the GetACORDMessage method, which invokes the ACORDXMLRetrieve stored procedure. This in turn creates the Quote Request XML.

e A call is made to CFWPost, sending the Request XML and receiving back the Quote Response XML.

f Error checking is done, and if errors exist, the response XML containing the errors is sent back to the XMLGateway.

g The data is retrieved from the NB database using SQLXML, a call is made to the GetACORDMessage method, which invokes the ACORDXMLRetrieve stored procedure. This in turn creates the Add Request XML.

h A call is made to CFWPost, sending the Add Request XML and receiving back the Add Response XML.

i Error checking is done, and if errors exist, the Response XML displaying the errors is sent back to the XMLGateway.

j A call to AssociateXMLs combines the converted Rq to Rs XML with the return XML from CFW.

k Post processing is done, such as database update.

l Response XML is returned to the XMLGateway.




Notice of Loss Processing StepsA NOL request would be processed with these steps.

a ClaimNotification XML is received from the XMLGateway.

b The data from the XML is loaded into the NOL database using SQLXML, a call is made to PersistXMLData. and the XML is passed to the ACORDXMLInsert stored procedure. This in turn populates the database.


d Error checking is done, and if errors exist, the response XML displaying the errors is sent back to the XMLGateway.

e Response XML is returned to the XMLGateway.

XMLX FunctionalityThe diagram below shows the full functionality of XMLX, which includes the Electronic Edition section.

Figure 7. XMLX component structure

See documentation on XMLX for additional information.


. . .


Designer/Builder Architecture – Electronic Edition Objects

Designer/Builder Architecture – Electronic

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Edition Objects

The following descriptions outline the objects and/or components used for Agency Link (Designer/Builder architecture) Electronic Edi-tion.

ASPX Object – EELaunch.aspx – XMLGateway.ASP Object

DESCRIPTION This object handles all the XML requests for all lines of business. It accepts “headless” XML requests into Agency Link. The XMLGateway Object ASPX is called by a post from a form within an ASPX page. The data stream posted to the ASPX contains the XML file. When instantiated, the XMLGateway Object performs a query of the request to get the processing parameter (RequestParm). This dic-tates the type of response processing being requested.

PROCESSING The ASPX accepts the HTTP post information submitted from the user’s system and creates the instance of XMLGateway Object.

INPUT The HTTP post information submitted from the ASPX file.

OUTPUT XMLGateway Object instance.

Component – XMLGateway.DLL

DESCRIPTION This component acts as a gateway in the processing of the XML business message request. It validates the XML against the ACORD DTD. It authenticates the user ID and password passed with the XML business message request. It calls XMLX, sending parameters and the request XML.

PROCESSING The XML loads into the XML document for validation against the Document Type Definition (DTD). If the XML load detects a valida-tion error, a message is returned to the user. If the XML is validated, the XMLGateway Object obtains the user ID and password from the XML data and calls the Agency Link Security object to authenticate the user. If the user ID is not valid, or the user ID is valid and the password is not valid, an XML response message with appropriate errors is sent to the user.

PARAMETERS • XML calls the XMLX object and responds with the XML data.




• The application calls the XMLGateway object, which creates the Agency Link session and displays the Agency Link Applicant Information page populated with the data fed by the XML response into the Agency Link XML transactions database.

• Log-on calls the XMLX object and displays the Agency Link Log-on page.

The XMLGateway Object uses XMLX to initiate the process. The XML string passes to the XMLX (Designer/Builder module) in a variant and the string loads into the XML document without validation to the DTD. The validation is done only once by the XMLGateway. After processing is complete, the XMLGateway Object receives an XML string from the XMLX in the response XML format.

INPUT The ASPX form containing the XML file selected on the ASPX page and the mode of processing.

OUTPUT Output from the XMLGateway happens in two ways. They can be classified as “before” and “after” processing of the XML business message request information.

Before processing: The information from the ASPX is processed in the XMLGateway and passed to XMLX. Processing Message type, parameters collected from the Web security, and the XML file are the three pieces of information passed to XMLX component from the XMLGateway.

After processing: After the XML business message request and response are processed, XMLGateway displays the output to the user. XMLGateway updates necessary session values. At this point the component performs the specified response. (See Electronic Edi-tion User Information on page 5.)

1 The response XML is displayed in the browser.

2 The request will be redirected to the Agency Link Applicant Infor-mation page. The URL for redirection will be retrieved from the Set-tings.xml.

3 The request will be redirected to Agency Link sign-on page. The URL for redirection will be retrieved from the Settings.xml.

REMARKS XMLGateway differentiates between Agency Link with Designer/Builder architecture and Agency Link with standard archi-tecture based on the value in the <version> element in the business


. . .



message request. In the case of Agency Link (Designer/Builder architecture), the value in the <version> element is <ver-sion>XML_Transactions</version>.

Application Object – XMLX.dll

DESCRIPTION XMLX acts as an agent that takes in the ACORD XML business mes-sage request, translates it into individual screen XMLs, and stores it into the database XMLTransactions. XMLX is a generic XML processor that “persists” XML data into the Agency Link XML database and retrieves data from the database. It creates an ACORD request XML document.

PROCESSING XMLX component has a ProcessEE function which acts as a routing agent within the component. ProcessEE identifies the type of pro-cessing from the message type passed to the XMLX. ProcessImport is the function which is utilized for Designer/Builder architecture Electronic Edition processing. Within this function the following steps take place:

1 The input XML file from the user is loaded into an XML document. A stylesheet is used to transform it into individual screen XMLs.

2 CheckRequired function is called to validate that all required data are available.

3 The screen XMLs are concatenated with the corresponding parame-ters and saved into the database.

4 In the case of QuoteInqRq business message request, the screen XMLs are retrieved from the database and transformed into a QuoteInqRq business message using a stylesheet and sent to CFW or InterfaceVPMS component as needed.

Note: The decision for sending the business message request to the Host or the Agency Link Builder rating model is handled by a switch in the Settings.xml.

5 In the case of AddRq business message request, the screen XML is retrieved from the database, transformed in an AddRq business mes-sage using a stylesheet, and the message is sent to the host via CFW for rating and issuing.




INPUT The Message itself (which holds the ACORD XML); Message type; and Process Type (which indicates whether architecture is standard or Designer/Builder).

OUTPUT Output from the XMLX can be classified on the basis of the business message being handled inside.

QuoteInqRq business message: When the business message request is rated, the premium values are appended to the busi-ness message response and sent back to the XMLX.

AddRq business message: When an AddRq business message is processed, the appropriate tag in the XML business message request is changed from Rq to Rs to get an AddRs business mes-sage. The AddRq request is processed for rating and issuing, and the resulting AddRs has the premium information. The AddRs with premium information is merged with the existing AddRs (AddRq converted to AddRs) and the resulting XML is sent back to the XMLGateway.

Component – InterfaceVPMS.dll

DESCRIPTION InterfaceVPMS component calls the objects necessary for communi-cating with the Agency Link Builder model for any business process-ing like rating or underwriting. InterfaceVPMS converts the XML business message request into flat XML using a stylesheet. This component invokes the objects to pass data to the Agency Link Builder model.

PROCESSING InterfaceVPMS is instantiated by the XMLX if business processing needs to be done in the Agency Link Builder model. The Inter-faceVPMS takes in the XML business message request from the Import XML. It loads the XML business message request into the XML document and transforms it into a flat XML using a stylesheet. This transformed flat XML is passed to the objects that communi-cate with the Agency Link Builder model and returns back premium or other business processing result.

INPUT ACORD XML business message request

OUTPUT ACORD response with premium information


. . .



Processing EditsTwo processing edits are executed in the XMLGateway component.

1 Validation of the XML against the DTD

Successful loading of the XML business message request into the XML document confirms the validation against DTD. The DTD needs to be in the same virtual directory as the XML being processed.

2 Verification of the user ID and password in the XML file

The XML business message request contains the user ID and pass-word necessary to clear the security criteria of any particular envi-ronment. The user ID and password data are extracted from the XML and passed on to the Security component and verified against the information stored in the database.

Errors/Error HandlingAn error occurs when an invalid XML file or no XML file is imported into the XMLGateway. XMLGateway posts an error to the user in the form of a screen as shown in the Business Specification document. Runtime errors are handled as per the Agency Link error handling standard.

Row Processing/LayoutThe XML business message request is transformed into screen XML and stored into the Agency Link (Designer/Builder architecture) database (XMLTransactions). For every XML business message request that is converted into screen XML, a unique application ID (appID) is generated and stored in the XMLTransactions database. The appid is generated in the XMLX component. After quoting is done, the XML business message response is stored with the same appID in the database as a new row.


E L E C T RO N I C E D I T I O N F L OW ( S T A N D A RD A RC H I T E C T U RE )


A p p e n d i x A

Appendix A: Electronic Edition Flow

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(Standard Architecture)

Figure 8. Electronic Edition flow diagram for Agency Link standard architecture

User selects the XML business message request, as well as the type of system response. Depending upon the XML business message request and the system response selection, the information in the XML business message request is transformed into screen XMLs and stored in the New Business or in the NOL database.

Agency Link Databases

Communications Framework

XML Gateway ACORD Rq

XML

XMLX

Requester

ACORD Rs XML

Agency Link Applicant Page (or NOL Entry Page)

Agency Link Log-on

POINTServer-Side

Rating

Verify User ID and

Password

Agency Link Security System

SQL Agency Link Security

Database

. . .

. .E L E C T RO N I C E D I T I O N D A T A F L OW ( D E S I G N E R / B U I L D E R A RC H I T E C T U RE )

Appendix B: Electronic Edition Data Flow(Designer/Builder

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Architecture)

Figure 9. Electronic Edition data flow diagram for Designer/Builder architecture

1 XMLGateway.asp creates the object of XMLGateway and passes the inputs to the XMLGateway. The XML business message request is val-idated against the DTD. The user ID and password information from the XML business message request are verified against the informa-tion in the Agency Link Security system.

2 Upon the successful completion of the validation and verification, the XML business message request is sent to the XMLX.

XML input stream andprocessing parameters

1

2

Verify User ID and

Password

ASPXObject

XML GatewayValidates XML against DTD

Agency Link Security System

XMLXSplits the ACORD XML into screen

XML, and stores into database

Which Response?

Return XML to Browser

Agency Link Sign-on Page

Agency Link Applicant

Information Page

CFW

Rating Model

63

74

AddRq or QuoteInqRq?

Sessions updated5

SQL Agency Link Security

Database

SQL Agency Link XML_Transactions

Database


E L E C T RO N I C E D I T I O N D A T A F L OW ( D E S I G N E R / BU I L D E R A RC H I T E C T U RE )A p p e n d i x B

3 XMLX calls the ProcessImport function and passes the XML business message request. The XML business message request is loaded into the XML document and transformed into individual screen XMLs using a stylesheet.

4 The screen XMLs are stored in the Agency Link database (XMLTrans-actions).

5 Depending upon the XML business message request, the quote or issue process is initiated. In the case of QuoteInqRq, the quote pro-cess is initiated. In the case of AddRq, the issue process is initiated.

6 The screen XMLs are retrieved from the database and transformed into an ACORD request business message. The switch in the Set-tings.xml file decides whether a model-based rating or a host-based rating should be activated. In the case of model-based rating, the XML file is passed to the InterfaceVPMS component. In the case of host-based rating, the XML file is passed to CFW.

7 The response XML is returned to XMLX. In the case of model-based rating, the premium values generated in the model are appended to the response XML and returned to XMLX. In the case of host-based rating, the response XML from the host contains the premium infor-mation.

8 XMLX identifies the appID from the XML file and stores it tempo-rarily in a variable for further processing.

9 The system response may be a specified Return XML as shown in the drop-down, the Agency Link Applicant Information page, or Agency Link sign-on page. In the case of Agency Link Applicant Informa-tion page and Agency Link sign-on, the session needs to be updated on the browser before calling the corresponding URL.


. . .

. .E L E C T RO N I C E D I T I O N P RO C E S S F L OW ( D E S I G N E R / B U I L D E R A RC H I T E C T U RE )


Appendix C: Electronic Edition Process Flow(Designer/Builder

. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Architecture)

Figure 10. Electronic Edition process flow diagram for Designer/Builder architecture

User selects the XML business message request, as well as the type of system response. Depending upon the XML business message request and the system response selection, the information in the XML business message request is transformed into screen XMLs and stored in the XML transactions database.

ASPX Input File

ASPX Object

XML Gateway

Interface VPMSRating Model

(Builder)

SQL

CFW

HTTP

HTTP

XML

OUTPUT(Browser)

XMLX

Web Server App Server

PA

CPP

POINTenterprise

POINT IN Agency Link 5.0 iSolutions 5.0 Guide to Agency ...ELECTRONIC EDITION USER INFORMATION...

Documents

Transcript of POINT IN Agency Link 5.0 iSolutions 5.0 Guide to Agency ...ELECTRONIC EDITION USER INFORMATION...