Transcription

1 TAM Integration Guide Revision 5 11/5/2004

2

3

4 Table of Contents Requirements for DocSTAR/TAM Integration...3 Requirements for DocSTAR/TAM Online Integration...3 Introduction to Insurance Agency Workflows...4 Back End Scanning... 4 Front End Scanning... 4 Hybrid Workflows and Distributed Scanning... 4 Configuring the TAM Integration...5 Step 1: Install the TAM ConneXion Toolkit... 7 Step 2: Install DocSTAR/TAM Module... 8 Step 3: Test the ConneXion Installation... 8 Step 4: Create the TAM 3 rd Party Links... 9 Configuring DocSTAR for use with ConneXion...13 Step 1: Install the DocSTAR TAM license onto the DocSTAR Host Step 2: Configuring DocSTAR Admin Step 3: Create DocSTAR Filing Templates that utilize the TAM Integration Integrating into other areas of TAM (Optional, for Local TAM only) Does not apply to TAM Online installations...49 Step 1: Create an ODBC Data Source Step 2: Create the DataLinks Step 3: Create the Templates Step 4: Create DocSTAR Integration hotkeys... 64

5

6

7 Requirements for DocSTAR/TAM Integration 1. DocSTAR v3.3 Workgroup (or higher) running Windows 2000 Server (or higher). 2. Applied Systems TAM v7.1.0 or higher on server supporting long file names. 3. Server for the ConneXion Web Service, which must run Microsoft Internet Information Server (IIS) and the Microsoft.NET Framework (this server can be the DocSTAR Server). 4. DocSTAR TAM Integration Module. Please note: There is an annual licensing fee for this module. 5. TAM ConneXion toolkit (included with DocSTAR TAM Integration Module Package). a. When ConneXion is going to be installed on the DocSTAR server, the customer should alert Applied ConneXion support up to one week in advance but at least three days prior. The installation should not proceed until it is confirmed that ConneXion support will be standing by to assist. b. When ConneXion is going to be installed on any other server, the customer is wholly responsible for installing it and testing it with assistance from ConneXion support, again the customer should alert Applied ConneXion support up to one week in advance but at least three days prior. The DocSTAR integration install should only proceed after confirmation that the ConneXion toolkit was installed successfully. 6. DocSTAR Integration Agent Build 18 or higher, required for integrated retrieval (must be pre-installed on DocSTAR Host). 7. DocSTAR Barcode module, for indexing w/barcode cover pages (typically only necessary for scan stations that are running templates on the barcode cover pages). (Optional for back-end scanning). Please note: Client stations only need the barcode font (included w/integration Agent Module) pre-installed to generate barcode cover pages. 8. DocSTAR DataLink module (must be pre-installed on DocSTAR Host. Optional for further integration). Requirements for DocSTAR/TAM Online Integration 1. DocSTAR v3.3 Workgroup (or higher) running Windows 2000 Server (or higher). 2. Active v7.1.0 TAM Online account with Applied Systems. (Customer may have to request their online version be upgraded, this should be done at least a week in advance). 3. DocSTAR TAM Integration Module. Please note: There is an annual licensing fee for this module. 4. ConneXion Web Service and V-Channel Server Service for TAM Online (included with DocSTAR TAM Integration Module Package). a. When the DocSTAR TAM Integration Module is ordered from DocSTAR, DocSTAR informs Applied Systems. The ConneXion Web Service and V-Channel Server Service are then activated by Applied Systems. The activation process may take up to a week. The customer should alert Applied ConneXion support up to one week in advance but at least three days prior. The DocSTAR/TAM Online integration installation should not proceed until it is confirmed that ConneXion support has activated the Connexion Web Service and V-Channel Server Service and will be standing by to assist. 5. V-Channel Client Software (for each client, available from Applied Systems). 6. DocSTAR Integration Agent Build 18 or higher, required for integrated retrieval (must be pre-installed on DocSTAR Host). 7. DocSTAR Barcode module, for indexing w/barcode cover pages (typically only necessary for scan stations that are running templates on the barcode cover pages). (Optional for back-end scanning). Please note: Client stations only need the barcode font (included w/integration Agent Module) pre-installed to generate barcode cover pages. DocSTAR TAM Integration Guide Page 3

