Yeah, I've seen that the Modify Escalations seem to update all records, because I haven't found a effective and efficient way to check for changes, and it would probably take almost as much time to do the check as it would to update the data anyway. Thankfully, we're under a thousand, so actions to submit and/or modify all records only take a minute or so. The data is fairly volatile, so I'll try updating it every few hours during the day. It shouldn't be a noticeable impact, and if it is, we can always back it off to an acceptable balance. Thanks again! Rick _____
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Roger Justice Sent: Monday, May 14, 2007 12:57 PM To: [email protected] Subject: Re: ITSM 7/LDAP not importing some records ** When I did the push qualification I did a RequestID != Remedy Login. My Vendor request ID is mapped to the network login. The only potential problem is that if you have 5000 entries the qualification will require all records be compared and of course the escalation should be run after hours. -----Original Message----- From: [EMAIL PROTECTED] To: [email protected] Sent: Mon, 14 May 2007 3:39 PM Subject: Re: ITSM 7/LDAP not importing some records ** Thanks, Roger and Fred, I'll do that. Interesting that the Default value wouldn't be seen by Filters and Escalations. Have you found any other gotchas with LDAP? Also, am I assuming correctly that the Escalation, when it fires against the Vendor form, will do a fresh pull from LDAP vs. just getting whatever might be in that form from the last manual search? Rick _____ From: Action Request System discussion list(ARSList) [mailto:[email protected] <javascript:parent.ComposeTo(> ] On Behalf Of Roger Justice Sent: Monday, May 14, 2007 12:09 PM To: [email protected] <javascript:parent.ComposeTo(> Subject: Re: ITSM 7/LDAP not importing some records ** Yes, mine did the same thing and I created 2 escalations 1 if there was a phone number and 2 if there was no phone number. On the no phone number I hard coded the receptionist. -----Original Message----- From: [EMAIL PROTECTED] <javascript:parent.ComposeTo(> To: [email protected] <javascript:parent.ComposeTo(> Sent: Mon, 14 May 2007 2:52 PM Subject: ITSM 7/LDAP not importing some records ** I have an ARDBC integration between ITSM 7.0.2 and LDAP that is working fine, except that it won't import records for which there is no phone #. Even though there is a Default Phone # in the Business Phone # field, only LDAP records with a value in the 'telephoneNumber' attribute get imported. The really puzzling part is that after running Filter and Escalation logs while the data is importing, the error is not generated from Remedy workflow, from what I can see. The Escalation displays that an error occurred at the end of each record's Push Fields, but is no more specific than that. The Filter logs don't show any related problems at all. Has anyone run into this before? Rick Cook __20060125_______________________This posting was submitted with HTML in it___ _____ AOL now offers free email to everyone. Find out more about what's free from AOL at <http://www.aol.com/?ncid=AOLAOF00020000000437> AOL.com. __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 ARSlist:"Where the Answers Are"
