Developer ToolsFree referencePDF, Excel, Word exportInfor SyteLineAll Infor SyteLine (CloudSuite Industrial) tools

SyteLine Event Action Types Reference

This is a reference of the 26 application event action types on the Event Actions form in Infor SyteLine 8, 9 and 10. Each row says what the action does, which parameters matter, a typical SyteLine use and whether it makes the handler wait.

Download:

Action type	What it does	Key parameters to set	Typical use in SyteLine	Waits or suspends
Achieve Milestone	Records a milestone and sets the designer-defined event state, then the handler continues	State text (read later with EVENTSTATE)	Show 'Credit approved' on Event Status partway through an approval flow	No
Attach	Attaches, links, updates or detaches document attachments on records while the handler runs	Record, document, attach or detach mode	Link a signed PDF to a customer order during an approval flow	No
Audit	Writes an audit entry for the handler run	Text or expression to record	Record who approved a price override and when	No
Branch	Jumps to another action in the sequence when a condition is met	Condition, destination action	Skip the approval prompt when the order total is below a limit	No
Call Database Method	Runs a stored procedure or database function	Method name, input and output parameters	Call a custom stored procedure that writes to a user-defined table	No
Call IDO Method	Invokes a method on an IDO with parameters and captures output parameters	IDO, method, parameter list, output variables	Call a SyteLine IDO method to recalculate or post after a change	No
Call Web Service	Calls an external web service and returns the response	URL, request, result variable	Check a carrier or tax service from an event	No
Dispatch IDO Request	Sends an IDO request to a site or system the user is not connected to	URL() of the target, IDO request XML, result variable	Read or update data in another SyteLine site; parse the result with Transform XML	No
Execute IDO Request	Runs an IDO request XML in the current configuration	IDO request XML, result variable	Run a multi-step IDO request built from expressions	No
Fail	Stops the handler with Failure status when its condition is met	Condition, result message	Block deletion of an item, or reject an update that breaks a rule	No
Finish	Ends the handler with Success and an optional result message shown on Event Status	Condition, result message, state	End early once an approval is granted	No
Generate Event	Fires another event, usually a custom one, with parameters	Event name, parameters, synchronous or not	Split a long flow into reusable custom events	No
Goto	Jumps unconditionally to another action	Destination action	Loop back to a prompt after a rejection is reworked	No
Load IDO Collection	Loads rows from an IDO into a named result set	IDO, properties, filter, record cap, result set name	Load open lines for an order, then read them with P3 and ROWS(collection)	No
Load IDO Row	Loads one row from an IDO and puts property values into variables	IDO, properties, filter, target variables	Read a customer's credit limit before deciding to prompt	No
Notify	Sends a message to users or groups that needs no response	Recipients, subject, body, attachments	Tell the buyer a PO receipt was posted	No
Prompt	Sends a message that requires a response, with optional voting rules and timeouts	Recipients, choices, voting rule, timeout and destination	Credit-hold release approval on an SLCos update	Yes
Run Background Task	Submits a background task, such as a report or utility	Task name, parameters	Run a report after an approval is granted	No
Send BOD	Builds a BOD from noun, verb and body and places it in the Replication Document Outbox	BOD noun, BOD verb, body expression	Publish a custom BOD to ION when a record changes	No
Send Email	Sends an email to addresses outside the Inbox	To, subject, body, attachments	Email a supplier when a PO line due date changes	No
Set Attributes	Sets attributes of the running handler or event as listed on its parameter form	Attribute names and values	Set values that later actions or Event Status read	No
Set Values	Assigns values to event variables, or to properties of the row in an On item event	Variable or property names and expressions	Default a field on SLCoitems insert before the save commits	No
Sleep	Pauses the handler for a period of time	Duration	Wait before re-checking an external status	Yes
Transform XML	Applies a transform to XML and returns the result	Source XML, transform, result variable	Parse the result of a Dispatch IDO Request	No
Update Collection	Inserts, updates or deletes rows in an IDO collection	IDO, action (insert, update, delete), property values	Write a log row to a user-defined table IDO	No
Wait	Holds the handler until a condition is true or a timeout passes, then resumes	Condition, retest interval, timeout	Wait until a job is released before notifying the shop	Yes