8 Introduction to Insurance Agency Workflows How DocSTAR will be used in the agency s operations will greatly affect what templates will be needed and how the integration will be configured. Generally, agency practices fall into one of the following workflows. You must understand which of these will be employed. Back End Scanning Agencies receive paper via mail, fax, and courier. These documents must be processed, generally by customer service reps (CSRs), who often need to enter or verify information in TAM based on the document. The Back End Scanning approach does not change the process of receiving and distributing paper to CSR s who then perform their data entry or verification or other processing tasks. However, after processing is complete but while still in TAM in the policy or client or claim screen related to the transaction, the CSR prints a barcode cover page from TAM and places it on top of the document. Documents with barcode cover sheets are collected and scanned. Thanks to the cover pages, filing is completely or largely automated and requires no specialized knowledge. Proponents of this workflow favor it because it involves minimal change to the work processes for the CSRs. Front End Scanning A higher level of automation and efficiency can be gained by scanning (or importing) incoming documents as soon as they are received and routing them to appropriate CSR s before they are filed using DocSTAR folders. Each CSR is responsible for check his or her personal folder (effectively, their own Inbox), processing it, and then filing each document. This does involve more change for the CSRs who must now do their work from images, rather than from paper. However, front end scanning saves labor and speeds processing by not requiring paper to be distributed. It also avoids the possibility that a document will be lost during distribution or processing by the CSR. Finally, it gives manages a way (DocSTAR s folders) to monitor workload at each CSR. Use of cover pages is not practical for front end scanning, but DocSTAR s TAM Integration offers other ways for CSRs to conveniently file documents with accurate data from TAM. Hybrid Workflows and Distributed Scanning There are other possible workflows, such as performing front end scanning for certain documents but back end scanning for others, or using desktop scanners at each CSR s desk rather than cover pages and a centralized scanner. Templates and integration mechanisms for these workflows can be adapted from those used with the more common front end and back end scanning. Page 4 DocSTAR TAM Integration Guide

9 Configuring the TAM Integration Before scheduling this installation, examine the appropriate diagram below (Local TAM or TAM Online) and read through the installation steps thoroughly. Diagram for Local TAM Installation: The proper version of TAM (v7.1.0, verify that the customer is on the proper version first as the upgrade may have to be scheduled well in advance with Applied Systems Support) and the ConneXion Toolkit Installation (Step 1 below) are required before the DocSTAR/TAM Integration Installation can proceed. DocSTAR TAM Integration Guide Page 5

10 Diagram for TAM Online Installation: The proper version of TAM (v7.1.0, verify that the customer is on the proper version first as the upgrade may have to be scheduled well in advance with Applied Systems Support), the ConneXion Toolkit, and the V-Channel Server Service must be installed by Applied Systems before the DocSTAR/TAM Online Integration Installation can proceed. Page 6 DocSTAR TAM Integration Guide

11 Step 1: Install the TAM ConneXion Toolkit TAM Online Note: Applied Systems, Inc. will set up ConneXion and the required V- Channel Server Service for a TAM Online customer at their data center, so this step is not required and you may go to step 2. However, the customer must request set up of ConneXion and the V-Channel service (described below) at least one week prior to the planned installation. It should also be confirmed that ConneXion and the V- Channel Server Service have been activated at least 3 days prior to the planned installation date. (Often, this setup must be completed by Applied Systems, Inc. over a weekend.) *Note: Applied Systems, Inc. will deliver the ConneXion license, software download instructions, and installation instructions to the end user via . If the customer already has the ConneXion Toolkit installed for other 3 rd party integrations such as rating software, they may have to upgrade the ConneXion software to the latest version. This may render any other integrated applications inoperable, this should be verified and addressed before attempting to upgrade the ConneXion toolkit. * This step should be performed by the customer s IT department. Installation of the ConneXion Toolkit is not the responsibility of the DocSTAR Partner and it is not included in the price of the DocSTAR TAM Integration Module. However, if a DocSTAR Partner Technician is overseeing or actually performing the Connexion Toolkit installation (with assistance from Applied Systems), it is fair and reasonable to charge appropriately for time spent in this process. If ConneXion is installed on the DocSTAR server, the customer should be asked to alert Applied ConneXion support up to one (1) week in advance but at least three (3) days prior. The installation should not proceed until it is confirmed that ConneXion support will be standing by to assist. If ConneXion is installed on any other server, the customer is wholly responsible for installing it and testing it with assistance from ConneXion support. The DocSTAR integration install should only proceed after confirmation that the ConneXion toolkit was installed successfully. In order to install the ConneXion toolkit, the server will need to have IIS installed and configured, and also updated with the Microsoft.NET Framework, which is available from the Microsoft Windows Update website. The main TAM application must also be installed. Complete ConneXion installation instructions and support are available from Applied Systems, Inc. Technically, the DocSTAR server can also perform the duties of the ConneXion web server. However, installing TAM and ConneXion on the DocSTAR server is not optimal due to potential performance and serviceability issues. Also needed to install ConneXion is a license key. Currently, this is provided via by Applied Systems, Inc. to each TAM Integration customer reported by DocSTAR. In the future, a web-based self service portal is planned by Applied DocSTAR TAM Integration Guide Page 7

