Send 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.

You can easily send copies of vault documents to these projects through the Meridian Enterprise integration with Meridian Portal. When the revisions (and any new documents) are approved in Meridian Portal, they are automatically imported back into the vault.

Notes about Functionality

This command requires a Package export type publishing job definition in Meridian Enterprise Server. For information about configuring publishing jobs, see the Accruent Meridian Enterprise Server Administrator's Guide .
When a document is sent to Meridian Portal:
- 'For information', it is not locked.
- 'For revision' it is locked.
Documents sent to Meridian Portal remain locked to the export package in which they were sent until they are returned from Meridian Portal. If the package transfer fails, you can unlock the documents from the package as described in Lock And Unlock Documents. Documents must be unlocked from PowerUser or from PowerWeb with a site cache configured and the ActiveX compatibility mode option disabled.
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.
Documents sent to Meridian Portal must first be synchronized to a Meridian Explorer repository. This will be done automatically, if necessary, but it might delay the documents' availability in Meridian Portal.
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 Meridian Portal projects option enabled. If you are unsure of the configuration of the folder types in your system, contact a system administrator.
To include a transmittal sheet with the package, ensure that you have your Transmittal Document Type configured.

Prerequisites

PowerWeb Procedures

Use these steps for PowerWeb.

To send documents to Meridian Portal:

Select the project copies that you want to send.
In the Workflow ribbon, in the Manage group, click Send to Portal.

The Send to Meridian Portal dialog appears and lists the members of the Meridian Portal project that is linked to the vault project folder. The command is unavailable if no parent folder in the document path is linked to a Meridian Portal project.
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 sent for the Issue Reason of For Revision). 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.

The package includes documents referenced by a reference belonging to a Reference Type configured with the option Include to a Portal package.

PowerUser Procedures

Document Export Options

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 recipient that has the Document Controller role or the special Project Document Control recipient that makes the package available to all users with the Document Controller role in the project. It will also cause the documents to skip the Acknowledge and Accept states of the workflow in Meridian Portal and go directly to the For Routing state. A notification email message will also be sent. This feature assumes that all document compliance checks have already been performed in Meridian such as if the Meridian user who is sending the documents is also the person who will receive them in Meridian Portal. If the recipient has the Contractor role: The recipient is notified by email A package of the documents is assigned to the recipient, The recipient can acknowledge receiving the package, which notifies the sender by email.
Package description	Type a description of the package for the recipient.
Include CAD references	Also send any CAD reference documents to Meridian Portal that reside in the same project folder as the selected parent documents. In PowerWeb, when the user sends the document to Portal with CAD references for revision: editable reference documents are included for revision non-editable reference documents are included for revision If the project copy has CAD references to documents outside the project, these referenced documents are included in the package for information. In PowerWeb, when the user sends the document to Portal with CAD references for information: reference documents are included for information
Purpose	Select the purpose for sending the package: For revision — documents that are editable for the user are sent for revision and can be updated in Portal. All other documents are sent for information. For information — all documents are sent for information, and are read-only in Portal
The latest released revision	When selected, the latest released revision of the document is sent to Meridian Portal instead of the working copy (default).