Many of the capabilities and features in Sweet use execution tasks. For example custom commands, keyboard shortcuts, triggers and smart templates all use this underlying framework.
Execution tasks provide a framework for writing/changing data, and performing workflows or activities in the application.
The purpose of this section is to explain the different execution tasks that are available and when they can and cannot be used (ie. the list of execution tasks available for custom commands is not the same as those available for triggers or smart templates.)
Most execution tasks are configured in the tasks dialogue (launched as part of configuring a custom command or smart template.).
It is important to note that execution tasks are run in order, and each tasks must complete before the next task is run. If data is being written to a geodatabase, then the tasks will all be part of the same data operation.