Yep.  It is.  I think we have tried just about every possible combination of
syntax.  The odd thing is that it either pops up with the group error or
populates with the settings from the Dynamic Access field on the user form.
It looks like it is somehow using that field as a translation from the user
form.

 

From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Axton
Sent: Thursday, September 29, 2011 4:26 PM
To: arslist@ARSLIST.ORG
Subject: Re: Using login id in field 112

 

** Did you check that your servers is configured to allow multiple assignee
groups?

 

Axton Grams

On Thu, Sep 29, 2011 at 3:04 PM, Brian Pancia <panc...@finityit.com> wrote:

** Tried droping the quotes and semicolons at the beginning and end.  Also,
tried using field 6090 and 112.  Neither work.  This might be a bug in
7.6.04.  The documentation says it's support, but it looks like I might have
to go the individual group route.

 

On Thu, Sep 29, 2011 at 9:44 AM, Frank Caruso <caruso.fr...@gmail.com>
wrote:

** 

I tested the following in version 7.1p7:

 

Set Field ID 112 to: 'user login';'user login';'user login'

 

Set request ID to Assigned Group permission only. Only users whose userid
appears in field id 112 can see the record.

On Thu, Sep 29, 2011 at 9:35 AM, Misi Mladoniczky <m...@rrr.se> wrote:

Hi Axton,

I tried this with the 112 field when the 60xxx fields was first
introduced, but was unable to get it to work for 112... Maybe I made a
mistake, or this was added/fixed later...

       Best Regards - Misi, RRR AB, http://rrr.se <http://rrr.se/> 


>>From the docs it appears both field types support login names, group
>> names,
> and role names:
>
> *To permit multiple user, group, and role names in the Assignee Group
> field
> and dynamic fields, select Enable Multiple Assign Groups on the
> Configuration tab of AR System Administration: Server Information form. To
> enter users Dan O'Connor and Mary Manager, group ID 12000, role ID -9000,
> and role Managers, use the following syntax:*
> *
> *
> *'Dan O''Connor';'Mary Manager';12000;-9000;Managers*
>
>
> Axton Grams
>
> On Thu, Sep 29, 2011 at 8:26 AM, Misi Mladoniczky <m...@rrr.se> wrote:
>
>> Hi,
>>
>> I do not think that the 112-field can hold user names. You have to use
>> the
>> 60xxx-fields for that. If you use those fields, your syntax should be
>> correct.
>>
>> Just to be clear, the value of the data should be:
>> ;'joeuser';'janeuser';
>>
>>        Best Regards - Misi, RRR AB, http://www.rrr.se
<http://www.rrr.se/>  (ARSList MVP 2011)
>>
>> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11):
>> * 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 <http://rrr.se/> .
>>
>> > We are currently trying to setup ITSM 7.6.04 to restrict access based
>> on
>> a
>> > selected group of people.  This group will be different for each
>> ticket.
>> > Basically, the user will go into an Incident and select people to add
>> to
>> a
>> > restricted access list.  We are trying to push this list of users to
>> field
>> > 112.  The BMC workflow documentation spells out the syntax
>> > (";'joeuser';'janeuser';").  However, this throws out Error 417
>> stating
>> > there is no group defined.  Now a way around this is to add each user
>> as
>> > their own group.  However, adding groups for each user and maintaining
>> > that
>> > as people are added/removed would probably not be the best idea.  Has
>> > anyone
>> > had any success implementing this in 7.6.04?
>> >
>> >
>> >
>> > Brian
>> >
>> >
>> >
>> >
>> >
>>
____________________________________________________________________________
___
>> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
<http://www.arslist.org/> 
>> > attend wwrug11 www.wwrug.com <http://www.wwrug.com/>  ARSList: "Where
the Answers Are"
>> >
>>
>>
>>
____________________________________________________________________________
___
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
<http://www.arslist.org/> 
>> attend wwrug11 www.wwrug.com <http://www.wwrug.com/>  ARSList: "Where the
Answers Are"
>>
>
>
____________________________________________________________________________
___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
<http://www.arslist.org/> 
> attend wwrug11 www.wwrug.com <http://www.wwrug.com/>  ARSList: "Where the
Answers Are"
>

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
<http://www.arslist.org/> 
attend wwrug11 www.wwrug.com <http://www.wwrug.com/>  ARSList: "Where the
Answers Are"

 

_attend WWRUG11 www.wwrug.com <http://www.wwrug.com/>  ARSlist: "Where the
Answers Are"_ 


_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 

 

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to