Page Comparison

...

INTAKE

1. Customer portal and/or 3rd permitting application send plan review documents in PDF format to Partner applications for validation.
2. Partner application calls the e-PlanSoft PlanSoft™ Scout API to validate each plan review document.
3. Plan Review documents that do not pass Scout will not be accepted by e-PlanREVIEW® (EPR).

PROJECTS

1. Partner application creates the new project in EPR. This includes the project info, project address and project team members.
   1. If the contact record does not exist, Partner application creates the contact record.
   2. Partner application associate the contact record to the project record as the primary contact.
2. Partner application updates the project information/address/contact when it is modified in the permitting application.

DOCUMENTS

1. Partner application calls the EPR API to upload plan review documents in PDF format. Partner is responsible for document versioning (1st submittal, 2nd resubmittal, etc.).: step-by-step guide
2. To upload project attachments instead of plan documents, you will need to send files to our AWS S3 bucket. There are 3 calls you have to make:
   1. Get s3 presigned URL link to our AWS S3 bucket via the API:
      1. Method: GET
      2. URL: https://<epr_url>/resources/s3/uploadUrl?contentType=text%2Fxml&directory=attachments&filename=sample.xml
         
         
   2. PUT the file to this URL
      1. Method: PUT
      2. AWS S3 URL from step 1
         
         
   3. Finally, call project attachment api to finalized upload
      1. Method: POST
      2. URL: https://<epr_url>resources/projectAttachments
         
         
3. Supporting attachments are also uploaded to EPR but are not inspected by Scout.

ASSIGNMENTS

1. Partner application calls the EPR API to create plan review assignments for the newly uploaded plan review documents.
2. Partner application calls the EPR API to update an existing EPR assignment record (due date, status, user reassignment etc.) as necessary.

PLAN REVIEWEPR PUSHES TO EXTERNAL APPLICATION

1. EPR calls the Partner application API to report a change in the plan review assignment status.
2. EPR calls the Partner application API to when all plan review assignments are complete.

...

DOCUMENT CHECK IN

1. EPR users will create a compressed ZIP file of from all the selected documents to return to Partner application (reviewed plans, attachments/correction reports, etc.)
2. EPR will call the Partner Partner application ‘check in’ API to provide a URL to retrieve the ZIP file from the EPR server.

...

DOCUMENT RE-SUBMITTAL

If any of plan review documents need corrections, repeat the process starting at INTAKE.

...