Third-Party options when Interfacing with eLandings

Third-party developers can interface with eLandings in several ways depending on need and resources. Third-party developers may opt to make use of the eLandings public web services. Or third-party developers may attempt to build integration strategies around the eLandings web page data import and export capabilities.

• The third party system can download reports from eLandings using the web services. Typically the third party system would download once a day, but could download more or less often. All reports submitted or updated within a specified time period would be downloaded.
• Users can download each report from its web page as they complete edits to it. They can then load the report into their third party system.
• Users can download a set of reports from the report extract web page, and then load the reports into their third party system. All reports submitted or updated within a specified time period would be downloaded.
• The third party system can generate an eLandings report based on data entered by users. The report can be submitted to eLandings via the web services. This approach requires that the third party system be able to notify users about errors if the report fails validation on submission.
• The third party system can generate an eLandings report as a file, based on data entered by users. A user can then import the report file into eLandings using the report import web page, and then submit the report, making any edits needed. This approach work is preferred if the report has IFQ, since the generation of IFQ reports from landing report data is complex, and the eLandings system provides tools to assist the user in working through issues and getting the IFQ report data correctly aligned with the report data.

Third party developers can architect their systems to use more than one of these approaches, depending on specific user needs.