Page Comparison

...

1. Customer portal and/or 3rd permitting application send plan review documents 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.

...

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 RE-SUBMITTAL

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

...