<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 29-3-2016 2:09, Jeffrey Pilant
wrote:<br>
</div>
<blockquote
cite="mid:3135BE7DD2D7484C840CDD011A999B7456D693BB@MOXCXR.na.bayer.cnb"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Arial","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoPlainText">Joop wrote:<o:p></o:p></p>
<pre>> Jeffrey Pilant wrote:<o:p></o:p></pre>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
><i> Could this be a customization of the old system? If
so, what files would exist
<o:p></o:p></i></span></p>
<p class="MsoNormal"><i><span
style="font-size:10.0pt;font-family:"Courier
New"">> > to hold the customization? [I know
there is an overload mechanism, and maybe some
<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span
style="font-size:10.0pt;font-family:"Courier
New"">> > config stuff, but I don't recall the
details.] If I could locate the old file set
<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span
style="font-size:10.0pt;font-family:"Courier
New"">> > and look at those files, maybe it
will give me an idea to try.<o:p></o:p></span></i></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">><i><o:p> </o:p></i></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
Possible but it could be hidden or it could be obvious.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
If its done well than the customisation should be done in
the<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
/opt/rt4/local/ tree and it would survive updates. Now its
probably not<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
a plugin so you could skip looking at the plugins folder but
you never<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
know. Do you run plugins?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
Anything in the 'lib' or 'html' folder may overrule the same
file from<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
/opt/rt4/{lib|html} and anything in the callback folder can
add/overrule<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
parts or anything using the callback mechanism built into RT<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
So is anything in it in the old system?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
If it isn't done nicely then things get tricky. Source files
can be<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
altered directly and finding them could involve getting a
diff between<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
whats installed now and how a pristine installed tree looks
like.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
Looking at modified dates might also be a way to find diffs.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
Lets see how far we get this time :-)<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">>
Joop<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">I
think I have some customized old system files. I don’t have
any .../local file<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">Overrides
in the 3.8.4 system. But based on your info, I found the
file<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">
Ticket/Elements/ShowSummary<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">Which
looked to be customized (or at least it shows the text
“Custom Fields”.</span></p>
</div>
</blockquote>
I also run an old RT install (3.8) and that is how the ShowSummary
should look.<br>
<br>
<blockquote
cite="mid:3135BE7DD2D7484C840CDD011A999B7456D693BB@MOXCXR.na.bayer.cnb"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New""><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Courier New"">Comparing
the two, it is clear that the 4.2.10 version does not have
these Fields as part of the file. Below is a DOS diff,
showing the differences of between the files. Can you tell
me what file(s) I need to create to make a local override in
the new system, and what you suggest for the contents? The
new system is a clean install, so the files should be
default values. Also, what other files do I need to look at
for these custom fields? I.e., ticked edit, self-service,
others....<o:p></o:p></span></p>
<br>
</div>
</blockquote>
In 4.2 BP introduced the concept of CustomFieldGrouping where you
can add CFs to other metadata blocks like Dates or People thats why
ShowSummary is different.<br>
Could it be that the configuration variable todo wiht CF-Grouping
has been modified (incorrectly)??<br>
<br>
Joop<br>
<br>
<br>
</body>
</html>