The 26 action types follow the SyteLine Action Type help. Newer releases can add further types, so check the Action Type list on your own Event Actions form. Parameter names are shown in plain terms: build exact syntax with Edit Parameters and Check Syntax.

Design an approval flow with us

Describe the approval or alert you want in SyteLine and we will send back a handler and action sequence you can build, with the synchronous and suspend settings it needs.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Search for the job you need to do, for example 'approval', 'BOD' or 'block'. In SyteLine, open Event Handlers, pick the handler, click Event Actions, choose the Action Type and click Edit Parameters. Each action type opens its own parameter form, which writes the correct syntax back to the Parameters field. Infor recommends using those forms rather than typing parameters by hand, then clicking Check Syntax before saving. Give every action a description: when a handler has several Notify or Set Values steps, the description is what you see in the sequence list and in Event Status.

Synchronous handlers and actions that suspend

A synchronous handler runs inside the user's request, and if it fails the whole sequence fails, which is what lets Fail block a save. Prompt, Wait and Sleep are adjourning actions: they wait for an outside stimulus or a time, and the event system sets the handler to retest or time out and resumes it later. That only works when the handler is allowed to suspend. For a user-facing validation, keep the synchronous part short and decisive (Load IDO Row, Branch, Fail) and move people-based approvals into a flow that can suspend.

Fail and Finish end the handler; Branch and Goto move within it
Prompt with several recipients needs a voting rule: Majority, Plurality, Conditional Plurality or Minimum Count
Use Notify for information, Prompt only when you need an answer

Worked example: block item deletion

Create a synchronous handler on IdoOnItemDelete applying to SLItems. Action 1, Load IDO Row, reads whether the item has open demand into a variable. Action 2, Fail, has a condition on that variable and a message such as 'Item has open orders; set it to Obsolete instead'. Action 3, Finish, ends with Success. Users deleting a clean item see no change, while a delete with open orders is rejected with the message. The same pattern, swapped to a Prompt, gives a credit-hold approval on SLCos updates.

Common mistakes

The most common mistake is putting Prompt in a handler that cannot suspend and then wondering why users wait or the action errors. The second is using Execute IDO Request when the target is another site; Dispatch IDO Request is the one built for a system the user is not connected to. Third, people send Send BOD output and expect it to arrive immediately: the BOD goes to the Replication Document Outbox first, so check that form when it does not appear in ION. Finally, a Load IDO Collection without a tight filter and record cap can load thousands of rows on every save.

Frequently Asked Questions

What is Infor Mongoose?

Mongoose is the Infor application framework SyteLine and CSI are built on. It provides IDOs (the business object layer), the WinStudio form designer, the application event system with these action types, background tasks and the IDO request service used by APIs. Customising SyteLine mostly means working in Mongoose tools.

What is the difference between Notify and Prompt?

Notify sends a message that needs no reply and the handler carries on. Prompt sends a message with choices, waits for the response and returns it to the handler, optionally counting votes from several recipients and applying a timeout. Because Prompt waits, the handler must be able to suspend.

When should I use Dispatch IDO Request instead of Execute IDO Request?

Use Execute IDO Request to run an IDO request in the configuration where the event is running. Use Dispatch IDO Request when the request has to run on another site or system the user is not connected to, given by a URL. Its result comes back as XML that you usually parse with Transform XML.

Where do I see whether my event action ran?

Open the Event Status form for the event run, then Event Handler Status for each handler. You can see the actions executed, the result (Success or Failure), messages from Finish or Fail and any state set by Achieve Milestone. Prompts waiting for responses appear there too.

If you want approvals and notifications like these driven by plain-English questions over SyteLine data on your own servers, we can build that with you.

Talk to an Expert Explore More Free Tools