My understanding of the view form (based on discussions with remedy instructors) is that it does not cache the information, so accessing the form is the same as making a sql call, you're just not doing the SQL logic against the information until it exists locally. I would love for someone to refute this, as I would prefer 1-2 hour caching over real-time calls.
-Paul -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger Sent: Wednesday, April 23, 2008 11:38 AM To: [email protected] Subject: Re: Active Link After Submit Instead of Filter How about creating a View form to your view in the external db? Then you do not need a SQL call. HTH, Roger A. Nall Manager, OSSNMS Remedy T-Mobile, USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Paul Blasquez Sent: Wednesday, April 23, 2008 2:32 PM To: [email protected] Subject: Active Link After Submit Instead of Filter Hello, I have a custom 6.3 Remedy implementation which is used by our Netcool monitoring system to open tickets based on certain events. The netcool remedy gateway is used to push a few fields to Remedy and open a ticket, then the Request ID is passed back to netcool and used for future updates to the event. All of this works just fine. The issue I am seeing is that after Remedy receives the fields and the ticket is saving, I fire 2 filters to pull data out of an external database via a SQL call over a view in the local Oracle DB. This call can sometimes time out. When it does, this causes the netcool gateway to receive an ARERR 92 and a request ID is never created. I am trying to work around this by doing the filter actions with an active link that fires after submit. I have tried it with both set field alone and with a set field then a push field of matching IDs to the same request ID. Neither of these methods have worked. Although the ticket opens fine, the SQL results are not pushed to the fields. Once again, the priority is that netcool receives a request ID in an action that is separate from the SQL call. I realize that an 1-2 minute escalation could accomplish this but I don't like that from a performance standpoint. Any input is appreciated, thanks! ____________ Paul Blasquez Senior Network Engineer/Remedy Developer | Desk - 408.360.5220 | Cell - 408.627.5714 ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
