Forums
Smart Notification
Executing Stored Procedures via SmartNotes.
Author
Messages
updiksc
New Member
Posts: 1
5/23/2006 2:09 PM
Basically, we have a need to have a Smart Notification execute a stored procedure in addition to sending the email based on a defined query. The stored procedure will be designed to update tables based on the assumtpion that an email was generated and sent.
The issue at hand is that we are being told by our technical team that if the notification is executed in a preview mode (i.e., no notifications are actually sent out), that the stored procedure would be executed as well. In effect, there is no way to configure the notification to only execute the SP when emails are sent and to ignore the SP when the notification is executed in this preview mode. I have a hard time believing this. There's got to be a way to configure the notification to generate and pass information to the SP whether or not emails were sent out (via parameters, etc).
Any information that you can provide would be greatly appreciated.
Thanks,
Scott
John Henley
Senior Member
Posts: 3348
5/23/2006 7:33 PM
You could include a parameter/attribute on the stored procedure (e.g. update_flag). Depending on the value passed from LSN to the database for that parameter, the stored procedure could skip it's logic. When running in preview, send a "N" value. When putting it into production, set the value to "Y".
IloveLawson
Basic Member
Posts: 13
5/4/2007 10:49 PM
Hi, I am looking a way of triggering a java program during LSN delivering a notification. Do you think it is possible? I am trying to setup XML via HTTP type of device, however, I do not have enough info to get it working. Any suggestions? thanks.
Chiahao
Will
Veteran Member
Posts: 39
5/4/2007 10:54 PM
How about a db trigger on the LawsonSN.EMPDELIVERYLOG table, assuming you are routing those logs to the database?
John Henley
Senior Member
Posts: 3348
5/8/2007 8:34 PM
Chiahao, I haven't done that via HTTP device delivery, but if anything, that would be the place to try it.
Guillaume's suggestion of using a db trigger might be easier.