Understanding subscriber action types
Each event corresponds to different actions that can happen. Not all types of subscriber actions are available in all cell types. Some actions require additional parameters to be supplied (Arg1, Arg2, and Arg3). Not all actions correspond to each event.
An action is what happens when an event takes place in a cell. The type of action you use depends on the cell type.
Action Type | What it does |
---|---|
Opens the Add Carrier Bid pop-up window This action uses the leg number and the truck carrier ID number. Additional arguments required for this action are:
This action is for Brokerage only. |
|
Opens the Add Check Call pop-up window The additional argument required for this action is:
This action is for Brokerage only. |
|
Assign Assets action for each asset type |
Six separate actions are available to assign specific asset types: These actions open the Asset Assignment window, and assign the asset to the leg. You can use them with a CustomMenuCommand event. The additional arguments required for these actions include:
|
Opens the Asset Assignment window for the leg The user must assign the specific assets to the leg. The additional argument required for this action is:
|
|
Opens the Advanced Carrier Selection window and assigns a carrier to a leg When you pair this action with a DragDrop event, additions arguments are required:
When this action is not paired with a DragDrop event, the required arguments are:
This is for Brokerage only. |
|
Opens the load assignment form for that leg number, and allows the user to dispatch a load It will not send a message to the truck’s device. The additional argument required for this action is:
|
|
Opens the load assignment form for that leg number, and allows the user to dispatch a load and send a message to the truck’s device |
|
Filters data based on the data of the publisher row Usage varies based on published and subscriber cell types. For example, for a specific driver this action could allow the user to show all the loads assigned to the driver. The FilterData action for each different cell is described below.
|
|
Filters data based on the planning board configuration search criteria This action applies only to the Branch Tree cell. This is a custom code only. It is not user definable. |
|
Filters data on Grid cell types, using scroll search criteria It selects the subscriber’s rows that have the same value as the publisher’s clicked row. For example, suppose a specific driver has a unique Driver ID. A filter can be set on the Driver ID number, which is the parent key. The filter finds all loads that correspond to that Driver ID number in the loads, or child, grid. |
|
Selects the row that corresponds to the point clicked on the map |
|
Used in two different ways:
|
|
Plots the leg and the last known check call for the leg |
|
Opens the Advances/Misc Labor Window You use the window to send a carrier advances. Normally, you use this action with a CustomMenuCommand event; it can be used only on a grid. The additional arguments required for this action are:
|
|
Opens a new instance of the Order Maintenance window and displays the trip for the order header number If an instance of the Order Maintenance is already open, it is reused. The additional argument required for this action is:
|
|
Opens a new instance of the Order Maintenance window and displays the trip for the order header number The additional argument required for this action is:
|
|
Opens a new instance of the Trip Folder window and displays the trip for the order header number If an instance of the Trip Folder is already open, it is reused. The additional argument required for this action is:
|
|
Always opens a new instance of the Trip Folder window and displays the trip for the order header number The additional argument required for this action is:
|
|
Posts the load to the Freight Board Interface Note: To use this action, you must be licensed for the Freight Board Interface. For more information, contact Trimble Sales. |
|
Refreshes the carrier bids in the Load Information cell This is for Brokerage only. |
|
Refreshes the check call in the Load Information cell For an example of this, see AddCheckCall. After the check call was added, the data in the Carrier Load Information was refreshed using this action to incorporate the new check call. This is for Brokerage only. |
|
Refreshes the data in the subscriber cell When you use it in a:
Normally, RefreshData is set up with the AfterCellControlUpdated event, so that the data in the grid is refreshed. Note: To see a full list of events you can use with this action, see Understanding how events and actions work together. |
|
Sets the BookedRevType1 value for that leg to the selected branch Additional arguments required for this action are:
|
|
Many different Grid cells can be plotted on a single map. This action shows or hides a map layer represented by the publisher. |
|
Refreshes the map data by retrieving the latitude and longitude data represented by the publisher and plotting the points |
|
Refreshes the selected row |