Creating and managing layouts and reports > Setting up script triggers > Actions that don’t activate script triggers
 
Actions that don’t activate script triggers
Bulk operations that may change many records at once will not activate a script trigger.
Spell checking (Edit menu > Spelling > Check All or the Check Found Set script step) or a Find/Replace (Edit menu > Find/Replace or the Open Find/Replace script step) on more than one record at a time will not activate script triggers.
When you check spelling for all fields in a record or all records in a found set (as in the Check Found Set script step), script triggers will not activate except:
If a field is active when an operation starts, the OnObjectExit script trigger will activate.
If a field is active at the end of an operation, the OnObjectEnter script trigger will activate for that field.
Only direct operations can activate script triggers:
Changes made directly to a layout object or using a layout will activate script triggers, while changes made to the underlying data will not activate a script trigger.
Changes made to a field in one layout object instance will not activate script triggers on other layout objects on the same layout or a different layout.
Script steps and menu commands that apply directly to the table data rather than the layout, such as Import Records, Replace Field Contents, and Relookup Field Contents will not activate script triggers.
Changes made to a field from the Show Custom Dialog script step will not activate the OnObjectModify script trigger.
Script steps that can change a field directly, such as Set Field, Set Field By Name, and Set Web Viewer will not activate the OnObjectModify script trigger. Script steps that work on a layout object even though their target is specified as a field, such as Insert Text, will activate the OnObjectModify script trigger.
Apple events that apply directly to or work through layout objects will activate script triggers. Apple events that bypass the layout will not activate the script triggers.
Schema changes that change the data in fields will not activate script triggers.
Summary fields and calculation fields:
The OnObjectEnter, OnObjectExit, and OnObjectKeystroke script triggers activate for summary and calculation fields. The OnObjectModify script trigger can be set for summary and calculation fields, but it will not activate.