Video Overview ~ ISIR Corrections Configuration

Step by Step Guide

This guide will walk you through setting up ISIR corrections in CL Connect.

The Automated ISIR Corrections Batch Processing option runs on a daily basis, the time at which the process runs is completely up to the client. At the designated time everyday all ISIRs that are in need of corrections are batched and stored in a designated directory of one's choice.

1. Open CL Connect and select the Clicking Here option on step 1.

2. Select ISIR Batch Corrections from the list and click continue.

3. Pass the API credentials and Application Settings screens (see this guide 'Setting API Credentials' for help with setting your API credentials) and navigate to ISIR Batch Corrections.

4. Enter the Days to Run, file path that the correction files will be placed in and which days and times you would like the service to run.


***File name is optional and only recommended if you plan on using the TD Client integration shown below. If you plan on using this, we recommend you use the following name (or some variation of): CORR{{AYEnd}}IN{{MM-dd-yyyy-HH-mm-ss}}. More details regarding this can be found below.***

5. Click continue and then Save on the next screen.

*ISIR Corrections File Path: The path used by the ISIR Correction process. If using the ISIR Upload / AwardLetter Upload features,the path

must be different. You must also allow the appropriate read/write permissions on the specified path.  

File Name:  The name of the file. Default value will be AwardYearInteger_UniqueGUID.txt if none specified.

  • Available tokens:
    • {{AYLong}}
    • {{AYShort}}
    • {{AYStart}}
    • {{AYEnd}}
    • {{MM-dd-yyyy}}
    • {{MM-dd-yy}}
    • {{MM-dd-yyyy-HH-mm-ss}}

File Extension: 
The extension for the batch file. Options include .txt and .dat. Default is .txt

*Time to Run: The time to run the process. Default value is 12AM UTC time.

*Days to Run: The days of the week to run the process. At least one day must be selected.

TDClient Integration Enabled: The ability to turn on/off TDClient Integration.

* = Required

Web.config example:

Optional - Only if you want TD Client to send the correction files back to the Fed.

If you chose to enable the TD Client integration, please follow the steps below:

***You must install an instance of TD Client on the machine running CL Connect.***

***Please install TDClient directly within the C drive. Any spaces in the file path may cause the up***

1. Change the option from no to yes and enter the requested file path information.

TDClient Executable Path: The location of the tdclientc.exe file.

TDClient secfile Folder Path: The location of the TdClient secfile file. This is needed as part of the required fields for the send file command

Archive File Path: The location where isir correction files will be placed for archiving once they are sent to TdClient. This cannot be the same path as ISIR Corrections File Path

Name of Transfer: This names the transfer being created.

SAIG mailbox User ID: SENDUSERID is a required parm in the Transfer command line. You must use a valid TG ID as a place holder in this field. Using your own TG ID is highly recommended. 

Note: For more information about TDClient you can refer to their documentation here:

**The Host Communications Guide is a good document to review for TDClient**:

Move on to the "Test Correction File" page.