Type: Model object attribute (text)
The following syntaxes are supported:
Syntax | Description |
---|---|
attrname=attrvalue | Excludes any parallel versions whose attrname attribute value matches attrvalue. Example: status=rejected |
attrname!=attrvalue | Excludes any parallel versions whose attrname attribute value does not match attrvalue. Example: |
EXISTS(attrname) | Excludes any parallel versions that have an attribute named attrname. Example: EXISTS(is_product) |
EXCLUDE_NON_LEAF_NODES | Excludes any non-leaf nodes on parallel versions. |
NOT_EXISTS(attrname) | Excludes any parallel versions that do not have an attribute named attrname. Example: NOT_EXISTS(is_product) |
MATCHING(attrname) | Excludes any parallel versions for which the attrname attribute value matches that of the self version. Example: MATCHING(release) |
NOT_MATCHING(attrname) | Excludes any parallel versions for which the attrname attribute value does not match that of the self version. Example: NOT_MATCHING(release) |
NOT_MATCHING(release)
NOT_MATCHING(platform)
This example illustrates how to disable parallel checkin/checkout warnings about parallel object versions that have a specific release value. For example, to suppress parallel notification when the parallel object version has a release value of 3.0_beta, use the rule:
release=3.0_beta
As in the previous example, you can suppress parallel warnings for object versions with specific platform attribute settings. So if you are doing both SUN, HP, NT, and Microsoft Windows98 development, you can set the parallel_exclude_rules to have the following exclude lines:
platform=sun
platform=nt
platform=hp
platform=win98
The platform values listed must correspond to the values listed in the om_hosts.cfg file under the CCM_HOME/etc directory of the server. There are no notifications of parallels when the parallel object version has one of the listed platform values. However, you receive a notification if no platform value is set on the parallel version, or if it is set to a value not specified.