Adjusting the Process Monitor Grid

The following sections explain how to configure Process Monitor grids for evaluation and adjust them to your requirements.

You configure the Process Monitor grids in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow.

Proceed as follows

  1. Open the technical workflow BPC_299_PM_Configuration for editing.

  2. Open the variables mapping of the BPC_Assign_hook module.

  3. Select the XSLT Source variable.

  4. In the Source section, click the Edit button next to the Style sheet label to open the XSLT editor.

  5. Adjust the element(s) described in the following sections

  6. Save the changes and publish the BPC_299_PM_Configuration workflow.

Adjusting the Number and Display of Grids

In the default configuration, the included workflows generate five Process Monitor grids distributed among one single grid and two grid groups:

process monitor guide 1341 0

Multiple grids can be combined to form a grid group. A grid group can consist of multiple (single) grids and you can decide for each grid group whether the grids should be displayed cascaded or on tabs:

  • Single grid

    Contains a single Process Monitor grid and a corresponding dashboard.

  • Grid group 1

    In the default configuration, contains two Process Monitor grids (single grids) each displayed on their own tab (sub tab 1 and sub tab 2). For the entire grid group, there is a group dashboard as well as a separate dashboard for each grid on its tab.

  • No tabbed Group

    Also contains two Process Monitor grids, but cascaded rather than on separate tabs.

You can adjust the number and display of grids individually: You can display multiple single grids as well as multiple groups of grids.

Each Process Monitor grid is represented by a Grid element and every grid group is represented by a Group element in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow. The grouping of grids is represented by nesting the grid elements in the group element:

process monitor guide 1342 0

Displaying Single Grids

Single grids are each represented by a Grid element in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow:

process monitor guide 1343 0

Prerequisites

The database schema exists, but no tables have been generated yet.

Refer to Centralized Administration of Logging Database

Proceed as follows

  1. If you want to display multiple single grids, insert multiple Grid elements into the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow like in the above excerpt from the XML configuration:

    1. Open the technical workflow BPC_299_PM_Configuration for editing.

    2. Open the variables mapping of the BPC_Assign_hook module.

    3. Select the XSLT Source variable.

    4. In the Source section, click the Edit button next to the Style sheet label to open the XSLT editor.

    5. Under LoadInformation/ProcessMonitor/DefaultGridOptions, set the value of element tabbing to`false`.

  2. Click OK to save the changes.

  3. Publish the workflow.

  4. Create a new database table:

    Refer to Creating Database Tables

  5. Log on to the portal again to display the changes.

Combining Single Grids to Form Grid Groups

You can combine multiple groups to form grid groups and decide for each group whether the grids should be displayed next to each other on tabs or cascaded.

Prerequisites

The database schema exists, but no tables have been generated yet.

Refer to Centralized Administration of Logging Database

Proceed as follows

  1. In the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow, insert a Group element.

  2. Copy one or more Grid elements with all sub-elements and insert them into the Group element. Alternatively, you can also create new Grid elements in the Group element. The XML structure for a grid group looks like this, for example:

    process monitor guide 1344 1

  3. Ensure that the attribute gridGroupId of all sub-elements in a group (grid or group) corresponds to the id attribute of the Group element according to the following pattern:

    Group(id=abc)
+ Grid(gridGroupId=abc)
+ Grid(gridGroupId=abc)
+ Group(id=xyz; gridGroupId=abc)
+ Grid(gridGroupId=xyz)
+ Grid(gridGroupId=xyz)

    All id attributes of Grid and Group elements in the entire XSLT variable must be unique. The gridGroupId attributes, by contrast, must be present multiple times.

  4. Define whether the grids in a grid group are displayed on tabs or cascaded:

    • Group with tabbing:

      Check whether in LoadInformation/ProcessMonitor/DefaultGridOptions the value of element tabbing is set to true as in the default configuration.

    • Group without tabbing:

      Under LoadInformation/ProcessMonitor/Group/Options insert a tabbing element and set its value to false.

  5. Define a title for the grid group in the title attribute of the Group element and—if tabs were created—tab titles in the title attribute of the Grid element.

    You can combine grid groups even further by nesting them according to the pattern for grouping grids in the XML configuration.

  6. Publish the module.

  7. Create a new database table:

    Refer to Creating Database Tables

  8. Log on to the portal again to display the change.

Adjusting the Height of Process Monitor Grids

