Re: how to define access to Assignee Group
** 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 frederick.w.gro...@xo.com 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___
Re: how to define access to Assignee Group
Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305)" Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___
Re: how to define access to Assignee Group
Ok, submitter is handled in the usual way. Give the built in group submitter, access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
** my problem is exactly here: all people are in the same group let say "Callers" They all can submit tickets. So with the submitter I have no problem. But then in addition to this: they should be allowed to access tickets only when they are in the CC field. So question: how am I going to check the $USER$ against that CC list using the Dynamic Group ? Sorry I don't get it. I can populate the Dynamic Group with the groupids. But then everybody from that group will have access to the ticket. Which I don't want. How can I build a workflow to give access on the user basis? keeping in mind I need to extract at some point my user from the CC list field The documentation is poor and wrong. Serouche Rod Harris wrote: ** Ok, submitter is handled in the usual way. Give the built in group "submitter", access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305)" Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___
Re: how to define access to Assignee Group
Serouche, Forget using groups for now then. Just put each userid in the 112 field surrounded by single quotes. Create a filter on submit/modify that looks at the CC field and places each user login ID in the cc field (you may need to do a lookup of the user form if you have full email addresses in the CC field) into the 112 field. Surround each user id with single quotes. Give assignee group permission to the relevant fields. Use request ID (1) to restrict row level access. Once you do this the built in permissions system will do the rest. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** my problem is exactly here: all people are in the same group let say Callers They all can submit tickets. So with the submitter I have no problem. But then in addition to this: they should be allowed to access tickets only when they are in the CC field. So question: how am I going to check the $USER$ against that CC list using the Dynamic Group ? Sorry I don't get it. I can populate the Dynamic Group with the groupids. But then everybody from that group will have access to the ticket. Which I don't want. How can I build a workflow to give access on the user basis? keeping in mind I need to extract at some point my user from the CC list field The documentation is poor and wrong. Serouche Rod Harris wrote: ** Ok, submitter is handled in the usual way. Give the built in group submitter, access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ __Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
** doesn't work I gave access the Assignee_Group to the Request_ID field. I put in the Assignee_Group field the ID of my user. I tried with quotes and without quotes. Maybe I should try with double-quotes. I put my user in the CC list as well I tried to access the ticket using this user. The system doesn't find the request. There is something missing, or ? serouche Rod Harris wrote: ** Serouche, Forget using groups for now then. Just put each userid in the 112 field surrounded by single quotes. Create a filter on submit/modify thatlooks atthe CC field and places each userlogin ID in the cc field (you may need to do a lookup of the user form if you have full email addresses in the CC field) into the 112 field. Surround each user id with single quotes. Give assignee group permission to the relevant fields. Use request ID (1) to restrict row level access. Once you do this the built in permissions system will do the rest. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** my problem is exactly here: all people are in the same group let say "Callers" They all can submit tickets. So with the submitter I have no problem. But then in addition to this: they should be allowed to access tickets only when they are in the CC field. So question: how am I going to check the $USER$ against that CC list using the Dynamic Group ? Sorry I don't get it. I can populate the Dynamic Group with the groupids. But then everybody from that group will have access to the ticket. Which I don't want. How can I build a workflow to give access on the user basis? keeping in mind I need to extract at some point my user from the CC list field The documentation is poor and wrong. Serouche Rod Harris wrote: ** Ok, submitter is handled in the usual way. Give the built in group "submitter", access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305)" Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
Re: how to define access to Assignee Group
You seem to be following the right steps. It is definitely a single quote around the userid. You have stopped getting the error message when modifying the assignee group field right? Check that you're doing everything right. Try it using your own dynamic group field if you're still stuck. You have to create a group and a field with the same ID, and it must be in the correct range. I've used this feature quite a lot in many different versions of AR so it does work as documented. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** doesn't work I gave access the Assignee_Group to the Request_ID field. I put in the Assignee_Group field the ID of my user. I tried with quotes and without quotes. Maybe I should try with double-quotes. I put my user in the CC list as well I tried to access the ticket using this user. The system doesn't find the request. There is something missing, or ? serouche Rod Harris wrote: ** Serouche, Forget using groups for now then. Just put each userid in the 112 field surrounded by single quotes. Create a filter on submit/modify that looks at the CC field and places each user login ID in the cc field (you may need to do a lookup of the user form if you have full email addresses in the CC field) into the 112 field. Surround each user id with single quotes. Give assignee group permission to the relevant fields. Use request ID (1) to restrict row level access. Once you do this the built in permissions system will do the rest. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** my problem is exactly here: all people are in the same group let say Callers They all can submit tickets. So with the submitter I have no problem. But then in addition to this: they should be allowed to access tickets only when they are in the CC field. So question: how am I going to check the $USER$ against that CC list using the Dynamic Group ? Sorry I don't get it. I can populate the Dynamic Group with the groupids. But then everybody from that group will have access to the ticket. Which I don't want. How can I build a workflow to give access on the user basis? keeping in mind I need to extract at some point my user from the CC list field The documentation is poor and wrong. Serouche Rod Harris wrote: ** Ok, submitter is handled in the usual way. Give the built in group submitter, access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche
Re: how to define access to Assignee Group
** ok many thanks for your infos Rod. One thing I am noticing is that having the user id in that field seems to slow down the system Am I right? Is there anything to do to improve the perfs? serouche Rod Harris wrote: ** You seem to be following the right steps. It is definitely a single quote around the userid. You have stopped getting the error message when modifying the assignee group field right? Check that you're doing everything right. Try it using your own dynamic group field if you're still stuck. You have to create a group and a field with the same ID, and it must be in the correct range. I've used this feature quite a lot in many different versions of AR so it does work as documented. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** doesn't work I gave access the Assignee_Group to the Request_ID field. I put in the Assignee_Group field the ID of my user. I tried with quotes and without quotes. Maybe I should try with double-quotes. I put my user in the CC list as well I tried to access the ticket using this user. The system doesn't find the request. There is something missing, or ? serouche Rod Harris wrote: ** Serouche, Forget using groups for now then. Just put each userid in the 112 field surrounded by single quotes. Create a filter on submit/modify thatlooks atthe CC field and places each userlogin ID in the cc field (you may need to do a lookup of the user form if you have full email addresses in the CC field) into the 112 field. Surround each user id with single quotes. Give assignee group permission to the relevant fields. Use request ID (1) to restrict row level access. Once you do this the built in permissions system will do the rest. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** my problem is exactly here: all people are in the same group let say "Callers" They all can submit tickets. So with the submitter I have no problem. But then in addition to this: they should be allowed to access tickets only when they are in the CC field. So question: how am I going to check the $USER$ against that CC list using the Dynamic Group ? Sorry I don't get it. I can populate the Dynamic Group with the groupids. But then everybody from that group will have access to the ticket. Which I don't want. How can I build a workflow to give access on the user basis? keeping in mind I need to extract at some point my user from the CC list field The documentation is poor and wrong. Serouche Rod Harris wrote: ** Ok, submitter is handled in the usual way. Give the built in group "submitter", access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on
Re: how to define access to Assignee Group
Hi Serouche, I don't think using dynamic groups should impact performance too much. You might be seeing some recaching as you change things at the moment. Things should sort themselves out and settle down. If they don't then depending on what's causing a performance problem there are a lot of different things you can do to improve it. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** ok many thanks for your infos Rod. One thing I am noticing is that having the user id in that field seems to slow down the system Am I right? Is there anything to do to improve the perfs? serouche Rod Harris wrote: ** You seem to be following the right steps. It is definitely a single quote around the userid. You have stopped getting the error message when modifying the assignee group field right? Check that you're doing everything right. Try it using your own dynamic group field if you're still stuck. You have to create a group and a field with the same ID, and it must be in the correct range. I've used this feature quite a lot in many different versions of AR so it does work as documented. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** doesn't work I gave access the Assignee_Group to the Request_ID field. I put in the Assignee_Group field the ID of my user. I tried with quotes and without quotes. Maybe I should try with double-quotes. I put my user in the CC list as well I tried to access the ticket using this user. The system doesn't find the request. There is something missing, or ? serouche Rod Harris wrote: ** Serouche, Forget using groups for now then. Just put each userid in the 112 field surrounded by single quotes. Create a filter on submit/modify that looks at the CC field and places each user login ID in the cc field (you may need to do a lookup of the user form if you have full email addresses in the CC field) into the 112 field. Surround each user id with single quotes. Give assignee group permission to the relevant fields. Use request ID (1) to restrict row level access. Once you do this the built in permissions system will do the rest. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** my problem is exactly here: all people are in the same group let say Callers They all can submit tickets. So with the submitter I have no problem. But then in addition to this: they should be allowed to access tickets only when they are in the CC field. So question: how am I going to check the $USER$ against that CC list using the Dynamic Group ? Sorry I don't get it. I can populate the Dynamic Group with the groupids. But then everybody from that group will have access to the ticket. Which I don't want. How can I build a workflow to give access on the user basis? keeping in mind I need to extract at some point my user from the CC list field The documentation is poor and wrong. Serouche Rod Harris wrote: ** Ok, submitter is handled in the usual way. Give the built in group submitter, access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in single quotes though to distinguish it from a group name. The same rules apply for the dynamic groups fields (fields and matching group IDs in the range of 6 to 60999). Dynamic groups enable you to have more than 1 field with the same attributes as the special 112 field. I think this feature was added in about V6. One note of caution when you put userids into a dynamic group field. Watch out for userids that have a single quote in them eg. 'Peter o'connell'. You need to put a second single quote in front of the one in the name in these cases. Rod On 07/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon
Re: how to define access to Assignee Group
** many thanks again Rod. But it still doesn't work. I tried without quotes. I noticed the system translates the userid 0001024 into ;0001024; then I tried with '0001024'. The same translation happened ;'0001024'; I also tried with double-quotes I created my own Dynamic Group and added the same into that group Nothing helped: my user does not get access to the request. But probably you are right, I need to look what is elsewhere going wrong serouche Rod Harris wrote: ** Hi Serouche, I don't think using dynamic groupsshould impact performance too much. You might be seeing some recaching as you change things at the moment. Things should sort themselves out and settle down. If they don't then depending on what's causing a performance problem there are a lot of different things you can do to improve it. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** ok many thanks for your infos Rod. One thing I am noticing is that having the user id in that field seems to slow down the system Am I right? Is there anything to do to improve the perfs? serouche Rod Harris wrote: ** You seem to be following the right steps. It is definitely a single quote around the userid. You have stopped getting the error message when modifying the assignee group field right? Check that you're doing everything right. Try it using your own dynamic group field if you're still stuck. You have to create a group and a field with the same ID, and it must be in the correct range. I've used this feature quite a lot in many different versions of AR so it does work as documented. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** doesn't work I gave access the Assignee_Group to the Request_ID field. I put in the Assignee_Group field the ID of my user. I tried with quotes and without quotes. Maybe I should try with double-quotes. I put my user in the CC list as well I tried to access the ticket using this user. The system doesn't find the request. There is something missing, or ? serouche Rod Harris wrote: ** Serouche, Forget using groups for now then. Just put each userid in the 112 field surrounded by single quotes. Create a filter on submit/modify thatlooks atthe CC field and places each userlogin ID in the cc field (you may need to do a lookup of the user form if you have full email addresses in the CC field) into the 112 field. Surround each user id with single quotes. Give assignee group permission to the relevant fields. Use request ID (1) to restrict row level access. Once you do this the built in permissions system will do the rest. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** my problem is exactly here: all people are in the same group let say "Callers" They all can submit tickets. So with the submitter I have no problem. But then in addition to this: they should be allowed to access tickets only when they are in the CC field. So question: how am I going to check the $USER$ against that CC list using the Dynamic Group ? Sorry I don't get it. I can populate the Dynamic Group with the groupids. But then everybody from that group will have access to the ticket. Which I don't want. How can I build a workflow to give access on the user basis? keeping in mind I need to extract at some point my user from the CC list field The documentation is poor and wrong. Serouche Rod Harris wrote: ** Ok, submitter is handled in the usual way. Give the built in group "submitter", access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I
Re: how to define access to Assignee Group
HI Serouche, What are you using for userid? It should be the login ID of the user, not the entry ID of the user record. eg. 'rharris' Try this and see how it goes. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** many thanks again Rod. But it still doesn't work. I tried without quotes. I noticed the system translates the userid 0001024 into ;0001024; then I tried with '0001024'. The same translation happened ;'0001024'; I also tried with double-quotes I created my own Dynamic Group and added the same into that group Nothing helped: my user does not get access to the request. But probably you are right, I need to look what is elsewhere going wrong serouche Rod Harris wrote: ** Hi Serouche, I don't think using dynamic groups should impact performance too much. You might be seeing some recaching as you change things at the moment. Things should sort themselves out and settle down. If they don't then depending on what's causing a performance problem there are a lot of different things you can do to improve it. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** ok many thanks for your infos Rod. One thing I am noticing is that having the user id in that field seems to slow down the system Am I right? Is there anything to do to improve the perfs? serouche Rod Harris wrote: ** You seem to be following the right steps. It is definitely a single quote around the userid. You have stopped getting the error message when modifying the assignee group field right? Check that you're doing everything right. Try it using your own dynamic group field if you're still stuck. You have to create a group and a field with the same ID, and it must be in the correct range. I've used this feature quite a lot in many different versions of AR so it does work as documented. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** doesn't work I gave access the Assignee_Group to the Request_ID field. I put in the Assignee_Group field the ID of my user. I tried with quotes and without quotes. Maybe I should try with double-quotes. I put my user in the CC list as well I tried to access the ticket using this user. The system doesn't find the request. There is something missing, or ? serouche Rod Harris wrote: ** Serouche, Forget using groups for now then. Just put each userid in the 112 field surrounded by single quotes. Create a filter on submit/modify that looks at the CC field and places each user login ID in the cc field (you may need to do a lookup of the user form if you have full email addresses in the CC field) into the 112 field. Surround each user id with single quotes. Give assignee group permission to the relevant fields. Use request ID (1) to restrict row level access. Once you do this the built in permissions system will do the rest. Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** my problem is exactly here: all people are in the same group let say Callers They all can submit tickets. So with the submitter I have no problem. But then in addition to this: they should be allowed to access tickets only when they are in the CC field. So question: how am I going to check the $USER$ against that CC list using the Dynamic Group ? Sorry I don't get it. I can populate the Dynamic Group with the groupids. But then everybody from that group will have access to the ticket. Which I don't want. How can I build a workflow to give access on the user basis? keeping in mind I need to extract at some point my user from the CC list field The documentation is poor and wrong. Serouche Rod Harris wrote: ** Ok, submitter is handled in the usual way. Give the built in group submitter, access to everything that it needs, request ID field in particular. For the user(s) in the CC field I would create a dynamic group field and put everyone in the CC field (groups if necessary too) into the dynamic group field. If you are not already using 112 for anything else then this can be used to hold the CC users and groups. Give assignee group access to request ID also. In summary. Yes - you are on the right track. I think the main problem was that you just didn't get the syntax quite right for userids. Good luck, Rod On 08/04/2009, Remedy Maniac remedy.man...@googlemail.com wrote: ** right. Many thanks for this infos. Somehow I have the feeling that I am loosing my first goal: I need to give access on requests on an individual basis. Depending whether the user is either the submitter or in the cc list field. Would that be the way to proceed: using the Assignee Group combined with Dynamic group? Or am I just walking in lost corridors? Many thanks for your help Serouche Rod Harris wrote: ** Serouche, Yes, you can use the assignee group field to hold individual users. The userid needs to be enclosed in
Re: how to define access to Assignee Group
The 112 field is used for GROUPS not User Logins -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Remedy Maniac Sent: Tuesday, April 07, 2009 9:34 AM To: arslist@ARSLIST.ORG Subject: how to define access to Assignee Group dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are DISCLAIMER Important! This message is intended for the above named person(s) only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient of this e-mail and have received it in error, please immediately notify the sender by return email and then delete it from your mailbox. This message may be protected by the attorney-client privilege and/or work product doctrine. Accessing, copying, disseminating or re-using any of the information contained in this e-mail by anyone other than the intended recipient is strictly prohibited. Finally, you should check this email and any attachments for the presence of viruses, as the sender accepts no liability for any damage caused by any virus transmitted by this email. Thank you. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
Agreed...but they could create their own dynamic group/field and it will accept users and groups...:) -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Tanner, Doug Sent: Tuesday, April 07, 2009 7:47 AM To: arslist@ARSLIST.ORG Subject: Re: how to define access to Assignee Group The 112 field is used for GROUPS not User Logins -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Remedy Maniac Sent: Tuesday, April 07, 2009 9:34 AM To: arslist@ARSLIST.ORG Subject: how to define access to Assignee Group dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are DISCLAIMER Important! This message is intended for the above named person(s) only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient of this e-mail and have received it in error, please immediately notify the sender by return email and then delete it from your mailbox. This message may be protected by the attorney-client privilege and/or work product doctrine. Accessing, copying, disseminating or re-using any of the information contained in this e-mail by anyone other than the intended recipient is strictly prohibited. Finally, you should check this email and any attachments for the presence of viruses, as the sender accepts no liability for any damage caused by any virus transmitted by this email. Thank you. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
Of course, I am just not feeling a long and wordy explanation, Doug -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ Longwing Sent: Tuesday, April 07, 2009 9:49 AM To: arslist@ARSLIST.ORG Subject: Re: how to define access to Assignee Group Agreed...but they could create their own dynamic group/field and it will accept users and groups...:) -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Tanner, Doug Sent: Tuesday, April 07, 2009 7:47 AM To: arslist@ARSLIST.ORG Subject: Re: how to define access to Assignee Group The 112 field is used for GROUPS not User Logins -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Remedy Maniac Sent: Tuesday, April 07, 2009 9:34 AM To: arslist@ARSLIST.ORG Subject: how to define access to Assignee Group dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are DISCLAIMER Important! This message is intended for the above named person(s) only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient of this e-mail and have received it in error, please immediately notify the sender by return email and then delete it from your mailbox. This message may be protected by the attorney-client privilege and/or work product doctrine. Accessing, copying, disseminating or re-using any of the information contained in this e-mail by anyone other than the intended recipient is strictly prohibited. Finally, you should check this email and any attachments for the presence of viruses, as the sender accepts no liability for any damage caused by any virus transmitted by this email. Thank you. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are DISCLAIMER Important! This message is intended for the above named person(s) only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient of this e-mail and have received it in error, please immediately notify the sender by return email and then delete it from your mailbox. This message may be protected by the attorney-client privilege and/or work product doctrine. Accessing, copying, disseminating or re-using any of the information contained in this e-mail by anyone other than the intended recipient is strictly prohibited. Finally, you should check this email and any attachments for the presence of viruses, as the sender accepts no liability for any damage caused by any virus transmitted by this email. Thank you. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
that's what I also understood. So then I tried with the Submitter field of the User form which is a Group. Same result. It should work with this or ? Tanner, Doug wrote: The 112 field is used for GROUPS not User Logins -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Remedy Maniac Sent: Tuesday, April 07, 2009 9:34 AM To: arslist@ARSLIST.ORG Subject: how to define access to Assignee Group dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are DISCLAIMER Important! This message is intended for the above named person(s) only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient of this e-mail and have received it in error, please immediately notify the sender by return email and then delete it from your mailbox. This message may be protected by the attorney-client privilege and/or work product doctrine. Accessing, copying, disseminating or re-using any of the information contained in this e-mail by anyone other than the intended recipient is strictly prohibited. Finally, you should check this email and any attachments for the presence of viruses, as the sender accepts no liability for any damage caused by any virus transmitted by this email. Thank you. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
Hi, The field ID 112 should contain a group name, not a login name. In your case, you should create a group for each user. Best regards Jean-Louis Halleux www.arsmarts.com On 07 Apr 2009, at 15:33, Remedy Maniac wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
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) [mailto:arsl...@arslist.org] On Behalf Of ARSmarts Support Sent: Tuesday, April 07, 2009 8:48 AM To: arslist@ARSLIST.ORG Subject: Re: how to define access to Assignee Group Hi, The field ID 112 should contain a group name, not a login name. In your case, you should create a group for each user. Best regards Jean-Louis Halleux www.arsmarts.com -Original Message- On 07 Apr 2009, at 15:33, Remedy Maniac wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
Re: how to define access to Assignee Group
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 frederick.w.gro...@xo.com 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) [mailto:arsl...@arslist.org] On Behalf Of ARSmarts Support Sent: Tuesday, April 07, 2009 8:48 AM To: arslist@ARSLIST.ORG Subject: Re: how to define access to Assignee Group Hi, The field ID 112 should contain a group name, not a login name. In your case, you should create a group for each user. Best regards Jean-Louis Halleux www.arsmarts.com -Original Message- On 07 Apr 2009, at 15:33, Remedy Maniac wrote: dear listers, I am trying to build an access based on individual basis. i.e: the user can access any ticket as soon as s/he is either the Submitter or in the CC list field found in the ticket itself (= there is a character field used to cc some people) So i created a character field with id 112 named Assignee Group I've built a workflow which reads the User form and set the field 112 to the login name of the $USER$ the Request-ID field is readable by the field id 112 This later is correctly updated base on the login found in the User form But then I keep getting the following message: You cannot translate the group name in the Group List or Assignee Group Field. : Assignee Group (ARWARN 9305) Can anyone help on solving this issue? Thank you Serouche PS: ARS 6.00.01 with Mid-tiers 6.3 on Solaris 8 with Sybase 12.5.3 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
