Another option would be to put the page in an iframe or a view field
(visualization field in ARS 7+) to mask the URL.  This may not keep
the more advanced users from figuring out the URL in the iframe/VF and
putting the address right in the browser address field.  If it needs
to be more secure then an AL is the way to go.

To build apon the AL method... If you need to allow a user to the form
but after checking some logic (beyond just pemissions), you could have
ALs that run to do your checking on a form before the form being
protected is opened (an init form maybe), set a hidden field on the
first form and pass that value to a hidden field on the form you are
protecting in the open windows action.  On windows open If that hidden
field is NULL on your protected form you can run your AL to close the
window because they didn't access the form using the proper process or
failed the logic check.

Jason


On 12/18/07, vikas kapoor <[EMAIL PROTECTED]> wrote:
> Hi Misi,
>
> Thanx for the reply. But this change would restrict all the users for
> accessing the forms.
> How could i restrict it for some specific user?
>
> Thanks in Advance !!
> -Vikas Kapoor
>
>
> ----- Original Message ----
> From: Misi Mladoniczky <[EMAIL PROTECTED]>
> To: arslist@ARSLIST.ORG
> Sent: Tuesday, December 18, 2007 12:58:04 PM
> Subject: Re: Restricting User for accessing certain forms on Midtier
>
> Hi,
>
> You could create an ACTL that gives an Error-message when opening forms
> that are not allowed.
>
> Form Name: All forms that are prohibited
> Execute On: Window Open
> Run If: ($CLIENT-TYPE$ = 9) # mid-tier
> Action: Message Error
> Permissions: Public
>
>         Best Regards - Misi, RRR AB, http://www.rrr.se
>
> Products from RRR Scandinavia:
> * RRR|License - Not enough Remedy licenses? Save money by optimizing.
> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
> * RRR|Translator - Manage and automate your language translations.
> Find these products, and many free tools and utilities, at http://rrr.se.
>
> > Hi,
> >
> > We have an external Web Interface where we have a web view of several
> > Forms on the Midtier(Tomcat 5.0).
> > user can open certain forms on this.
> >
> > For e.g he can open form on  midtier as
> >
> http://localhost:8080/arsys/forms/tmsupki/Customer+Start/Default+Administrator+View
> >
> > But if he replaces Customer+Start with Customer or any other form name as
> > ,
> >
> http://localhost:8080/arsys/forms/tmsupki/Customer/Default+Administrator+View
> >
> > He is able to access this page too and see all the customer and this we
> > doesn't want.
> >  How we can restrict the user for accessing Customer form ?
> >  Please give any suggestion/Solution. An early reply would be appreciated
> > !!
> >
> > Thanks & Regards,
> > -Vikas Kapoor
> >
> >
> >
> ____________________________________________________________________________________
> > Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile.  Try it now.
> > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> >
> >
> _______________________________________________________________________________
> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> >
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
>
>
> ____________________________________________________________________________________
> Never miss a thing.  Make Yahoo your home page.
> http://www.yahoo.com/r/hs
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to