projects / civicrm-core.git / blame
| Commit | Line | Data |
|---|---|---|
| 6a488035 TO |
1 | <?xml version="1.0" encoding="UTF-8"?>\r |
| 2 | <!--\r | |
| 3 | includeRule can be "include" or "exclude".\r | |
| 4 | include means include the fields listed in the region.\r | |
| 5 | exclude means include all fields not listed in the region AND not listed in the exclusionCorrespondingRegion.\r | |
| 6 | \r | |
| 7 | includeTime is true or false and says whether to include the time component of date fields.\r | |
| 8 | It can be overridden at the Field level.\r | |
| 8ef12e64 | 9 | \r |
| 10 | ifBlank specifies an alternate field to display if the field is blank.\r | |
| 6a488035 TO |
11 | -->\r |
| 12 | \r | |
| 13 | <regions>\r | |
| 14 | <region name="leftpane" includeRule="include" includeTime="false">\r | |
| 15 | <fields>\r | |
| 16 | <field ifBlank="Due Date">Actual Date</field>\r | |
| 17 | <field ifBlank="Activity Type">Subject</field>\r | |
| 18 | </fields>\r | |
| 19 | </region>\r | |
| 20 | \r | |
| 21 | <region name="rightpaneheader" includeRule="include" includeTime="true">\r | |
| 22 | <fields>\r | |
| 23 | <field>Activity Type</field>\r | |
| 24 | <field>Subject</field>\r | |
| 25 | <field>Actual Date</field>\r | |
| 26 | <field>Created By</field>\r | |
| 27 | <field>Revision</field>\r | |
| 28 | </fields>\r | |
| 29 | </region>\r | |
| 30 | \r | |
| 31 | <!-- The rightpane body then gets "everything that isn't in the header", EXCEPT\r | |
| 32 | the fields you specify here. This seems a good compromise\r | |
| 33 | over explicitly having to define which fields we want for each activity type,\r | |
| 34 | given that they are custom.\r | |
| 8ef12e64 | 35 | \r |
| 6a488035 TO |
36 | One future tweak is to improve the way the fields get ordered here. Right now\r |
| 37 | they'll just come out the same order as in the export, which will likely be semi-random.\r | |
| 38 | -->\r | |
| 39 | <region name="rightpanebody" includeRule="exclude" exclusionCorrespondingRegion="rightpaneheader" includeTime="true">\r | |
| 40 | <fields>\r | |
| 41 | <field>Some field nobody likes</field>\r | |
| 42 | </fields>\r | |
| 43 | </region>\r | |
| 44 | \r | |
| 45 | <!-- Haven't decided if this one belongs in here. Probably belongs in yet another config file.\r | |
| 46 | This tells us which field has the semantic meaning of "status", and which value indicates "completed".\r | |
| 47 | -->\r | |
| 48 | <completionStatus>\r | |
| 49 | <label>Status</label>\r | |
| 50 | <value>Completed</value>\r | |
| 51 | </completionStatus>\r | |
| 52 | <!-- Similarly this probably doesn't belong in here. This tells what field(s) to sort by.\r | |
| 53 | -->\r | |
| 54 | <sortByLabels>\r | |
| 55 | <label>Actual Date</label> <!-- Sort by this first -->\r | |
| 56 | <label>Due Date</label> <!-- Then if equal sort by this -->\r | |
| 8ef12e64 | 57 | <label>Date and Time</label>\r |
| 6a488035 TO |
58 | </sortByLabels>\r |
| 59 | \r | |
| 60 | </regions>\r |