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 19 Current »

This article provides information a high level overview the project and plan review lifecycle and typical integration scenarios for connecting e-PlanREVIEW® (EPR) to an external application using our Connect API toolkit.


In this article:


High Level Overview

A typical plan review Project undergoes this basic process:

  1. Create a Project: A project record is necessary as a container to upload files.
  2. Upload files via the Upload API
    1. Upload files
    2. Trigger assignment creation for plan files to be reviewed
  3. Conduct plan review and Complete assignments.
    1. Reviewer will give a status upon completion of assignment (completed, cancelled, approved, etc)
  4. A deliverable package with the marked up documents is prepared, this completes the 1st submittal cycle.
    1. Return the deliverable package to the customer for corrections via 3rd party upload api or pull from EPR api.
  5. Corrected documents are provided by the customer as the next submittal. Repeat from step 2.
    1. Existing assignments are reopened with a Not Started status and markups are carried forward to the latest version.
    2. Repeat steps 3 and 4
      • The process repeats until all noted issues are resolved and project is closed or archived.


Integrated Environments

Variations on the process described above include the following scenarios when EPR is integrated to another application using our Connect API toolkit:

Integration Option 1

The integrated application:

  1. creates a project via project create API
  2. uploads file to EPR
  3. manually creates plan review assignments in EPR thus not using EPR's API
  4. return final PDF files to the integrated application using API calls provided to EPR.

Integration Option 2

  1. creates a project via project create API
  2. uploads file to EPR
  3. creates plan review assignments in EPR using EPR's assignment API
  4. during plan review, based on some event trigger a callback to 3rd party application
  5. return final PDF files to the integrated application using API calls provided to EPR.


Best Practices

For stand alone deployments, email notifications should be configured to alert the appropriate project team members when a project cycle is set to Cycle Complete so that a deliverable package can be prepared.


































  • No labels