Repository Trigger Properties in EPIM Database - EnterWorks - EnterWorks Process Exchange (EPX) - Precisely EnterWorks - 10.5

EnterWorks Classic Administration Guide

Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks > EnterWorks
Precisely EnterWorks > EnterWorks Process Exchange (EPX)
Precisely EnterWorks
Version
10.5
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks Classic Administration Guide
Topic type
Configuration
Administration
First publish date
2007

To modify a repository’s Trigger properties through the EnterWorks Classic UI:

  1. Log into EnterWorks Classic as a user with Administrative privileges.

  1. In the Feature bar, open the Content Feature, select the desired repository, select Edit, and select Trigger Properties.

  2. The Trigger Properties editor will appear.

A screenshot of a cell phone Description automatically generated

  1. Edit the settings as desired:

  • Trigger Enabled:

    • Check this checkbox to enable the trigger.

    • Uncheck this box to disable the trigger. After a trigger has been disabled and the Trigger Properties are saved, all settings in the database regarding this Trigger will be cleared.

  • External Handler Class Name: The java class name. The class must be accessible from the EnableServer Tomcat or EnableServer JBoss services.

    • To be accessible for the EnableServer Tomcat service, the class must be a JAR file and be placed in the folder:

<drive>:\Enterworks\EnableServer\tomcat\webapps\webcm\WEB-INF\lib

  • To be accessible for EnableServer JBoss service, the class must be injected into the epimServer.ear file. Execute the following for each EnableServer JBoss service:

<install_drive>:\Enterworks\bin\DeployServicesJar.bat

  • External Handler PassIn DBSession Indicator: If this is set, the database session is passed to the trigger’s doWork() method as an argument. This session provides access to the EPIM database without having to open another connection.

  • External Handler Sync: This is the event synchronous/asynchronous indicator:

    • If it is set to true, the event is a synchronous event, which means that if a user saves a record in the UI, the UI will not refresh until after the trigger has completed processing. Any changes the trigger made to the record being edited will be shown in the editor (if the editor is kept open).

    • Otherwise, it is an asynchronous event, which means that if a user saves a record in the UI, the UI will refresh immediately, potentially before the trigger has completed processing. If the trigger changes the record being edited, those changes will not be reflected in the editor (if the editor is kept open).

  1. Save and exit the Trigger Properties editor.

  2. Clear the data cache and restart EnterWorks services.