You can set the height of the Process Monitor grid by defining the heightOffset as the minimum space between the grid and the bottom of the browser (in pixels). The default value of heightOffset is 200.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Under LoadInformation/ProcessMonitor/Options enter the minimum space to the bottom of the browser as value for the heightOffset element.

  3. Publish the workflow.

  4. Log on to the portal again to display the change.

Adjusting the Height of Child Grids

You can set the height of a child grid in pixels by defining the heightChildGrid element. The default value of heightChildGrid is 150.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Under LoadInformation/ProcessMonitor/Grid/Options, enter the required child grid height as value for the heightOffset element.

    You can use this setting for a grid within a group as well. To do this, navigate to the heightChildGrid element within the options of the respective grid in the group: LoadInformation/ProcessMonitor/ Group/Grid/Options/heightChildGrid.

  3. Publish the workflow.

  4. Log on to the portal again to display the change.

Adjusting the Initial Sorting of Log Entries

You can specify how the log entries are supposed to be sorted initially. In the default configuration, entries are sorted by their time stamps (LoadInformation/ProcessMonitor/DefaultGridOptions/ initialSortField:timestamp).

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Under LoadInformation/ProcessMonitor/DefaultGridOptions enter the name of any XML element that generates a table column as the value for the initialSortField element, e.g. initialSortField:status. Parent log entries are then sorted according to this column in the grid.

  3. To define the sorting direction, enter either asc or desc as the value for the initialSortDirection element.

    If you want to change the initial sort order of child entries, fill the properties initialChildSortField and initialChildSortDirection with the desired values like in steps 2 and 3.

  4. Publish the workflow.

  5. Log off from the portal and then log on again to display the changes.

Controlling the Sorting of Columns

You can define whether the user shall be able to sort the log entries by columns in the Process Monitor grid. To do this, use the sortable attribute for the relevant columns and set it to true (sortable) or to false (not sortable).

By default, some columns are sortable (e.g. Status) while others are not sortable (e.g. remoteFilterTest). If you omit the attribute, the column is sortable.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Navigate to the column definitions of the related grid whose columns you want to configure: LoadInformation/ProcessMonitor/Grid/Data or LoadInformation/ProcessMonitor/Group/Grid/Data.

  3. To control the sorting for a column, define the sortable attribute for the related element and set its value to true (sortable) or to false (not sortable), e.g. LoadInformation/ProcessMonitor/Grid/Data/IconTest/ sortable = false:

    process monitor guide 1347 1

    If you want the column to be sortable, you can omit the definition of the sortable attribute.

  4. Publish the workflow.

  5. Log off from the portal and then log on again to display the changes.

Defining the Column Order in the Process Monitor Grid

The order of the columns in the Process Monitor grid is defined by the order of the corresponding XML elements in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow below the corresponding Grid element in the Data element:

  • Order of XML elements in the stylesheet:

    process monitor guide 1348 0

Users can use drag and drop to change the order of the columns in the detailed display.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Adjust the order of the elements below the Grid element in the `Data `element.

  3. Publish the workflow.

  4. Log off from the portal and then log on again to display the changes.

Showing/Hiding Columns in the Process Monitor Grid

The following applies to the visibility of database columns in the form of grid columns: By default, all database columns configured with XML elements are available as columns in the Process Monitor grid.

In the grid, the columns can then be shown or hidden through checkbox activation:

Refer to Grid Functions

Through the XML configuration, you can show or hide specific columns in a Process Monitor grid (attribute hidden) and make columns available or unavailable in the selection list for columns in the grid (attribute hideable).

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Add attribute hidden=true to the column that you want to be hidden in the grid, for example:

    process monitor guide 1348 1

    The corresponding column is not displayed in the Process Monitor grid. It can always be reactivated through the column selection list in the context menu of the grid columns

  3. To deactivate display of the column in the column selection list in the grid, add the attribute hideable=false to the element, e.g.:

    If you set attribute` hidden=false` in combination with attribute hideable=false, you generate a column that is visible and cannot be hidden even through the column selection list.

  4. Publish the workflow.

  5. Log off from the portal and then log on to display the changes.

Changing the Names of Columns in the Process Monitor Grid

Column names are defined in the title attribute. In the default configuration, the value is defined with a key and its key value from the properties file of the desired language; the value of the useRessourceBundleHeader attribute is true. If you want to change the name of a column, you can do so either by changing the key value in the respective properties file or directly by entering the desired title in the title element.

