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. Where the business rules are not sufficient, you may create custom logic using Dynamic logic.

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

NOTE

Oracle Health Insurance uses Java 11 and Groovy 3.0.19.

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

A user must test a 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 to test a unit of dynamic logic through an API. Read the Unit Testing chapter in the Developer Guide for more details.

There are operations that are simple and others that are complex. Simple ones include displaying something on the user interface. Complex operations include querying database or using loops with large numbers or objects. Such complex operations take a long time to perform and can influence 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 execution time of every logic. You can use the logger in a test environment to find out the impact. Read Dynamic Logic Testing article in the Applications chapter of the System Administration Guide for more information.