Macro Definition

Macros are means to perform configurable actions, such as quickly setting an end date for a record and all underlying details.

A macro definition consists of the following settings:

Table 1. Macros
Field Description

Code

The code of the macro.

Description

The description of the task that the macro performs.

Type

When a macro is started, it invokes one of the following:

  • Dynamic Logic

  • Bulk Update

  • Oracle Insurance Gateway (OIG) Integration

Context

The following are the execution levels of the macro:

  • Group Client

  • Group Account and

  • Group Account Product

  • Registration

Based on the context, the user gets an option to start the macro from UI pages.

List?

The macro definition is for one subject or a list of subjects. A typical use case is sending a list of records as input to an OIG exchange.

Bulk Update Definition

The referenced bulk update definition gets invoked for a Bulk Update (type) macro.

Dynamic Logic

The referenced dynamic logic gets invoked for a Dynamic Logic (type) macro.

Access Restriction

Only a user with the specified access can invoke the macro.

Page Template

The referenced floorplan enables the selection of contextual attributes. This configuration does not apply to bulk update type or list based macros. The macro uses the Object Selection page template.

For Oracle Insurance Gateway Integration, the following additional settings apply:

  • The property ohi.macro.{0}.endpoint must specify the integration end point{0} as the macro code.

  • Credentials must be set for client OIG_INTEGRATION_{macrocode} or INTEGRATION_{macrocode} (depending on the macro type).

For additional information on setting credentials, see credential integration point.

A macro can specify one or more parameters.

The parameter provides a means to supply execution or contextual data for macros of type dynamic logic, Oracle Insurance Gateway Integration, and bulk update (as activity parameter: named value pair). This configuration is intended to assist a user to initiate a macro from the user interface; therefore, it is not mandatory.

For example, a macro to end-date group account products linked to a specific enrollment product can specify a single-value date type parameter endDate and a single-value char type parameter of type enrollmentProduct.

The value of the endDate parameter provides information about the date from when the group account product ended. Similarly, the value of the enrollmentProduct parameter specifies the selection criteria for the group account product.

Table 2. Parameters
Field Description

Usage Name

Name of the parameter. The usage name makes the parameter key.

Display Name

The display name of the parameter.

Data Type

The following are data types:

  1. Char

  2. Number

  3. Date

  4. Boolean

Mandatory?

true or false.

Multi Value?

true or false.

Pick List

The reference to List of Value Floorplan template.

Filter

Applicable only in the context of a pick list. Specifies the filter criteria for a list of values. Supports filter criteria based on context values only for non-list macros.

Users can start the macro from the Oracle Health Insurance user interface (JET) or the Macro Integration Point.

A history record gets created when a user starts a macro. The historical record has the following fields:

Table 3. History Record
Field Description

Macro

The macro to which the history record belongs to.

Request

The macro request JSON.

Response

The macro response JSON.

Subject Id

ID of the context object.

Monitor Id

Task ID, Bulk update activity ID, or Oracle Insurance Gateway exchange ID.