Customer Requirements

The extension requires the setup of an OAuth2 client for the FSM Account and appropriate access permissions for each company. This needs to be done to enable the installation of the extension.

Account Information

You need to provide the technical names of the account and company in FSM along with the cluster their instance is installed in. This information can be found in the administration panel as shown in the images below:

Company Information

In the above example images, the required information is:

·        Account name: Teamviewer-demo

·        Company: DemoCompany1,

·        Cluster: DE

Note: The extension can support more than one company, please specify all companies that will use it.

User Group

The extension requires only a few permissions to function. It acts as a ‘Dispatcher’ in the sense that it reads ‘ServiceCall’ and ‘Activity’ objects. It then creates an ‘Attachment’ object for the matching ‘ServiceCall’. It will also delete created assets in case of updates.

You can either decide the use of the existing ‘Dispatcher’ role in FSM or you can create a new one to be used by the client. One way to create a suitable group is copying the existing ‘Dispatcher’ group.

With this copy you can then further restrict the access if required, e.g. you can remove Create and Delete permissions for all objects (except for ‘Attachment’ objects).

Client

To technically access the FSM, the extension requires an OAuth2 client setup.

In the FSM Clients configuration, you need to create a new client.

Note:  While saving, make sure to note down the generated client secret. This is required by the TeamViewer Solution Delivery Team to provide the extension instance.

With the access permissions set and the client id and client secret pair TeamViewer can provision the extension for the FSM account. Provide the client id and client secret over a secure communication channel to your TeamViewer contact.

Extension Installation in FSM

Extension link

After the extension instance has been provisioned an Extension Access URL will be provided by TeamViewer that is used to install the extension.

Installation

The extension is installed via the Foundational Services configuration in the Installed overview on the left.

⇒There will be an Extension tile in the FSM Directory for the integration, but the installation will only be supported via custom URL provisioning upon request.

1.      Select Add Extension prompts you for the URL provided by TeamViewer.

Note: Please type in the URL exactly as provided (it may end with a ‘/’ that is required).

2. Review settings and allow data sharing with the extension.

3. Optional: You can put the extension into your sidebar. You can uncheck this if you would like to manually add the extension later.

4. Click on Install.

⇒The extension is available.

Sidebar

If you selected to not install the extension into the sidebar at first, you can do so manually.

1.      Open the Extension Configuration of your sidebar.

- Frontline Cloud Private Frontline Cloud Private Cloud On-Premise

Type of Instance

Shared 

Individual 

Individual 

Individual 

Data Isolation

Data separated in shared database

Data separated in shared database

Data in customer's own data base

Data in customer's own data base

Runs where?

in Azure cloud

in Azure cloud

in customer's cloud environment

on customer's own server

Operated by

TeamViewer

TeamViewer

Customers

Customers

Update Policy

Regularly 

on customer request

individually

individually

2. Click on Add Extension.

3. Select Frontline xAssist.

4. Click on Add. Close the Extension Configuration.

The extension is now installed!

Uninstalling / Removing from Sidebar

You can safely uninstall or remove the extension at any time. While your instance is still valid you can later reinstall or reenable the extension with the same Extension Access URL.