The Null Action does nothing. It is a no-op. The Null Action is useful for providing transaction breaks. By default, Null Actions are not transactional, while all the other core actions and triggers are transactional. By inserting a Null Action in your workflow, you can create a “transaction break”. At transaction breaks, Flux commits the current database transaction. See Transactions for more information about how Flux handles these transactions.
Because it is an implementation of the Action class, the Null Action also inherits all latent properties an action contains. These include the use of postscripts and prescripts and join points. It is considered good practice to use the pre or postscript on a null action to do light processing that doesn’t warrant a full Java Action.
For example, the following prescript on a Null Action will get a boolean result from the last action to run, then add it to a new variable, “lastResult”.
boolean lastResult = flowContext.get("RESULT.result"); lastResult = (lastResult==true?false:true); flowContext.put("lastResult", lastResult)";