Adding and configuring fields on views

You can add different kinds of fields to views and control how they are displayed.

Displaying a URL launcher field as a button or link

You can configure a URL launcher field to display as a button or link.

About this task

The property that controls how a URL launcher field is displayed is valid in Creation Views and Task Views.

URL launcher fields can be configured as a button or link. Whereas, URL fields always display as links. Display Type is not shown in the property panel for URL fields.

For more information about URL launcher fields, see Using object fields to launch JavaServer Pages and external URLs.

On the JSON tab, display type is defined by setting subDisplayType to button or link. The field's display type must be set to URL. If subDisplayType is not provided, the URL field displays as a link.

Procedure

  1. In the View Designer, click the Design tab.
    The palette is displayed.
  2. Click a URL launcher field.
  3. In the properties panel, set Display Type to Button or Link.

Displaying a number field as a progress bar

You can display a number field as a progress bar. Valid in Grid Views, Creation Views, and Task Views.

About this task

You can configure a number field to display as a progress bar. The field must be an integer or decimal, and it must have a minimum and maximum value that is defined at the field level.

For information about defining color ranges, see Colors for field value ranges.

On the JSON tab, a progress bar is defined by setting subDisplayType to Progress for a number field.

Procedure

  1. In the View Designer, click the Design tab.
    The palette is displayed.
  2. Click the field that you want to display as a progress bar.
  3. In the properties panel, set Display Type to Progress.
  4. Click Done.

Adding a classifier field that makes taxonomy suggestions

You can add classifier fields that make taxonomy suggestions using a natural language processing service.

Before you begin

The natural language processing service must already be configured to make taxonomy suggestions. Find out the classier fields and classifier target fields before you get started. For information, see Natural language processing services.

About this task

Classifier fields that make taxonomy suggestions are valid in Creation Views and Task Views.

The UI supports making taxonomy suggestions and object association suggestions. For information about object association suggestions, see Adding a classifier field that makes object association suggestions.

When a user accesses a Creation View or Task View with a classifier field, an IBM Watson® Insights button appears in place of the classifier field. The button name changes to the classifier field label. Click the button and an IBM Watson Insights panel displays the results.

The classifier field and the classifier input field must both be in the view. The classifier target fields can optionally be included in the view. It is not necessary to configure the Watson statement on the classifier input field (Adding a description improves IBM Watson Suggestions), the IBM Watson Insights button, or the IBM Watson Insights panel. These elements display automatically for classifier fields.

The classifier field label is used as both the button label and the title of the IBM Watson Insights panel. Otherwise, they cannot be customized.

You can add multiple classifier fields to a view.

You cannot add classifier fields that make taxonomy suggestions to Grid Views. However, you can add classifier target fields to Grid Views.

In this example, the text in the Description is used as input to a natural language processing service that makes taxonomy suggestions. The loss event categorization field is configured to be a classifier field.

Figure 1. Example of a Classifier field that makes taxonomy suggestions
When adding a risk, the taxonomy suggestions are displayed in the right panel

On the JSON tab, no properties are needed for taxonomy classifier fields.

Procedure

  1. In the View Designer, click the Design tab.
    The palette is displayed.
  2. Drag the classifier input field either from the palette or the canvas and add it to a section or group.
  3. Drag the classifier field either from the palette or the canvas and add it to a section or group. It is this field that is replaced with an IBM Watson Insights button.

    Although it might make sense to place the two fields near each other, they can be in different groups or sections.

  4. Click Done.

Adding a business entity selector field

A business entity selector field enables users to quickly identify the role a business entity plays.

Before you begin

The business entity selector field must already be configured. For more information, see Defining business entity selector fields.

About this task

Business entity selector fields can be added to Grid Views, Creation Views, and Tasks Views.

Business entity selector fields can be added as key fields in user guidance.

In GRC Workflow, business entity selector fields can be used in task view override fields. They can also be used in conditions and validations. The options are Empty or Not empty.

The following example shows how a business entity selector field is rendered in a Creation View.
Business entity selector

Procedure

  1. In the View Designer, click the Design tab.
    The palette is displayed.
  2. On the canvas, drag a field that is defined as a business entity selector field to the canvas. The field attribute panel opens.
  3. Set Read Only to true or false.
  4. Set Required to true or false.
  5. Add rules (optional). For more information, see Configuring rules.
  6. Click Done.
  7. Publish the view.

Configuring how text fields are displayed

You can configure how text fields are displayed. The fields can display all the text or show some of the text with the more or less option available to show the rest.

About this task

Fields with display types of text area or rich text can be configured to display all text or to be expandable. For Task Views, Grid Views, and Admin Views, the default display option is Expandable with more/less. For Report Views, the default display option is All text visible. This setting is not relevant for Creation Views. In Creation Views, all text is displayed because the fields are always in edit mode.

Procedure

  1. In the View Designer, click the Design tab.
    The palette is displayed.
  2. Click a text area or rich text field.
    For example, you can click Description in the General section.
    The panel where you configure the text field is displayed.
  3. Choose one of the following options for Display:
    • Select All text visible to show all the text in the field.
    • Select Expandable with more/less to make the field expandable.
    The following image is an example of the text display settings for the Description field:
    Example of text display settings for the Description field.

Adding machine learning models to buttons

You can add a machine learning model to generate AI insights for the user, which is displayed as a View AI insights button in a view. The button can be added anywhere in the view and is customizable.

Before you begin

Make sure that you have a custom view to add the model to and that it is the default view. For more information about creating a custom view, see Creating custom views. Also, make sure that you connected a model to OpenPages.
Note: You must enable the All Permissions > SOX > User Interfaces > Show AI Insights permission for users to view insights.

About this task

The View AI insights button is valid in Creation Views and Task Views.

The button can be added for both View definition and Object fields input types.

Procedure

  1. In the View Designer, click the Design tab.
    The palette is displayed.
  2. Drag a View AI insights button element from the palette to a section.View AI insights button in the View Designer palette.
  3. Enter a value for Label. This label is what the user sees in their view.
  4. Select an AI model from the Select AI model integration drop-down list.
  5. If the AI model that you selected is a View definition input type, then select a view that is sent to the model from the Select a view to send to the model drop-down list.
    You can open the view that you selected.
  6. Click Done.

Configuring user and group fields

You can configure user and group fields to specify a Starting Group that is based on the context of its object rather than the user's profile.

About this task

You can specify an override in the field configuration in a view.

Procedure

  1. In the View Designer, click the Design tab.
    The palette is displayed.
  2. Click a user or group field, for example, if you added a field like Owner or Assignees.
  3. Click Edit and select an option to choose the Starting Group Field:
    • None
    • A field in the current object
    • A field in a related object - If there are multiple related objects that meet the criteria, the one that is related through the primary parent hierarchy is used.
    • A field in a Preference object - If there are multiple Preference objects associated to the object, the first Preference object is used.

    The list of fields in the drop-down only contain fields that can have a group value, not only a user value. If there are no such fields, the drop-down is empty.

    If the Starting Group field contains more than one group, all the names from the groups are used.

  4. Click Done.