Events
Learn about events, their role in application logic, and event types.
This section includes
- Event basics and how events trigger methods in application logic.
- Procedures to configure external, change, transitioned, and range transitioned events, and delete events.
- An example of using transitioned events to open and close a dialog box.
- Event type categories, including alarm, audit, communication driver, condition, model change, program and task, user interface, workflow and user session, and variable and data events.
- Objects that include predefined runtime events.
Overview
An event occurs at runtime to indicate that a certain situation has occurred. Then, the
system or user performs an action or method. Both users and the system can cause events on
the HMI device. For example, an event can occur when the user clicks the mouse button. The
system can also trigger events. For example, the system could trigger an event when a
graphic element enters a specific state, such as a color changing values.
Events perform methods to build application logic. Add a method to an event and configure
the method so the event performs the method at runtime. For each event, configure one or
more methods to perform specific actions. For more information about methods, see Methods.
For detailed event configuration procedures, see:
TIP:
Events trigger across the
FactoryTalk Optix Application
runtime. When an event occurs, such as a value change or
variable transition, any part of the project can subscribe to the event and respond
accordingly. For example, you can open a dialog box or change screens based on controller
tag values, conditions, or events. For more information, see Configure transitioned events to open and close a dialog box.Event types
Objects predefined with events
Some objects generate events at runtime. The predefined events for objects may include:
Objects | Events |
|---|---|
|
|
|
|
|
|
Provide Feedback