Description:
This technical document provides additional information about using the MLIST created by the STANDARD_LISTS statement.
Solution:
Sometimes STANDARD_LISTS statements are used to customize the web interface.
When an MLIST and/or an RLIST is created:
- It is created in the domsrvr cache.
- The out-of-the-box web engine only uses the MLIST to populate the data in the web forms.
- The STANDARD_LISTS statement alone does not necessarily affect what entries are listed in a dropdown field. In order to effect the dropdown list of a web interface form, additional changes may be required.
With regards to point #3 above, for example, when the customization requirement is for the Family field in the Configuration Item List search filter be a dropdown that lists only the inactive families, after adding the following to site\mods\majic\wsp.mods:
MODIFY FACTORY nrf {
STANDARD_LISTS {
SORT_BY "id";
WHERE "delete_flag = 1";
};
};
the dropdown does not only list the inactive families.
To complete the intended customization, create a search filter with inactive CI families by changing this line in the list_nr.htmpl file:
<PDM_MACRO NAME=sfDropdown hdr="Family" attr="family" factory=nrf>
to this thes two lines:
<PDM_LIST PREFIX=list FACTORY=nrf WHERE="delete_flag=1"> searchFilterDropdown
("Family","family","","$list.COMMON_NAME","$list.REL_ATT
R","","" );
</PDM_LIST>
In the above example, both MLIST and RLIST are created - including SORT_BY causes the MLIST to be created; including WHERE causes an RLIST to be created.
Note: The example above is a suggestion only - It is not supported by CA Support. It should be tested thoroughly before use.