Brien, As far as I know, the $Application$ keyword refers to the actual Application wrapper, not the Entry or Access points within the Application. Opening the Entry Points for an Application from the Home Page, does not mean that you have opened the Application itself, you are accessing everything in the application from the entry point down and around. >From the Object List, if you open the actual Application (where the 'Type' = Application), you would of course have to log into another User tool session; however, I believe this is the 'wrapper' that this Keyword is referring to, and that is why the documentation says that if you access the form from outside the application, the keyword is NULL. It doesn't mean you are doing anything wrong with your Application usage or how you have it set up, it's just what the intended use is for the keyword. I hope that makes sense... Janie
_____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Brien Dieterle Sent: Wednesday, October 22, 2008 9:27 AM To: [email protected] Subject: Re: $application$ null ** :-) Believe me the more you read on this, the more confusing it gets. We do use applications (associating forms to those applications, etc). There is even a default application called "AR System Administration". Since this application is a "deployable" application, it gets it's own header on the Application List on the Home Page (local applications do not). However, the clickable links below this are still Entry Points defined on the forms within that application-- thus even these are not "application mode" links. I'm not even sure if we want "application mode" anyway, since by default it seems to want to cordon you off from anything not in the application-- and with the user tool it always seems to want to make you log in again in an entirely new instance of the User Tool. So, I suppose I will do without $Application$. We prefix our forms with an acroynm of the application, ie: "Helpdesk" becomes "HD: new employee form", etc, so I more-or-less capture application information anyway. Thanks! Brien On Wed, Oct 22, 2008 at 9:18 AM, jham36 <[EMAIL PROTECTED]> wrote: I was just doing some more reading and it is a little confusing on how it works. You may need to add entry points to the forms within the application. James Hamilton Business Systems Manager The NPD Group, Inc. 900 West Shore Road Port Washington, NY 11050 USA + 1.516.625.2468 On Oct 22, 12:16 pm, jham36 <[EMAIL PROTECTED]> wrote: > I think what you may need to do is to create an Application. Define > the forms in the application. Choose one of the forms as your primary > form within the application properties. Do not set an entry point on > any form. Applications should automatically appear on the Home Page > in alphabetical order as long as a user has permission to it. > I have not tested this, but according to the admin tool help file, it > should work. > > James Hamilton > Business Systems Manager > The NPD Group, Inc. > 900 West Shore Road > Port Washington, NY 11050 USA > + 1.516.625.2468 > > On Oct 21, 7:09 pm, Brien Dieterle > > > > > > <[EMAIL PROTECTED]> wrote: > > I'm adding a little "report problem" button to a lot of our custom forms to > > basically submits a bug report for the form. I am capturing the Form, View, > > etc. I wanted to captured Application but it is null unless you open the > > actual application, which we apparently have not been doing :-) > > > From the manual: > > $APPLICATION$: The name (not label) of the currently running application. On > > the web client, this keyword is set to NULL when the form is opened from a > > URL that does not include the application's name. In BMC Remedy User, this > > keyword is set to NULL when the form is opened outside of an application. > > > Ok, so, have we been using (local) Applications all wrong? We set the Entry > > Point on the Primary Form for each application so that it shows up on the > > Home Page "application" list. Clicking these actually bypasses the > > "application mode" completely and is like opening and independent form. > > Everything in the manual seems to suggest than an "Application List" (such > > as on the homepage) is composed of links to Applications and yet... they > > are not. > > > From the manual: > > Presenting applications to users: > > The typical or default method to present an application to users is to > > define entry points that appear in a home page, as explained in Chapter 9, > > "Defining entry points and home pages." > > > Are there any suggestions for enforcing $application$ usage rather than > > direct forms? I couldn't see any way to get a true "application" link to > > appear on the Home page. > > for instance here is an "actual application" URL: > > >http://server/arsys/*apps*/server/AR+System+Administration > > > but the link on the Home Page is to the *form*: > > >http://server/arsys/*forms*/server/AR+System+Administration%3A+Consol... > > > As always, if there is a better way to skin this cat (bug reporting) I am > > all ears! > > > Thanks! > > > Brien > > > ___________________________________________________________________________- -____ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > Platinum Sponsor:www.rmsportal.comARSlist:"Where the Answers Are" > > ___________________________________________________________________________- ____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > Platinum Sponsor:www.rmsportal.comARSlist: "Where the Answers Are"- Hide quoted text - > > - Show quoted text - ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