If you enter a column title for which there is no key (value) in the properties file as the title attribute and useRessourceBundleHeader=true is set, an ErrorString (".undefined" added to the value of the title element, e.g. “ProzessID.undefined”) is displayed in the portal. To enter any given column title as the title attribute, you must set the value for the useRessourceBundleHeader attribute to false.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Select the XML element that generates the column that you want to change, e.g.:

    process monitor guide 1349 2

  3. Select one of the possible ways of changing the column title:

    • Change the column title via the properties file:

      1. Remember the key that defines the value of the title element of the desired column.

      2. Open the Repository tab.

      3. Display the directory ProcessMonitor > ressourceBundle.

      4. Open the file of the desired language, e.g. Application_de_DE.properties, for editing.

      5. Search for the key that defines the value of the title element of the desired column.

      6. Change the key value.

      7. Save your changes.

      8. Close the properties file.

    • Change the column title via the title element`:`

      1. Set the value of element useRessourceBundleHeader to false. The column title is no longer automatically taken from the properties file.

      2. Open the Repository tab.

      3. As the title element, enter the value of your choice to be used as the column title.

      4. Save the changes and publish the workflow.

      5. Log off from the portal and then log on again to display the changes.

    To use multilingualism, the element useRessourceBundleHeader with the value true must exist for each column. Only in this case, the change is adopted in the respective language and the language-specific value displayed as the value of the label in the Process Monitor. Otherwise, the value of title is adopted and not translated.

Refer to Using Multilingualism in the Process Monitor

Changing Status Names and Displays in the Grid

In the Process Monitor grid and on the dashboards, the different statuses of processes and log entries are displayed with different colors, names, and icons.

Status display in the grid

The statuses of the log entries are displayed using colored icons in Process Monitor grids:

process monitor guide 1350 1

Status display on the dashboard

On the dashboard, the different statuses are color-coded:

process monitor guide 1351 0

Default status display

The default configuration provides the following statuses for monitored processes:

  • process monitor guide 1351 1 Error

  • process monitor guide 1351 2 Warning

  • process monitor guide 1351 3 OK

  • process monitor guide 1351 4 Processing

Default status configuration

The corresponding configuration in LoadInformation/ProcessMonitor/DefaultDashboardOptions/ StatusColor looks like this:

process monitor guide 1351 5

You can change the assignment of the statuses to colors, change the names of the statuses, and swap icons. If you wish, you can also display log entries without icons.

You have to adjust the names of the status values if your log entries contain status values other than those that have been predefined, for example, Fehler instead of Error.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. You define the status names, status colors for dashboard and icons as well as the graphics in the elements in the StatusColor element in LoadInformation/ProcessMonitor/DefaultDashboardOptions/StatusColor.

    process monitor guide 1352 1

    The graphic to be loaded is derived from the respective element name, e.g. for the element or status Blue, the Blue.gif file is loaded.

    • Icons:

      All predefined and selectable status icons are found in the repository in directory Process Monitor > Icons >status. Your own graphics must be saved as *.gif files. The file names must conform to the pattern [color].gif.

      Icons are assigned to status values based on the element name.

      To change an icon, define the name of the element such that the element name and file name of the icon are the same.

      Example: The file with the icon is saved under the name down.gif in the repository. The information in the XSLTvariable is:

      process monitor guide 1352 2

    • Status name:

      The value of this element defines the name of the status.

      To change the name of a status, change the value of the corresponding element.

      Example: The element Red, which defines the status with the name Error, is designated as follows in the XSLT variable:

      process monitor guide 1353 1

    • Status color on the dashboard:

      The attribute dashboardColor specifies the color as a hex value for display on the dashboard.

      Change the value of the corresponding dashboardColor attribute.

      You must perform all status changes once globally in LoadInformation/ProcessMonitor/ DefaultDashboardOptions/StatuColor and then once again for the individual grids in LoadInformation/ProcessMonitor/[…]/Grid/Data/Status to ensure that all statuses are available globally as well as for the individual grids.

  3. Save the changes and publish the workflow.

  4. Log off from the portal and then log on again to display the changes.

Displaying Reference Files for Log Entries

For every log entry, it is possible to save a reference file, e.g. a message. In the Process Monitor grid, the download icon indicates that a message can be viewed:

process monitor guide 1353 2

You can display and save the message by clicking the download icon.

Proceed as follows

  1. Activate technical workflow BPC_PM_Show_Reference.

  2. To save and display messages, you must configure the logging in your technical workflows accordingly. You can save messages either in the database or in the file system of the INUBIT Process Engine:

    Refer to

Saving Messages in the Database

In the default configuration, messages are stored in the database.

To write messages to the database, you have to fill the following XML elements with values:

