Thanks to Ben & Carey for their help - works a treat .
 
Got slightly muddled up with public permissions to the request-id -
removed that and it works exactly how
I want it to (and will use a hidden field for the request-id if I need
it).
 
Thanks,
 
            Colin
 


________________________________

        From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Ben Cantatore
        Sent: 30 January 2007 16:05
        To: [email protected]
        Subject: Re: User permissions
        
        
        ** 
        I can think of two ways to do this.   
        - One, you make the field public and enforce permissions through
workflow.   
        - Two, you keep the current permissions on the field you have
and create another hidden field with public permissions where you mirror
the value of the original field.  Modify your notification to use the
duplicate field. 
        
        
        
        
Colin Love <[EMAIL PROTECTED]> 
Sent by: "Action Request System discussion list(ARSList)"
<[email protected]> 

01/30/2007 09:38 AM 
Please respond to
[email protected]


To
[email protected] 
cc
Subject
User permissions

        




        Hello,
          We have recently upgraded to v7 of ARS (from v4.0!!) which was
done
        via a new install.  Obviously lots of things have changed
between the
        two versions, but there is one thing I dont seem to be able to
nail.
        
        We are intending to use mid-tier to allow users to submit and
review
        their
        own tickets, and have set up some LDAP authentication against AD
for
        this
        and it works well utlising the submitter field. We can further
use 
        field permissions to restrict access so the user can only see
their
        entries and nobody elses.  This is what we want.
        
        However, we also have notifications going out from the form in
question
        that go to what would be deemed public email addresses (ie dont
appear
        in ARS) and for the field values to work we need to open up
permissions
        for Public on the fields, which then breaks the user access as
they can
        then see all of the calls.
        
        Is there a way of locking down permissions to allow both
functions to
        happen correctly, or perhaps a way for the notification to be
run as
        a defined user that we can assign a group permission for
(instead of 
        Public) ?
        
        Thanks in advance.....
        
                                                          Colin
        
        
        
------------------------------------------------------------------------
        --------
        Colin Love - Technical Infrastructure Manager         E-Mail:
        [EMAIL PROTECTED]
        Senate House Services Ltd
        University of London Computer Centre               Telephone:
020 7692
        1304
        20 Guilford St., London, WC1N 1DZ.                       FAX:
020 7692
        1234
        
------------------------------------------------------------------------
        --------
        
        
________________________________________________________________________
_______
        UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:"Where the Answers Are"
        
        __20060125_______________________This posting was submitted with
HTML in it___


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

Reply via email to