Differences

This shows you the differences between two versions of the page.

Link to this comparison view

72:ptc_cms_profile_old [2018/07/10 16:27] (current)
bkkr created
Line 1: Line 1:
 +[[:​72:​ptc_integration_old|PTC Integrity Integration Older than 2009]]
 +
 +====== Creating a CMS Profile ======
 +
 +**Steps:**
 +
 +   - Navigate to Process Workbench
 +  - Click dropdown-menu "​Actions / CMS Profiles"​
 +  - Click dropdown-menu "​Actions / Create new CMS profile"​ and select "PTC Integrity"​ in the submenu
 +  - The CMS profile property dialog is shown. Project related settings may be configured here
 +  - Project related settings:
 +      - Name: If you plan to use more than one CMS profile in your project, use this name to distinguish between the different profiles.
 +      - CMS: Selection of a CMS System. Only CMS Systems as predefined in file PKitConfig.xml may be selected.
 +      - Host Name: Name of the Integrity server
 +      - Port: Default: 7001
 +      - Project Name: Name of the project
 +      - User: Username for accessing Integrity. If this field is left empty the username from PKitConfig.xml will be used.
 +      - Password: Password for accessing Integrity. If this field is left empty the username from PKitConfig.xml will be used
 +      - Development Path Name: If no development path name is specified, the main development branch (trunk) will be used.
 +      - Change Package ID: This optional value (e.g. 42:1) will be handed over as an Integrity change package identifier when performing a modifying action (e.g. checkin).
 +      - Create Sub-projects:​ Controls whether to create sub-projects for each subdirectory encountered when adding members. This option is commonly used where you anticipate working with a large directory structure, because multiple sub-projects are easier to manage than many subdirectories within one project.
 +      - Use as Default: If you plan to use more than one CMS profile in your project, you should define one of them as default. This profile will be used by all documents that are not assigned to a specific one.
 +      - Use for Resources: If you plan to integrate resources from this CMS, you should mark this profile.
 +      - Predefined Comment: Here you can predefine global comments every operator can use when files is checked in or lifecycle states is changed.
 +      - Sandbox Path: After saving the CMS profile, Stages creates a sandbox path. The sandbox root path is predefined in PKitConfig.xml
 +