Rebook

When the mobile worker is onSite, the flow-preference allowOnSiteRebook allows to choose from additional Reasons For Disruption (RFD) having the follow-on-type=4. Choosing one of those RFDs leads to rebooking the task, which means, the status of the original task is changed by the transition rebook (usually to a closed state), and a copy of the task is created, with the state defined in the RFD (usually a plannable state). To prepare for using the onSite-Rebook functionality, read the Task Attachment Guide (subType rebook), create one or more of this kind of RFD (with follow-on-type=4), add a closed task state, for onSite task-cancellation, and connect this state from onSite with the transition rebook. To finally enable the feature in OMD Mobile, set the allowOnSiteRebook flow-preference to true.

In addition to rebooking onSite tasks, OMD can create a note and attach it to the new copy of the rebooked task. The note contains the comment entered by the mobile worker when rebooking the original task. The note is only created, if the flow-preference onSiteRebookNoteCategory is defined. Its value may contain the name of the note category and an optional sub-category, separated by a pipe character ("|"). The usual actions related to the note (e.g. sending of mails) apply.

When using Service Objects, OMD Mobile offers two No Service buttons: one on task level, the other on Service Object level. The listed Reasons For Disruption (RFD) differ, depending on the level and if the task was onSite or not.

On Service Object level, for a collection in status onSite, all RFDs with follow-on type 4 are shown. If pressed, the single task of the selected service object is canceled with reference to the selected RFD. Note that The "No Service" button is displayed even though the user might have changed one of the items' MobileUIs.

In case the selected service object happened to be related to the lead task of the collection, OMD Mobile will create a rebook attachment, causing the related task to be copied onto a new task with an identifier postfixed by RB. The service object and it's related items in the attachment list of the task will be moved to the new task which can then subsequently be planned by the planner.

In case the preference createRebookTask is false, OMD will avoid the creation of the rebook task. Instead, the closed attachment of the lead task will be marked with the value rebook in the processFlow field. This will allow the ERP to create a new task with a suitable identifier and send it to OMD as a new unplanned task.