Application properties - Handler definition

Applications module Application node, Pages, Data group Properties Handler tab / Add handler definition

Name

Enter a name for the new handler here.

Action

If you are defining an action handler, select the desired action underneath that will be used to trigger the script. This option is not available for rendering handlers.

Method column

The method is stated here.

Groovy script column

States the path to the referenced Groovy script file.

Add method
Select the desired time at which the script is run here. You can select from the following phases here: Once the desired method is selected, the Groovy file manager will open automatically, where the storage location of the script can be defined. The storage location is found in the portal directory internal/application/store/(Application GUID)/groovy. Open the application GUID that corresponds to the current application. You can find this out by selecting the application node and then pressing F4. This will only work if the expert options have been activated. Within both handler types as well, according to the application structure, there is an order of processing:

RenderingHandler

processBefore:
  1. RenderingHandler of the application
  2. RenderingHandler of the data group
  3. RenderingHandler of the page
processAfter: The reverse order from above.

ActionHandler

processBefore and processBeforeWorkflow:
  1. ActionHandler of the application
  2. ActionHandler of the data group
  3. ActionHandler of the page
processAfter: The reverse order from above.

Remove method
Removes the method currently selected in the list.

Edit script
Opens the Groovy Script Editor.

Select script file
Opens the Groovy file manager.

Cache compiled script classes

The compiled Groovy script classes are stored in the cache.

Error when the script does not exist

Displays a message when the referenced script is not found.

Disable print out

Disables PrintIn messages.