|
Policy Option
|
Description
|
||||
|
Change Packages Enabled
|
Allows the use of change packages. To control whether change packages are optional or mandatory, you can set the related policy for Change Packages Mandatory. To allow the use of change packages, retain the default enabled setting. To disallow the use of the change packages, disable the option by clearing the check box.
|
||||
|
Use Change Package Tracking Labels
|
Determines if a tracking label is created when checking in a member. If enabled, then each checkin operation places the MKS_<cpid#> label on the revision being checked in. To use tracking labels when checking in, enable the option by checking the check box.
By default, this option is disabled.
|
||||
|
Change Packages Mandatory
|
Determines if a change package is required for checkin, check out or lock operation. When disabled, the user decides whether or not to use a change package if change packages are enabled.
Use this option if you want to maintain tight control over all changes to your source code. To enforce the use of change packages, enable this policy option by checking the check box.
By default, this option is enabled.
|
||||
|
Change Packages Transactional
|
Determines if change packages are required to be submitted before its changes are committed to the server repository. Enabling this policy requires users to submit changes packages similar to a change package review, but with no review requirement. Until a change package is submitted, its entries are either deferred or pending, depending on the options the user selects when performing the operation backing the entry.
By default, this option is not enabled.
|
||||
|
Change Package Review Enabled
|
Enforces that change packages go through the review process before being closed. This option must be set to true to use the change package review process; however, change packages can still be used if this option is set to false. The option can be set globally or per-project.
Enabling this option causes the following:
• Change packages are mandatory.
• Change packages must be submitted using the Submit Change Package command.
• Each submitted change package must be reviewed and then accepted by the reviewers listed in the corresponding Change Package Reviewers option settings before the contents of the change package are committed to the repository. By default, this option is not enabled.
|
||||
|
Integrity Manager Enabled
|
Allows communication between the server components for workflows and documents (Integrity Manager), and configuration management. To enable communications between the components, enable the option by checking the check box. This policy option can only be set at the global level and is unavailable for project policies.
If you decide to enable workflows and documents after you have been using configuration management change packages, Integrity Lifecycle Manager assigns an item for each change package. The original creator of the change package is set as the assigned user by Integrity Lifecycle Manager.
By default, Integrity Lifecycle Manager creates the SI Change Packageitem type to manage configuration management change packages. Change packages are then tracked by Integrity Lifecycle Manager in a project called SI Change Package. The SI Change Package project is visible to the everyone group. For more information on changing project visibility, see the Workflow topics.
The SI Change Package project can be renamed; however, once it is renamed, the associated change packages can no longer be used on a stand-alone basis by Integrity Lifecycle Manager.
By default, this option is not enabled.
|
||||
|
Integrity Item Mandatory
|
Enforces if an item must be associated with a change package upon creation. If set to false, the user decides whether to associate a newly created change package with an item. If set to true, then the user must use a change package that is associated with an item. If this policy is locked at the global level, it prevents the creation of any change package without an associated Item.
By default, this option is not enabled.
This setting is ignored when Integrity Manager Enabled is set to false.
|
||||
|
Change Package Reviewers
|
Determines the list of reviewers for change packages. The option can be specified globally, per project, per project with devpath, or for a global devpath. Only one change package review rule appears in any policy section. If event triggers are enabled, reviewers receive e-mail notifications during the review process (see the Setting Up E-Mail Notifications in the Server Administration documentation).
To create a change package review rule, click Change. The Specify Users and Groups dialog box displays. For information on using the filtering users and groups, see the Filtering Data topic in the Getting Started documentation.
For the Change Package Reviewers policy, reviewers display in the following comma delimited format:
• user:<username>
• group:<groupname>
By default, global reviewer rules are used for all projects and subprojects. If project rule is specified, it is used instead of the global rule; unless Append is enabled for the global rule, then the project rule is appended to the global rule, and treated as one rule. Similarly, a project rule is used for all subprojects, unless a subproject rule is specified. Then the subproject rule is used; unless Append is enabled in the parent project, whereby the subproject rule is appended to the parent project rule, and treated as one rule.
To illustrate, if a global rule is specified (but Append is not enabled), and a project rule is specified, then the project rule is used for change packages associated with that project, instead of global rule. If a global rule is specified with Append enabled and a project rule is specified, then the project rule is appended to the global rule, creating a new combined rule used for the change packages associated with that project.
• Change Package Reviewers Appended From Parents displays a listing of reviewers that were inherited from the parent project, global dev path, or the global policy section.
• Change Package Watchers Appended From Parents displays a listing of change package watchers that were inherited from the parent project, global dev path, or the global policy section.
To summarize:
• If Append is not enabled in the parent project, then the subproject rule is used instead of the parent project rule.
• If Append is enabled, then parent project rule is appended by the sub rule to form a single rule.
By default, Append is enabled in the global policy.
|
||||
|
Change Package Watchers
|
Determines the list of change package watchers for a change package. If event triggers are enabled, change package watchers are notified when a review change package closed, thereby signifying that it has completed the review and the changes have successfully been committed to the repository.
Change package watcher rules match the change package reviewer rule syntax. For more information, see the Change Package Reviewers option.
|
||||
|
Integrity Item Fields
|
Determines the list of fields available in the data filter when creating change package items. The option can only be specified globally and is not available for project-level policies. Multiple fields can be specified as comma separated values. The following field types are not supported:
• Computed fields
• Field Value Attribute (FVA) fields
• Item Backed Picklist fields (IBPL)
• Relationship fields
• Attachment fields
To specify fields, enter valid field names. Invalid field names are ignored by the Integrity Lifecycle Manager client.
By default, ID and Summary fields are displayed and no additional fields are specified or displayed for users creating change packages.
|
||||
|
Change Package Description Template Enabled
|
Allows editable change package Description template text to appear when creating, editing, and submitting change packages. The option can be specified globally or per project.
To allow the use of change package description templates, enable the setting by selecting the check box. To disallow the use of the change package description templates, disable the option by clearing the check box.
By default, this option is not enabled.
|
||||
|
Change Package Description Template
|
Specifies the change package Description template text for users to populate. The option can be set globally or per project.
In the Integrity Lifecycle Manager client, when a global change package description template is locked, users are prompted to populate Description template text when creating a change package. When description templates are enabled per project, users are prompted to populate Description template text when editing or submitting the change package.
By default, this option is not enabled.
|
