Glossary

Shared UI Elements

The following interfaces are present across the Cloud:

Search/Filter

Non-case-sensitive liveUpdating the results as you type. query with wildcard support:

• * is equivalent to any sequence of characters.
• ? is equivalent to any non-zero-length sequence of characters.
• $ forces suffix matchMatch whose results end with the query string. (trailing match) if appended to the end of the query string.

In HMI interfaces, search only returns matched initial substrings. Thus, query delta will return a tag or page named delta_temp but not temp_delta.

Where the Search or Filter field is associated with a hierarchyAny tree-like structure that contains a root location branching into sublocations such as folders, it provides top-down search only; thus, it will return results from the current level of the hierarchy and its sublevels, but not from higher levels.

Search is available in the following interfaces:

Localization

In a text field, click on to access the localization table for the field, where translations can be entered or erased individually for each language. Text entered/contained in the field itself is also the localization string for the project’s default locale; however, translations in other languages can be provided regardless of its presence or absence.

Once saved, localized version of the field’s content will be shown to HMI users with the matching locale; default localization is displayed if translation in the user’s locale is missing.

In export and import files, localization is rendered as a JSON array where:

• A single key corresponds to a single language; only unique language-keys are allowed.
• Each language-key’s value is another JSON object with a single key, message.
• The value of the message key is the localized version of the string in the target language.

Example:

{
  "en":
    {
      "message": "This is the localized text in English."
    },
  "ru":
    {
      "message":"Это — текст локализации на русском."
    },
  "da":
    {
      "message":"Denne lokaliseret besked er på dansk."
    },
  "de":
    {
      "message":"Das ist ein deutsches Lokalisationsbeispiel."
    }
}

Language codes are as follows:

• en for English
• ru for Russian
• da for Danish
• sv for Swedish
• fr for French
• de for German
• es for Spanish
• ja for Japanese
• pl for Polish

Localizable fields can be found in the following interfaces:

Tag Selector

Tag selection interface for a variety of purposes. Provides two selection methods:

•  Select tag from page opens the list of all pages in their respective directories as arranged under Pages. Select a page and click OK to open page viewer, then select a tag present on the page. To go to a different page, click on its name in the upper right corner to open a dropdown menu of pages. Alternatively, click CANCEL or anywhere outside the page viewer to go back to page selection.

  Only managed tags will appear on the page.

•  Select tag from tree opens the list of all tags in their respective directories as arranged under Tags; filter field atop functions as a search bar.

Tag selector can be invoked from the following interfaces:

View/Edit Mode

View mode shows the current parameter values for the active tab (if the interface is tabbed) but may hide sensitive data such as API or encryption keys. It also shows if the configured entity (a device, a third-party integration, etc.) is enabled (✓) or not (×).

• In some interfaces, edit mode might display more settings as non-configured parameters and empty fields are hidden in view mode.
• Edit mode works simultaneously across all tabs; thus, closing the mode will save or cancel changes in all configurations. Tabs that have unsaved changes are marked with an asterisk

In editable configurations with the Enable(d) option, the checkbox can be unchecked to disable the configured entity. This, however, does not affect any other parameters; any earlier configured but disabled entity can be re-enabled without reconfiguring.

Some tools that do not affect the configuration, e.g., connection tests, can be used in both view mode and edit mode.

View mode and edit mode apply in the following interfaces: