Configuring Other Settings

Objective

After completing this lesson, you will be able to configure Global Features, languages, and cross references.

Global Features

The Global Features page includes a list of options that allow the implementor to enable or disable specific tasks related to payout processing. This option can be found under AdministratorConfigurationGlobal Features.

The Global Features screen

By default, some global features are already enabled. Some key features you can control on this page are:

Customer Match enables the Producer Ownership tab of the Customers portal, which allows the creation of match rules.

Credentialing enables the licensing and credentialing features of APM.

Data Dictionary grants access to information in the data dictionary.

Data Protection and Privacy (DPP) enables the Data Protection and Privacy feature of the system. When enabled, the system performs additional steps to protect and log private data.

Holds allows the system to place a hold on payments based on configured rules.

Enable Global Features

Business Example:

In this exercise, you will use Global Features to configure Agent Performance Management.

Steps

  1. From the Administrator portal, select ConfigureGlobal Features.

  2. Verify the Credentialing feature is enabled.

  3. Verify the Data Dictionary feature is enabled.

  4. Scroll to the Customer Match row and select the checkbox.

  5. Scroll to the Query Builder row and select the checkbox.

  6. Select Save.

Languages in Agent Performance Management

By default, English is the only language in the APM system, but you can configure additional languages, and set any language as the default.

Administrators can add additional languages, and individual users can designate a default on their user profile. Once you have added a language, you can add a translation term to any entity label, such as a code type, field, or form label.

The following image shows the addition of a language translation of the First Name field on the Producer record into German.

The Labels screen of a producer record, showing the addition of the German language with a translation of the First Name field.

Add a Language

Steps

  1. From the Administrator portal, select ConfigurationLanguages.

  2. Select (+).

  3. Enter a new Language ID. This may be the name of the language, such as German or Deutsch.

  4. Select Save.

Add a Language Translation to a Field Label

Steps

  1. Open the form containing the field to translate.

  2. Double-click a field label.

  3. Select Labels.

  4. In the column for the new language, enter the new term.

  5. Select Save.

Event Messaging

Event Messaging enables data to be sent via API to an endpoint when configured events take place, such as a change in an entity occurs or a process, or a task completes or fails. By default, this feature is disabled.

Once Event Messaging is enabled, it is active for Posting tasks and batch entity updates. If you don't want the Event Messaging functionality enabled, you can disable the feature via the corresponding Processing Configuration or Batch Entity Update definition.

To enable Event Messaging:

  1. From the Administrator portal, select Configure → Global Features.
  2. Scroll to the Event Messaging row and select the checkbox.
  3. Select Save.

Once Event Messaging is enabled, events can be managed in the Event Option Detail screen. To disable this feature for a Batch Entity Update, select the Skip Event Messages? checkbox on the Batch Entity Update Detail screen.

Cross References

The Cross Reference functionality is one of its most versatile and leveraged features in Agent Performance Management. Cross references allow you to create custom lookup tables, which consist of key and target fields. Cross reference data can be easily managed by Business Users through the UI, or through the Integration Portal with Excel/CSV upload files.

What is the advantage of cross references? Let’s look at two examples.

You can use cross references to create a mapping table to relate one set of fields to another set of fields. For example, you can populate a field on the transaction with a specific value based on the contents of two other fields.

You can also use cross references to create custom screens that enable you to record and store data that isn't already part of the application. For example, a new workspace is required to store information for each Producer about the clubs, organizations, and charities to which they’re affiliated. This type of information doesn’t have a logical out-of-box workspace, but you can configure a Cross Reference Type that uses the context of Producer to store this data. You can also add the new workspace to a menu so users can access the data.

Cross References are configured in the Cross Reference Types workspace.

In the following image, a Cross Reference Type record has been configured to show a list of all contacts for a given agency. A list of fields to display has been configured.

A Cross Reference Type that will contain a list of agency contacts. The list of fields is highlighted.

On the Cross Reference Values tab, these same fields display the data about the contacts for each agency.

A Cross Reference Type record. The Cross Reference Values tab is selected, and the list of field labels is highlighted.

Summary

  • The Global Features page includes a list of options that allow the implementer to enable or disable specific tasks related to payout processing.
  • Administrators can add additional languages, and individual users can designate a default on their user profile.
  • Cross references allow you to create custom lookup tables, which consist of key and target fields.
  • You can use cross references to create both mapping tables and custom screens.
  • The Event Messaging functionality enables data to be sent via API to an endpoint when configured events take place, such as a change in an entity occurs or a process, or a task completes or fails.