Execution

Synchronous or Asynchronous

The associated action can be synchronous or asynchronous, as determined by the type property, pentaho.action.Base.isSync. The execution of a synchronous action is completed synchronously. while that of an asynchronous action only completes asynchronously, due to its asynchronous "do" phase.

The execute method handles the execution of both types of actions. When the associated action is asynchronous, or it is not know if it is synchronous or asynchronous, after calling execute, obtain the value of the promise property and wait for its resolution.

Execution model

The following is a detailed description of the action execution model:

1. When an action execution is constructed, it is in the unstarted state.

   The action's label and description properties, and any other property which defines what it ultimately does, can still be freely modified.

   In this state, the execution cannot be settled by marking it done or rejected.

2. When the execute method is called, the execution enters the init phase:

   • the state is set to init;
   • the _onPhaseInit method is called.

   The action's label and description properties, and any other property which defines what it ultimately does, can be freely modified at this stage.

   The execution can be settled by marking it rejected in which case it transits to the finally phase.

   Otherwise, if the associated action is not valid, the execution is automatically rejected with the first reported validation error.

   Otherwise, the execution automatically transits to the will phase.

3. In the will phase, what the associated action will do is already determined and cannot change anymore:

   • the state is set to will;
   • the associated action is frozen, using Object.freeze, and should not be modified anymore (e.g. by modifying nested objects); trying to modify direct properties of the action will throw a TypeError;
   • the _onPhaseWill method is called.

   From this point on, an execution can be canceled based on what exactly the associated action will do.

   The execution can be settled by marking it rejected, in which case it transits to the finally phase.

   Otherwise, the execution automatically transits to the do phase.

4. In the do phase, the execution, proper, is carried out:

   • the state is set to do;
   • the _onPhaseDo method is called.
   • if after calling _onPhaseDo, the execution is not yet done or rejected, the _doDefault method is called, allowing the action execution class to clearly handle a default behaviour.

   The execution can be settled by marking it rejected or, alternatively, done.

   In either case, the execution transits to the finally phase.

5. In the beginning of the finally phase, the execution is considered settled, with or without success.

   If this phase was entered due to a rejection, the execution is in one of the states canceled or failed, depending on the type of rejection reason, isRejected is true, and an error may be available.

   Otherwise, the execution was successful and it is in the did state. Property isDone now returns true and a result may be available.

   The _onPhaseFinally method is called.

   The finished state bit is set to on. Property isFinished now returns true.

AMD Module

require(["pentaho/action/Execution"], function(Execution) { /* code goes here */ });

Extends

• pentaho.lang.Base

Constructor

Members

Methods

Constructor Details

Members Details

Methods Details