12 Systems, which will allow customers to receive their own license key after receiving a password from DocSTAR. Please note that that problems running ConneXion have been discovered on older versions of Novell. Step 2: Install DocSTAR/TAM Module In this step you will need to install the DocSTAR/TAM module CD onto the IIS Server (or DocSTAR server if it is assuming the role of the IIS Server) and each DocSTAR client (be sure that DocSTAR v3.3 client software has been loaded n the client workstations first). Insert the DocSTAR TAM module CD into the CD drive, and run SETUP.EXE. This will install all of the necessary files and will also start the.net framework installation if required. TAM Online Note: The DocSTAR TAM Module CD is only installed on the Client stations since the IIS Server for the ConneXion toolkit is installed and maintained by Applied Systems, Inc. In addition, the Virtual Channel (V-Channel) client, must also be installed on each workstation. It may be downloaded from: The V-Channel client installation instructions may be downloaded from: The V-Channel client installation can be completed by the end-user. In fact, it may already be in place if the end-user has integrated 3 rd party rating software with TAM. Note: These files are maintained by Applied Systems, Inc. Step 3: Test the ConneXion Installation Once ConneXion has been installed and configured (step 1) the setup may be tested to ensure that you are communicating properly. To test the ConneXion configuration do the following: Open Internet Explorer, and enter the URL replacing IISservername with the actual name of the IIS server. If the resulting page looks like the one below, ConneXion has been configured properly. TAM Online Note: The test URL for TAM Online is one of the following: Lisle data center: Dallas data center: Page 8 DocSTAR TAM Integration Guide

13 **Note: If the screen does not have the above results, ConneXion is not communicating properly and needs to be properly configured. Step 4: Create the TAM 3 rd Party Links In this step you will create the links that will appear under the TAM 3 rd party button. Three different DocSTAR-related links are available. Your application may not need all of them, so you may choose to create only those links which you will use. To create the 3 rd party links, run TAM and log on as an administrator. Click on the Utilities button and expand System Administrative DocSTAR TAM Integration Guide Page 9

14 Click on Define TAM Links and click on to continue. In the Defined Links screen choose the 3 rd Party Integration radio button. Click the Add button to create links. Create the 3 rd Party Links select the Pass Client Information checkbox on each link defined below. TAM Online Note: One additional option is present on third party links for TAM Online users. Choose Client Station on each link. This will allow TAM Online client software to use the V-Channel to communicate to the user s local workstation to facilitate the DocSTAR/TAM Online integration. Note: V-Channel Server Service must be enabled on the TAM Online Server and the V-Channel Client software must be loaded on each client PC to enable proper integration. Page 10 DocSTAR TAM Integration Guide

15 Description: Path: Usage: DocSTAR Coverpage Link C:\docstar\tam\dstamcoverpage.exe Generates a barcode cover page from TAM with client, policy, and claim identifiers. Useful in a back end scanning workflow. Description: Path: Usage: DocSTAR Filing link C:\docstar\tam\dstamfiling.exe Pushes client and policy and claim identifiers to DocSTAR during filing. Useful in a front end scanning workflow. Description: Path: Usage: DocSTAR Retrieval Link C:\docstar\tam\dstamretreive.exe Retrieves document(s) from DocSTAR/Integration Agent related to current client or policy. Useful in all workflows. DocSTAR TAM Integration Guide Page 11

16 Once the links have been created, click the button to exit the Utility Manager. Page 12 DocSTAR TAM Integration Guide

