Manage a Repository's Trigger Properties - Precisely_EnterWorks - EnterWorks - 11.0

If you migrate a repository, its trigger properties will be migrated as well.

Anytime you modify trigger properties you must restart services and clear the data cache for the new property values to take effect.

To modify a repository's trigger properties:

1. Log into EnterWorks Classic as a user with administrative privileges.
2. Open the Trigger Properties editor. In the Feature bar, open Content, open the desired repository folder, select the desired repository, select Edit, and select Trigger Properties.
3. The Trigger Properties editor will appear. Edit the settings as desired:
   • Trigger Enabled: The trigger must be enabled before you can edit the trigger's properties.
     • Check this checkbox to enable the trigger.
     • Uncheck this box to disable the trigger. After a trigger has been disabled and the Trigger Properties is closed, all settings in the database regarding this trigger will be cleared.
   • External Handler Class Name: The Java class name and the full path to the class. For example:

     com.enterworks.services.triggers.MyRepositoryTrigger

     The class must be accessible to EnableServerTomcat and all EnableServerWildflyWorker services.
   • External Handler PassIn DBSession Indicator:
     • True: The database session is passed to the trigger's do Work() method as an argument. This session provides access to the EPIM database without having to open another connection.
     • False: A new connection to the EPIM database will be opened each time the handler is invoked. If the handler is accessing the EPIM database you should not be opening a new connection each time. Update the handler to use the database session passed in to the trigger's do Work() method.
   • External Handler Sync: This is the event synchronous/asynchronous indicator. Set it to True.
     • True:Use this value. It indicates 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).
     • False: Do not use this value. It indicates this 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).
4. Save and exit the Trigger Properties editor.
5. Each trigger class must be compiled and included in .jar a file that must be deployed to the EnterWorks servers in order for the trigger to be available. If the handler's jar file has been modified since it was last injected or the jar file is new to EnterWorks, deploy the jar file.
6. Clear the data cache and restart EnterWorks services.