<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
code
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>Thanks Armin,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>That did the trick!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>I did get a reply off the list too (thanks Tony) advising of </span><code><span lang=EN-US style='font-size:10.0pt'>$AssetBasicCustomFieldsOnCreate</span></code><span style='color:#1F497D;mso-fareast-language:EN-US'>; I appreciate the link to the Assets_Config page - can’t believe I missed it before.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>Brett<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Armin Liedtke [mailto:armhamer@uw.edu] <br><b>Sent:</b> Thursday, 26 November 2015 7:07 AM<br><b>To:</b> Brett Chambers <bchambers@ambertech.com.au>; rt-users@lists.bestpractical.com<br><b>Subject:</b> RE: [rt-users] RT Assets grouping behaviour<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Brett,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I didn’t see any replies to this so I thought I would send this along.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Check out </span><code><span lang=EN-US style='font-size:10.0pt'>$AssetBasicCustomFieldsOnCreate</span></code><span lang=EN-US style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><a href="https://www.bestpractical.com/docs/assets/1.05/Assets_Config.html">https://www.bestpractical.com/docs/assets/1.05/Assets_Config.html</a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Set($AssetBasicCustomFieldsOnCreate, [</span><span style='font-size:8.0pt;font-family:"Courier New";color:red'>'Manufacturer', 'Master ID', 'Part number', 'Serial number', 'Install date'</span><span lang=EN-US style='color:#1F497D'>] );<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Hope that helps!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Armin<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> rt-users [<a href="mailto:rt-users-bounces@lists.bestpractical.com">mailto:rt-users-bounces@lists.bestpractical.com</a>] <b>On Behalf Of </b>Brett Chambers<br><b>Sent:</b> Sunday, November 15, 2015 5:23 PM<br><b>To:</b> <a href="mailto:rt-users@lists.bestpractical.com">rt-users@lists.bestpractical.com</a><br><b>Subject:</b> [rt-users] RT Assets grouping behaviour<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve been experimenting with RT Assets – specifically <a href="https://www.bestpractical.com/docs/assets/1.0/RT/Extension/Assets.html#Groupings">Asset custom field grouping</a>. I’ve encountered the following behaviour, which seems like a bug to me.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In RT_SiteConfig.pm, I’m trying to add Asset custom fields to the built in grouping ‘Basics’. Extract below…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New"'>Set(%CustomFieldGroupings,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New"'> <span style='color:#0070C0'>'RT::Ticket' => [<o:p></o:p></span></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New";color:#0070C0'> 'Product Details' => ['Manufacturer', 'Product', 'Master ID', 'Part number', 'Part description', 'Serial Number', '', 'Date of Purchase', 'Purchased from'],<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New";color:#0070C0'> 'Basics' => ['SLA', 'Fault Type'],<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New";color:#0070C0'> 'People' => ['Phone number', 'Postcode'],<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New";color:#0070C0'> 'RA Details' => ['Detail of Fault', 'Warranty Status', 'Pronto Job #', 'Vendor RA Approval #', 'Vendor RA Order #', 'Vendor shipping method', 'Incoming Vendor tracking', 'Faulty part received', 'Replacement part received', 'Replacement part sent', 'Outgoing Vendor tracking'],<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New";color:#0070C0'> 'Support Actions' => ['Return auto-reply'],<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New";color:#0070C0'> ],<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New"'> <span style='color:red'>'RT::Asset' => {<o:p></o:p></span></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New";color:red'> 'Basics' => ['Manufacturer', 'Master ID', 'Part number', 'Serial number', 'Install date'],<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New"'> <span style='color:red'> },</span><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;font-family:"Courier New"'>);<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When I go the ‘Create Asset’ page to create a new asset in the defined Asset Catalog, my custom fields do not appear under ‘Basics’.<o:p></o:p></p><p class=MsoNormal>However, if I search ‘Assets’, the Custom Fields appear under the built in ‘Basics’ group.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The behaviour is different to that of creating a new Ticket – custom fields appear under the ‘Basics’ built in group for tickets, as you would expect.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Furthermore, if I use a custom grouping name instead of the built in ‘Basics’ (e.g. ‘My Asset’), the defined group and the assigned CFs appear in the ‘Create Asset’ page.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Has anyone experienced this behaviour before, or should I log a bug for it?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Version info<o:p></o:p></p><p class=MsoNormal>RT v4.2.12<o:p></o:p></p><p class=MsoNormal>RT Assets v1.0.5<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards,<o:p></o:p></p><p class=MsoNormal>Brett<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>