17 Configuring DocSTAR for use with ConneXion Step 1: Install the DocSTAR TAM license onto the DocSTAR Host In this step you will need to install the DocSTAR TAM Integration license onto the DocSTAR Host (running v3.3 or higher) in order to activate the DocSTAR TAM Integration module. Step 2: Configuring DocSTAR Admin Open the DocSTAR Administration program, and click on the Integration button. Enter the following information: 1. Select the correct TAM System Type by selecting the correct radio button. 2. Enter a valid TAM user ID and password. This user ID and password will be used by DocSTAR when accessing the TAM database via ConneXion. The TAM Administrator may wish to create a TAM user ID and password specifically for DocSTAR access. 3. Enter the Web Service URL using the name of the ConneXion IIS server. In the screen below the local IIS server was named DS_DEMO1. TAM Online Note: Enter one of the Web Service URLs listed below (depending on which TAM Online Data Center the client connects to): Lisle data center: Dallas data center: Enter TAM ConneXion License Key of 21051P 1. **Note the two spaces between P and If the system utilizes a TAM Online account, enter the TAM Central Agency Tag, otherwise leave this field blank. 6. Enter a valid Who Code as the Activity Followup Code. This code identifies who is assigned to follow up on each Activity log entry created by DocSTAR. The TAM Administrator may want to create a TAM Who Code specifically for DocSTAR. Failing to set this to a valid Who Code will result in runtime errors whenever DocSTAR attempts to create an Activity. 7. Enter the DocSTAR WebView URL, usually DocSTAR TAM Integration Guide Page 13

18 Step 3: Create DocSTAR Filing Templates that utilize the TAM Integration In this step the DocSTAR Filing Templates that utilize the appropriate TAM links will be created. Based on the needs of the client, many aspects of the template(s) used can be highly customized to populate the Title, Keywords or Custom Fields using data provided by TAM or entered by the user. However, the following custom fields are required for TAM integration. Check or Create Custom Fields Four custom fields are required for the TAM Integration and the TAM Integration Setup program creates them automatically. To check on these custom fields, open the DocSTAR Administration program and click on the Custom Fields button. Click Edit to check the properties of each of these four fields. If necessary, click New to create them. Page 14 DocSTAR TAM Integration Guide

19 DocSTAR TAM Integration Guide Page 15

20 Confirm the following properties. If necessary, correct them and click Save. Custom Field 1: Name ActivityRecord Type Text Length 6 Notes Tam Activity Record Custom Field 2: Name ClaimRecord Type Text Length 6 Notes Tam Claim Record Page 16 DocSTAR TAM Integration Guide

21 Custom Field 3: Name ClientCode Type Text Length 7 Notes Tam Client Code Custom Field 4: Name PolicyIndex Type Text Length 12 Notes Tam Policy Index DocSTAR TAM Integration Guide Page 17

22 TAM Templates The following templates file documents with TAM-provided data and allow for integrated retrieval. Each may be customized as long as the required custom fields are populated with the correct data. This table summarizes these templates. The step-by-step process for creating each is detailed below. TAM Integration Front End Scanning Action Destination Description CustomerID None Gets CustomerID, which may be typed, pushed from the 3 rd party link in TAM, or looked up. Policy Index None Gets Policy Index, which may be typed, pushed from the 3 rd party link in TAM, or looked up. Name Keywords Puts the CustomerID and Name into keywords. Title Replace Title Begins building a title with the CustomerID. Transaction Type Add to Title Provides a drop-down list of transaction types. Transaction Date Add to Title Prompts for a transaction date. Policy Info Keywords Puts various policy info into keywords. Client Code CF Custom Field REQUIRED for integrated retrieval. Policy CF Custom Field REQUIRED for integrated retrieval. TAM Integration Front End Scanning Action Destination Description CustomerID None Reads CustomerID from barcode. Policy Index None Reads Policy Index from barcode. Title Replace Title Begins building title with CustomerID and Name. Transaction Type Add to Title Provides a drop-down list of transaction types. Policy Info Keywords Puts various policy info into keywords. Client Code CF Custom Field REQUIRED for integrated retrieval. Policy CF Custom Field REQUIRED for integrated retrieval. Template 1: TAM Integration Front End Scanning This template is valuable in a front end scanning workflow wherein users will push indexing data from TAM. It is also useful for backfile scanning because client and policy data can be looked up in the TAM database directly from DocSTAR without having to look them up within TAM. With a document scanned into the Inbox, choose File Manually, and click the Template button: Page 18 DocSTAR TAM Integration Guide

