The event type

An event object represents the synchronization event that triggered the workflow script.

Literal syntax

Remarks

Event objects are read-only.

The event object is available only in scripts that are triggered by a synchronization event (set up using the for endsynceventtab-name trigger declaration). You can access the fields of the triggering event in a script using dot notation as the event field of the endsync variable. The name, number, and type of the fields in an event object is determined by their events table schema.

Using the following ping events table schema,

ping.evem

<Event Name="ping" xmlns="http://schemas.mobilengine.com/event/v1">
  <Columns>
    <Column Name="user" Type="Text" AgentName="true"></Column>
    <Column Name="item" Type="Text"></Column>
  </Columns>
</Event>

the pingPopulator workflow script creates three new events with fixed string type values.

pingPopulator.rfs

server program pingPopulator for form dummy
using eventtab ping;
{
  events.ping.Create({user: form.info.user.name, item: "Athos"});
  events.ping.Create({user: form.info.user.name, item: "Porthos"});
  events.ping.Create({user: form.info.user.name, item: "Aramis"});
}

The pingListener workflow script is triggered on the server when the mobile client of the user designated in the event schema sends the server acknowledgement that it has downloaded the changes to the pingeventtab from the server.

pingListener.rfs

server program pingListener for endsync ping
 {
  trace endsync.event.item;
 }

Because the pingPopulator script created three events, the pingListener script will be triggered three times, with the following console output.

"Athos"

"Porthos"

"Aramis"

eventtab.Cancel()

The form data type

Developer Documentation

Workflow Script Reference Guide

The event type