When an action is exported, all referenced components are automatically included in the produced plist file. It is possible to indirectly reference many Yate component types such as actions, rename templates, search templates, etc. When a component is indirectly referenced, it will not automatically be included in the produced export file.
You can force the inclusion of various component types by specifying them on Include statements. Include statements are ignored when processing an action and have no more overhead than a Comment statement. They are only referenced when an action is being exported.
While editing an action, items which do not contain escape characters and are not currently defined will be flagged with a warning.
When the export occurs, if the named item does not exist it will be silently ignored at runtime.
Note that occurrences of \af (case insensitive) in the name field are replaced with the name of the action containing the Include statement. This allows you to include components of the containing action without explicitly naming the component. If an action and its components are later renamed, the Include statement will still be valid.
For the purposes of exporting, Action and Batch Chain Action includes are equivalent. However Batch Chain Action is used to establish the batch chain. Note that actions included with the Batch Chain Action mode must exist when accessed by the Batch Processor.