23 Click New This will bring you to the following Template Creation screen. Choose the Actions tab to create a new action. DocSTAR TAM Integration Guide Page 19

24 Click New to create a new action and select the following: Name CustomerID Data Source TAM Prompt Prompt Text Please enter TAM Client ID Lookup Field Customer ID Destination None Page 20 DocSTAR TAM Integration Guide

25 Click on the Verification tab, and select the following: Verification Type: Exists in TAM Lookup Field CustomerID DocSTAR TAM Integration Guide Page 21

26 Click New for a new action and select the following: Name Policy Index DataSource TAM Prompt Prompt Text Please enter TAM Policy Index Destination None Page 22 DocSTAR TAM Integration Guide

27 Click on the Verification tab, and select the following: Verification Type: Exists in TAM Lookup Field Policy Index DocSTAR TAM Integration Guide Page 23

28 Click New to create another action and select the following: Name Name Data Source Other Action Source Action CustomerID Destination Add to Keywords Page 24 DocSTAR TAM Integration Guide

29 Select the Transformation tab and select the following: Transform Type TAM Lookup Field Customer ID Output Text Use the dropdown list and select the fields to be added, note the space between each field. Default Output Text <Customer Not Found> (This text will be entered if the information is not found). DocSTAR TAM Integration Guide Page 25

30 Click New to create another action and select the following: Name Title Data Source Other Action Source Action CustomerID Destination Replace Title Page 26 DocSTAR TAM Integration Guide

31 Click New to create another action and select the following: Name Transaction Type Data Source Drop Down List Prompt Text Please select a transaction type List Ask the customer for a list of transaction types to be entered. Destination Add to Title DocSTAR TAM Integration Guide Page 27

32 Click New to create another action and select the following: Name Transaction Date Data Source User Prompt Prompt Text Please enter transaction date Data Type Date Destination Add to Title Page 28 DocSTAR TAM Integration Guide

33 Click New to create another action and select the following: Name Policy Info Data Source Other Action Source Action Policy index Destination Add to Keywords DocSTAR TAM Integration Guide Page 29

34 Click the Transform tab and select the following: Transform Type TAM Lookup Field Policy Index Output Text Use the dropdown list and select the fields to be added, note the space between each field Default Output Text <Policy Not Found> This information will be added if the policy number is not found. Page 30 DocSTAR TAM Integration Guide

35 Click New to create another action and select the following: Name Client Code CF Data Source Other Action Source Action CustomerID Destination Place in Custom Field Custom Field ClientCode DocSTAR TAM Integration Guide Page 31

36 Click New to create another action and select the following: Name Policy CF Data Source Other Action Source Action Policy Index Destination Place in Custom Field Custom Field PolicyIndex Page 32 DocSTAR TAM Integration Guide

37 Click on the Options tab, and select the following: Send to Reviewbox: After Action Failure Select the Include Custom Fields in Text Index checkbox. Select the Create TAM Activity Record checkbox Associate the following custom fields to the template: o ActivityRecord o ClaimRecord (not used at this time) o ClientCode o PolicyIndex Save the Template as TAM! DocSTAR TAM Integration Guide Page 33

38 Template 2: TAM Coverpage Back End Scanning With a document scanned into the Inbox, choose File Manually, and click the Template button: Click New This will bring you to the following Template Creation screen. Choose the Actions tab to create a new action. Page 34 DocSTAR TAM Integration Guide

39 DocSTAR TAM Integration Guide Page 35

40 Click New to create a new action and select the following: Name CustomerID Data Source Barcode Engine Destination None Page 36 DocSTAR TAM Integration Guide

41 Click on the Verification tab, and select the following: Verification Type: Exists in TAM Lookup Field CustomerID DocSTAR TAM Integration Guide Page 37

42 Click New to create a new action and select the following: Name Policy Index Data Source Barcode Engine Destination None Page 38 DocSTAR TAM Integration Guide

43 Click on the Verification tab, and select the following: Verification Type: Exists in TAM Lookup Field Policy Index DocSTAR TAM Integration Guide Page 39

44 Click New to create a new action and select the following: Name Title Data Source Other Action Source Action CustomerID Destination Replace Title Page 40 DocSTAR TAM Integration Guide

