See related documentation.īefore ( Task.ChildInsertionLocation r/o) An array of FileWrapper objects representing the attachments associated with the task.For tasks in the inbox, the tentatively assigned project or parent task, which will be applied on cleanup.Īttachments (Array of FileWrapper).
A positional indicator that reference the list posotion directly following this task instance.ĪssignedContainer ( Project, Task, or Inbox or null).PropertiesĪn instance of the Task class is defined by the value of its properties.Īfter ( Task.ChildInsertionLocation r/o) In the following documentation, consider tasks to be equivalent to actions. Scripts reference tasks, and the graphical user-interface of OmniFocus references actions. In other words: a “task” is a something that needs doing, and “action” is the element in the OmniFocus interface that represents that need or to-do item. The Omni Automation support in OmniFocus considers the terms “action” and “task” to be functionally synonymous, and refers to the scriptable element representing an “action” as a “task.” However, in the OmniPlan application, such a time-related element is called a “ Task.” When interacting with the OmniFocus application’s user-interface (UI for short), you will encounter the term “Action” which refers to a new to-do item for a project.