Archiving the CSV file used in splitter

The CSV file used in Splitter is archived. This is implemented to avoid duplicate processing and is persisted for audit purpose. The sublists that are created using splitter are also archived. When you execute the splitter for a CSV file, all the sublists CSV files from $POM_HOME/archive/<org-id>/splitter/<splitter-id>/sublist.csv are archived at $POM_HOME/archive/<org-id>/contactlistimport/sublist.csv_<splitter-id>_timestamp.

Archiving the CSV file for the local configuration in the data source

When the administrator runs the splitter to import the sublist using the local configuration in data source, the configured CSV file is moved in the archive directory matching to organization of the data source and the file name is not valid for the next splitter.

For example, if the local path configured in data source is $POM_HOME/public/<org-id>/contactlistimport/collectiondata.csv, the file is deleted. The file available at $POM_HOME/archive/<org-id>/splitter/<splitter-id>/collectionData.csv_<splitter-id> is moved to $POM_HOME/archive/<org-id>/contactlistimport/collectiondata.csv_<splitter-id>_timestamp after the file is processed.

The remaining CSV and error CSV files are also archived from $POM_HOME/archive/<org-id>/splitter/<splitter-id>/remaining.csv to $POM_HOME/archive/<org-id>/contactlistimport/remaining.csv_<splitter-id>_timestamp.

Archiving the CSV file for SFTP configuration in data source

When the administrator executes the splitter from CSV file using the SFTP configuration in the data source execution, the configured CSV file is moved in the archive directory matching to organization of the data source and the file name is not valid for the contact list import.

For example, for the SFTP configuration in data source is the file is located at $POM_HOME/archive/<org-id>/splitter/CollectionData.csv, the file is moved to $POM_HOME/archive/<org-id>/contactlistimport/CollectionData.csv_<splitter-id>_timestamp location after the file is processed.