Using the “Is Defined/Is Not Defined” Flags

Use the Is Define/Is Not Defined flags to filter items by their defined xProperties. The @defined_as attribute enables you to precisely specify how an xProperty is defined. The attribute uses the following allowed values:

• Class enables you to define an xProperty according to its classification. It does not matter if the xProperty is defined or not defined explicitly.
• Explicit enables you to define an xProperty explicitly. It does not matter if the xProperty is defined or defined using classification.
• Class|explicit enables you to define an xProperty both explicitly and using classification.

The following example retrieves all parts from the database where the xProperty is defined:

<AML>
                                            

<Item type="Part" action="get">

<xp-cost condition="is defined"/>

</Item>
                                            

</AML>

This example retrieves all parts from the database where the xProperty is explicitly defined:

<AML>
                                            

<Item type="Part" action="get">

<xp-cost condition="is defined" defined_as="explicit"/>

</Item>
                                            

</AML>

This example gets all the parts from the database where the xProperty is NOT defined using classification:

<AML>
                                            

<Item type="Part" action="get">

<xp-cost condition="is not defined" defined_as="class"/>

</Item>
                                            

</AML>