XML element Explanation

Reffile

Column in which the message is saved. Reference data is stored in the BLOB column (Reffile element) of the database

Reference

Column in which the file name is saved. This defines the file name that is loaded from the grid. Required column!

MimeType

Save file type, e.g. plain/text. MimeType defines the file extension that is loaded from the grid.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Expand the XML destination element tree to LoadInformation/ProcessMonitor/[Group/]Grid/Data.

  3. If one of the elements Reffile, Reference or MimeType does not exist:

    1. Create the element.

    2. Delete the log table.

      Refer to Deleting Database Tables

    3. Create a new log tables.

      Refer to Creating Database Tables

  4. Fill the values with these elements according the table above.

  5. Publish the workflow.

With this standard configuration, the data or message is transferred as follows: It is first checked whether in the logEntry structure a value is set for the Reffile element that can be written to the database. If the value of the Reffile element is blank, the variable logRefFile is output, transferred to the INUBIT Process Monitor as the Workflow Connector PM_doFunctionalLogging (in TWF PM_LogDB_Administration) and written to the database. The message is displayed in the grid when the respective icon is clicked.

The data of the Reffile element and the logRefFile variable must be base64-coded.

Compressing Reference Data

You can save the contents of the logRefFile variable to the database in a compressed (zipped) form, thus reducing total data volume of the Process Monitor in the database. To do so, you must set the value of the zipReference variable to true.

Proceed as follows

  1. In the diagram tree, navigate to technical workflow BPC_PM_LogDB_Administration.

  2. Open the variable mapping at the Workflow Connector BPC_PM_doFunctionalLogging.

  3. Set the value of the zipReference variable in the Source area to true.

By doing so, the reference data that is transferred by the logRefFile variable is zipped before being saved to the database.

Opening Messages in a New Window

You can display messages in a new window.

To display messages in a new window, you have to fill the following XML element with a value:

XML element Explanation

Reference

Column in which you have to create the attribute blank=true. This defines the information that the message shall be displayed in a new window that is loaded from the grid. Required column!

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Expand the XML destination element tree to LoadInformation/ProcessMonitor/[Group/]Grid/Data.

  3. If the element Reference does not exist:

    1. Create the element.

    2. Delete the log table.

      Refer to Deleting Database Tables

    3. Create a new log tables.

      Refer to Creating Database Tables

  4. Create the attribute blank for the Reference element and assign the value true to it (see the table above).

  5. Publish the workflow.

When you click the download icon, a new window opens.

Offering Actions for Log Entries

In the INUBIT Process Monitor, you can offer any actions you wish for each parent or child log entry. For example, you can show details for a log entry or start a process again if it has Error as the status.

You can use the following technique for these actions:

Asynchronous Ajax request

The action is triggered in an additional column in the Process Monitor grid using buttons. Clicking a button sends an Ajax request to an HTTP connector and starts the underlying workflow. The call is asynchronous, thus, the function that is triggered by the action button does not interrupt the application. The Process Monitor is still running while the server–by callback–processes the data that have been loaded and returns a reply to the browser. You can define the workflow as you wish.

Refer to Configuring Actions.

Configuring Actions

You can offer for each parent log entry a single action or several actions at the same time.

Offering a Single Action

You configure a single action with an action_ element and the corresponding type attribute set to the value action, respectively.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Below the Data element in a Grid element, generate a new element for an action button and name it, in this case action_test, for example.

  3. Create action for parent log entry:

    Add a type attribute with the value action, here for example:

    process monitor guide 1356 1

    The values from all fields of the parent record are passed to the workflow with their respective column name, e.g. action_test, action_test2, Status, ProcessID.

  4. To configure the desired actions for the action button, open the workflow BPC_PM_LogMonitor_Action_AJAX for editing.

  5. Replace the Empty module with modules that execute the desired action. Here you can configure your desired reactions to a single action or multiple actions (two branches).

  6. Publish and activate the workflow BPC_PM_LogMonitor_Action_AJAX.

Offering Several Actions at the Same Time

If you want to offer several actions for a log entry at the same time, you need a separate button for each action and a new column in the log database table for each button.

Actions are displayed in the Action column, in the context menu, and in the detail window being displayed when double- clicking an entry.

process monitor guide 1356 2

To display the new columns in the Process Monitor, you must delete and recreate the database tables and log off from the BPC Portal and then log on again.

All actions are performed by sub-workflows of workflow PM_LogMonitor_Action_AJAX. To address the appropriate sub- workflow, the content of the action_ element must be evaluated. This element signalizes which button was clicked. The value of the element is always the name of the database table in which the clicked button label was saved.

