Customizing Queries
Customizing Global Sets
Customizing Filters
Queries are used to map objects loaded in CATIA to objects existing in the VPDM. Three queries are provided for mapping objects to ENOVIA V5 VPM: Easy Query, Query Document by Part Id and Mapping Objects using Query. Two queries are provided for mapping objects to ENOVIAVPM: Simple Query and Intermediate Query. Custom queries can be defined based on any of the standard queries. Custom queries can define the parameters that make up the query and/or supply default values for the query parameters. The following steps summarize how the custom query works:
To produce a custom query you will need to:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
In the CATReconcileCustomize.xml file, each custom query will define, at a minimum, the query name, the standard query on which it is based and the xslt (Extensible Stylesheet Language Transformations) files (In/Out). Example of a Custom Query definitionThis sample CATReconcileCustomize.xml file defines three custom queries: UserCriterion_1, UserCriterion_2, UserCriterion_3. All are based on the Query by Object Id standard query. All specify the same In/Out xslt files: UserCriterionIn.xsl and UserCriterionOut.xsl.
How to Use a Custom Query in the Global Query Global SetThe custom queries you develop can be incorporated in the Global Query global set by editing the xml that describes the parameters of this global set. To do this, modify the following file located in: UNIX: <unload_dir>/<os>_a/reffiles/SuppChain MS-Windows: <unload_dir>\<os>_a\reffiles\SuppChain For ENOVIA V5 VPM: CATPDMAutoRulesValuator_GlobalQueryXSMLForm_ENOVIAV5.xml For ENOVIA VPM V4: CATPDMAutoRulesValuator_GlobalQueryXMLForm_VPM1.xml Add a line for each custom query in the
Defining the In/Out XSLT FilesEach of the standard queries is defined by an xml file which describes all the available attributes for the query. When you are mapping objects in the reconciliator and you select a particular query (for example, Easy Query) the xml file defining all the attributes is used to create the query displayed. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
To assist you in defining your own custom queries, the environment variable REC_Display_CustomCriterion=1 can be set to display (in standard output) the xml for any query in the reconciliator.
To create a custom query, you will need to create two xslt files
|
Global Sets are pre-defined rules that allow you to automate the process of defining reconciliation rules. You can customize global sets by inheriting existing (base product) global sets and fixing some of their input values. Global Sets are customized similar to the way queries
are customized, i.e. they are defined in the CATReconcileCustomize.xml Example of a Custom Global Set definition
The following table details global set definition in the xml file
The following table details available input parameters for each global set:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Customizing Filters
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|