Understanding how events and actions work together
Not all events and actions are available in every publisher/subscriber combination. In each cell, the events and actions listed are for that particular base cell type.
The Actions field drop-down list includes any actions supported by that cell type. The events available for a particular subscription depend on the publisher. The actions for a specific subscription depend on the subscriber.
For example, suppose you make a subscription from a Grid cell to a Map cell.
The publisher is a Map cell. The only event options are AfterCellControlLoaded and MapMarkerClicked.
The subscriber is a Grid cell. The available actions include:
-
AddCheckCall
-
DispatchDontSendToTruck
-
DispatchSendToTruck
-
FilterDataCustom
-
FilterOnParentKey
-
LocateDataRow
-
OpenOrderEntry(New)
-
RefreshData
However, these are not all valid event-action relationships. For example, MapMarkerClicked and AssignTrailer is not a valid event-action relationship, even though it is possible to set it up this way.
Some of the correct event-action relationships are shown in the following tables.
These are not the only combinations-just all that have been documented. |
Grid cell as a subscriber
Event | Actions | Publisher basic cell types |
---|---|---|
DragDrop |
AssignCarrier/Driver/Driver2/ |
Grid |
AssignCarrierACS |
Grid |
|
RowClicked |
FilterDataCustom |
BranchTree |
FilterOnParentKey |
Grid |
|
PostLoadToFBI |
Grid |
|
CustomMenuCommand |
FilterOnParentKey |
Grid |
AddCheckCall * |
Grid * |
|
OpenTripFolder/ |
Grid * |
|
OpenOrderEntry/ |
Grid * |
|
MapFindPoint |
Grid |
* Indicates the publisher is equal to the Cell Name. In other words, the publisher and the subscriber are the same.
Map cell as a subscriber
Event | Action | Publisher basic cell type |
---|---|---|
AfterCellControlUpdated |
UpdateMapData |
Grid |
CustomMenuCommand |
MapFindPoint |
Grid |
MapZoomToLocation |
Grid |