Hi Jason,

Can you please tell how do i give the permission to the Attachment field.?


On Tue, Jul 22, 2014 at 5:05 PM, Jason Miller <jason.mil...@gmail.com>
wrote:

> **
> What about the attachment field?  I don't see the permissions for it in
> the screenshot.  The error is specifically indicating the attachment field
>  ('Attach') does not have any permissions, NOT the attachment pool.  This
> is also supported by being able to see the attachment pool while logged in
> as a non-admin but not the attachment field in the pool.
>
> An attachment pool is a collection of one or more attachment fields.  For
> the most basic attachment functionality you use 1 attachment pool and 1
> attachment field in that pool.  Each attachment field can have permissions
> separate form the attachment pool.  An attachment pool cannot have write
> permissions because it is just a container to displaying attachment fields.
>  An attachment field can have write permissions because it has data
> directly associated with it.
>
> Jason
>
>
> On Mon, Jul 21, 2014 at 11:34 PM, Karthick S <karthick...@gmail.com>
> wrote:
>
>> **
>> Hi Doug,
>>
>> Please find the attached screenshots.
>>
>> When i add label name 'Attach' in 'Attach Fields' and while saving the
>> form i am receiving the message.
>> Yes, like you said i have given the write permission to Attachment Pool.
>>
>>
>> On Tue, Jul 22, 2014 at 3:03 PM, Mueller, Doug <doug_muel...@bmc.com>
>> wrote:
>>
>>> **
>>>
>>> Which field was this commenting on?
>>>
>>>
>>>
>>> Did you set permission on the Attachment Pool.  Probably setting Public
>>> access because you want everyone
>>>
>>> to be able to read attachments and just control who can write.
>>>
>>>
>>>
>>> If it is complaining only about the attachment field itself, then if you
>>> want everyone to be able to read it,
>>>
>>> add Public  -- Read access to that field.  That should let everyone read
>>> the attachments.  I don't know why
>>>
>>> you are getting the message about only the Admin having access if you
>>> did assign another group Write
>>>
>>> access to the field.  Verify that you have a group of type Change (you
>>> should not be able to assign change
>>>
>>> permission if the group is not type Change so it should be this way).
>>>
>>>
>>>
>>> Make changes to ONE field at a time and save to make sure you know what
>>> any message is referring to in
>>>
>>> case there is any confusion.
>>>
>>>
>>>
>>> Doug
>>>
>>>
>>>
>>> *From:* Action Request System discussion list(ARSList) [mailto:
>>> arslist@ARSLIST.ORG] *On Behalf Of *Karthick S
>>> *Sent:* Monday, July 21, 2014 8:09 PM
>>>
>>> *To:* arslist@ARSLIST.ORG
>>> *Subject:* Re: Restrict a specific users or group for Adding/Deleting
>>> in Attachment Pool field
>>>
>>>
>>>
>>> **
>>>
>>> Hi Doug,
>>>
>>>
>>>
>>> Like you said, i created a Attachment field in a Regular form and i have
>>> added a group which has write access, then while saving the form i got the
>>> below message.
>>>
>>>
>>>
>>> "Only the Administrator has access to this field (ARWARN 50)"
>>>
>>>
>>>
>>> Now in this Only i am able to attach or see the attachment file when i
>>> log-in as Admin. else nothing work.
>>>
>>>
>>>
>>> Help me out.
>>>
>>>
>>>
>>> On Thu, Jul 17, 2014 at 9:15 AM, Karthick S <karthick...@gmail.com>
>>> wrote:
>>>
>>> --- Thanks Gregory, Doug, Misi.. Let me try and let you know output.
>>>
>>>
>>>
>>> Thanks once again for your Answers and Suggestion.
>>>
>>>
>>>
>>> On Thu, Jul 17, 2014 at 3:06 AM, Mueller, Doug <doug_muel...@bmc.com>
>>> wrote:
>>>
>>> Permissions are almost always the answer whenever the question is
>>>
>>> "restrict/allow users to do xxxx"
>>>
>>> So first, set up permissions on the attachment fields themselves to have
>>> permission
>>> for a group that everyone is in to have read access -- but not write
>>> access.  Have
>>> another group that has write access to the attachment fields.   Note
>>> that everyone
>>> should have access to the attachment pool if they have read access at
>>> least to the
>>> attachment fields.
>>>
>>> Now, give all users the read group (you probably use a group they are
>>> already in
>>> for this) and give the users you want to have write access to the
>>> attachment fields
>>> the second group.
>>>
>>> This strategy protects change from the screen AND from API programs AND
>>> from any
>>> other access method the user may try.
>>>
>>> If you just play with buttons or hiding/showing on the screen, you can
>>> prevent them
>>> from doing the operation on the screen, but it does not protect access
>>> by the API
>>> or by email or by any other means.
>>>
>>> I hope this helps,
>>>
>>> Doug Mueller
>>>
>>>
>>> -----Original Message-----
>>> From: Action Request System discussion list(ARSList) [mailto:
>>> arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky
>>> Sent: Tuesday, July 15, 2014 11:57 PM
>>> To: arslist@ARSLIST.ORG
>>>
>>> Subject: Re: Restrict a specific users or group for Adding/Deleting in
>>> Attachment Pool field
>>>
>>> Hi,
>>>
>>> Permission groups are used to ADD, not to RESTRICT.
>>>
>>> You need to make sure that the users in question does NOT belong to a
>>> group that has write access to the field (attachment slots/pool).
>>>
>>>         Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP
>>> 2011)
>>>
>>> Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13):
>>> * RRR|License - Not enough Remedy licenses? Save money by optimizing.
>>> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
>>> Find these products, and many free tools and utilities, at http://rrr.se
>>> .
>>>
>>> > Hi All.
>>> >
>>> >
>>> > Is there any way to restrict a specific users or group for
>>> > Adding/Deleting files in Attachment Pool field?
>>> >
>>> >
>>> > I have tried one solution like Removing 'Delete' from 'Display Labels
>>> > in View' in Field Properties, but it restricts all the users.
>>> >
>>> >
>>> > Please provide your suggestion on this.
>>> >
>>> >
>>> > *Regards,*
>>> >
>>> > *Karthick Sundararajan*
>>> >
>>> > ______________________________________________________________________
>>>
>>> > _________ 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"
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>>
>>>
>>> *Thanks and Regards,*
>>>
>>> *Karthick S*
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>>
>>>
>>> *Thanks and Regards,*
>>>
>>> *Karthick S*
>>>
>>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>>>  _ARSlist: "Where the Answers Are" and have been for 20 years_
>>
>>
>>
>>
>> --
>>
>>
>> *Thanks and Regards,*
>> *Karthick S*
>>  _ARSlist: "Where the Answers Are" and have been for 20 years_
>>
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_
>



-- 


*Thanks and Regards,*
*Karthick S*

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to