So what I did is create a People record with the login ID of 'AR_ESCALATOR' and gave it the three Contact permissions. There may be a better way, but this worked for me.
Thanks, Ron Legters ITIL Tools & Process Admin From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Jorge Polo Sent: Friday, September 24, 2010 10:15 AM To: arslist@ARSLIST.ORG Subject: Re: Incident Management Remedy_Login_ID ** The userid is AR_ESCALATOR...... I have an escalation that trigger filters to do the updates and adds .... Our server version is 7.5..... From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Ron Legters Sent: Friday, September 24, 2010 12:58 PM To: arslist@ARSLIST.ORG Subject: Re: Incident Management Remedy_Login_ID ** I remember running into this when I was upgrading to ITSM 7 (and from the field list you provide I'm assuming you're using ITSM7). As I recall the userid doing the updating of people records needs to belong to the permission group that allows modifying the 'Remedy_Login_ID'. I just don't recall which one that is. I'm pretty sure it's either 'Contact Organization Admin', 'Contact People Admin', or 'Contact Support Admin'. Thanks, Ron Legters ITIL Tools & Process Admin From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Jorge Polo Sent: Friday, September 24, 2010 9:22 AM To: arslist@ARSLIST.ORG Subject: Incident Management Remedy_Login_ID ** Hello, We are in the process of automating the maintenance of our "People" records for Remedy. Here's our issue - When we try to create a record for a new person, the Workflow will not create the Remedy_Login_ID at the same time we do our initial Push. We use the CorporateID field for all records, and is a part of the Qualification 'Corporate ID' = $OPSYS..SearchID$. On the "Record does not match" condition, we set the following fields and then do the push. If we include the Remedy_Login_ID, the push fails with no explanation. 1) Unrestricted Access 2) Default Country 3) Site ID 4) Phone Number Bussiness 5) Corporate ID 6) Corporate E-Mail 7) Internet E-Mail 8) Desk Location 9) Local Bussiness 10) Area Business 11) CC Business 12) Client Sensitivity 13) Support Staff 14) Job Title 15) Client Type 16) First name 17) Last name 18) Organization 19) Company 20) Site 21) Department 22) Full Text License type 23) Short description 24) Profile Status 25) Submitter Similarly, during Updates of existing records, we cannot update People Records that do not contain the Remedy_Login_ID Any ideas? ________________________________ Portions of this message may be confidential under an exemption to Ohio's public records law or under a legal privilege. If you have received this message in error or due to an unauthorized transmission or interception, please delete all copies from your system without disclosing, copying, or transmitting this message. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ ________________________________ Portions of this message may be confidential under an exemption to Ohio's public records law or under a legal privilege. If you have received this message in error or due to an unauthorized transmission or interception, please delete all copies from your system without disclosing, copying, or transmitting this message. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
