Thanks Axton. I kind of figured that Remedy was not able to identify the change. I have setup a proof of concept using the Escalation idea. I just fear that I may have to have several escalations running that have to run every minute. But if we set it up right it may only have a few records to search through. Thanks for the ideas.
Ron Smith Web/Remedy System Developer Providence Health System [EMAIL PROTECTED] 503-216-7866 ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Tuesday, December 19, 2006 11:06 AM To: [email protected] Subject: Re: Question about View forms and the DB it is connected to. ** Remedy has no bindings to the tables accessed using view forms, as far as transactions occur, unless they originate from Remedy, in which case filters will work for your needs. The most common approach is to have a modified time column in the view form, the run an escalation that checks for updates based on that time value. Some other approaches that come to mind: - use the db to monitor for transactions; if a transaction is caught, use an api to trigger the workflow within Remedy Axton Grams On 12/19/06, Smith, Ron <[EMAIL PROTECTED]> wrote: ** I want to know if there is a way to detect that a new INSERT or UPDATE has occurred in the Database Table that a View form is connected to. It can be done with an escalation, but would like to have it be real time. Any information or documentation anyone might have on this would be appreciated. Thanks <mailto:[email protected]> Ron Smith Web/Remedy System Developer Providence Health System [EMAIL PROTECTED] 503-216-7866 DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
