QuickListMaster.xml file includes the following set of tags for each rule:
Name. Case-sensitive code-style name (that is, one with no spaces or special characters) that uniquely identifies the rule. The name is used throughout all the files to link information together, and it must be consistent with the
<name>value in the rule definition.
Enabled flag. Flag to indicate whether or not the rule should be used. You must change this flag on any predefined rule that is to be replaced by a custom rule. Allowed values are N and Y.
File path. Path to the file that defines the rule, relative to the
quicklistdirectory. This path is as follows:
>for predefined rules
>for custom rules.
We recommend that you make the values of
>unique for each rule across the
Following is a sample
<quicklist> <derivation> <name>tasks_assigned_to_me</name> <enabled>Y</enabled> <file>core_derivations/tasks_assigned_derivation.xml</file> </derivation> <derivation> <name>work_items_on_last_time_sheet</name> <enabled>Y</enabled> <file>core_derivations/work_items_on_last_time_sheet.xml</file> </derivation> <derivation> <name>requests_available_to_you</name> <enabled>Y</enabled> <file>core_derivations/request_resources_assignees_derivation.xml</file> </derivation> <derivation> <name>my_tasks</name> <enabled>Y</enabled> <file>custom_derivations/MyTasksRule.xml</file> </derivation> </quicklist>
After you complete the new rule and the revision of the
QuickListMaster.xml file, the application can apply the new rule.
For more information about adding or revising rules, see Configure custom rules for the Suggested Items list.