--- title: "Default Service View" slug: "default-service-view" updated: 2025-10-01T08:21:47Z published: 2025-10-01T08:21:47Z canonical: "learn.servitly.com/default-service-view" --- > ## Documentation Index > Fetch the complete documentation index at: https://learn.servitly.com/llms.txt > Use this file to discover all available pages before exploring further. # Default Service View The initial configuration of your DPS already contains a Service View you can use as a starting point. The default service view is composed of the following pages. ## Overview This is the home page of a service user who accesses the DPS. It is designed to provide a glance at the overall status of the install base. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(838).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A58%3A39Z&se=2026-10-16T18%3A58%3A39Z&sr=c&sp=r&sig=ZcCktDQKIHZ7DBRRditQCq6jPha6kI3CA1Wq2vsP5yU%3D) It includes the [Active Alert List](/docs/active-alert-list-widget) widget displaying the presence of active alerts visible by the technician, including these details: - machine ID - customer and location - alert title and short description - duration (the time the alert is active) - takeover [status](/docs/events-filter) related to the event By clicking on a row, the user can access the alert details page, which provides all the information about the event that generated the alert. The overview page also contains the [Map](/docs/map-widget) widget, which provides a map with the geolocated markers of the machines managed by the service. Markers can be highlighted according to the presence of failures and anomalies. ## Customers This page allows technicians to efficiently manage and search for customers they are responsible for. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(839).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A58%3A39Z&se=2026-10-16T18%3A58%3A39Z&sr=c&sp=r&sig=ZcCktDQKIHZ7DBRRditQCq6jPha6kI3CA1Wq2vsP5yU%3D) It includes a [Customer List](/docs/customer-list-widget) of customers visible by the service, including these details: - customer name - [machine count](/docs/data-binding#statistic-data-binding) - presence of active failures ## Machines This page allows technicians to efficiently track, monitor, and search the machines they are responsible for. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(840).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A58%3A39Z&se=2026-10-16T18%3A58%3A39Z&sr=c&sp=r&sig=ZcCktDQKIHZ7DBRRditQCq6jPha6kI3CA1Wq2vsP5yU%3D) It includes a [Thing List](/docs/thing-list-widget) of machines visible by the technician, including these details: - machine ID - customer and location - connection status (offline/online) - operating status (standby, working, error) - presence of active failures - presence of a service contract ## ToDo This page helps technicians efficiently manage their workload by listing pending actions (scheduled maintenance, urgent repairs). ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(843).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A58%3A39Z&se=2026-10-16T18%3A58%3A39Z&sr=c&sp=r&sig=ZcCktDQKIHZ7DBRRditQCq6jPha6kI3CA1Wq2vsP5yU%3D) It includes the [Active Alert List](/v1/docs/active-alert-list-widget) widget displaying all the active alerts the technician must manage, including these details: - alert activation date - severity - alert name - machine ID - customer and location - alert duration By clicking on a row, the technician can access the action details page, which provides all the information about the tasks to perform. ## Data On this page, technicians can download data for the machine they are responsible for. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(844).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A58%3A39Z&se=2026-10-16T18%3A58%3A39Z&sr=c&sp=r&sig=ZcCktDQKIHZ7DBRRditQCq6jPha6kI3CA1Wq2vsP5yU%3D) Through the [Data Export](/v1/docs/data-export-widget) widget, they can select a period, a customer, and a set of machines and metrics to export through a CSV file. ## How search works Depending on the navigated page, the DPS user can interact with a [Search Field](/v1/docs/search-field) to filter the page content, for instance: - search for [customers](/v1/docs/customer-list-widget); - search for [machines](/v1/docs/thing-list-widget) with a specific model; - search for [events](/v1/docs/event-list-widget) with a certain severity and timing; - search for [active alerts](/v1/docs/active-alert-list-widget) or [historical alerts](/v1/docs/historical-alert-list-widget) with a certain severity and timing; - search for [active work sessions](/v1/docs/active-work-session-list-widget) or [historical work sessions](/v1/docs/historical-work-session-list-widget) with a certain severity and timing; - searches for [actions](/v1/docs/action-list-widget); - display aggregated values on the searched things (e.g., [Value](/v1/docs/value-widget#multiple-things-aggregation), [Time Series Chart](/v1/docs/time-series-chart-widget#multiple-things-charting)); Service users can only search for objects limited to their context visibility (e.g., customers, locations, things, events, alerts, work sessions, actions). The search form can be located at the top of the page. In this case, updating an input field updates all the other widgets on the same page that are [bound](/v1/docs/search-field#binding-with-other-widgets) to it. It can be composed of a simple text key input, but it can also include advanced search inputs, allowing the definition of multiple search conditions. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image-1759304540434.png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A58%3A39Z&se=2026-10-16T18%3A58%3A39Z&sr=c&sp=r&sig=ZcCktDQKIHZ7DBRRditQCq6jPha6kI3CA1Wq2vsP5yU%3D) The [Search Field](/v1/docs/search-field) can be placed in a common template (e.g., [Control Bar](/v1/docs/views#control-bar-template)) and reused among different pages. In this case, when navigating another page, the search inputs are preserved. Optionally, the search field can be embedded directly into widgets (e.g., [Thing List](/v1/docs/thing-list-widget)). This is usually done when there is only one widget on the page. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image-1759304749717.png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A58%3A39Z&se=2026-10-16T18%3A58%3A39Z&sr=c&sp=r&sig=ZcCktDQKIHZ7DBRRditQCq6jPha6kI3CA1Wq2vsP5yU%3D)