The modify needs to be done through the api. This is either an escalation, or some other api client that does it, but nothing at the db can do it.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Adarsh Sent: Wednesday, November 07, 2012 1:38 AM To: [email protected] Subject: Re: Remedy Integration ** Thank You Very much guys for the reply .. If I create a DB trigger on insert and have some field modified just after the data has been inserted by the .jsp will that help in triggering the remedy filter. Jason, Thank you very much for the advice, I too would have used an Escalation instead of other options But we already have multiple escalations running every minute in my environment :-( On Tue, Nov 6, 2012 at 9:42 PM, Longwing, LJ CTR MDA/IC <[email protected]> wrote: Jason, You are right, I was going off of the ability to call the script from either the same process that creates the db record, or a db trigger, but you are 100% correct. If instead of creating the db record, the integration could do something else as you suggested, it could remove the 'need' for the api script all together. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jason Miller Sent: Tuesday, November 06, 2012 9:04 AM To: [email protected] Subject: Re: Remedy Integration ** Just to expand on that little... if the process is only dropping a record into a DB table you will need a timer component somewhere unless you create a DB trigger to call a 'client'. Since the record came in at the DB level, under the AR api's radar, you need some method of letting AR System know that new record is there for filters to fire on. In LJ's example you might have a cron job or Windows scheduled task to call your api client that would let AR System know the new record is there. At that point why not use an Escalation? As long as the record count in the SQL table is kept under control there isn't a performance issue. True the fastest it can run is once every minute but for most processes that is frequent enough. The benefit of using an Escalation is you remove the added complexity of needing to create you own api client and the need to manage an external scheduling component. I completely understand not wanting to create an Escalation to watch for a new record every minute. We have a few of these types of integrations and I hesitate each time we build one but when it comes down to it the level of effort and added complexity to create and maintain all of the external moving parts isn't worth it. Looking at this a little differently, it sounds like you already have a process that is picking up the SMS messages and putting them into a table. Can you give use a little more detail about this process? Is it a custom process? Instead of dropping records into a DB table can it call a web service, custom api program, shell script, etc.? Maybe there are some options here to remove the need for a timer component altogether. Jason On Nov 6, 2012 6:11 AM, "Longwing, LJ CTR MDA/IC" <[email protected] <mailto:[email protected]> > wrote: Adarsh, You are thinking down the correct path regarding API. You will need to write a small, simple API based 'client'. This client could be as simple as a perl script that does a modify on the record in question, that modification could of course trigger the filters you are looking for. The official API's are Java and C, but there are tons others out there (PHP, .NET, Perl, etc). -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Adarsh Sent: Tuesday, November 06, 2012 5:07 AM To: [email protected] Subject: Remedy Integration ** Hi Guys, I am sure you might come across this question in past, if someone could please help me with this .. I am currently working on an integration where users can send a SMS to get an Incident created. Sms sent by an user is captured in one of the table in the arschema. I have created a view table in remedy to view the data in this table. based on the phone no of the users I will be capturing the users details and these details with required fields to generate an incident will be pushed to incident interface create form. Now !!! I dont want to use an escalation to trigger the filters :-( .. even if i write a trigger in the database which would push all the values to incident interface form still the incident wont get created as the filter wont come to know about the table update .. Is there any other way I can get the filter triggered once there is a new entry in the view form. I somewhere read about using API calls or web services but its not mentioned anywhere how to use it. I am using remedy 7.6.04 _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
