3.6. Actions

You can use actions in these ways:

Actions have access to globals and those variables that are defined for the process and the predefined context variable. This latter is of the type org.drools.runtime.process.ProcessContext and can be used for the following tasks:

Java actions should be valid Java code.

MVEL actions can use this business scripting language to express the action. MVEL accepts any valid Java code but also provides support for nested accesses of parameters (such as, person.name instead of person.getName()), and various other advantages. Thus, MVEL expressions are normally more convenient for the business user. For example, an action that prints out the name of the person in the rule flow's requester variable will: look like this:

// Java dialect
System.out.println( person.getName() );

//  MVEL dialect
System.out.println( person.name );

// Java dialect
System.out.println( person.getName() );

//  MVEL dialect
System.out.println( person.name );