Configuring Monitor Columns

Specifying ` false ` means no renderer is used. With ` true , the monitor component configuration (`Monitor_CustomRenderer) first searches for a renderer with a matching name. Matching is performed via Renderername = Dataindex der Spalte (e.g., ` PROCESSID ` = ` PROCESSID`). The purpose is to display different renderers for different values in the same column. If no renderer with a matching name is found, the defaultRenderer is used.

If you specify the renderer’s name as a string, a search is performed in column_customerRenderer for a renderer with the specified name. .Example: "customRenderer": "TEST-RENDERER" expects an entry "TEST-RENDERER" in column_customRenderer.

To use custom renderer functions, the syntax MODUL!_!FUNKTION must be used during configuration. This specification is converted to the form MODUL.Module.FUNKTION(). This function is evaluated, and the renderer function is expected as the return value. To use a custom function, it must be loaded when the monitor is called. This can be done, for example, by including a custom BPC module or via the configuration "view_additionalFiles" (see Core Services Settings).

If no renderer is defined, the system checks whether the respective column has a ` dataIndex STATUS . If so, the ` `defaultRenderer ` from the object is used. Additional column configuration parameters can be found directly in the ExtJS documentation.

If the formatter attribute in the column configuration is set to "translate", the values in this column will be translated, provided a corresponding translation is available.

If, for example, the formatter attribute in the column configuration is set to "date(Y-m-d)", the values of this column are displayed in the monitor as dates in the specified format.

If, for example, the attribute formatter is set to "round(2)" in the column configuration, the values in this column are rounded to two decimal places.

If, for example, the attribute formatter is set to "lowercase" in the column configuration, the values in this column are displayed in lowercase. This configuration also works similarly with uppercase.

For more information on formatting in monitor columns, see the ExtJS documentation.

The templatecolumn allows you to modify the column’s value in the frontend. For example, you can shorten it, convert it, or enrich it with values from other columns. This can be used, for example, to create a hyperlink column. To create a column with a hyperlink, you can define the xtype templatecolumn and the template tpl in the column’s ColumnConfig. Placeholders enclosed in curly braces can be used to access all data (columns) of the current record (the current row) via their dataIndex. If functions are to be applied to the value, square brackets must also be inserted within the curly braces. In this case, values. must be prepended to dataIndizes.

In this example, a column with the dataIndex "JIRA" is created, which contains a Jira link in OpenSearch. In BPC, the column is populated with a hyperlink that opens in a new window (target="_blank"). Its href is the value of the column itself: {JIRA}. The text of the link is truncated to the substring after the last slash using the JavaScript function values.JIRA.substr(values.JIRA.lastIndexOf('/') + 1). This is achieved in the template via {[values.JIRA.substr(values.JIRA.lastIndexOf('/') + 1)]}.

With this column type, the system attempts to interpret the column’s value as a date and display it in a formatted manner. The date format can be controlled using the format attribute. The syntax for the format can be found in the ExtJS documentation. If no format is specified for the column, the date format of the monitor instance is used.

If action columns are configured in a monitor that can be executed via the toolbar or the context menu, it is possible to create an action button for each row by adding this column. Multiple action columns, as well as multiple action entries within a single column, are grouped into a dropdown menu. The number of actions is displayed on the button. If only one action is available, it can be started directly by clicking the button. The column can accept the additional parameter ` showIconOnly , which accepts ` `true ` or ` false ` as values. This controls whether the button displays the full text per column or only the icon and the number of available actions. The default value is ` false`.

This column type can be used to directly provide a download button for columns that contain a file. To do this, the JSON setting ` fileConfig ` must be configured in the column field with the fields ` columnFileName ` and ` columnContentType `. This setting defines the name of the column, the filename, or the content type.

Optionally, in fileConfig, the setting ` dataSource ` can be used to specify that files always come from a specific source. Possible sources include file storage, OpenSearch, or a backend Connection (e.g., INUBIT).

The following options are available: FileStorage, OpenSearch, BackendConnection, and auto. In the case of auto (default), the system attempts to determine the source based on the contents of the file column. If files are to be downloaded via an HTTP proxy connection, the monitor setting httpProxy_referenceEndpoint must also be configured. This configures the HTTP proxy connection, including the download endpoint.

The jsonColumn is used to display structured JSON data in the monitor. It is specifically designed for OpenSearch object and flat_object fields that are stored in the database as true JSON structures (rather than serialized JSON strings).

The column offers the following display options:

It is possible to define a column for boolean values that displays a checkbox instead of the value. The values for "true" are:

To use a corresponding filter for the column, type must be set to 'check' within filter.

To jump from the monitor to another module (e.g., another monitor), an additional column with the xtype bpcModuleJumpColumn must be inserted in the column_config. In this column, the ID of the target module is entered under targetModule. The column is then displayed with an icon in each row of the monitor. Clicking the icon executes the jump.

It is also possible to trigger the jump to the target module via the context menu. In the context menu, the target module can be opened in three different modes:

If sourceColumn and targetColumn are specified, the current value from the sourceColumn is set as a filter on the targetColumn column in the target monitor when jumping.

If a CustomRenderer has been defined for a column, it is also applied to the suggestion list in the filter field.

First, the rendered value is displayed, followed by the source value in parentheses, and finally—if known—the number of records with that value. If you do not want the source value to be displayed, you can hide it by specifying ` "hideRawValue": true ` in the filter configuration.

This filter allows you to enter any text for filtering.

The dynamicList filter allows the user to select filter values from an automatically generated list. The list is compiled from all values for this column available in the monitor. If this list of results is incomplete, a warning is displayed indicating the number of values not shown. If all values are to be displayed, the filter can either be set to remote or the maxQuerySize Parameter can be increased.

This filter provides a selection component for absolute and relative time periods. The quick selection of rolling time periods can be configured using the configuration parameter dateRange_favorites. The component can be customized as needed using the fieldConfig on the columns.

This filter allows you to filter using numeric values. The default operator can be defined in ColumnConfig. If none is defined, = is the default operator. You can also set the operator (>, <, =, ⇐, >=) via the column menu.

The JSON filter enables filtering within structured JSON data fields. It allows the user to define and combine multiple filter criteria (key-value pairs) for a single column simultaneously.