You can configure how multiple action buttons are displayed, refer to Grouping Multiple Actions – MultiAction Button.

Grouping Multiple Actions – MultiAction Button

Multiple actions are displayed in the in the Action column, in the context menu, and in the detail window, refer to Detail Window.

process monitor guide 1357 0

For more on creating actions, refer to Configuring Actions.

Displaying the MultiAction Button for Each Log Entry

For a more convenient display of multiple action buttons for each log entry, all individual action buttons for a log entry can be grouped in a so-called MultiAction button or common action button with dropdown function. This enables you to provide multiple actions for each log entry in a grouped presentation, e.g.:

process monitor guide 1357 1

To do so, you have to make some adjustments for the MultiAction button in the configuration of the grid in the actions element in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow.

Displaying the MultiAction Button in the Toolbar

If you want to provide or select an action for various log entries or processes simultaneously, you can display your own Actions button in the toolbar of the grid:

process monitor guide 1358 1

This enables you to, for example, select multiple processes (MultiSelect) and cancel them collectively using a corresponding Action button.

Prerequisites

In the logEntry structure the same value is used for all actions (action_*).

Manually Changing Parent Log Entries

You can manually change the status of a parent entry displayed in the grid, for instance to set the status from Error to Warning during error analysis:

process monitor guide 1358 2

In a manual status change, a new child entry is automatically created. A comment can be added to it, and the system automatically logs which user made what status change and when.

It is also possible to select multiple processes and change their status collectively (MultiSelect).

Configuring Manual Status Changes in the XSLT variable of the BPC_Assign_hook module

In order to change the status of log entries manually, you must configure this function in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow.

Proceed as follows

  1. To display the Change status button in the grid toolbar, in LoadInformation/ProcessMonitor/Grid/Options/statusEditor set the value of element statusEditable to true.

  2. In a status change, a new child entry is automatically created; you can set the status displayed for this:

    In LoadInformation/ProcessMonitor/Grid/Options/statusEditor, add any value, e.g. Info as the value of the element childLogStatus:

    process monitor guide 1358 3

  3. If appropriate, restrict the statuses that can be selected for a status change:

    1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

    2. In LoadInformation/ProcessMonitor/Grid/Data/Status for all option status elements, add a selectable attribute and set the following values:

      • selectable=true, if you want the status to be available for manual status changes.

      • selectable=false, if you do not want the status to be available for manual status changes.

        If the selectable attribute does not exist, the value true is automatically set and the status is selectable.

  4. Save the changes and publish the workflow.

  5. Log off from the portal and then log on again to display the changes.

Performing Manual Status Changes in the Grid

After performing the required configuration, you can perform manual status changes in the Process Monitor grid.

Prerequisites

Required configuration has been performed in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow.

Refer to Configuring Manual Status Changes in the XSLT variable of the BPC_Assign_hook module.

Proceed as follows

  1. Select one or more processes or log entries by selecting the corresponding lines:

    process monitor guide 1359 0

  2. Click the Change status button.

→ The Edit status dialog opens.

  1. Follow the instructions in the dialog and fill the required fields.

  2. Change the status as desired and select a new status from the list field.

  3. Click OK.

→ A confirmation is displayed.

  1. Click OK. The status of the corresponding parent log entry is changed.

A child log entry is automatically created at the same time. This new child entry records which user changed the status when and any comments entered when the change was made, e.g.:

process monitor guide 1359 1

Displaying Columns with Checkboxes

In the Process Monitor grid, you can display columns with checkboxes.

