Tip: Start typing in the input box for immediate search results.
-
Quick Start
-
- What is Fieldcode?
- Definitions
- What are tickets, projects and workflows?
- How to log in to Fieldcode
- What is the Fieldcode Support Panel?
- What are components?
- What are views?
- Ticket statuses and their meaning
- Ticket colors and their meaning
- Map symbols and their meaning
- Frequently Asked Questions
- Setting up Fieldcode
-
-
Release Notes
-
Short Overview
-
Fieldcode Work Place
-
-
- How to schedule tickets
- How to search for tickets
- How to expert-search for tickets
- How to filter for tickets
- How to grab/ungrab tickets
- How to link & unlink components together
- How to download ticket data as a excel sheet
- How to copy filters/queries for colleagues
- How to email filters/queries to colleagues
- How to assign/unassign tickets to partners
- How to manage spare parts
- How to show tickets on Map
- How to use the Clipboard
- How to open tickets in a new tab
- How to use container tickets
-
-
- How to use the Optimizer in the Timeline
- How to schedule tickets
- How to publish tickets to engineers from the Timeline
- How to lock/unlock tickets
- How to manually reschedule PUDOs
- How to show tickets on Map
- How to manage availabilities
- How to manage subgroups
- How to display an additional time zone
- How to move tickets back to the Ticket Pool
-
-
-
- How to use the Interaction buttons
- How to assign/unassign tickets to partners
- How to manage spare parts
- How to use the Workflow buttons
- How to use the Ticket info button
- How to use the Email button
- How to use the Comment button
- How to schedule tickets
- How to use the Remove Pending button
- How to cancel a ticket
-
Fieldcode Admin Panel
-
- What is the Process menu?
- What is the Workflows menu?
- How to create & edit projects
- Automated Actions in the overview
- How to setup custom Automated Actions
- How to setup pre-configured Automated Actions
- How to create & edit conditions
- How to create & edit indications
- How to set up email templates
- How to create & edit ticket durations
- How to create & edit custom fields
- How to create & edit custom forms
- How to create & edit value sets
- How to create & edit SLA Profiles
- How to move stuck tickets via Ticket Workflow Monitoring
-
- Articles coming soon
-
Fieldcode Mobile App
-
Fieldcode Customer Portal
Map symbols and their meaning
The Map component assists dispatchers by giving them an alternate view of tickets on a world map to better visualize daily tickets and engineer routes.
The Map component gives you the option to check the daily engineer routes for their assigned tickets, allows you to check route segment durations,
allows you to filter for dates, statuses, individual tickets, and engineers and therefore is an alternative way to gain an overview of daily dispatched tickets.
The Map displays tickets, engineers’ locations, engineer routes, segment drive durations, ticket clusters, and other valuable Ticket Details.
The Map colors are similar to the ticket colors on the Timeline.
The Map legend helps you to understand what the different symbols on the Map mean.
Map colors
Symbol | Status | Explanation |
---|---|---|
![]() | NOT ASSIGNED | The ticket is currently free for assignment and scheduling in the Dispatch tab. |
![]() | ASSIGNED | The ticket is assigned to an engineer. An appointment still needs to be scheduled with the customer. |
![]() | SCHEDULED | The ticket has a scheduled appointment with the customer. The ticket isn't visible to the engineer because it needs to be published first. |
![]() | PUBLISHED | The ticket is not yet successfully synchronized with the engineer. |
![]() | SYNCHRONIZED | The ticket is visible in the selected engineer's Mobile App and the service delivery takes place. |
![]() | DELIVERED | The ticket has been reported and the service delivery is done. |
Map legend
Symbol | Explanation |
---|---|
![]() | The starting point or finish point of the engineer (usually the engineer's home or base location). Hovering on the house button will reveal the engineer's address. When the route is selected the symbol will turn orange. |
![]() | The temporary start and end location of an engineer (both are configured as equal locations if you see this symbol). You can configure temporary locations under Users inside Fieldcode Admin Panel. orange |
![]() | The temporary start location. You can configure temporary locations under Users inside Fieldcode Admin Panel. When the route is selected the symbol will turn orange. |
![]() | The temporary end location. You can configure temporary locations under Users inside Fieldcode Admin Panel. When the route is selected the symbol will turn orange. |
![]() | A cluster of more engineer base locations. The number indicates how many engineer base locations are located inside the selected map zoom level. |
![]() | A cluster of more tickets. The number indicates how many tickets are located inside the selected map zoom level. |
![]() | The current live location of the engineer. The live location is updated every five minutes. The location of the technician is not shown exactly on the map, but within a 1-kilometer radius in order to not endanger the technician's privacy. |
![]() | A PUDO location/waypoint on the technician's calculated route. They are sorted alphabetically (eg. A-B-C) and represent a PUDO location on the calculated engineer route. |
![]() | A ticket/waypoint on the technician's calculated route. They are sorted alphabetically (eg. A-B-C-D-E-F-G) and a single letter represents a ticket on the calculated engineer route. Note: If several waypoints are at the same location, the intervening waypoint is not displayed, e.g. for A-B-D-E, waypoint C is at the same location as D. |