Library Applications - Google Workspace

Overview

Google Workspace has become increasingly popular as organizations' go-to productivity and collaboration suite. However, like any other digital productivity application, if their performance is poor, so will employees' experience and, ultimately, their productivity

The Google Workspace library pack contains a suite of pre-configured applications to monitor using Nexthink’s Applications module.

These can be installed from the Nexthink Library to monitor the adoption, speed and stability of Google’s productivity and collaboration suite.\

Find out more about the Applications module:

Google Workspace Applications

The library pack covers Google Workspaces' most common applications, as listed below.

Requirements: Some of the applications in this library pack require an Application Experience license to function.

The following applications use more than three key pages and transactions and require an Application Experience license to function:

  • Google Workspace: Gmail

  • Google Workspace: Jamboard

  • Google Workspace: Meet

  • Google Workspace: Chat

  • Google Workspace: Sites

The following applications use more three or fewer key pages and transactions and do not require an Application Experience license to function:

  • Google Workspace: Docs, Sheets, Slides, Forms

  • Google Workspace: Admin

  • Google Workspace: Drive

  • Google Workspace: Contacts

  • Google Workspace: Groups

  • Google Workspace: Calendar

Key pages

The key pages for each application have been pre-defined to cover the standard pages accessed when using Google Workspace applications. The Screenshots below provide an example of how these key pages are pre-defined.

Screenshots below shows some details of key pages.

Transactions

The main transactions for each application have been pre-defined to cover the standard application usage. The screenshot below provides an example of how these are defined and can be used as a template to create similar transactions if needed.

Below are the examples of how the transactions were defined.

“Save Event (Small Dialog)” transaction

Transaction start is triggered on “Save” button click with automatic option for transaction end.

“Save Event (Full Dialog)” transaction

Transaction start is triggered on “Save” button click with automatic option for transaction end.

Last updated