S3 has functionality to configure the application to work with two file types:
- Inbound: Another location sends the file to the application, which binds its contents to the appropriate entities to update the affected database table(s).
- Outbound: The application compiles the file and sends it to another location, which regards it as an inbound file.
Regardless of whether a file is inbound or outbound, the following project files are required to successfully process it:
- File business object: This is a C# class that hosts the logic for processing or creating the file. In the current version of the framework, the inbound file business object inherits from busInboundFileBase and the outbound file business object inherits from busFileBaseOut. Older versions inherit from busFileMain.
- Staging folders: These are project folder locations where the application keeps the file during various stages of processing: upon reception/creation, during validation, etc.
- XML file: This configures important file properties and contains the record layout that the application reads to either process or create the file.
- Application record: This maps the XML file to the application so it can refer to it in the job schedule, batch handler, and elsewhere.
- Application job schedule record: This instructs the application when to process or create the file. It defines the steps the application should follow when doing so.
- Batch handler switch(es): This is the logic for running each step in the job schedule record.
This post is part of the Files topic. Click here to open the Files Overview.