Using Database Triggers with Remote Users

Database triggers supporting Workflow Policies are only created on the Siebel server database; they are not created in Siebel Remote or Siebel Replication databases. For this reason, database changes associated with a Workflow Policy will only trigger when a Siebel Remote or Replication node synchronizes to the primary server database. For example, if a trigger is due to an update to Account information in the S_ORG_EXT table, the trigger will not fire until that change is synchronized to the primary database. If you configure a Workflow Policy that creates database triggers that compare changes in the Siebel database to a Workflow Policy condition, and if these changes affect this condition during synchronization, then the database triggers fire and Siebel CRM writes rows to the S_ESCL_REQ table. For more information, see Tables That Workflow Monitor Agent Uses.