Siebel Store-and-Forward Messaging Guide for Mobile Web Client > Siebel Store-and-Forward Messaging Sample Workflows >

Dispatch Board - Generic Workflow

This topic describes the Dispatch Board - Generic workflow for Store-and-Forward Messaging. The workflow is shown in Figure 7.

Figure 7. Dispatch Board - Generic Workflow

As shown in Figure 7, the Dispatch Board - Generic workflow enforces start time restrictions during manual assignment of activities to field service engineers. It also calls the SAF - Activity workflow when Store-and-Forward messaging is the appropriate channel for dispatching the activity to the engineer. This workflow contains the following steps:

1. Query Activity: This step gets the information for the selected activity
2. Earliest/Latest Start Violation Check - User Property: This step checks whether an administrator has enabled or disabled a check for start and end time restrictions. Specifically, this step checks the value of the Enable Earliest/Latest Start Violation Check user property on the FS DB Planned GanttChart AX applet.
   • If the value is TRUE, the check is enabled, and the workflow proceeds to Step 3.
   • If the value is not set, the workflow skips to Step 4.
   • If the value is FALSE, the check is disabled, and the workflow skips to Step 5.
3. Enforce Earliest\Latest Start Violation: This step enforces the check for start and end time restrictions.
   • If the current time is earlier than the earliest start time for the selected activity, or if the current time is later than the latest start time for the selected activity, the workflow stops, preventing the assignment of the activity.
   • If the current time falls within the allowed start time range for the selected activity, the workflow proceeds to Step 5.
4. Check Earliest Latest Violation: This step checks whether the current user has enabled or disabled a check for start and end time restrictions. Specifically, this step checks the value of the Enable Earliest Latest Start Violation user preference on the Dispatch Board User Preference applet.
   • If the value of the user preference is TRUE, the workflow enforces the check for start and end time restrictions.
     • If the current time is earlier than the earliest start time for the selected activity, or if the current time is later than the latest start time for the selected activity, the workflow stops, preventing the assignment of the activity.
     • If the current time falls within the allowed start time range for the selected activity, the workflow proceeds to Step 5.
   • If the value of the user preference is FALSE, the workflow proceeds to Step 5 without checking whether the current time meets the specified start time restrictions.
5. Assign Activity: This step assigns the selected activity to the employee chosen by the user of the Dispatch Board.
6. Load into ABS: This step checks whether or not to use the Appointment Booking Engine (ABS) to schedule the activity.
   • If the system is set to use ABS, the workflow proceeds to Step 7.
   • If the system is not set to use ABS, the workflow skips to Step 8.
7. Load Activity: This step uses the Appointment Booking Engine (ABS) to schedule the activity.
8. Store and Forward: This step calls the SAF Activity workflow to use Store-and-Forward Messaging to dispatch the activity to the assigned employee.