- You can use Groovy rules only for applications of type "Enterprise" (available with Enterprise PBCS or PBCS Plus One licenses), Oracle Strategic Workforce Planning Cloud, or Oracle Sales Planning Cloud.
- Groovy rules are not supported in composite forms.
Groovy business rules allow you to design sophisticated rules that solve use cases that normal business rules can't solve; for example, rules to prevent users from saving data on forms if the data value is above a predefined threshold.
You create Groovy rules in Calculation Manager and execute them from any place that you can execute a calc script rule in a Planning application; for example, on the Rules page, within the context of a form, in the job scheduler, in dashboards, in task lists, and so on.
Groovy rules are also supported in rulesets. You can have a combination of calc script rules and Groovy rules within a ruleset.
You can execute jobs of type rules, rulesets, and templates synchronously from a Groovy rule.
Oracle supports two types of Groovy rules:
Rules that can dynamically generate calc scripts at runtime based on context other than the runtime prompts and return the calc script which is then executed against Essbase.
For example, you could create a rule to calculate expenses for projects only for the duration (start and end dates) of the project.
Another example is a trend-based calculation that restricts the calculation to the accounts available on the form. You could use this calculation for various forms in Revenue, Expense, Balance Sheet, and Cash Flow. This allows for optimization and reuse.
Pure Groovy rules that can, for example, perform data validations and cancel the operation if the data entered violates company policies.