Destination and Naming Convention Profiles

When configuring a job, you can now apply destination and naming convention profiles to the job. A profile is a template that contains certain publishing settings that will be used in the i-model publishing job.

Destination profiles define where the new files will be stored. Naming convention profiles define how the new files are to be named.

Bentley Automation Service delivers default profiles. You can use the delivered profiles as is, edit them, or configure your own.

These profiles are similar to the profile components used with Bentley i-model Composition Server for PDF, except they are selected or configured directly from the Job Builder dialog in Orchestration Framework Administrator and they are stored in the Orchestration Framework database.  All profiles can be reused on subsequent jobs.

Output Destination Folder Profiles

Output destination folder profiles can be specified for intermediate, package, and .imodel files. In the job definition, on the iCS for i-models tab, if the file type is enabled, the profile options are available. The job profile will be listed with a pull-down available listing for all available profiles.

There are four delivered default rendition profiles, one for each file type (intermediate, package, mobile .imodel and transformed output). You can add new profiles, remove existing profiles, and edit existing profiles. To access the Profile Manager dialog, select the ellipsis to the right of the current profile.

Select the “plus” symbol to add a new profile. The appropriate create dialog will display.

Intermediate Profile Manager

For intermediate files, there are two choices for the output destination folder: source file folder and relative folder from source file. Selecting source file folder will store the renditions in the same folder as the input files. For intermediate files, you can specify attribute mapping settings.

 The relative folder from source file will store the output files in a sub-folder under the source folder called Intermediate Files.

Package/.imodel Profile Manager

The package and .imodel output destination folder profiles can be shared which means creating a new profile for one will appear as an option for the other. There are four choices for the destination folder: source file folder, specified folder, relative folder from source file, and relative folder from parent project. All options allow symbols to be used in the folder name specification, versioning options, and attribute mapping.

If using specified folder, you can browse to the specific folder in the current ProjectWise data source or in another data source:

If using relative folder from source or relative folder from project, specify the folder using relative terms (i.e. ..\Output to go up one folder or .\Output to stay on the same level). Indicate if the folder should be created when it does not exist and how the folder environment and storage folder will be set.

Naming Convention Profile

In the job definition, on the iCS for i-models tab, select Options to specify the naming convention profile for intermediate, package, and .imodel files. A default naming convention is delivered for each output file type.

Select the ellipses to the right of the current naming convention profile to get the Naming Convention Profile Manager dialog. Here you can add, remove, and edit naming convention profiles.

Select the plus symbol to add a new naming convention profile. The Create New Naming Convention Profile dialog will appear. Here you can specify the profile name, profile description, file name pattern, and file description pattern.

Note: When adding a naming convention profile for intermediate files, the dialog will be called Create New Fixed file name and description pattern naming convention profile.

Attribute mapping

Attribute mapping defines how attributes are mapped from the input source file to the output destination file. Once defined, the attributes are mapped automatically when the job is executed. To set the attribute mapping definitions, select Attribute Mapping on the output destination folder profile. You can map document attributes and environment attributes.