Zulu - Event Hooks
From 360Works Product Documentation Wiki
(Difference between revisions)
(→Zulu_PreDelete) |
|||
Line 6: | Line 6: | ||
=Zulu_PreDelete= | =Zulu_PreDelete= | ||
This script is invoked before an event record is "deleted". The found set will be the event being deleted. Zulu does not actually delete events but puts a 1 in the Deleted field. This script need not have any steps but you can use this to enforce deletion rules. | This script is invoked before an event record is "deleted". The found set will be the event being deleted. Zulu does not actually delete events but puts a 1 in the Deleted field. This script need not have any steps but you can use this to enforce deletion rules. | ||
+ | |||
+ | One way to prevent an event from being removed from a calendar, is to use the "Omit Record" script step to remove this record from the found set before it is deleted. |
Revision as of 17:39, 14 January 2019
- The following event hooks are called after Zulu modifies records in FileMaker.
Zulu_PostEdit
This script is invoked after an event record is inserted or updated. The found set will be the event being inserted/updated. The script need not contain any steps, but you can use this do do things like enforcing new record creation rules.
Zulu_PreDelete
This script is invoked before an event record is "deleted". The found set will be the event being deleted. Zulu does not actually delete events but puts a 1 in the Deleted field. This script need not have any steps but you can use this to enforce deletion rules.
One way to prevent an event from being removed from a calendar, is to use the "Omit Record" script step to remove this record from the found set before it is deleted.