Differences

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

Link to this comparison view

72:ptc_new_profile [2018/07/10 14:49]
bkkr created
72:ptc_new_profile [2018/07/10 14:59] (current)
bkkr [CMS Profiles]
Line 3: Line 3:
 ====== CMS Profiles ====== ====== CMS Profiles ======
  
-For the creation of a new CMS profile for your Stages project you can directly select Integrity in the submenu of the action “Create new CMS profile”. If you defined both interface types in PKitConfig.xml – the interface for Integrity release 2009 SP7 or newer and the interface for older Integrity releases.+For the creation of a new CMS profile for your Stages project you can directly select Integrity in the submenu of the action “Create new CMS profile”. If you defined both interface types in PKitConfig.xml – the interface for Integrity release 2009 SP7 or newer and the interface for older Integrity releases. If you defined only one Integrity interface you will have one submenu entry named “PTC Integrity”. Entering a name for a CMS profile is optional. When a //name //is specified it will be displayed in forms where a document/​file is associated with a CMS profile.
  
-If you defined ​only one Integrity ​interface ​you will have one submenu entry named “PTC Integrity”.+Integrity CMS profiles require the selection of an Integrity host (as defined ​in PKitConfig.xml). Moreover the name of an existing (Source) ​Integrity ​project (or subproject) must be specified (e.g. /​MY_PROJECT/​MY_SUBPROJECT/​project.pj or C:/​Projects/​Project1/​project.pj). Optionally ​you can also reference an existing development path (by entering its name; e.g. MY_DEV_PATH) if it shall be used instead of the mainline.
  
-Entering a name for a CMS profile is optional. When a //name //is specified it will be displayed in forms where a document/​file is associated with a CMS profile. +You can also define if change packages are mandatory. Defining change packages as mandatory has the following effect: Users have to select a change package of their own when they perform one of the following operations on a file: Create checkout, checkin or change state. They can also go to the Integrity web client and create a new change package there if necessary. Pressing the button “Refresh” after that will update the list of selectable change packages in the Stages form. When change packages are not mandatory, users will not be asked for a change package id when they perform these file handling operations.
- +
-Integrity CMS profiles require the selection of an Integrity host (as defined in PKitConfig.xml). +
- +
-Moreover the name of an existing (Source) Integrity project (or subproject) must be specified (e.g. /​MY_PROJECT/​MY_SUBPROJECT/​project.pj or C:/​Projects/​Project1/​project.pj). +
- +
-Optionally you can also reference an existing development path (by entering its name; e.g. MY_DEV_PATH) if it shall be used instead of the mainline. +
- +
-You can also define if change packages are mandatory. +
- +
-Defining change packages as mandatory has the following effect: Users have to select a change package of their own when they perform one of the following operations on a file: Create checkout, checkin or change state. They can also go to the Integrity web client and create a new change package there if necessary. Pressing the button “Refresh” after that will update the list of selectable change packages in the Stages form. +
- +
-When change packages are not mandatory, users will not be asked for a change package id when they perform these file handling operations.+
  
 **Caution**:​ This setting must be in convergence with the change package policy in Integrity (otherwise the mentioned file operations will lead to an Integrity error message). **Caution**:​ This setting must be in convergence with the change package policy in Integrity (otherwise the mentioned file operations will lead to an Integrity error message).