A checkbox is always displayed as selected, if a value is available in the database. If the database value is Null, the checkbox is not selected.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Add to the XML element Checkbox, through which the database column is configured a type attribute with the value boolean`, e.g.:

    process monitor guide 1360 0

  3. Publish the workflow.

  4. Log off from the portal and then log on again to display the changes.

The depicted configuration ensures that the checkboxes in the respective column of the Process Monitor grid are always selected whenever there is a value in the corresponding database column.

You can modify the name of the column individually, refer to Changing the Names of Columns in the Process Monitor Grid.

Displaying Columns with List Filters

You can offer two types of list filters for columns in the Process Monitor grid: either a pre-defined set of available filter options or a dynamic list filter for configuring filter parameters.

Displaying Columns with pre-defined List Filters

You can configure columns in the grid in a way to offer a pre-defined selection list for filtering the respective column, e.g.:

process monitor guide 1360 1

You define the column types (e.g. type=status or type=listFilter) and the available filter options in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. In a (single) Grid element, navigate to the Data element.

  3. In the Data element, navigate to the respective element that creates the database and grid column for which you want to create and display selection filters. Here, e.g., you navigate to the Status element since the selection list shall be displayed in the Status column.

  4. Add a type attribute with one of the following values to the element, depending on whether you want to display a regular selection filter or a selection filter containing status information that can also have an impact on the display of icons in the grid:

    process monitor guide 1361 0

    • `type=listFilter `to offer a pre-defined selection list of filter options upon calling a filter.

    • `type=status `to offer a pre-defined selection list of filter options with status information that can also have an impact on the display of status icons in the grid.

  5. To define the selection options offered in the portal, add a desired number of Option elements and enter per element a specific value that is used as option label in the Process Monitor grid, here e.g. OK, Error, Warning.

  6. You can overwrite the internal identifiers of the selection filter list values for making them more meaningful. To do this, add the label attribute to the Option elements whose value identifier (e.g. In_Progress) you want to overwrite, and set its value to the preferred In Progress identifier.

    process monitor guide 1362 0

  7. Publish the workflow.

  8. Log off from the portal and then log on again to display the changes.

Displaying Icons in Pre-Defined List Filters

For the status column, also icons are defined. You can determine by configuration, if the icons are displayed in the filter list in addition to the filter values.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. To display the icons in the filter list in addition to the filter values, set the value of the element listFilterIcons `in the XML element `DefaultGridOptions to true (default):

    process monitor guide 1362 1

  3. Publish the workflow.

  4. Log off from the portal and then log on again to display the changes.

Displaying Columns with Dynamic List Filters

You can configure columns in a way to offer to grid users a dynamic selection list for defining parameters when filtering the respective column. Users have then an input field at their disposal that, after entering at least 3 letters or characters, automatically updates the filter parameter on the basis of all values contained in the respective column, thus dynamically and further restricting the filter selection, e.g.:

process monitor guide 1363 1

You define the column type type=dynamicList in the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. In a (single) Grid element, navigate to the Data element.

  3. In the Data element, navigate to the respective element that creates the database and grid column for which you want to create and display a dynamic selection filter. Here, e.g., you navigate to the Text element since the selection list shall be displayed in the Description column.

  4. To the Text element, add a type attribute with the value dynamicList:

    process monitor guide 1363 2

    The dynamic selection filter is NOT case-sensitive. Parts of character strings are also searched without you specifying wildcards.

  5. Publish the workflow.

  6. Log off from the portal and then log on again to display the changes.

Dynamically Filtering Data in Other Process Monitors

By clicking in a Process Monitor grid, you can filter the data in another Process Monitor grid. With it, you can display, for example, more detailed information for a selected log entry in the second Process Monitor grid.

Filtering is triggered with the process monitor guide 1363 3 button in the Filter column: In the XML configuration, you must define the parameters for the column to be filtered, the target grid to be filtered and the name of the column to be filtered.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Add the following attributes to element remoteFilterTest in LoadInformation/ProcessMonitor/[…]/Grid/Data:

    process monitor guide 1364 0

    • title: Any name for the display in the monitor

    • type: You use remoteFilter to define the functionality of the column.

    • icon: search.gif; graphic file displayed as a button. The graphic must be in the repository in directory ProcessMonitor > Icons.

    • localField: The of the column whose values are supposed to be used for filtering. Refers to the grid in which filtering is triggered.

    • targetGrid: ID of the Process Monitor grid to be filtered. You take this ID from the id attribute of the grid to be referenced, e.g.:

      process monitor guide 1364 1

    • targetField: Name of the column whose values are supposed to be filtered.

  3. Save and publish the changed modules and workflows.

Changing the Date Display in the Process Monitor Grid

For date columns with type date, you can change the display of the date.

Proceed as follows

  1. Open the XSLT variable of the BPC_Assign_hook module in the BPC_299_PM_Configuration workflow for editing.

  2. Insert the attributes format and db_format to the column element:

    • db_format: Date format in the database. Example: Y-m-d H:i:s.u

    • format: Date format for the display. The formatting string must be valid as the format parameter of the Ext JS function Ext.util.Format.dateRenderer. Example: d.m.Y H:i:s

      process monitor guide 1364 2

  3. Save the changes and publish the workflow.

  4. Log off from the portal and then log on again to display the changes.

Press Esc to exit full screen
Modal image placeholder
Press Esc to exit full screen