Learning Objective
By the end of this module, participants will be able to:
Understand and configure the enrollment file transformation and validation process.
Identify and set up the necessary components, including FTP locations, archive paths, and database configurations.
Manage and troubleshoot the transformation and validation workflows.
Utilize custom plugins for data handling and formatting within the enrollment process.
| Info |
|---|
Use Case - : Convert Customer/Vendor Enrollment Files to Specific ADI Format Description: The process aims to convert customer or vendor-specific enrollment files into specific ADI standard format (eEnroll2 Template). Each employee record in the enrollment source file, which comes in multiple lines for each benefit within a single policy, needs to be transformed into a single record per employee per policy. |
...
Client: The entity providing the enrollment files.
System: The automated process that handles file transformation and validation.
End User: The administrator managing the process and handling notifications.
PreconditionsPre-conditions:
The client file is available in the input FTP location.
The system is configured with the correct source and target file paths.
Required plugins and process flows are deployed and functional.
...
Download the Object Zip: Zip Link and migrate to Adeptia Connect platform
Post conditions:
The client file is archived.
A standard XML file is created in the in-progress folder.
The original client file is deleted from the input FTP location.
An entry file named
CLIENT_FILE_RECEIVEDis created.
...
The PF_Enrollment_Inbound process flow facilitates the conversion of client-specific enrollment files into a standardized canonical format. This standardized format, typically XML, enables seamless integration and processing within User's systems.
...
Process Steps:
File Data Retrieval:
The process initiates by fetching the client-specific enrollment file from a designated FTP location, identified based on a specified file pattern.
Archiving Original File:
Upon retrieval, the original client file is copied to an archive folder. This archival step ensures a backup for future reference or auditing purposes.
Format Conversion:
The retrieved client file undergoes conversion into a standard XML format. This transformation prepares the data for further processing and integration.
Temporary Storage:
The newly formatted XML file is stored in an in-progress folder. This temporary storage facilitates subsequent processing steps without disrupting ongoing operations.
File Handling After Successful Conversion:
Post successful execution of the conversion process, the original client file is deleted from its original location on the FTP server. This helps maintain data cleanliness and prevents redundancy.
Metadata Creation:
An additional step involves the creation of an entry file named CLIENT_FILE_RECEIVED in JSON format. This file contains metadata such as the original file's name, its path, and the timestamp indicating when the file was received. This metadata aids in tracking and managing file-processing activities.
PF_Enrollment_Data_Validation Process
...