Event listeners are the integration point between client applications and Process Manager, enabling them to interface with one another to exchange the required data needed to conduct workflow processes. Event listeners enable you to define specific conditions that once met, will automatically initiate the specified workflow. Process Manager can use the following client applications to initiate a workflow process:
The Type tab describes how event listeners are used by Process Manager to initiate workflow processes and to exchange required data. It also includes a brief description of the three types of listeners and lets you specify which type you want to create.
Use the Details tab to name the listener and specify which workflow to start when the event occurs. Once you have finished configuring the event listener's parameters, and you have saved the listener, return to this tab to start the listener. Once an event listener has been started, its listener status is reported in the Last time listened and Next time to listen text boxes.
You can also specify the interval (in minutes) at which you want the listener to poll the database (for database listeners) or the e-mail account (for e-mail listeners).
On this tab, you provide the necessary information, login credentials, queries, etc., to access or retrieve data from the source being listened to. The settings that appear on this tab depend on the type of listener you are defining. Refer to the three event listener types above for specific instructions.
For database and e-mail listeners, you can click Test to insure the login or authentication information you provided were entered correctly and that Process Manager is able to successfully connect to the database or e-mail account you specified.
Each event listener requires an external unique system identifier to be defined, in order to create a traceable link between each workflow instance and the specific event on the external system that triggered it. The external system identifier pinpoints the application that initiated the workflow and serves as a reference number to the client application. The Mappings tab lets you autogenerate this system identifier, or you can specify one yourself.
If you specify a Requester, the requester's name will be included in the workflow's audit history and other reports.
Finally, if you do not want to define your own field mappings (see"Field mapping"), you can click Autogenerate field mappings to have Process Manager automatically generate mappings for every column in the data source you specified on the Settings tab.
Note: A variety of sample event listeners are included with the product and can be imported into Process Designer and then modified for your own use. For information, see "Adding sample content". You can also share event listeners between users on your system. See "Exporting and importing event listeners".