No, I don't know the answer to which you seek...but I can hypothesize?....:)
Ok...so field help can be 'bulky' at times....and the client (web browser) doesn't keep a copy of the form in question in the same way that the user tool did...so to try to keep the communication size between client/mid-tier/server as small as possible, as well as keep the Mid-Tier cache smaller, it was decided to not include the 'help' for each and every field on each and every form in cache, and transferred across the wire just a guess though...I certainly don't work for, nor represent BMC on this, nor ANY matter....but my explanation makes sense to ME :) On Mon, Aug 26, 2013 at 2:04 PM, Joe D'Souza <[email protected]> wrote: > ** > > Does anyone know the reason why the Mid-Tier is unable to support the > $FIELDHELP$ keyword? The help on this keyword states that “Web applications > do not support the $FIELDHELP$ keyword; it returns NULL.”**** > > ** ** > > Any reason why this would have been hard to implement on the Mid-Tier?**** > > ** ** > > I was hoping to use it on a very small form wherein I could set > $FIELDHELP$ to a temp display only field on every gain focus action of a > field, displaying the help of that field in that display only field. Works > like a charm on the User tool, however it does not on the Mid-Tier because > of this said limitation of the said keyword.**** > > ** ** > > With the impending slow death of the thick client, it would have been nice > to have features such as this available at the Mid-Tier level as well.**** > > ** ** > > If you ask me this feature would have been more useful on the web for > intuitive field help for a end user, than it is on a native thick client.. > **** > > ** ** > > Joe**** > _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"
