Yep that's true, but in our case, they didn't want the technician to have to take that step, so we're assigning based on some internal criteria.
I just mentioned it because sometimes it all looks okay, (the group info all appears fine) but the error still occurs. What I found is that the support person we were trying to assign it to, did not belong to the support group itself. Once we corrected that it all worked great. -Mary _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of T. Dee Sent: Monday, December 17, 2007 7:46 AM To: arslist@ARSLIST.ORG Subject: Re: Error while trying to create incident record via push action ** You don't have to assign it to a Person, just a group - then someone in the group will assign it to themselves when they get the notification. On 12/17/07, Mary Dollus <[EMAIL PROTECTED]> wrote: ** Morning, Yes I struggled with that for a bit as well. You have to set the Assignee groups and Assignee Group ID, but you also have to make sure that if you are assigning to a person.. that they are also have perms to that support group. Hope that makes sense, if not let me know. - Mary Dollus _____ From: Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] On Behalf Of T. Dee Sent: Monday, December 17, 2007 7:35 AM To: arslist@ARSLIST.ORG <mailto:arslist@ARSLIST.ORG> Subject: Re: Error while trying to create incident record via push action ** If I am not mistaken these fields are required so when you are using HPD:IncidentInterface_Create you need to provide these OR as I did I used Auto Assign which automatically populates these. Ty On 12/14/07, T Wang < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: ** Hi List, Did anybody ever encounter this error message while trying to create incident record through HPD:IncidentInterface_Create? "The Assigned Group fields are invalid. Use the associated field menus Support Company, Support Organization, and Assigned Group or the type-ahead-return function on the Assigned Group field to select this information. (ARERR 1291049)" Thanks. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
