BlueCielo Meridian Enterprise 2018 User's Guide

Sending documents to Meridian Portal

Meridian Portal provides a project type named Standard Project that supports a simple document revision workflow outside of the vault. This makes it possible for new revisions to be made by business partners without access to the Meridian vault. When the revisions (and any new documents) are approved in Meridian Portal, they are automatically imported back into the vault.

You can easily send copies of vault documents to these projects through the Meridian Enterprise integration with Meridian Portal.

Note    
  • This command requires a Package export type publishing job definition in Meridian Enterprise Server. The job must have the Content to include option set to Current project copy. For information about configuring publishing jobs, see the BlueCielo Meridian Enterprise Server Administrator's Guide .
  • Documents sent to Meridian Portal will remain locked to the export package in which they were sent until they are returned from Meridian Portal.
  • When documents are imported back into the vault, they are subject to the Field-Path definition of the vault’s configuration like any other document. This might place the documents in other folders than where they originated.
  • When a document’s parent folder is linked to Meridian Portal, the ProjectFolderPropertySet.ProjectNumber property of the child documents is set to the destination project in Meridian Portal. This data must be sent to Meridian Explorer before the documents can be exported to Meridian Portal. Otherwise, the export job will fail. Therefore, either wait for the next scheduled Meridian Explorer synchronization job to complete or run the synchronization job manually before sending the documents to Meridian Portal. This restriction is expected to be resolved in a future Meridian version.
  • If the Existing documents option of the import profile that is used to return documents from Meridian Portal to the vault is set to New revision and the source document is in a custom workflow but not in the Released state when the document is imported back to the vault, the import will fail. If this happens, change the state of the vault document to Released and restart the import job.
  • The folder used in this task must be of a folder type that has its Can be linked to M360 projects option enabled. If you are unsure of the configuration of the folder types in your system, contact a system administrator.
Before you begin    
  • Do the following prerequisite tasks:
    1. If it does not exist already, create a folder in the vault to represent the Meridian Portal project as described in Creating a folder.
    2. Link the folder to a Meridian Portal project as described in Linking folders to Meridian Portal.
    3. If they do not exist already, create project copies of the master documents (and any required CAD references) into the folder as described in Copying a master document to a project folder.
    4. Wait until the Meridian Explorer repository is synchronized from the Meridian vault. Documents may only be sent to Meridian Portal if they exist in both the Meridian vault and the Meridian Explorer repository. This may be done periodically by a scheduled task or manually. If you are unsure of when this occurs in your system, contact a system administrator.

To send documents to Meridian Portal:

  1. Select the project copies that you want to send.
  2. In the Workflow ribbon, in the Manage group, click Send to Portal. The Send to M360 Project Portal dialog appears and lists the members of the Meridian Portal project that is linked to the vault project folder.
  3. Click options using the descriptions in the following table.

  4. Click OK.

    A dialog box shows the progress as the documents are sent to Meridian Portal in an export package and locked in the folder. If you enabled the Include CAD references option, the referenced documents are sent also, even if they were not selected. If the Export Packages property page is enabled in your system, it shows information about the export package in which the documents were sent. If the document already exists in the Meridian Portal project, the document is added as a new revision.

To send documents to Meridian Portal:

  1. Select the project copies that you want to send.
  2. Right-click over your selection, point to Master/Project Copy, and click Send to portal. The Send to M360 Project Portal dialog appears and lists the members of the Meridian Portal project that is linked to the vault project folder.

  3. Click options using the descriptions in the following table.

    Click OK.

    A dialog box shows the progress as the documents are sent to Meridian Portal in an export package and locked in the folder. If you enabled the Include CAD references option, the referenced documents are sent also, even if they were not selected. If the Export Packages property page is enabled in your system, it shows information about the export package in which the documents were sent. If the document already exists in the Meridian Portal project, the document is added as a new revision.

Document export options
Option Description

Recipient

Select the recipients that you want to work with the documents in Meridian Portal.

Note    You may select a special Project Document Control recipient that will cause the documents to skip the Acknowledge and Accept states of the workflow in Meridian Portal and go to the For Routing state. This assumes that all document compliance checks have been performed in Meridian such as if the Meridian user who is sending the documents from Meridian is also the person who will receive them in Meridian Portal.

Content

Select which document content to send.

Include CAD references

Also send any CAD reference documents to Meridian Portal.

Copyright © 2000-2018 BlueCielo, an accruent company