Example usage of EPM-set-condition-by-check-validation-result

NX setup
----------
In NX, setup the validation test
Analysis --> Check-Mate --> Setup Tests...

In the Tests tab, we will use

Modeling --> Examine Geometry --> Objects - Tiny

as a Chosen Test
If you highlight the chosen test and press the Customize button on the right,
you will see that this corresponds to %mqc_check_tiny_object

On Run Options tab,

be sure *not* to generate an external log file,
else results that passed are *not* saved in part.
 Also, set “Always Save” for the other save options, just to be sure.

Teamcenter setup
----------

Here, our workflow has a Do Task, a Condition Task that branches out to two other Do Task and ends
with an Or Task.

Do Task 1 --> Condition Task 1 -+- true -> Do Task 2 -+- Or Task 1
| |
+- false -> Do Task 3 -+
The workflow handler of interest is in the Condition task. Its Complete action shows

EPM-set-condition-by-check-validation-result

Argument(s) Value(s)
-------------------- --------------
-rule_item_revision dgvd/A

Referencing the rule_item_revision argument in the handler, our test ItemRevision “dgvd/A” has a
ValidationRuleSet dataset attached with a Validation relation.
Below are the contents of the rule set file within the dataset

<?xml version="1.0" encoding="utf-8"?>

<!-- GENERATED BY: PLM XML SDK 7.0.3.292 -->
<PLMXML xmlns="http://www.plmxml.org/Schemas/PLMXMLSchema”
xmlns:rule="http://www.plmxml.org/Schemas/PLMXMLValidationRuleSchema"
schemaVersion="6" date="2008-06-25" time="10:40:36" author="tester">
<rule:ValidationRuleSet id="id1" name="Test_rule_set_1"
ruleRefs="#id3">
<Description>Validation Rule Set
example</Description></rule:ValidationRuleSet>
<rule:ValidationRule id="id3" name="rule 2"
checker="mqc_check_tiny_object" mandated="true">
<rule:Target id="id2" targetType="Dataset">
<Item value="UGMASTER"></Item>
<Item
value="UGPART"></Item></rule:Target></rule:ValidationRule></PLMXML>

Note the checker="mqc_check_tiny_object" which matches what we found on the NX side.

Validation steps
----------
In NX, we create a tiny sphere part that would fail mqc_check_tiny_object
e.g.
Diameter = .001 mm
For comparison, we also create a part that would pass mqc_check_tiny_object
e.g.
a block 100mm by 100mm by 100mm
If mqc_check_tiny_object is not run or fails (i.e. the tiny sphere) and we run the workflow on the
dataset, then the workflow goes to the false path.
However, if mqc_check_tiny_object passes validation on the part (e.g. the block part), then the
workflow goes to the true path
Roy Fujii