To configure an attached action script

When you leave the text editor and return to the Triggers (datrg1100m000) session, the trigger program is regenerated automatically, if the text was changed.

When you change the Action Template from 'Attached Script' to another setting, the text content is not deleted. So when you switch back to the 'Attached Script'Action Template, the existing text is used.

The first time you run the Configure Action command, for a trigger with Action Template = 'Attached Script', the system generates a default template with the following content:

function extern long process.event(ref long io.event)
| IMPORTANT: do not change the interface (function name, parameter, 
| and return value)
{
DLLUSAGE
Desc            This function processes a trigger event.
Input           io.event: event
Output          return value: 0 (OK) or < 0 (an error value)
                io.event: the event may (but need not) be updated 
                within this function
Precondition:   io.event contains an event that is formatted according 
                to library datrgevent and must be read using that       
                library.
ENDDLLUSAGE


        | < Add implementation here > |


        return(0) | OK
}

Instead of writing an action function from scratch, you can customize a generated script. This is useful if you want to define actions that are not supported by the Triggers (datrg1100m000) session.

You can use a customized program if you want to take another type of action, such as invoking an LN program, an operating system script, or a Java method.

Assume you configured an XML File Action for a trigger. In that case a generated program is available in the Path for Program that is specified for the trigger; the file name is <path>/<trigger>.src.