Interference Detection
You want the Description, Assignee, State, User Severity, and Name for new and existing Interferences in an Interference Report to be set to specific values when Windchill Visualization Services (WVS) is processing Interference Detection results generated by the Creo View Client Adapter. You also want to change the out-of-the-box behavior as to how WVS determines equivalency between Interferences contained in multiple reports.
Background
When an Interference Definition has been submitted for Interference Detection, the Interference results are returned to WVS to be processed. Based on these results, WVS will create a new Interference Report and associate new or existing Interference objects to that report. Each Interference object has Description, Assignee, State, User Severity, and Name attributes with corresponding out-of-the-box values of “blank”, “unassigned”, “Open”, “0” and a unique object identifier. For the State attribute, the default value of “Open” is determined by the out-of-box lifecycle template and maybe different depending on the lifecycle template in use. This document will describe how to customize WVS to automatically set the Description, Assignee and State based on customer business needs.
Additionally, the first time an Interference Definition is submitted for Interference Detection, only new Interference objects are created. All subsequent submissions of the same Interference Definition will result in a new Interference report that may have existing Interference objects from previous reports. The WVS Interference processor has the ability to identify if existing Interference objects already exist and link them to the new Interference report rather than creating new ones. The processor conforms to a set of rules for determining if an Interference described in the results returned from the Creo View Client Adapter matches an Interference object already associated to the current definition. This document explains how to customize these set of rules for determining equivalency between Interferences.
Scope/Applicability/Assumptions
Custom Interference Detection should be used if the default values for Description, Assignee, State, User Severity, and Name for new or existing Interference objects are not adequate. Also should be used if the out-of-the-box rules for determining Interference equivalency doesn’t meet requirements.
Intended Outcome
Using this best practice will allow end users to perform Interference Detection in a manner that addresses their business requirement whenever the out-of-the-box Interference mechanisms are not sufficient.
Was this helpful?