You bring up a good point. Flushing the cache from the mid-tier server will force a re-pull of the object definitions from the Remedy server.
Just hitting save on the Remedy server doesn't necessarily mean that all of the definitions are updated across the server group. Each server in the server group will pick up the changes when it notices, which is not necessarily immediately. It very well could be an issue where you are seeing slightly different versions between the session. However, there are small differences between the browser interfaces. I have never set about itemizing them because the differences are usually innocuous. Sometimes they are a bit bigger. For instance, with one release of mid-tier you can only multi-select table fields in certain browsers. This could be a situation where with this particular version of midtier behaves slightly differently between browsers. I just re-verified. I have no problem seeing or copying read only fields. The behavior described sounds like a disabled field rather than a read-only field. Is this behavior being exhibited across other read only fields or just this one? I would do things like: * re-creating the field from scratch (no copy/pasting) * moving the field around * deleting the functionality, clear the cache, go get coffee. Recreate it, go get coffee, flush midtier, flush browser cache, reboot my pc, try again. * check client side logs to verify that there's no unexpected changes to the field by workflow. * spend some time querying the KB and reading release notes. (maybe this should be earlier in my process :) ) * having a look at things in something like firebug. On Tue, Feb 26, 2013 at 4:40 PM, Rick Westbrock <[email protected]> wrote: > Have you tried accessing the form with multiple user accounts? I have > recently seen that sometimes when making a change to form fields that some > users will see the change and others won't if only a simple MT cache flush > has been done. We now stop Tomcat, delete the cache files and restart > Tomcat > to effectively rebuild the cache from scratch instead of just refreshing > it. > This seems to have resolved the seemingly arbitrary issues we were seeing > for one subset of users one time, then a different subset of users another > time. > > -Rick > > > ___________________________ > Rick Westbrock > QMX Support Services > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Longwing, LJ CTR MDA/IC > Sent: Tuesday, February 26, 2013 3:36 PM > To: [email protected] > Subject: Re: New custom field oddity > > Ron, > What version of Remedy and what version of Mid-Tier are you running? > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Peters, Ron > Sent: Tuesday, February 26, 2013 4:28 PM > To: [email protected] > Subject: Re: New custom field oddity > > ** > > After some more testing, I can rule out the AL. I simply created a new > character field on both forms, gave them a default value, gave them > 'display' for their entry modes, and changed their name/display from > 'character field' to 'test field'. I added them both to their respective > 'work detail' tabs in an open space for visibility. > > > > Flushed cache. > > > > In Chrome/FF, when creating a new record, the field on HPD:Help Desk has > it's default value that can be highlighted/copied/pasted etc. The field on > CHG:Infrastructure Change can do no such thing though it is accessible > within IE. > > > > I'm still pretty green at this but that just seems stupid. Am I missing a > setting? > > > > Thoughts? > > > > Thanks. > > > > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Pargeter, Christie :CO IS > Sent: Monday, February 25, 2013 3:16 PM > To: [email protected] > Subject: Re: New custom field oddity > > > > ** > > Did you flush your MidTier cache after you added the field? > > > > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Peters, Ron > Sent: Monday, February 25, 2013 10:57 AM > To: [email protected] > Subject: New custom field oddity > > > > ** > > Hi all, > > > > I created a new field on both the HPD:Help Desk and CHG:Infrastructure > Change forms. They are both similar in that they are read-only display > fields. Each one has an active link that gives the field its value. The AL > is working fine as the value is correct on both. The issue I'm having is > browser based. Both fields work correctly in IE. However, Only the INC > field > works in FF and Chrome. The field is there and visible, but I'm unable to > interact with it. I can't select/highlight/copy the field contents in those > browsers. > > > > Any thoughts why one field works but not the other? Is there some setting > that I'm missing? > > > > Thanks in advance, > > Ron > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > ____________________________________________________________________________ > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the > Answers > Are, and have been for 20 years" > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