45 Click on the Transformation tab, and select the following: Transform Type: TAM Lookup Field Customer ID Output Text Use the dropdown list and select the fields to be added, note the space between each field Default Output Text <Customer Not Found> This will be inserted if the customer is not found. DocSTAR TAM Integration Guide Page 41

46 Click New to create another action and select the following: Name Transaction Type Data Source Drop Down List Prompt Text Please select a transaction type List Ask the customer for a list of transaction types to be entered. Destination Add to Title Even though the cover page from TAM doesn t indicate a transaction type, it is often an important datum to add to each title. However, it introduces a challenge the person performing scanning and filing doesn t necessarily know anything about the documents being scanned. How does he or she know what transaction type to select? Here are recommended solutions: Have CSRs hand write the transaction type on each cover sheet when it is printed. Then this information will be available to the scanning/filing clerk. Modify the coverpage.asp file using a suitable editor to include a list of transaction types and have the CSR circle the correct one on each sheet when it is printed. HTML and VBScript programming skills are necessary. Page 42 DocSTAR TAM Integration Guide

47 Contract DocSTAR s Professional Services to customize the cover page with a prompt to ask each CSR for a transaction type (or other custom info) when each cover page is printed. These can then appear on the cover page in a barcode font so that it can be included in a fully automated filing process. Alternately, if the customer doesn t need to have a transaction type recorded, this Action can be omitted, in which case you might create another Action similar to Policy Info which would put the Policy Type and Date into the title. DocSTAR TAM Integration Guide Page 43

48 Click New to create a new action and select the following: Name Policy Info Data Source Other Action Source Action Policy Index Destination Add to Keywords Page 44 DocSTAR TAM Integration Guide

49 Click on the Transformation tab, and select the following: Transform Type: TAM Lookup Field Policy Index Output Text Use the dropdown list and select the fields to be added, note the space between each field Default Output Text <Policy Not Found> This will be inserted if the policy number is not found. DocSTAR TAM Integration Guide Page 45

50 Click New to create a new action and select the following: Name Client Code CF Data Source Other Action Source Action CustomerID Destination Place in Custom Field Custom Field ClientCode Page 46 DocSTAR TAM Integration Guide

51 Click New to create a new action and select the following: Name Policy CF Data Source Other Action Source Action Policy Index Destination Place in Custom Field Custom Field PolicyIndex DocSTAR TAM Integration Guide Page 47

52 Click on the Options tab, and select the following: Send to Reviewbox: After Action Failure Select the Include Custom Fields in Text Index checkbox. Select the Create TAM Activity Record checkbox Associate the following custom fields to the template: o ActivityRecord o ClaimRecord (not used at this time) o ClientCode o PolicyIndex Save the template as TAM Barcode! Page 48 DocSTAR TAM Integration Guide

53 Integrating into other areas of TAM (Optional, for Local TAM only) Does not apply to TAM Online installations. With the addition of the optional module DataLink and the Integrator utility which comes with DocSTAR s Integration Agent, DocSTAR can be integrated with other areas of TAM such as (but not limited to) Vendors, Employees, Companies, Producers, and Brokers. The templates will be setup identically with the exception of the lookup fields and SQL statements. This step will show you how to integrate into the brokers section of TAM. This template can be easily modified to other sections as well. Step 1: Create an ODBC Data Source Data Sources are created by opening the Control Panel and clicking on the Administrative Tools icon. DocSTAR TAM Integration Guide Page 49

54 Then click on the Data Sources (ODBC) icon. Select the System DSN tab, and click ADD to create a new Data Source. Page 50 DocSTAR TAM Integration Guide

55 Select Microsoft Visual FoxPro Driver from the list and click finish. Name the Data Source Tam-Advanced, click on the Free Table directory radio button, and enter the path to the TAM database. Click OK to create the link. DocSTAR TAM Integration Guide Page 51

56 Step 2: Create the DataLinks Open the DocSTAR Administration, and click on the Datalinks button. Name the DataLink Brokers and click Build to create the connection string. Page 52 DocSTAR TAM Integration Guide

