Preventing a Customer Extension From Being Added (INFRACustoExtensionCheck)

An opening ID is an entry point used to customize business logic.Preventing a Customer Extension From Being Added (INFRACustoExtensionCheck) is used to prevent users from adding a customer extension.

Note: For more information about customization by business rules, see Installation and Setup: Customize: Behavior: Data Setup: Customization by Business Rules.

This page discusses:

General Information

This opening ID is invoked:

  • after calling a Deployment Extension Choice or an INFRADeployment ExtensionComputation opening.
  • Using the Customer Extension command in the LifeCycle section.
  • Calling the AddExtension method in EKL.

Note: at creation time, the values of attributes or the presence of extensions may be difficult to assess. The business logics (BL) call sequence varies according to the application.
ContextCall Sequence
For Add > New ContentPolicy BL > Deployment BL > Initialization BL (or Propagation BL or Attribute Check BL) > Finalization BL > CustoExtension BL.

Note: When the CustoExtension BL is called, fully initialized attributes are available on the object (a proxy). A customer extension filtered out by the CustoExtension BL may temporarily appear in the Add > Content dialog box.

In 3DXML import scenario

CustoType mapping BL > Policy BL > Deployment BL > CustoExtension BL > Import/Export attribute BL > Initialization BL.

The attribute values are the default ones when the CustoExtension BL is called.

In V5 import scenario

CustoType mapping BL > Policy BL > Import/Export attribute BL > Initialization BL > Deployment BL > CustoExtension BL.

Note: Relying on attribute values must be done with caution.
Important: At creation time, the list of extensions on the object is directly linked to the order in which they are given by the Deployment BL. This BL returns a list of extensions that are tested/added in the following sequence:
  • Deployment BL: returns list of extensions
  • for each extension: if allowed by the CustoExtension BL, the extension is added.

DefinitionDescription
PLM Opening IDINFRACustoExtensionCheck
Customization intent Validation
Execution contextClient

Input Objects

Input objects must be of the following types:

  • ThisObject corresponds to the real object or to a proxy because this opening is a plain object one and not a type opening. Hence the possible actions (possible according to Knowledge exposition) on that object may be restricted, specifically navigation (on relation or instance/reference). This is why actions should be restricted to plain (not computed) attribute values reading and EKL non-navigating functions.
  • Parameters corresponds to the context object.
  • Validation

Context Object Parameters

Parameter NameTypeRead or WriteComments
FactTypeAny EKL type—Type of ThisObject in the business rule body.
PolicyString Read-
CustoExtensionNameStringReadName of the customer extension you want to add.