Removing Non-mandatory Plan Fragment Attributes

You can modify the rule-base to remove the non-mandatory Plan Fragment attributes from the drop-down displayed on PRODUCT edit on TIBCO MDM native UI, or the Graphical Edit screen.

You can modify the rule-base to remove the non-mandatory Plan Fragment attributes from the drop-down displayed on PRODUCT edit on TIBCO MDM native UI, or the Graphical Edit screen.

By default, Plan Fragments drop-down shows a combination of the following attributes:

  • Plan Fragment Name
  • Plan Fragment Version
  • Plan Fragment Type

To select the attributes to display on drop-down, perform the following steps:

Procedure

  1. Go to $MQ_COMMON_DIR/<enterprise>/catalog/master/<Catalog_ID_PRODUCT>. Where:
    1. enterprise is the actual enterprise name for which the rule can be disabled.
    2. Catalog_ID_PRODUCT is the actual PRODUCT repository ID. It can be seen from the UI in the repository list.
  2. Open the catalogvalidation.xml file with a text editor.
  3. Change the given constraint to remove the values, which are not required. 
    <constraint>
<name>PlanFragments</name>
<description>Displays available PlanFragments for selection</description>
<usefor>
<var>PROVIDEPLAN</var>
     <var>CEASEPLAN</var>
     <var>UPDATEPLAN</var>
     <var>CANCELPLAN</var>
     <var>AFFINITYPROVIDE</var>
     <var>AFFINITYCEASE</var>
     <var>AFFINITYUPDATE</var>
     <var>AFFINITYCANCEL</var>
</usefor>
<action>
<select novalue="default" showoninput="2,3,4"> 
             <!-- 2nd, 3rd and 4th below will be displayed on UI dropdown -->
<table source="sql">
     		<literal>PLANFRAGMENT/PRODUCTID</literal>
                 <literal>PLANFRAGMENT/PLANFRAGMENTNAME</literal><!-- This is 2 -->
                 <literal>PLANFRAGMENT/PLANFRAGMENTVERSION</literal><!-- This is 3 -->
                 <literal>PLANFRAGMENT/PLANFRAGMENTTYPE</literal><!-- This is 4 -->
                 <where type="SQL">
                 	<sql>
                     <neq>
		<literal>PLANFRAGMENT/PLANFRAGMENTNAME</literal>
     	<const type="string">NO_RECIPROCAL_ACTION</const>
                     </neq>
                     </sql>
</where>
</table>
     </select>
</action>
</constraint>