Configuring the publishing options

The number of seconds for the system to wait for each attempt of publishing a document to complete before retrying. The default is 180 seconds. If all attempts fail to complete within this period, the result will be noted in the publishing log of the document but no errors will be generated.

This timeout is applied to each layout of a drawing being rendered. If a drawing contains many layouts, the total timeout time can be lengthy and not interrupt rendering as expected.

The number of retries for the rendering step of a publishing job. This is the number of retries to publish or render a document before proceeding to the next document or rendering attempt.

Attempts will only be called if there is an issue with the rendering profile. If the rendering profile does not fail but there is another issue with the publishing job, Meridian will not retry the rendition.

When large jobs run, Enterprise Server slices them into batches so that it can insert other pending publishing jobs in its queue. This prevents a large job from monopolizing the server and delaying all other jobs until it has completed.

This setting specifies the maximum number of documents to include in each batch. The default is 0 (unlimited), which is the maximum of 10000 documents. When a publishing job includes more documents than the batch size, the job will be truncated to one batch of this size and the remaining documents will be published in separate batches by each scheduled run of the job until the entire job is complete. If the job is not scheduled to run again, the batch is simply truncated.

If enabled, the publishing job is started immediately when new documents are created in the source vault.

Under certain conditions, such as with very large documents, this option can result in the previous revision of the document being published instead of the new document. If this occurs in your environment, disable this option and schedule the job with a short interval instead, for example, once every minute.

Causes the PublisherSourceEvent_BeforePublish, PublisherSourceEvent_AfterPublish, and PublisherDestinationEvent_AfterPublish VBScript events to occur. They can be used to update the publishing status properties in the source or destination. For more information about the VBScript events, see the Accruent Meridian Enterprise VBScript API Reference.

By default, the source document name is used as the name (without file extension) in the destination system. You may also apply the value of a property as the destination document name or you can define an expression to calculate the destination name (only for jobs with a Meridian Enterprise vault as the source system).

To select the property:

1. Click SELECT.

   The SELECT PROPERTY dialog box appears and lists all of the available properties.

2. To filter the list to show only similar property names:

   1. Type the beginning of a property set name or a property name in the filter box.

      The search operator that will be used is Starts With.

   2. Click the search icon .

      The list refreshes to show the results of your filter.

   3. To reset the filter results, clear the filter box and click the icon again.

3. Click the name of the property that you want to use and then click OK.

   The selected name appears as the option value.

To remove the current property:

• Click CLEAR.

  The property name is removed.

To define an expression to calculate the file name:

1. Click EXPRESSION. The EXPRESSION dialog box appears and lists the available properties in the source system.

2. In the Expression pane, type an expression to be evaluated during publishing. The expression may use any .NET compliant methods (except Parse) and operators in the C# language syntax. The result of the expression will be the file name in the destination system. Double-click a property in the list to insert it into the expression. For multi-sheet drawings, layout properties may also be selected, __LayoutProperties._NAME, for example. The result of the expression must be string data. If necessary, you can convert data types, for example, using the ToString method.

   Following are examples of expressions:

   {Title 1} + " " + {Title 2} + " " + {Title 3}
   {PropertyName}.SubString(0, 10)
   {NonStringProperty}.ToString()

   To set the file extension, enable the Enable Meridian script events option and calculate the file extension in the PublisherDestinationEvent_AfterPublish VBScript event handler. For more information about the VBScript events, see the Accruent Meridian Enterprise VBScript API Reference.

3. To validate the expression, click CHECK. Errors in the expression appear in the Errors pane. Correct all errors until the Errors pane is empty.
4. When you are finished editing the expression, click SAVE.

Reproduces the folder structure of the original location in the destination system.

Applies the value of the property as the destination parent folder.

To select the property, perform the steps listed for the SELECT command in the preceding option.

Creates the document's path in the selected navigation view as the path in the destination system.

To select the view:

1. Click SELECT. The USE MERIDIAN NAVIGATION VIEW PATH dialog box appears and lists the available navigation views in the source vault.
2. Click the name of a view and then click OK. The navigation view name appears in the option data.

The name of a folder in the destination system where to publish all documents.

The name of the SharePoint document library to publish the documents to. Publishing to a SharePoint picture library is slower than publishing to a document library due to thumbnail images that are generated by SharePoint. This option is only available for the SharePoint system link.

Applies the value of the property as the destination document type.

To select the type, perform steps similar the SELECT command in the preceding option.

Applies the value of the property as the destination document type.

To select the property, perform steps similar to the SELECT command in the preceding option.

If this option is used in a job for which the destination is a Accruent Project Portal workspace, the property must contain the ID of the document type, not the name of the document type.

Enable this option if the source file (including hybrid parts, if applicable) should be available in the destination system. Hybrid parts are always published if the destination system is a Meridian Enterprise vault.

At least one rendering profile must be specified for every publishing job that will generate renditions.

This setting does not work for the following publishing jobs, because the systems involved do not have the concept of a native document and associated rendition:

• BC Meridian - MS SharePoint

• MS SharePoint - MS SharePoint

• MS SharePoint - BC File System

• File System - MS SharePoint

• File System - File System

• BC Meridian Project Portal - MS SharePoint

• BC Meridian Project Portal - FileSystem

Enable this option to publish the source document redline data as rendition redlines for viewing in the destination system. The Include redlines in rendition option must also be enabled as described in Configure Rendering Options). This is only supported by the AutoVue Desktop Deployment rendering module.

Leave this option disabled for the Documentum system link.

If the Enable feedback functionality option is enabled for a detail page and redlines are edited using that page, the changes will be saved to the Meridian Enterprise vault.

Select which copy of a document to include in packages, the current master revision or the current project copy, if any.

Enable this option to lock any project copies in the repository that are added to packages. This will allow changes only by the package recipient. The project copies will be unlocked when the package is imported back into the repository.

Enable this option to lock the master documents of any project copies that are added to packages. This will allow only revisions by the package recipient to be released as new master document revisions. Project copies will also be made of any master documents that are referenced by the main project copies and they will also be included in the package for reference.