The sharedConfig.properties file used to be the only location of a repository’s Trigger property settings, but now many of them are also stored in the EPIM database and can be accessed through the EnterWorks Classic UI. In order to maintain backward compatibility, if a property is not available in the database, EnterWorks will fall back to reading the property from the sharedConfig.properties file.
Anytime you modify trigger properties, whether they are in the EPIM database or the sharedConfig.properties file you must restart services and clear the data cache for the new property values to take effect.
If you migrate a repository, its Trigger properties will be migrated as well.