Interactive Batch Screening

Adding a new job for interactive batch screening

Follow these steps to add a new job:
  1. Log in to Screener and click Screen from the top menu options.
  2. Click the Batch tab. This tab displays a list of batch jobs added by you along with the latest run of a job such as Job Name, Description, Job Status, Duration, Records, Matched records, Non-Matched records, and % Matched.

    This list is pre-sorted on the basis of latest job creation or edit date.

    You also have the capability of adding, editing, deleting, running, and re-run any job with the help of respective icons.
    Note: This list will be blank if you are creating a job for the first time.
  3. Click the icon to add a new job. The New Job page opens up.
  4. Enter your unique job name in the Job Name field.
  5. If required, enter a description for your job in the Description field.
  6. Click the Browse button, go to your Party data file and click OK.
    Note: The party data schema should be in this format: the in_PartyID field must be unique and not blank.
    Party Data Schema

    in_PartyID|in_Portfolio|in_SourceSystem|in_PartyName|in_PartyFirmName|

    in_PartyFirstName|in_PartyMiddleName|in_PartyLastName|in_PartyMaturitySuffix|

    in_PartyGender|in_PartyIdentifier|in_PartyIdentifierCountry|in_PartyIdentifierFormat|

    in_PartyBirthDate|in_PartyBirthCountry|in_PartyPrimaryCitizenshipCountry|in_PartyResidenceCountry|

    in_PartyPhoneNumber|in_PartyPhoneNumberCountryCode|in_PartyPhoneNumberExtension|

    in_PartyPhoneUsageType|in_PartyType|in_PartyEmailID|in_PartyAddressLine1|in_PartyAddressLine2|

    in_PartyAddressLine3|in_PartyAddressLine4|in_PartyAddressUsageType|in_PartyCity|

    in_PartyPostalCode|in_PartyRegion|in_PartyState|in_PartyCountry|in_PartyGUID
  7. Select the Party Group to define lists against which you want to screen from the list available in the drop-down.
  8. Select the Match Rule for cleansed and uncleansed list from the drop-down.
  9. Set the Match Threshold.
  10. Select the Match Key from the list displayed. The available options are Soundex, Metaphone, Phonix, or no match key.

    Select the check-box if you wish to Use substring as match key for company; this check-box is disabled for no match key. If you select Soundex, Metaphone, or Phonix, the value of Candidate Count will be set to 300 by default; and if you select No Match Key, by default it will be set to 1000. You have the flexibility of overriding these values.
    Note: No Match Key option should not be used for a large party data.
  11. Click the button to save your new job or the button to run the newly created job.

Viewing Details of Batch Screen Jobs

Job details and run history of previously run batch jobs can be viewed through the Batch Screen homepage. Click the desired job name from the list of batch jobs, the Job Details page is displayed.

Viewing Job Details

This page displays various details such as the Job Name, Description, Last Run Status, and the Job Run History.

The last run status and job run history specifies details such as Match Rule Name, Match Threshold, Match Keys, Start Time, Job Status, total number of Records, Matched records, Non-Matched records, and % Matched.
Note: You can re-run any job with the same configuration and party data by clicking the button. You must not try to multiple job re-runs when it is already in a running state.
Editing and Running

If you wish to run the same job with a different configuration or party data, click placed on the top-right of the screen.

A New Run pop-up is displayed showing configurations of the selected job.

You can choose to replace the Party data file by clicking on and go to the path where your new party data file resides. Party Group and Match Rule for cleansed and uncleansed list can be modified using the respective drop-downs. You also have the flexibility of modifying the Match Threshold and Match Keys.

After specifying the new configurations, click to re-run the job.
Note: Job configurations once edited by any user gets locked for all other users. This ensures that only one job can be edited at a time by a user.