Oracle BPM supports Groovy 2.1 compiler and runtime (with static compilation enabled) as a scripting language.

Scripting is available in the following contexts:

• Script task

  See How to Implement a Script Task

• Business object methods

  See Working with Business Object Methods

Within a script block, you can create and use types from the Business Catalog, Java 6 SE API Library, and from any JAR files included in the BPM project.

The BPM Code editor provides basic syntax highlighting, error and warnings highlighting, and code completion.

• Basic Syntax Highlighting

  It displays the code in different colors and fonts according to the category of terms. Syntax highlighting also helps developers find mistakes in their code.

• Error and Warnings Highlighting

  It highlights compiling errors and warnings while you are writing the code. It also provides a description of the problem.

• Code Completion

  It predicts a word or phrase that the user wants to type before they finish typing it.

The Code editor supports the following types of code completion:

• Inherited members (extends/implements)

• Instance members (fields/methods)

• Class members (fields/methods)

• Local variables

• Method parameters

• Primitive types

• Class Names (import will be automatically added if not exists)

The editor displays the options ordered by their relevance. If multiple options have the same relevance, the editor orders them alphabetically.

Figure 25-1 shows the Script editor with the implementation of a script task.

Figure 25-1 Script Editor

Description of "Figure 25-1 Script Editor"

The Scripting Catalog contains all the libraries available for you to use in your scripts. These libraries contain components that you can access by instantiating them and invoking their method. These components are stored in modules.

The Scripting Catalog contains the following components:

• The default Groovy libraries

• The default Java libraries

• The business catalog components

• The imported custom libraries

Figure 25-2 Scripting Catalog Window

Description of "Figure 25-2 Scripting Catalog Window"

You can use external Java libraries that contain functions that are useful for your project. This enables you to benefit from the vast amount of libraries that solve different problems and are available for Java developers to use.

You can import these Java libraries and invoke them from the Groovy scripts.

After you import a Java library, it becomes part of the Scripting Catalog for that BPM project and you can use the from the scripts you write.

You can access the value of some of the elements of a BPM project and you can manipulate their values or use them to perform operations.

You can access the following elements of a BPM project from a script:

• project data objects

• process data objects

• business parameters

Project and process data objects are available as variables in the script.

You can use the business objects defined in the business catalog in your scripts. To do this you must first import the business objects.

1. In the Script Editor, click Select Imports.

   The Select Imports dialog box appears.

2. Click the Add button.

   A new row appears in the imports table.

3. Start typing the path to the business object.

   For example: oracle.scripting.catalog.shipping.ShipOrder

   The auto-complete list displays a list of options.

4. Select the business object you want to import from the auto-complete list.
5. Click OK.

   The selected import is now available for you to use it in your code.

The variable predef is available in every script task method context. This variable enables you to access the available predefined variables.

A BPMN script task is an activity that runs a script.

This script is written in Groovy and can access and modify the value of the data objects defined in a BPM project.

This section describes the mapping between the XML schema data types and the type descriptions used in the scripts.