Extending transactions

This topic provides information on how to create custom time-triggered transactions.

About extending transactions
You can extend programmatically both to enhance the functionality of your implementation and to integrate with external systems.
About time triggered transactions
A time-triggered transaction, or agent, is a program that performs various individual functions, automatically and at specific time intervals. It is not triggered by conditions, events, or user input.
Using user exits to extend standard transactions
provides the ability to extend or override key business algorithms. This is accomplished through user exits that are invoked when the algorithms are run.
Using event handlers to extend standard transactions
The application raises events at specific moments in processing. It enables you to define an action to be performed when a specific event occurs.
E-mail message event handler
The application provides a standard Send E-mail event handler for sending e-mail messages on various events. For example, when a line is shipped, you can send shipment information. SMTP-based e-mail is supported for these messages. When configured in the Other tab when configuring an Action, the e-mail is sent synchronously. If the mail server is not available, an exception is thrown.
Exception alert event handler
The application supports standard event handlers sending exception alerts to the Alert Console. These exceptions are redirected to a specific user or to an exception queue for a group of users.
Publish event handler
The application enables publishing of data by the event manager to external systems for interoperability. You can configure any event to publish data to other systems. For example, upon the event ON_SUCCESS of the SHIP_CONFIRM transaction, you may want to publish data to an external financial system.
Execute event handler
The Execute event handler tells the event manager to invoke the specified program. The application looks for this program in the PATH. Data is passed to the program as the first command line argument. Like the Publish event handler, the Execute event handler is invoked asynchronously. This is achieved by using a custom API that runs the program in a service.
Java extensions as event handlers
Java™ extensions enable you to implement event handlers as Java classes. With each action, you can associate one Java event handler. The Java class you create must implement the com.yantra.yfs.japi.util.YFSEventHandlerEx interface. This is achieved by using a custom API which actually runs the program in a service.
Oracle stored procedures as event handlers
There are several parameter that are invoked with the stored procedure if you have configured and event handler as am Oracle stored procedure.
HTTP extension as event handlers
If you configure an event handler as an HTTP extension, the application sends data using the post() function to the specified URL.
COM extensions as event handlers
Using COM requires setting up your server and runtime clients.
Event chaining and event handlers
Some event handlers support invocation of APIs. These APIs can retrieve more data pertinent to the event being raised, or they may direct to perform a business computation or transaction. In turn, the transaction can raise other events, thus resulting in event chaining.
About condition builder
Condition builder is used as a part of the service definition framework or in pipeline definitions. This can be used if you want to define dynamic conditions but also use some static set of attributes present in the condition builder.