OMD Go
OMD Go is an application used by dispatchers and team leaders. it contains several perspectives:
- Trip Perspective
- Agenda Perspective
- Timeline Perspective
- Map Perspective
- Data Grid Perspective
- Capacity Perspective
- Control Perspective
- Call Intake Perspective
- Group Perspective
- KPI Perspective
- Operational Dashboard Perspective
- Profile Perspective
- Setup Manager Perspective
- User Permissions Perspective
Vertical Timeline
When the preference showFixedTimelineTick is defined the vertical timeline that shows the current time is permanently on.
| showFixedTimelineTick | ||
|---|---|---|
| Type | Default Value | Example |
| String | false | showFixedTimelineTick |
Stop List Template
When the preference StopListTemplate is defined it contains the reference to the template used to render the stop layout in the stop list.
| StopListTemplate | ||
|---|---|---|
| Type | Default Value | Example |
| String | stopListTemplate |
Stop List Template Mini
When the stop list is stretched it is possible to define another template different from StopListTemplate. The preference StopListTemplateMini contains the reference to the template used to render the minified stop layout in the stop list. If not defined the StopListTemplate or the standard layout will be applied.
| StopListTemplateMini | ||
|---|---|---|
| Type | Default Value | Example |
| String | stopListTemplateMini |
Task Tooltip Template Name
The preference TaskTooltipTemplateName contains the name of the template that is used to overwrite the standard tooltip when hovering over stops in the timeline and in the map.
| TaskTooltipTemplateName | ||
|---|---|---|
| Type | Default Value | Example |
| String | taskTooltipTemplate |
Attachment Entry Template
The preference AttachmentEntryTemplate contains the name of the template that is used to overwrite the standard attachment entry layout in the attachment list.
| AttachmentEntryTemplate | ||
|---|---|---|
| Type | Default Value | Example |
| String | attachmentEntryTemplate |
Avoid Resource Color
Indicates whether we want to avoid using colors to identify resources. When the preference
AvoidResourceColor is set to true all the resources will have the same transparent background in the drawer, their color will be set to black in timeline and map.
| AvoidResourceColor | ||
|---|---|---|
| Type | Default Value | Example |
| Boolean | false | true |
Max Resource Preselect
The preference MaxResourcePreselect determines the maximum number of resources that are pre-selected when reopening OMD Go. The pre-selection is determined by the resources that were selected during the last use of OMD Go.
| MaxResourcePreselect | ||
|---|---|---|
| Type | Default Value | Example |
| Integer | 10 | 15 |
Street View Control
The preference StreetViewControl indicates whether the Google Maps control in the map perspective should contain the Street View functionality.
| StreetViewControl | ||
|---|---|---|
| Type | Default Value | Example |
| Boolean | false | true |
HTML Date Time Format
The preference HTMLDateTimeFormat defines the format used for any datetime values in the application.
| HTMLDateTimeFormat | ||
|---|---|---|
| Type | Default Value | Example |
| String | ddd, d MMM yyyy HH:mm |
dd MM yyyy HH:mm:ss |
HTML Date Format
The preference HTMLDateFormat defines the format used for any date values in the application.
| HTMLDateFormat | ||
|---|---|---|
| Type | Default Value | Example |
| String | ddd, d MMM yyyy |
dd MM yyyy |
HTML Time Format
The preference HTMLTimeFormat defines the format used for any time values in the application.
| HTMLTimeFormat | ||
|---|---|---|
| Type | Default Value | Example |
| String | HH:mm |
HH:mm:ss |
Email Subject Template
The preference EmailSubjectTemplate contains the name of the template used for email subject lines.
The template does not depend on the type or process flow of the task.
| EmailSubjectTemplate | ||
|---|---|---|
| Type | Default Value | Example |
| String | emailSubjectTemplateName |
Control Attributes
The preference ControlAttributes contains a comma separated list of attributes representing the column names of the control table.
| ControlAttributes | ||
|---|---|---|
| Type | Default Value | Example |
| String | "Order", "External Id", "Employee", "Order number", "Customer", "Article number", "Description", "Price", "Quantity", "Total" |
Import Row Limit
The preference importRowLimit limits the number of rows a user can import with the Import Wizard.
| importRowLimit | ||
|---|---|---|
| Type | Default Value | Example |
| Integer | 1000 | 1700 |
Import Selection Schema
The preference importSelectionSchema contains a prefix that is concatenated with the name of the entity we want to retrieve the mapping schema for.
| importSelectionSchemaTask | ||
|---|---|---|
| Type | Default Value | Example |
| String | {} |
{externalId":"taskId","territory":"terr","name":"name","estimatedDuration":"estimatedDuration","postalCode":"code"} |
Grid Row Limit
The preference gridRowLimit limits the number of rows a user can show in a grid. If the value is greater than the default, this limit is added to the list of default row limits.
| gridRowLimits | ||
|---|---|---|
| Type | Default Value | Example |
| Integer | 1000 | 1500 |
Excel Export Limit
The preference ExcelExportLimit limits the number of rows the excel fill will have when exporting from grid.
| ExcelExportLimit | ||
|---|---|---|
| Type | Default Value | Example |
| Integer | 20000 | 1000 |
Task Id Pattern
When using the OMD Call Intake perspective, users can create tasks for existing customers. The number sequence for these
tasks is derived from a stored current value in combination with a customer-specific pattern stored in the preference counter.task.pattern.
The pattern can be defined according to the formatting described here.
| picknpackSortingTemplate | ||
|---|---|---|
| Type | Default Value | Example |
| String | SO-#, SO-#-001 |
Templates
With the preference TaskTooltipTemplateName you can define the name of a template that consists of an html template to define what the user will see when he hovers with the mouse cursor over a task in the timeline or map.
| TaskTooltipTemplateName | ||
|---|---|---|
| Type | Default Value | Example |
| String | TaskToolTipTemplate |
The template has to be stored under Configuration (Admin, Resellers) / Templates. Example of an HTML Template:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text" encoding="UTF-8"/>
<xsl:template match="Data">
<xsl:value-of select="@name" /> - <xsl:value-of select="@accountNumber"/> - <xsl:value-of select="@city"/>
</xsl:template>
</xsl:stylesheet>
Color Coding for Task Types
With OMD Go, it is possible to assign dedicated colors to tasks depending on the task type. These colors are visible in the Gantt chart (as a box shadow), the stop list, and the stop tab, providing users with an additional visual criterion to distinguish between tasks.
To do this, the task type(s) must be created in the menu under Planning/Task Types and assigned a color.
The preference GanttTaskTypeBoxShadow defines where the box shadow of a task should appear — above, below, to the upper right, or to the below right of the task box.
| GanttTaskTypeBoxShadow | ||
|---|---|---|
| Type | Default Value | Example |
| string | down | down |
above only a shadow above the box
below only a shadow below the box
up a shadow to the upper part of the box, i.e. above and to the right
down a shadow to the lower part of the box, i.e. below and to the right
Color suggestions for the task types:
| Color Name | RGBA Value | Preview |
|---|---|---|
| Dark Blue | rgba(36, 54, 114, 1.0) | |
| Medium Blue | rgba(0, 105, 180, 1.0) | |
| Red | rgba(149, 21, 33, 1.0) | |
| Dark Red | rgba(138, 42, 43, 1.0) | |
| Green | rgba(106, 146, 52, 1.0) | |
| Dark Green | rgba(0, 78, 50, 1.0) | |
| Yellow | rgba(225, 209, 0, 1.0) | |
| Dark Yellow | rgba(149, 193, 31, 1.0) | |
| Gray | rgba(107, 121, 131, 1.0) | |
| Medium Gray | rgba(200, 209, 214, 1.0) |
The final value in the RGBA definition (e.g., 1.0) controls the opacity of the shadow. A value of 1.0 means the color is fully opaque, whereas a value like 0.7 means the color is slightly transparent.
E-Mail Communication
OMD Go offers the possibility to communicate with customers and ressources by mail. The right-click menu of a task provides the E-Mail functionality.
A separate screen appears where the customers mail-address (derived from email field of the task header) is set as recipient. The BCC is automatically set with the user's mail address and the address stored in the note category that is selected.
The category drop down shows all note categories that are setup for this configuration.
A note category can be combined with a template that will be used to produce the E-Mail body. The temaplate can contain HTML and CSS Style attributes and has to be stored under Configuration (Admin, Resellers) / Templates.
With the preference AlternativeMail you can define an attribute from the extra data that provides an alternative mail address used for the mail screen in OMD Go. That name must match with a custom Task field for that configuration.
| AlternativeMail | ||
|---|---|---|
| Type | Default Value | Example |
| String | alternativeEmail |
With the flow preference setUserEmailToCC you can define that the user's email address is filled into the CC field instead of BCC, which is the default.
| setUserEmailToCC | ||
|---|---|---|
| Type | Default Value | Example |
| Boolean | false | true |
Template Examples
Appointment confirmation
The template has to be stored under Configuration (Admin, Resellers) / Templates. Example of an HTML Template:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output media-type="text/html" />
<xsl:template match="/Data">
<html>
<body>
<p>Dear customer,</p><br/>
<p>We hereby confirm the following appointment for you:<br/>
<span style="font-weight: bold;"><xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 9, 2)" />.<xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 6, 2)" />.<xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 1, 4)" /></span>
at
<span style="font-weight: bold;"><xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 11,6)" /></span></p>
<br/>
<span style="font-weight: bold;">Order type: <xsl:value-of select="omd.domain.s4.Task/@taskType" /> </span><br/>
<span style="font-weight: bold;">Address: <xsl:value-of select="omd.domain.s4.Task/@name" />, <xsl:value-of select="omd.domain.s4.Task/@street" />, <xsl:value-of select="omd.domain.s4.Task/@city" /></span><br/>
<span style="font-weight: bold;">Your customer number: <xsl:value-of select="omd.domain.s4.Task/@accountNumber" /></span><br/>
<p>If you have any questions about your planned customer service appointment, please contact our telephone support at: 0221 - 123456</p>
<br/>
<p>Best regards</p>
<p>Your smart services team</p><br/>
<p>* This is an automatic email, please do not reply. *</p>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
Appointment proposal
An appointment proposal can be used to send the customer a proposal for a planned task, which the customer can then confirm or reject. Depending on whether the appointment is confirmed or rejected by the customer, the status of the task changes to "Planned - confirmed" or "Planned - rejected". This allows the planner to see immediately whether an appointment has been confirmed or rejected, simplifying and accelerating appointment communication with the customer.
Proper status transitions must be set up in the system to manage the progression through the different status codes (ask your OMD consultant for assistance).
The template has to be stored under Configuration (Admin, Resellers) / Templates. Example of an HTML Template:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output media-type="text/html" />
<xsl:template match="/Data">
<html>
<body>
<p>Dear customer,</p>
<p>We would like to give you the following date for the installation on <span style="font-weight: bold;"><xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 9, 2)" />.<xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 6, 2)" />.<xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 1, 4)" /></span>
at
<span style="font-weight: bold;"><xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 11,6)" /> </span></p>
<span style="font-weight: bold;">Address: <xsl:value-of select="omd.domain.s4.Task/@name" />, <xsl:value-of select="omd.domain.s4.Task/@street" />, <xsl:value-of select="omd.domain.s4.Task/@city" /></span><br/>
<span style="font-weight: bold;">Your customer number: <xsl:value-of select="omd.domain.s4.Task/@accountNumber" /></span><br/><br/>
<span style="font-weight: bold;">Your technicians on site:</span><br/>
<xsl:for-each select="omd.domain.s4.Resource">
<table style="color:#000;background-color:#FFF;border-collapse:collapse;padding-bottom:5px;">
<tr>
<td style="padding:5px;border-left:solid #000;background-color:#f2f2f2;width:150px"><xsl:value-of select="@fullName" /></td>
<td style="padding:5px;border-left:solid #000;background-color:#f2f2f2;width:200px"><xsl:value-of select="@email" /></td>
<td style="padding:5px;border-left:solid #000;background-color:#f2f2f2"><xsl:value-of select="@phoneNr" /></td>
</tr>
</table>
</xsl:for-each>
<p>Please note that the planned technicians may change at short notice (e.g. due to illness).</p>
<p>The appointment is reserved for you for a week. Please give us feedback using the response fields provided:</p><br/>
<div id="confirm-wrapper">
<xsl:variable name="taskId" select="omd.domain.s4.Task/@externalId"/>
<table>
<tr>
<td>
<a id='confirm-section' class="confirm-link" status='IP-C' width="100%" href="https://{{website}}/omdservices/rs/v1/customer/task/confirm?configId={{configurationId}}&taskId={{taskId}}&status=IP-C&authentication={{authToken}}" style="border-radius: 0px;color:#ffffff;font-weight:bold;background-color:#20998a;padding:0px;border: 10px solid #20998a;text-decoration:none;cursor:pointer;">CONFIRM</a>
</td>
<td></td>
<td>
<a id='reject-section' class="confirm-link" status='IP-R' width="100%" href="https://{{website}}/omdservices/rs/v1/customer/task/reject?configId={{configurationId}}&taskId={{taskId}}&status=IP-R&authentication={{authToken}}" style="border-radius: 0px;color:#ffffff;font-weight:bold;background-color:#bd021b;padding:0px;border: 10px solid #bd021b;text-decoration:none;cursor:pointer;">REJECT</a>
</td>
</tr>
</table>
</div>
<p/>
<p>Best regards,</p>
<p>Your smart Services Team</p>
<p><i>This is an automatic email, please do not reply. </i></p>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
If the customer presses the confirm or reject button, a message appears in the browser that gives the customer feedback as to whether the confirmation or rejection was successful. The feedback texts can also be stored as templates under Configuration (Admin, Resellers) / Templates:
confirmationSucceeded
Example of a HTML Template:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output media-type="text/html" />
<xsl:template match="/Data">
<html>
<style type="text/css">
.body { color:#FFF;background-color:#000; }
.red_header { color:#F00;padding-top:15px; }
.table1 { color:#000;background-color:#FFF;border-collapse:collapse;padding-bottom:5px; }
.table1 th { padding:5px;border-left:solid #000;font-weight: normal; }
.table1 td { padding:5px;border-left:solid #000;background-color:#CCC; }
</style>
<body>
<p>Dear customer,</p>
<p>we thank you for your feedback. The appointment has been successfully fixed for you.</p>
<p>Beste regards</p>
<p>Your Smart Services Team</p><br/>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
Other Templates are:
confirmationFailed,
confirmationPartlyFailed,
rejectSucceeded,
rejectFailed,
rejectPartlyFailed
Automatical appointment confirmation
When a customer confirms an appointment proposal an automatic E-Mail can be sent out to inform the customer about the successful confirmation of his appointment. This has to be setup with Templates. The templates has to be stored under Configuration (Admin, Resellers) / Templates.
confirmationEmailBody
Example of a HTML Template:
<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"><xsl:output media-type="text/html" /><xsl:template match="/Data">
<html>
<style type="text/css">
.body { color:#FFF;background-color:#000; }
.red_header { color:#F00;padding-top:15px; }
.table1 { color:#000;background-color:#FFF;border-collapse:collapse;padding-bottom:5px; }
.table1 th { padding:5px;border-left:solid #000;font-weight: normal; }
.table1 td { padding:5px;border-left:solid #000;background-color:#CCC; }</style>
<body><p>Dear customer,</p>
<p>Thank you for confirming the appointment: <span style="font-weight: bold;"><xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 9, 2)" />.<xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 6, 2)" />.<xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 1, 4)" /></span>
at<span style="font-weight: bold;"><xsl:value-of select="substring(omd.domain.s4.Task/@scheduled, 11,6)" /></span>.</p>
<br/>
<span style="font-weight: bold;">Address: <xsl:value-of select="omd.domain.s4.Task/@name" />, <xsl:value-of select="omd.domain.s4.Task/@street" />, <xsl:value-of select="omd.domain.s4.Task/@city" /></span><br/><span style="font-weight: bold;">Your Ref: <xsl:value-of select="omd.domain.s4.Task/@accountNumber" /></span><br/> <br/> <p>Best regards</p> <p>Your smart services Team</p><br/>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
confirmationEmailSubject
Example of a HTML Template:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output media-type="text/plain" omit-xml-declaration="yes"/>
<xsl:template match="/Data">
<xsl:text>Thank you for your appointment confirmation</xsl:text>
</xsl:template>
</xsl:stylesheet>