Texts

Each project has its own cross-reference. When scanning the project, the cross-reference in a client project searches for uses of client-side and server-side texts in the client project (in the design area), e.g. in the LocalisableText property of the controls. The cross-reference of a server project searches for uses of server-side texts in the server project, e.g. in the Text parameter of the alarms. In single projects, the client and server are combined so that there is only one cross-reference that performs both searches.

The cross-reference checks for each use whether the respective text has been defined and, conversely, whether a defined text has been used.

Figure 1: Responsibility of the respective cross-reference for client-server projects and single projects

Legend:

The analysis is performed by the cross-reference of the client project. The starting point of the arrow indicates the source of the definition, the tip of the arrow indicates the use of the definition.

The analysis is performed by the cross-reference of the server project. The starting point of the arrow indicates the source of the definition, the tip of the arrow indicates the use of the definition.

In a single project, there is only one cross-reference. The starting point of the arrow indicates the source of the definition, the tip of the arrow indicates the use of the definition.

After scanning the project, the results are displayed in a table in the Texts view in the Cross-reference node of the respective project.

The table contains the following columns:

Text name

Specifies the full identifier of the text, but without specifying the text type. The text type is specified in the Text typecolumn to enable the results to be sorted by text type.

Text type

Specifies the text type.

No text

A checkbox activated here indicates an incomplete translation. No text is specified in at least one of the languages.

Status

Indicates the status of use: either Correct, Warning or Error.

Status Description

Detailed information on the status.

Status Description	Description of the	Status
Correct	The use of the definition is error-free.	Correct
Defined, but no use found	The text was defined but not used. Important: If the cross reference is not used for a text, it does not mean that the definition is superfluous and can be deleted for the following reasons: The text may have been used in the code. However, in Modern UI and Web UI projects, code files(*.cs, *.vb, *.js) are not analysed by the cross-reference. In Classic UI projects, the cross-reference analyses the code files (*.cs, *.vb), but not all code constructs can be interpreted. If text names are only obtained from a data source at runtime, for example, then these variables cannot be recognised by the cross-reference. Therefore, before you delete a text, check whether it is used in the code.	Warning
Used, but not defined	The text was used but not defined in the project file. Incorrect text output must be expected during the course of the application.	Error

System

Specifies the name of the system module (e.g. variables or alarms) in which the definition is used. If Design is specified as a system, the definition is used in the design area.

Used in

Specifies the type of definition (e.g. alarm) where the text is used in a parameter, or specifies the relative path of the form (Classic UI), view (Modern UI) or page (Web UI) where the text is used.

Source group, source, source detail

Further details on use