Using Appropriate Actions and Namespaces with Triggers for Expression Rules

The following table shows you which actions and namespaces you can use with the various triggers for Expression Rules. As a general rule, you cannot use asset-related actions with system-related triggers. Conversely, you cannot use system-related namespaces with asset-related triggers. The Trigger namespace is a universal namespace, which means that you can use it with any trigger. It allows you to get the name of the trigger and its date/time for auditing purposes (Audit action).

Note: The Asset Configuration triggers, ConfigurationValidation and DefinedConfiguration, do not use namespaces. These triggers provide functions to operate on ConnectedConfiguration configuration events.

 

With these Asset-based Triggers (Messages)

You can use these Namespaces

and these Actions

Alarm

AlarmExtendedDataChange

AlarmSeverityChange

AlarmStateChange

AssetTimer

Data

Event

File

InactiveAlarm

MobileLocation

Registration

StateChange

Alarm

DataItem

Device

File

Location

Registration

State

Event

 

EnableRule()

DisableRule()

ExecuteAction()

ExecuteCustomObject()

PublishObject() (not applicable to StateChange trigger)

Reevaluate()

RequestDataItem()

SendDataItem()

SetDataItem()

SetState()

Trigger

 

Also for the Alarm namespace:

With these Asset-based Triggers (Messages)

you can use these Actions

Alarm

AlarmExtendedDataChange

AlarmSeverityChange

AlarmStateChange

InactiveAlarm

Event

CreateAlarm()

SetAlarmState()

SetAlarmExtendedData()

SetAlarmSeverity()

 

 

With these system-based Triggers (Messages)

You can use this Namespace

and these Actions

SystemTimer

Trigger

EnableRule

DisableRule

UserLogin

UserLogout

User
(for UserLogin and UserLogout triggers, NOT for SystemTimer)

ExecuteCustomObject()

PublishObject()

EnableRule

DisableRule

Trigger