You are here: Understanding the system architecture > Understanding transfers to Project Portal

Understanding transfers to Project Portal

When a Meridian Enterprise user transfers documents to a Project Portal workspace, the following steps are performed:

  1. Schedule: Document transfer is scheduled by registering it in a Meridian Enterprise vault table.

    Note    This is different than the algorithm that is used for regular GCF updates in which the export processor searches for modified documents and registers them in the vault table. Direct registration is done to make the updates that are sent to Project Portal more controllable. However, the regular algorithm can be enabled with the ProjectPortalSyncModifiedDocs setting described in Configuring the export settings.

  2. Export: The Meridian Enterprise export processor reads the record in the table, creates a briefcase, and exports the document data into the briefcase as shown in the following figure. The export processor sets the In Transit field for the exported documents in the table.
  3. Import: The Project Portal import processor detects the received briefcase and imports its contents into the destination workspace. Upon completion, it clears the In Transit field in Meridian Enterprise vault table through Meridian Enterprise Web Access.

Related concepts

Understanding the architecture

Understanding share creation

Understanding transfers to Meridian Enterprise

Understanding status updates

Understanding the Meridian Enterprise extensions