Guide Section: Processing Events and Performing Actions | EASAP Tree: Event Processing Branch

CUSTOM ACTION is designed to execute custom written Java code placed within user’s EASA Client installations.

The specific code that is accessed is determined by the selection of the code’s fully qualified class name as the value of the Class: parameter. A few examples of possible actions performed a CUSTOM ACTION are as follows:

• Open a custom form, window or other GUI component
• Execute other software or system commands on the client computer
• Set values of scalar or list object
• Play a sound

An important detail about using existing CUSTOM ACTION's is that they may supply either SCALAR or LIST data to an EASAP by way of existing SCALAR DOR VALUE's and LIST DOR VALUE's. Therefore, you will need to know the data storage requirements of the custom code that you have selected and create the necessary SCALAR DOR VALUE's and LIST DOR VALUE's objects. Custom code creators within your organization will need to communicate these requirements to all authors who may need to make use of their custom objects within their EASAPs. For details on writing custom code for EASA, see Creating Custom Code using the EASA API.

Note: As with all custom objects, new parameters can appear for a CUSTOM ACTION once its Class: parameter has been selected. If coded properly, you can find out more about these new parameters by clicking on the parameter name and reviewing the Parameter Information displayed below the Parameter table.

CUSTOM ACTION
Essential Parameters
Class:	Fully qualified class name of the custom code
Optional Parameters:
Do if:	Logical expression, if TRUE then action performed, if FALSE then action NOT performed.