Skip to Content

Default language.

Additional considerations for sending events

Using the $EVENTTYPE$ keyword, the active link running on the Event condition can access the eventType specified in the PERFORM-ACTION-SEND-EVENT target eventType eventData command. (The $EVENTDATA$ keyword can represent event data to be attached.) Likewise, the recipient using the $EVENTSRCWINID$ keyword can access the window ID of the window sending the event.

When using the Run Process Send Event action with web browsers, sending a message to a parent window or child windows behaves in an undefined fashion if the contents of the windows are changed by:

  • Navigating to a new URL.
  • Clicking the Back, Forward, or Reload buttons on the browser.
  • Using an Open Window active link action that reloads new data into an existing window, causing the form to be unloaded.

If this event is sent to a data visualization field, the target must be F dataVisualizationFieldID.

An example of Run Process syntax that sends the ChildClosed event to the current window's parent is:

PERFORM-ACTION-SEND-EVENT @ ChildClosed

The syntax that sends the ParentClosed event to the current window's children is:

PERFORM-ACTION-SEND-EVENT # ParentClosed

Warning

Note

Quotation marks are optional in the Run Process command if the eventType does not contain a space. For example, they are optional for: PERFORM-ACTION-SEND-EVENT @ EventA but you must use them for: PERFORM-ACTION-SEND-EVENT @ "This is the event".


If you are using field references for the target and eventType, make sure the field is set properly prior to executing the Run Process command.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Remedy Action Request System 20.02