Before actually implementing a Trigger Set, consider where the database can best drive automation in your workflow. In some cases, this may be as simple as automatically sending an e-mail message or printing a file, while in other workflows, an elaborate series of Actions may be spawned from a single database change. To work effectively, Trigger Sets must be carefully planned and implemented to solve specific workflow problems or bottlenecks. Because some Actions make changes to the server file system and file-system changes can trigger other Actions, be cautious when adding a Trigger Set that there are no unintended consequences.