[Rt-commit] rt branch, 4.4/assets-customfieldgrouping-doc, created. rt-4.4.0-262-g2e2c211

[Jim Brandt]

The branch, 4.4/assets-customfieldgrouping-doc has been created
        at  2e2c211a83aaee5da46492330a41a1658bb27aaf (commit)

- Log -----------------------------------------------------------------
commit 2e2c211a83aaee5da46492330a41a1658bb27aaf
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Wed Jun 29 10:15:55 2016 -0400

    Add assets example to CustomFieldGroupings config doc
    
    Also update asset tutorial to use the arrayref config format
    rather than hashref. Both work, but this keeps the
    examples consistent.
    
    Fixes: I#32141

diff --git a/docs/customizing/assets/tutorial.pod b/docs/customizing/assets/tutorial.pod
index 8418ab1..53ec87f 100644
--- a/docs/customizing/assets/tutorial.pod
+++ b/docs/customizing/assets/tutorial.pod
@@ -169,10 +169,10 @@ similar custom fields and give them a custom name. If we add the following to
 F<RT_SiteConfig.pm>:
 
     Set(%CustomFieldGroupings,
-        'RT::Asset' => {
+        'RT::Asset' => [
             'Asset Details' => ['Serial Number', 'Manufacturer', 'Type', 'Tracking Number'],
             'Dates'         => ['Support Expiration', 'Issue Date'],
-        },
+        ],
     );
 
 and restart RT, the dates will be tacked on the end of the Dates portlet and we
diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 170a686..885fa7c 100644
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -927,12 +927,13 @@ Set(@CustomFieldValuesCanonicalizers, qw(
 
 =item C<%CustomFieldGroupings>
 
-This option affects the display of ticket and user custom fields in the
-web interface. It does not address the sorting of custom fields within
-the groupings; which is controlled by the Ticket Custom Fields tab in
-Queue Configuration in the Admin UI.
+This option affects the display of ticket, user, and asset custom fields
+in the web interface. It does not address the sorting of custom fields within
+the groupings; that ordering is controlled by the Ticket Custom Fields tab in
+Queue configuration in the Admin UI. Asset custom field ordering is
+found in the Asset Custom Fields tab in Catalog configuration.
 
-A nested datastructure defines how to group together custom fields
+A nested data structure defines how to group together custom fields
 under a mix of built-in and arbitrary headings ("groupings").
 
 Set C<%CustomFieldGroupings> to a nested structure similar to the following:
@@ -946,6 +947,10 @@ Set C<%CustomFieldGroupings> to a nested structure similar to the following:
         'RT::User' => [
             'Phones' => ['Fax number'],
         ],
+        'RT::Asset' => [
+            'Asset Details' => ['Serial Number', 'Manufacturer', 'Type', 'Tracking Number'],
+            'Dates'         => ['Support Expiration', 'Issue Date'],
+        ],
     );
 
 The first level keys are record types for which CFs may be used, and the

-----------------------------------------------------------------------