Hi,
It is not recommended to write custom code to perform normalization activity. Atrium has OOB capability to perform normalization, you may need to debug it and find out root cause for failure. Check atrium log in atrium folder where it would be easy to identify root cause. search in log with Instance ID or CI Name where normalization has been failed. And also check CI type mentioned on ProductAliasMapping form and on Product Catalog foundation form. We have faced this issue because of CI type mismatch. What Atrium version are you running on? Regards Kiran On Thu, Jul 18, 2013 at 8:38 PM, Kathy Morris <[email protected]>wrote: > ** > > Hi,**** > > ** ** > > We tried to set a normalization rule for a class of CIs and it was not > working properly.**** > > If we used a filter to set a field attribute in class BMC_OperatingSystem > – would the filter be more of a performance hit?**** > > Not sure of how the workflow is queried/modified thru the normalization > rule. Is it about the same performance hit as a filter?**** > _ARSlist: "Where the Answers Are" and have been for 20 years_ -- *Regards* * **Kiran Patil* *Cognizant Technology Solutions* *Pune, India* *Mob No: +91 989 037 7125 * _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
