Administration and serviceability enhancements

New system Title field

The new System Title Field feature provides additional options for administrators to use for referencing a record. Prior to 9.0, administrators were provided with only one option for referencing a record within OpenPages: the Name field (System Fields:Name).

The Name field is displayed in many prominent locations within OpenPages that cannot be configured to display a different field (including the banner at the top of Task Views, relationship tree diagrams, and panels and tabs on dashboards). The Name field must be unique within a folder, which, in turn, results in the field functioning more as an ID field than as the typical way of referencing a record by name. As a workaround to this issue, many clients use another field as the Title of the record, which results in a lack of standardization within and across client environments.

In order to balance preventing disruption for existing clients and a better experience for new customers, we have created a fully optional configuration that is available for each object type, Enable Title Component. This option controls how the reference to an object is displayed. If the Enable Title Component option is set to False (which is the default setting for clients upgrading to 9.0), then you will experience no change in behavior related to the System Name field.

An administrator can access this feature by clicking > Solution Configuration > Object Types. After you select an object, click the Edit button to open a side panel that displays the new Enable Title Component option. When you set the option to True, you are given three options for displaying the Name field: Title only, Title (ID), and ID (Title). This selection dictates how the object is referenced throughout the system and provides the Title component to the end user to populate on records of this object type. The Title component is not required to be unique within a folder and has a 4,000 character limit. In the same side panel, you can also make the Title a required field, which prevents users from saving a record unless the Title field is populated.

When Enable Title Component is set to True, the Name field displays two components: ID and Title. The ID field is populated with any existing values that were provided in the System Name field prior to 9.0. When Enable Title Component is set to False, the ID field is populated with any values populated in the Name field.

The ID component has the same rules that apply to the System Name field (a required field and unique within a folder) and auto-naming settings will apply to the ID component.

When the Title component is populated, the Name field is displayed throughout OpenPages according to the Name Display setting that is set on the Object Type page. The configuration setting also makes the Title component available within the workflow designer, calculations, and in the filters related to that object. If the Title component is not populated on a record, then the value that is provided in the ID component is displayed.

The following example shows the View Designer with the ID and Title components of the Name field. You can set the Title component’s Read-Only and Required settings on the view.

This example shows a Creation View in which the Title component is enabled and auto-naming is in place for the ID component.

Based on the setting that is configured on the KRI object, the Title component displays in prominent locations within the Task View. In the following example, clicking the Name field displays both the ID and Title components when at least one component is editable; otherwise the Name Display setting dictates the display of the Name field. In this example, the Name Display setting on the KRI object is set to Title Only, and so the Title component is displayed in the Task View header and within the relationship tree diagram.

The following example shows the Grid View for KRIs with Title enabled. The Title component displays in the Name column in grid views, based on the setting on the KRI object type. Hovering over the entry displays the ID and Title of the object. With the Title component populated on this object, the ID, Title, and Description are all available for search and filtering within Grid Views.

The following examples show a dashboard with the Name Display setting dictating the display of the Name field for KRI objects.

The Name Display setting provides the ID and Title components within the workflow and calculation engines. If the Enable Title Component setting is set to False, then only the Name field (and not the two ID and Title components) will display (the pre-9.0 to behavior).

The following example shows the workflow designer with the Name Display setting dictating the display of the Name field.

The following example shows a calculation with the Name Display setting dictating the display of the Name field.

The following example shows an email that was produced by a workflow that uses the Title component of the KRI, as established by the Name Display setting on the KRI object.

Migrating users, groups, and roles

The following example shows how you can export groups. When you export a group, the export includes the group hierarchy under the group, including sub-groups, users, user and group profile associations, and the group's administrators.

Updates to the user interface and custom themes (Carbon)

The user interface now uses Carbon 11. The names of the color settings for custom themes are now easier to understand.

If you are upgrading or migrating, you don't need to update your custom themes to use these new color settings.

For more information about the color settings, see https://carbondesignsystem.com/guidelines/color/usage

For more information about Carbon, see https://carbondesignsystem.com/all-about-carbon/what-is-carbon/.

For information about creating custom themes, see Defining custom themes.