Introduction

Oracle Health Insurance applications operate on business logic that implements business rules. Most rules come out of the box with standard options and menus. When the business rules are insufficient, you can create custom logic using Dynamic logic.

Dynamic logic is an entity in Oracle Health Insurance that stores a script. You can write the script using Groovy.

Oracle Health Insurance uses Java 21 and Groovy 5.0.7.

Each dynamic logic has a type and a signature attribute that define input variables and return values. A signature defines the use of the logic for a specific rule. The signature protects dynamic logic from breaking during application upgrades.

A user must test the logic, just like any other configuration. You can use integrated development environments (IDEs) like Eclipse with a code repository like Git. The application also provides a built-in feature that allows to test a unit of dynamic logic through an API. See the Unit Testing chapter in the Developer Guide for more details.

There are simple and complex operations. Simple ones include displaying something on the user interface. Complex operations include querying a database or using loops with large numbers of objects. Such complex operations take a long time to perform and can affect performance. You must avoid adding complex operations to your logic. To assess the impact of the logic on application performance and stability, you can run a performance test. The timing.dynamicLogic logger is a logger that logs the execution time of every logic. You can use the logger in a test environment to find out the impact. See the Dynamic Logic Testing article in the Applications chapter of the System Administration Guide for more information.