57 Select Tam-Advanced as the Data Source and click OK Depending on the field to be integrated into, enter one of the following SQL Statements: (For this example choose the brokers SQL), Select the Schedule checkbox, and set the time to an appropriate update time. Vendors: select rec as Clientcode, Name, street, city, st as state, zip from ins where key="v" Employees: select rec as Clientcode, Name, street, city, st as state, zip from ins where key="e" Companies: select rec as Clientcode, Name, street, city, st as state, zip from ins where key="y" Producers: select rec as Clientcode, Name, street, city, st as state, zip from ins where key="p" DocSTAR TAM Integration Guide Page 53

58 Brokers: select rec as Clientcode, Name, street, city, st as state, zip from ins where key="b" Prospects: select rec as Clientcode, Name, street, city, st as state, zip from prosp These statements will select the client code, name, street, city, state, and zip code from the TAM database, for indexing purposes. Click Save to save the DataLink. Page 54 DocSTAR TAM Integration Guide

59 Step 3: Create the Templates In this step the DocSTAR Filing Templates that utilize the appropriate TAM DataLinks will be created. Based on the methods of retrieval the Client will be using most frequently, you can create highly customized filing templates to populate the appropriate information into the Title, Keywords or Custom Fields using data provided by TAM. With a document scanned into the Inbox, choose File Manually, and click the Template button: Click New DocSTAR TAM Integration Guide Page 55

60 This will bring you to the following Template Creation screen. Choose the Actions tab to create a new action. Page 56 DocSTAR TAM Integration Guide

61 Click New to create a new action and select the following: Name Action 1 Data Source DataLink Search Prompt Text Please enter the Brokers Code Entry Field clientcode Search Field name Destination Add to Keywords DocSTAR TAM Integration Guide Page 57

62 Click on the Verification tab, and select the following: Verification type Exists in DataLink DataLink Brokers Lookup Field clientcode Page 58 DocSTAR TAM Integration Guide

63 Click New to create a new action and select the following: Name Transform Data Source Other Action Source Action Action1 Destination Replace Title DocSTAR TAM Integration Guide Page 59

64 Click on the Verification tab, and select the following: Transform Type DataLink DataLink Brokers Lookup Field clientcode Output Text Click the arrow and choose Name, then click the Add Field button Default Output Text Broker not found Page 60 DocSTAR TAM Integration Guide

65 Click New to create a new action and select the following: Name Transform2 Data Source Other Action Source Action Action1 Destination Add to Keywords DocSTAR TAM Integration Guide Page 61

66 Click on the Verification tab, and select the following: Transform Type DataLink DataLink Brokers Lookup Field clientcode Output Text Click the arrow and choose street, city, state and zip, then click the Add Field button Default Output Text Broker not found Page 62 DocSTAR TAM Integration Guide

67 Click New to create a new action and choose the following: Name Data Source Fixed String Destination Fixed Text Fixed Text broker Add to Keywords Save the template as TAM Brokers! **Note: To modify this template for other areas, simply modify the DataLink sections of actions 1, 2, 3, and 4 to reflect the correct DataLink! DocSTAR TAM Integration Guide Page 63

68 Step 4: Create DocSTAR Integration hotkeys In this step you will create the hotkey links that will allow further integration with TAM. Pressing the hotkey will launch Internet Explorer and display the requested documents. Install the Integrator (provided with DocSTAR Integration Agent) on a client machine that has access to TAM, and launch the Integrator Setup. Click New to create a new hotkey. Navigate in TAM to the window that you would like to create the first hotkey to, in this example we will connect to the Brokers screen, and note the client code for the selected broker. Page 64 DocSTAR TAM Integration Guide

69 From the Integrator Setup window, click Search and enter the client code that was noted in the last step, and click Find. Once the information has been found, the string will be highlighted in blue, click on the Close button. Select the appropriate hotkey combination, and set the Search Text to TEXT =, and click OK DocSTAR TAM Integration Guide Page 65

70 Page 66 DocSTAR TAM Integration Guide

71 The new hotkey will now appear in the display window, Click Edit to modify the Window Text. In the Application section, remove any data that does not remain consistent. In this case the Text: window should read Broker: DocSTAR TAM Integration Guide Page 67

72 Once the Text: area has been changed click the OK button and save the hotkey. Once all of the hotkey combinations have been created, copy the dsintegrator.xml (found in the c:\docstar\ directory) file to the same location of the integrator setup. This will allow for this file to be automatically copied to all of the client stations during the install of Integrator. Page 68 DocSTAR TAM Integration Guide