Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

This article describes how to use EPR's Connect API to upload documents for a particular project.

Prerequisites

A project record has been created. See Creating a new Project


Step-by-step guide

Call these methods in sequence.

Method
Notes
  1. POST /resources/document/upload/create
  • This method uploads the file to AWS S3 and creates the data records in the following tables: documents, documentPages, documentVersions and the documentPageVersions.
  • The document is then rendered.
  • If the incoming document is a new version of a previously submitted document, you must set the documentPrior_id value equal to the vendor_id of the first submittal.

NOTE: Scout PDF inspector will be invoked automatically for each incoming plan review document. Files rejected by Scout cannot be uploaded to EPR. The customer must correct the issues noted before proceeding. 

2.POST /resources/document/upload/intake
  • If your application will pass plan review assignments to EPR, call this method and set 'needsIntake' to False.
  • Otherwise, if your application will not pass plan review assignments to EPR, call this method and set 'needsIntake' to True. This will make the Project Intake tab visible so that an EPR user can manually perform intake and create assignments.
3. POST/resources/documentAssignments/batchCreate

Creates assignment records and display them in the EPR Review page.

Call this method after Intake if your application passes plan review assignments to EPR. Otherwise, do not call this method.



  • No labels