I have added this post after a question on a user group forum asking how to do this.
1) Open Events and filter for “IdoOnItemInsert” –> Click on the Event Handler button
2) Insert a new event handler
– Giving it a decent description
– In the “Applies To Objects” enter the IDO name you want to trigger the event from
– Make sure the active flag is checked
– Save the record & click event actions
3) In the event action, select the action type of “send email” and give it a decent description, then click event parameters
4) The parameters work as you would expect them to in relation to the to, cc, subject and condition.
5) If you wish to have details from the IDO included in the body or subject of the email, I use a substitution as shown here :-
This example is very much scratching the surface, and will get you started, but there is so much to consider and I would always recoment trawling through the infor documentation. 2 obvious thigs to mention are :-
– Use Global Constants for email addresses and such like. Then it is much easier to change when staff change over
– This example uses on ido update, you can use post ido update, and there is subtle differences between the 2 options. I believe record suspension is smoother on update rather than post update as the change is visible immediately to the user.
mpimperton placed this on the Syteline forum, which is very useful (Hope he doesn’t mind the quote being used)
Basically, the IdoOnItemInsert fires before the new row has been saved – it’s the row that “is about to be saved”. That means that auto-generated field values won’t yet be known and can show as “TBD”. For an Item record that’s probably irrelevant.
(For “update” triggers I have used IdoOnItemUpdate rather than IdoPostItemUpdate. That’s because the “On” trigger knows what the “old” values were (if you need those) whereas they’re not available if you use the “Post” version.)