Base de datos ICYT

Reduces the effectivity range of problem item objects attached to a change object so it does not overlap with the combined effectivity range of the solution items. This facilitates the release of solution items to replace problem items for a given effectivity range.

Note _{This handler should be used only for 4th Generation Design (4GD) objects.}

For example, a casted component C is a solution item for a forged component F, a problem item with a unit effectivity of 1 through 10 in 4G Designer on 4GD data. C is assigned the same effectivity (unit 1 through 10) because it has the same purpose. To replace C with F with unit effectivity 3 through 10, a change notice is created that tracks F as a problem item and C as a solution item. The change notice is assigned an unit effectivity of 3 and up. The handler applies the change notice effectivity to the solution item and then reduces the effectivity range of the problem item. As a result, C has an effectivity range of 3 through 10 and F’s effectivity is reduced to 1 through 2. For every unit in the range of 1 through 10, either C or F is effective. The effective ranges of C and F neither overlap nor do they have a gap.

The effectivity range of the change is determined by the release status attachment of the workflow process. If the process does not have a release status attachment, the release statuses of the change object are used. An error occurs if multiple release statuses with effectivity data are found and handler arguments are used that require the definition of the effectivity range of the change object.

EffectivityConfigurable objects with no effectivity data behave as if

they had an effectivity condition Unit=1 OR Unit!=1 (in other words,

TRUE unless explicitly stated otherwise). For more information, see the defaultSolveTypePreferenceName argument.

The effectivity range to be subtracted from a problem item attachment is the combined effectivity range of all EffectivityConfigurable objects in the corresponding solution item set. You can use the designatorProperty argument to define corresponding sets of solution and problem items. Solution item sets that do not correspond to a problem item set do not affect problem item effectivity ranges. Problem item sets that do not correspond to a solution item will be effected out permanently. Solution items without EffectivityConfigurable behavior (for example, datasets) are skipped in the computation of the effectivity range to be subtracted.

The EffectivityConfigurable behavior automatically checks out and revises POM revisable objects before changing effectivity data.

The handler only modifies objects exposing EffectivityConfigurable behavior, such as Cpd0DesignElement. These modifications are not subject to access control rules.

SYNTAX

CONFMGMT-cut-back-effectivity

[ -engineeringChangeTypeName = { ChangeNoticeRevision | object-type-name} ] [ -problemItemRelationshipName = { CMHasProblemItem | relationship-type-name } ] [ -solutionItemRelationshipName = { CMHasSolutionItem | relationship-type-name } ] [ -verifyEffectivity = { NoAction | Compare | Validate} ]

[ -designatorProperty = { “” | property-name} ]

[ -defaultSolveTypePreferenceName = { “” | preference-name} ] [ -defaultSolveTypePreferenceScope = { “” | preference-scope} ]

ARGUMENTS

-engineeringChangeTypeName

Sets the type of the target object managing the change. Any object type name is valid as long as there is only one such target attachment and the object type supports the relationship types specified below. The default value is ChangeNoticeRevision.

-problemItemRelationshipName

Sets the type name of the relationship that associates objects to be replaced by the objects specified by the -solutionItemRelationshipName argument with the change object. The type name must be compatible with the above change object type. The default value is CMHasProblemItem.

-solutionItemRelationshipName

Sets the type name of the relationship that associates objects, which replace the objects specified by the -problemItemRelationshipName argument, with the change object. The type name must be compatible with the change object type. The default value is CMHasSolutionItem.

-verifyEffectivity

Specifies the action to take with respect to the effectivity range of the change object and its solution item attachments. The action skips solution items for which no EffectivityConfigurable effectivity is saved or which do not expose

EffectivityConfigurable behavior. Possible values are:

• NoAction

Takes no action. This is the default. • Compare

Displays a separate warning for every solution item whose effectivity range does not equal the release status effectivity range of the change object. An error is returned if no release status effectivity has been saved for the change object. • Validate

Returns an error if any solution item’s EffectivityConfigurable effectivity range does not equal the release status effectivity range of the change object. An error is returned if no release status effectivity has been saved for the change object.

-solutionItemEffectivity

Specifies the action to take for solution item effectivity. Possible values are: • NoAction

Takes no action. This is the default. • ApplyCMEffectivity

Reduces the EffectivityConfigurable effectivity range of each solution item to be within the range of the release status effectivity of the change object (in other words, combines both with a logical AND). An error is returned if no release status effectivity is saved for the change object. The result is

identical to action ResetToCMEffectivity for solution items, for which no

EffectivityConfigurable effectivity has been saved, or which do not expose EffectivityConfigurable behavior.

• ResetToCMEffectivity

Sets the EffectivityConfigurable effectivity range of each solution item to equal the range of the release status effectivity of the change object. An error is returned if no release status effectivity has been saved for the change object. The result is identical to action NoAction for solution items, which do not expose

EffectivityConfigurable behavior. -designatorProperty

Specifies the property to use to group change object attachments into sets for the purpose of replacing problems items with corresponding solution items. These sets are formed by virtue of having a common value for the same property (for example, a logical designator as stored on a partition membership in the preferred partition scheme). If a property is specified, the solution item attachments of the change object are grouped into sets formed by the value for this property. If the property name is an empty string (the default) there is one set for all solution items that corresponds to one set for all problem items.

-defaultSolveTypePreferenceName

By default, EffectivityConfigurable objects without effectivity condition behave as if they had an effectivity condition Unit=1 OR Unit!=1, that is, equivalent to the Boolean constant TRUE. If the value for this argument is different from the empty string (default) it is expected to specify a preference having the same semantics as defined for TC_Default_Solve_Type in the confmgmt module, which can be used to define whether or not EffectivityConfigurable objects without effectivity condition pass effectivity filter criteria. If the given preference is not found in the scope specified by the defaultSolveTypePreferenceScope argument a default solve type of 529 is assumed, that is solveMismatch|solveFalse|solveInvert except where explicitly otherwise stated. The effectivity range that is assumed for

EffectivityConfigurable objects without effectivity condition can be configured

to be the following: • Unit=1 OR Unit!=1

Equivalent to the Boolean constant TRUE, if the solve type specifies that

EffectivityConfigurable objects without effectivity condition pass effectivity

filters.

• Unit=1 AND Unit!=1

Equivalent to the Boolean constant FALSE, if the solve type specifies that

EffectivityConfigurable objects without effectivity condition do not pass

effectivity filters.

-defaultSolveTypePreferenceScope

Specifies the scope to search for the above preference. An empty string (the default) is treated the same as 4, which is mapped to TC_preference_site via

PLACEMENT

A typical placement is to precede the add-status action handler that attaches the release status to the change object, so that the release status is not attached to the change object if this handler errors out.

RESTRICTIONS

None.

EXAMPLES

• This example illustrates the use of the handler with a change object type that is available in the Teamcenter foundation template. It configures the handler to reduce the effectivity of the solution item attachments to not be effective beyond the effective range of the change.

Argument Values -engineeringChangeTypeName ItemRevision -problemItemRelationshipName IMAN_reference -solutionItemRelationshipName IMAN_manifestation -verifyEffectivity NoAction -solutionItemEffectivity ApplyCMEffectivity -designatorProperty object_desc -defaultSolveTypePreferenceName TC_Default_Solve_Type -defaultSolveTypePreferenceScope 4

CPD-update-item-realization