E-mail event listener

E-mail event listeners enable Asset Lifecycle Manager to use an e-mail application to initiate workflow processes. An e-mail event listener monitors a designated e-mail account and initiates the assigned workflow process as soon as an e-mail meeting the specified conditions arrives.

Setting up e-mail event listeners

To set up an e-mail event listener, you need to select the workflow to initiate when the expected e-mail arrives. You also need to specify the e-mail account and the specific data you want the event listener to listen for. The e-mail account information includes the name of your e-mail server, the type of e-mail it supports, the specific mailbox (or folder) where the e-mails will be delivered, and the username and password needed to authenticate to the server. You should be able to get this information from your IT department.

Once you have provided the e-mail settings, you can test the connection to insure the listener can communicate with the specified server.

Next you need to specify the e-mail content with the values you want the listener to listen for. You do this by specifying a flat file, which consists of text that includes the values, separated by a delimiter. This could be a variety of file types, including .TXT, .XML, .RTF, and so on.

You also need to specify an external unique system identifier. You can autogenerate the identifier, or you can select a specific column from the flat file to serve as the external unique system identifier. The external system identifier indicates the application that initiated the workflow and serves as a reference number for the client application. The external unique system identifier is used within all Asset Lifecycle Manager applications to tell the database where to look for new records, what specifically to look for, and what to do with new records. It is also used to locate, identify, and track workflow instances in reports and audit histories.

Finally, you need to provide the required field mappings for the e-mail content. These mappings tell Asset Lifecycle Manager how to use (where to place) the specific values found in the e-mail.

To set up an e-mail event listener
  1. Click the Process tab, and click the Event listeners panel.
  2. Right-click the Event listeners folder, click New folder, and enter a name for the folder.
  3. Right-click the new folder and select New e-mail listener.
  4. Enter a name for the listener.
  5. Double-click the listener you created.
  6. Click the Details tab and select the workflow you want the e-mail listener to initiate.
  7. Click the Settings tab, select the mail server type, and enter the mail server and user information.
  8. Click Open, browse to and select the flat file containing the required values to watch for in the e-mail, then click Open.
  9. Check to see that the values inserted correspond to the expected e-mail content.
  10. Click Test, then click OK if the listener was successful in connecting to the e-mail server. If not, check the server name and authentication information and try again.
  11. Click the Mappings tab, then click the Autogenerate external unique system identifier checkbox or use the drop-down list box to select the external system identifier.
  12. Click Autogenerate field mappings, then click Yes to save the changes to the event listener. If you want to define your own field mappings, skip this step and use the field mapping tool. See Process fields.
  13. Click the Save toolbar icon. 

NOTE: Whenever a new workflow is initiated, the e-mail that triggered the workflow is automatically moved to a folder named Archive to prevent the listener from continually triggering new workflow instances.

To start (or stop) a mail event listener
  1. Double-click the listener you want to start or stop.
  2. Click the Details tab.
  3. Click Start listener (or Stop listener).

You can also use the spin box to indicate the interval (in minutes) at which you want the listener to poll the e-mail account.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.