The platform includes a set of built-in objects that Processes use to trigger automation, send emails, attach files, and surface messages to users. You do not create or configure these objects directly — they are pre-installed in every instance. Instead, you write records to them from a Process Output, and the platform responds by carrying out the associated action.

Understanding what these objects do is essential for configuring notifications, email distribution, and process chaining. Note that ES_ objects are not exposed to end users; see ES_ Object Configuration for more.

​

EU_NOTIFICATION is the standard mechanism for displaying messages to users during and after Process execution. When a Process writes records to this object, those messages appear on the Process Execution screen when the run completes, and are stored in the database for later reference via the Notifications screen.

Each record written to EU_NOTIFICATION represents one message. The record must include a severity (Warning, Error, or Information), a title, a descriptive message, a timestamp, a status (always Open on creation), and the name of the application where the notification should appear.

Notifications are configured in the Process Logic workbook and written via a Process Output. See Process Notifications for full configuration guidance.

​

EU_OUTGOING_MAIL allows a Process to queue outgoing emails. When a Process writes a record to this object, the platform adds the email to the outgoing mail queue and handles delivery asynchronously.

Each record defines the recipient or recipients, the subject line, and the message body. If the email requires file attachments, those are defined separately using EU_OUTGOING_ATTACHMENT.

EU_OUTGOING_MAIL is configured as a Process Output in the same way as any other output object.

​

EU_OUTGOING_ATTACHMENT is used alongside EU_OUTGOING_MAIL to attach files to queued emails. Each record written to this object defines an attachment file name and a reference to the associated email record. The platform retrieves the file from the Process Report file list and attaches it before sending.

This is the mechanism used for automated report distribution — a Process generates a report, writes it as a Process Report, then writes an EU_OUTGOING_ATTACHMENT record to attach it to an outgoing email.

​

EU_RUN_PROCESS is how a Process triggers other Processes to run in sequence. When a Process writes one or more records to this object, the platform queues and executes the listed Processes in the order they are defined.

Each record specifies the name of the Process to run and the parameter string to pass to it. This is the foundation of process chaining and workflow automation. If any Process in the chain fails, all Processes in the same chain are rolled back together.

See Chain Processes in a Workflow and Control Processes for how this object is used in practice.

​

ES_PROCESS_EXECUTION is the internal process execution queue. It stores records for both queued and completed Process executions, and is the object that Schedule Processes write to when building the automated execution schedule.

Unlike the other objects listed here, ES_PROCESS_EXECUTION is not typically used directly by configurators in everyday Process design. It is written to by Schedule Processes and read by the platform's scheduling infrastructure. See Run a Process on a Schedule for details. Note that ES_ objects are not exposed to end users; see ES_ Object Configuration for more.