Flow Details

This section describes the flows you need to run while performing scheduled batch screening.

Placement of Data Files

Copy your FCC_Repo to the C: drive. If you are not using the C: drive, change the paths of input and output files for the flows mentioned in the Screening Data/Process flow table. For more information, See Screening Data/Process Flows.

Process Flows

Data flow process data from one stage to the other. Output of one flow becomes the input of the next, this is not true always. There are process flows which use main flows for processing.

  • FCC-Integrated-Flow: An end-to-end integrated flow. It cleanses, screens and creates an alert for the data if any hit is found. This flow contains:
    • ProcFlow_PartyER_N_Screening
Process flows and their main data flows of various modules are summarized in these sections:
  • Party Management Data/Process: Run the FCC_ER_Party_PostProc1_CreatePartySearchIndex_v1 job before running any other flow. The input file for this job is DummyPartySearchIndex.txt and the outputs generated are:
    • To Index: ER_Party_SearchIndex
    • To File: SI_Update_All_Test.csv

Party Management flows:

Process Flow Main Flow Input Output
FCC_ER_Full LoadInitial_ProcessFlow_V1: This flow takes party data as input and performs cleansing, normalization, and intraflow matching before producing the output. FCC_ER_Party_ MainFlow1_Normalization _v1.df: For normalization of data. Takes a file with party data. Fields include:
  • inParty
  • inPartyAddress
  • inPartyPhone
  • inPartyEmail
  • inAccount
  • inPartyAccount
 It produces: Party_MainFlow2_1_input.txt
FCC_ER_Party_ MainFlow2_1_ IntraflowMatch_v1.df: Finds matches between similar data records. Party_MainFlow2_1_input.txt’ which is the output of FCC_ER_Party_ MainFlow1_ Normalization_v1.df It produces:

Party_MainFlow2_2_input.txt
FCC_ER_Party_ MainFlow2_2_ TransactionalMatch AndSurvivorship_v1.df: Finds interflow matches. Party_MainFlow2_2_input.txt which is the output of FCC_ER_Party_ MainFlow2_1_ IntraflowMatch_v1.df It produces:

Party_MainFlow3_input.txt
FCC_ER_Party _PostProc1_Update PartySearchIndex_v1: Updates a party search index based on Party ID. Party_MainFlow3_input.txt which is output of FCC_ER_Party_ MainFlow2_2_Transactional MatchAndSurvivorship_v1.df It produces:

To Index:

ER_Party_SearchIndex
Screening Data/Process Flows: This table summarizes the screening flows:
Process Flow Flow Input Output
Screening_Process: Performs screening and loads data into hub. Party_Screening: It performs party screening and stores results in a file. This will screen the parties against both cleansed and uncleansed List data. Party_MainFlow3_input.txt

This is the output of: FCC_ER_Party _MainFlow2_2_ TransactionalMatchAnd Survivorship_v1.df

 It produces these:
  • To File: Party_Cleansed _Hits.csv
  • To Uncleansed List: Party_ UnCleansed _Hits.csv
Screening_Output: Combines the results of cleansed and uncleansed matches and performs consolidation. This essentially means creating an alert in the Hub model and consolidating all the matches in a single alert. It takes cleansed data file Party_Cleansed_Hits.csv and uncleansed data file Party_UnCleansed_Hits.csv. These are output of: Party_Screneing.df Loads the data into hub.