# How the SyteLine Event System Works for Workflow Notifications > Source: https://netray.co/erp-help/syteline-event-system-app-events-workflow > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SyteLine's Event Manager lets administrators subscribe to IDO-level events, such as a purchase order being released or a customer credit hold being set, and fire an email, a Mongoose script, or a workflow action without writing an IDO extension. Cloud tenants can extend the same triggers into ION Workflow for multi-step, cross-application approval processes. ## Kind advanced ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Customization / Event Manager ## Query how does the SyteLine event system work for workflow notifications ## Alternate Queries - SyteLine Event Manager configure email notification - how to trigger a workflow when an IDO record changes in SyteLine - syteline business events vs ion workflow - csi event manager subscription setup ## Applies To SyteLine 8.x/9.x on-prem Event Manager; Infor CloudSuite Industrial with ION Workflow for cross-application processes. ## Steps ### Set up an event-driven notification **Items:** Open System Administration > Event Manager (Utilities menu in older versions) and review existing event definitions so you are not duplicating a subscription that already covers the same method. Identify the IDO and method that represents the business moment you care about, for example CustOrdr.Release or PurcOrdr.Approve, since events are attached to specific IDO methods, not a generic record-changed trigger. Create a new event definition pointing at that IDO method, and choose whether it fires Before or After the method executes, matching the Before/After model used by IDO extension classes. Attach an action to the event: a canned email notification using a mail merge template, a call to a Mongoose script, or in CSI a call into an ION Workflow process. Scope the event with a filter condition so it only fires for the records you actually want, for example only orders over a dollar threshold, rather than every save of that IDO. Assign the recipients or role, test with a real transaction in a non-production environment, and confirm the notification content pulls the fields you expect from the triggering record. Monitor the Event Manager log after go-live for failed sends, bad email addresses, template errors, since a silently failing notification is worse than no notification because people assume it is working. ## Sections ### Event Manager vs IDO extension classes vs ION Workflow **Body:** Event Manager is declarative and admin-configurable with no compile or deploy cycle, and it is the right tool for simple notification and single-step actions. IDO extension classes are code and are best for validation or business rules that must always apply regardless of the caller. ION Workflow, available in CloudSuite Industrial, is for multi-step approval processes that may span SyteLine and other Infor applications, with its own designer and audit trail. Choose Event Manager first for notify someone, extension classes for enforce a rule, and ION Workflow for route this through approvals. ### How event triggers relate to the IDO method model **Body:** Since events fire on specific IDO methods, understanding which method a UI action actually calls matters: a form button labeled Release might call a method with a different internal name. Use Application Studio's IDO documentation or trace tooling to confirm the exact method name before wiring an event to it, otherwise the event silently never fires because it is watching the wrong method. ### Debugging events that do not fire or fire too often **Body:** Most non-firing events trace back to watching the wrong method or IDO, a scoping filter that is too narrow, or an event defined on Before when the data needed for the filter is only populated After. Events that fire too often usually mean the filter condition was left too broad, or the same method is being called multiple times per user action, common with grid saves that validate then commit. ### ION Workflow for cross-application approval chains **Body:** In CloudSuite Industrial, ION Workflow can be triggered from a SyteLine BOD publish rather than the on-prem Event Manager, letting an approval chain span SyteLine and another Infor application, or escalate through Ming.le. This is the right tool when a notification needs to become an actual multi-person, multi-step approval with reminders and escalation, not just an FYI email. ## Pitfalls - Wiring an event to the wrong IDO method because the UI button label does not match the underlying method name. - Leaving the filter condition too broad, so the event fires on every save and either spams users or overloads an external system it calls. - Assuming Event Manager notifications are guaranteed delivery when a bad SMTP config or template error fails silently unless someone checks the log. - Putting heavy logic, loops over related records, external API calls, into an event action instead of an IDO extension built for that kind of work. - Not accounting for Before/After timing when a filter needs a field only set by the method itself, so the filter never matches on a Before event. ## Ai Angle ERPray can answer which events are configured on the CustOrdr IDO and what they do by reading the Event Manager configuration directly, faster than clicking through every event definition by hand, and it can flag events whose filter conditions look too broad based on how often they have fired. For teams moving from ad hoc email notifications to real approval routing, SyteRay can map an existing Event Manager notification to an equivalent ION Workflow definition as a starting point. ## Faq ### Can Event Manager call a custom Mongoose script? **Answer:** Yes, that is one of the standard action types: point the event at a Mongoose script that runs the logic you need, useful for actions more complex than a template email but not complex enough to warrant a compiled IDO extension class. ### Do events fire for changes made through integrations, not just the UI? **Answer:** Yes, because events are attached at the IDO method level, they fire regardless of which client called the method, the thin client, a Mongoose script, an ION BOD import, or a direct IDO API call, which is exactly why they are useful for consistent notification. ### What is the difference between an Event Manager action and an IDO extension's AfterModify logic? **Answer:** Both run after the same method, but Event Manager actions are configured by an administrator without code and are easy to change without a deployment, while extension class logic is compiled and should be used when the behavior must be guaranteed and cannot be accidentally disabled by an admin. ### Can I chain multiple actions off one event? **Answer:** Typically an event definition supports one primary action; for multiple downstream effects, either define multiple event records against the same method and filter, or move the orchestration into an IDO extension class or ION Workflow process that can sequence several steps explicitly. ### Why did my event fire on a record that should have been excluded by the filter? **Answer:** Check whether the filter references a field that changes value during method execution; if the event is set to Before and the filter checks a field that only gets its final value inside the method, the filter evaluates against the stale value and can match unintentionally. ## Search terms syteline event manager, syteline workflow notification setup, csi event manager subscription, syteline ion workflow approval, syteline business events, trigger notification on ido change syteline, syteline event manager vs extension class, infor cloudsuite ion workflow, syteline before after event, syteline event manager troubleshooting --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json