Configure the Meridian Enterprise Link To Projects – Meridian Portal Knowledge Base

Meridian Portal can be integrated with Meridian Enterprise so that documents can be sent from Meridian Enterprise project folders to Meridian Portal projects (standard projects, not packages-only projects) for revision, review, approval, and handover back to Meridian Enterprise. This workflow is shown in Moving documents in the workflow. When documents are approved, they are imported back into the Meridian Enterprise project folders automatically by a background task.

To configure the system for this process, perform the tasks listed in the following table. You can use the hyperlinks to jump to the corresponding topics for detailed help. If you have already done some of these tasks, you can jump ahead to the ones that you have not yet done.

Project integration checklist
Step	Completed	Task	Topic Reference
1	o	Verify the Meridian Enterprise version is 2019 or higher.	Meridian Enterprise Version Compatibility with Meridian Portal
2	o	In Meridian Enterprise Server Administration Console, configure the Portal tenancy options. This connection will be used to export documents from the source vaults to the project repositories. The integration commands will be hidden in PowerUser if these options are not set correctly.	Viewing and editing the connectivity settings
3	o	In Meridian Enterprise Server Administration Console, create the Meridian Explorer repository. Only documents synchronized to this repository will be available to Meridian Portal.	Creating a Meridian Explorer repository
4	o	In Meridian Enterprise Server Administration Console, register the Meridian Enterprise vaults that contain the documents that you want to send to Meridian Portal.	Registering a Meridian Enterprise vault
5	o	In Meridian Enterprise Server Administration Console, create and schedule a Configurable synchronization job to keep the Meridian Explorer repository up to date with changes made in the source vaults.	Creating a publishing job Configuring synchronization options
6	o	In Meridian Enterprise Server Administration Console, select properties for the Document number property, Tag number property, and Project number property options for the Meridian Enterprise vaults. These are the key values to identify documents in Meridian Portal.	Managing a Meridian Enterprise vault
7	o	In Meridian Enterprise Server Administration Console, create only one Package Export job (including property mapping to Portal) per Meridian Enterprise vault to specify how to export documents in packages sent to Meridian Portal. If the job definition has the Content to include option set to Current master, the job will fail if the master document does not reside in the Meridian Enterprise project. If the package export job option Publish the source is enabled, PDF source documents that are synchronized to Meridian Explorer and then included in packages sent to Meridian Portal become renditions in Meridian Portal. The original renditions are currently not synchronized. If the packages are returned to Meridian Enterprise, the files will be imported as new renditions, not as source document revisions.	Creating a publishing job Configuring a publishing job
8	o	In Meridian Enterprise Server Administration Console, create an import profile (including property mapping to Meridian Enterprise). This profile specifies how to import document revisions into the Meridian Enterprise vaults from Meridian Portal that were initially sent there in export packages and are now being returned. For Meridian Portal properties of the type Hierarchical Lookup, map only the Code property, which is unique, not the Label property. The Meridian PortalItem ID property currently cannot be mapped to a Meridian Enterprise vault property.	Creating an import profile
9	o	In Meridian Enterprise Administrator, configure the connection to the Meridian Enterprise Server computer.	Configuring the connection to Meridian Enterprise Server
10	o	In Meridian Enterprise Administrator, in the vault Properties dialog, on the Advanced Features tab, set the following options of the Meridian Enterprise source vaults that will use Meridian Portal: Enable packages support option is enabled and specify the Meridian Explorer repository name. Enable AccruentPublisher extension option is enabled Enable Advanced Project Workflow Module option is enabled	Viewing and editing vault properties
11	o	In Meridian Enterprise Configurator, confirm that a project definition exists to represent the linked folders or create one. If it will use an existing folder type, select it with the Folder type option.	Create a Project Definition
12	o	In Meridian Enterprise Configurator, enable the Can be linked to Meridian Portal projects option of the folder types that will send documents to Meridian Portal. A new property set ProjectFolderPropertySet will be created automatically and assigned to the folder type.	Creating and editing folder types
13	o	In Meridian Enterprise Configurator, ensure that the integration commands are enabled on the Command Filter tabs of the desired scopes.	Creating and editing folder types
14	o	(Optional) In Meridian Enterprise Configurator, implement the ExportPackagesPage_IsVisible and ImportPackagesPage_IsVisible event handlers to show the Export Packages and Import Packages pages for documents in the Meridian Enterprise clients.	<PageName>Page_IsVisible event
15	o	In Meridian Enterprise Configurator, implement the ImportPackage_AfterReadProperties event handler to assign the appropriate document numbers to new documents submitted in packages by external business partners. By default, the documents are assigned GUID values as temporary document numbers.	ImportPackage_AfterReadProperties event

For more information about sending documents from Meridian Enterprise, see the AccruentMeridian Enterprise User's Guide.