Wss3sdk: feature activation compliance and scope

Feature activation compliance indicates that there is a necessary relationship between the two feature. Whether in the same range or across different ranges of feature, you can express activation according
Slave relationship. Cross-range activation compliance instructs one feature in a specific range to be activated and requires another feature in different ranges to be activated. A typical cross-range activation example
A child is a website feature that complies with the website set feature.
You generally use the activation compliance relationship for the following two purposes:

• Concept of feature Group
  When one feature is activated, another feature can also be activated. For example, when the default "Working Group collaboration" feature (In \ 12 \ Template
  \ Features \ teamcollab) is activated, which activates many other feature by activating the dependency. When you activate the workgroup collaboration feature
  Activates the feature to make specific list templates available. When you close the feature, the feature it complies with will also be closed (if there are no other feature to follow)
  In this way, the List Templates become unavailable.

• Feature resource assuranceYou may need a website set feature to contain resources (such as a content type) and then include its implementation in a website feature. You can ensure that all feature items are activated by activating compliance.

Activate compliance rules

Activation compliance must comply with certain rules to avoid situations that affect performance, such as loop compliance and compliance chain.

Rules of the same range

• If one feature complies with another feature in the same range, and the second feature is disabled when the first feature is activated, WSS will activate the second featuer.
• If a feature is disabled, WSS will disable the hidden feature of the feature in the same range (when the visible feature of the last feature is disabled ).

Cross-range rules

• Cross-range activation compliance is not supported if the feature complies with a smaller range. For example, a website set feature cannot comply with a website feature.
• If the feature complies with an invisible feature, activation compliance does not support cross-range access. In other words, the feature of a website range cannot comply with the invisible feature in the UI of a website set range.
• If the feature to be followed is disabled, the feature activation will fail. For example, if the feature of a website complies with the feature of a website set, and the feature of the website is disabled, the feature of the website is provided (or the website definition that contains the feature of the website) will fail.

General rules

• Yi
  The slave only applies to a layer of depth. In other words, the compliance chain is not supported. WSS does not support activation compliance with more than one layer (if the last feature is visible ). That is to say, a visible
  The feature follows the second visible feature, followed by the third visible feature. However, WSS supports a visible feature following the second visible
  Followed by the third hidden feature.

• You can direct compliance to a hidden or visible feature, but hidden feature does not have activation compliance.FeatureElementHiddenThe attribute determines whether the feature is displayed in the UI.

• When
  When multiple feature values comply with a given feature, consider the danger of placing one or more feature values in the wrong environment. For example, assume that there is a visible website set range.
  The feature name is Feature B, followed by the name of Feature
  A hidden website set range feature. There is also a third visible site range feature named feature
  C. It also complies with featurea. If Feature B is disabled, feature a is also disabled, which puts feature C in an incorrect situation.