Labels / Tags

The following guide serves as an introduction to the labels of Pegasus Gateway.

Labels / Tags        1

Introduction        1

Core Labels / Labels        1

Site Labels / Labels        5

Managing Configurations with Labels / Tags        6

Introduction

The labels or tags are used to report the significance of an event code in a managed configuration (note that the word labels and tag are used interchangeably throughout the guide mean the same).

The administration of the labels can be done from the menu: Configuration Manager

There are two types of labels - Core and Site Labels

Core labels cannot be deleted, they are for standard gateway configurations.

Site Labels are labels that gateway administrators can create, edit and delete.

Core Labels

An example of the core islabel, ignon this label is used in all standard configurations to indicate that the vehicle was turned ON.

In configuration management you can see that you can only perform two actions to this label, either edit the description or set the default value.

When you edit the label, the short description is used in the alerts & events throughout the app, so in sections like rawdata & trips.

For example:

Changes to core labels affect any event generation of this label in the past.

If you want to make an action based on this new label, head to the Automation Application and select the condition: Reports any of the following labels

Now you can select the updated label

* Note - there are conditions that select some labels automatically, such as:


Site Labels

A Site label is a label that Gateway administrators can create, edit and delete.

To create a site label go to the Labels section and click on the upper right hand button.

Site labels are completely customizable, however we recommend that site labels are created with a core label first then a period followed by a custom word.  The only restriction is that site labels cannot be more than 10 characters long.

As an example let’s say that our managed configuration turns on a buzzer when the vehicle is speeding, and this buzzer is connected to output 2.

There’s already a core label called “out2on” so the idea is to use this and have a customizable part at the end that represents a buzzer, so we’ll create:

out2on.buz

After creating the label, notice how there’s two options in the menu that says edit and delete.


Manage Configurations with Labels / Labels

The last step is to add these new labels we created to a managed configuration. From the configuration manager we click on Managed configurations 

Select a managed configuration

Next we click on LABELS

Scroll down to the label we want to replace, and click on the edit icon

We select the label we just created and click on UPDATE

Note that in this case since we edited an existing label with a new one, the labels that generated before this change will not show the reflected name change, only labels from now on.

Also keep in mind that if you update a label here it will not update on the automation application, so if you had a trigger that depending on the old label you must update it manually to the new label.

End of Document.