** this is at the moment my guess too.
I'll try it.
But maybe I am doing something wrong.
Just to be sure and maybe to get some feedback from somebody on this forum, here is what I have:
a form with a character field that I called Assignee Group, Id of this field 112, lenght 255, permissions for my Group A
My workflow is quiet basic: one AL is fired on search and checks with the User table that my actually connected $USER$ is found with the corresponding login
So if match is found, the Assignee Group field, is set for the login
What puzzles me is that the field gets actually set to the login. But then I get the error message. I now believe I am missing something here.
Any help would be appreciated.
Serouche


Jason Miller wrote:
** Also sometimes when populating 112 or dynamic fields with workflow you have to use the group number instead of the name.  I can't think of the specific instances at the moment (maybe I was doing a filter loop/push) but I remember encountering that error when using workflow to set row level permissions.  If I remember correctly this was on 6 or 6.1 the first time I encountered it so it may be what you are seeing?

Jason

On Tue, Apr 7, 2009 at 7:29 AM, Grooms, Frederick W <[email protected]> wrote:
Actually according to the 6.3 Basic manual (starting on page 104) you
can place a user NAME (not login) or group ID in Field 112.  Since
RemedyManiac is still on 6.0 it may have only accepted group IDs then.

Fred

-----Original Message-----
From: Action Request System discussion list(ARSList)
__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___

__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___

Reply via email to