(Note: if a Project has no due or defer dates assigned, this property will revert to the database’s default setting.) When set, the dueDate and deferDate properties will use floating time zones.For example, the first task blocks the second one until the first is completed. If true, then children of this project form a dependency chain.See also lastReviewDate and nextReviewDate. The object holding the review repetition properties for this project.ReviewInterval ( Project.ReviewInterval or null) The object holding the repetition properties for this project, or null if it is not repeating.RepetitionRule ( Task.RepetitionRule or null) The Folder (if any) containing this project.An array of the notifications that are active for this project.Notifications (Array of Task.Notification r/o) Returns the very next task that can be completed in the project, or null if there is none or the project contains singleton actions.Returns true if this Project’s root Task has children, more efficiently than checking if children is empty.Tasks are sorted by their order in the database. Returns a flat array of all tasks contained within this Project’s root Task.An alias for flattenedTasks.įlattenedTasks ( TaskArray r/o).The flagged status of the project.įlattenedChildren ( TaskArray r/o).Returns a location referring to the position before the first Task directly contained in the root task of this project.įlagged ( Boolean).Returns the computed effective flagged status for the Project, based on its local flagged and those of its containers.Įnding ( Task.ChildInsertionLocation r/o).Returns the computed effective due date for the Project, based on its local dateDue and those of its containers.ĮffectiveFlagged ( Boolean r/o).

Returns the computed effective drop date for the Project, based on its local dropDate and those of its containers.ĮffectiveDueDate ( Date or null r/o).Returns the computed effective defer date for the Project, based on its local deferDate and those of its containers.ĮffectiveDropDate ( Date or null r/o).Returns the computed effective completion date for the Project, based on its local completionDate and those of its containers.ĮffectiveDeferDate ( Date or null r/o).If set, the project should be completed by this date.ĮffectiveCompletedDate ( Date or null r/o).If set, the project is dropped.ĭueDate ( Date or null).If set, the project is not actionable until this date.ĭropDate ( Date or null).If the property’s value is set to true, this is the Project that inbox tasks that have enough information specified (as selected by the user’s preferences) will be filed into upon a clean-up.ĭeferDate ( Date or null).If the property’s value is set to true, the project contains single tasks, and has no next task.ĭefaultSingletonActionHolder ( Boolean).If set, the project is completed.ĬontainsSingletonActions ( Boolean).If set, the project will be automatically marked completed when its last child Task is marked completed.ĬompletionDate ( Date or null).Note that a project may be effectively considered completed if a containing project is marked completed.ĬompletedB圜hildren ( Boolean) True if the project has been marked completed.An alias for the tasks property.Ĭompleted ( Boolean r/o).Returns a location referring to the position before the first Task directly contained in the root task of this project.Ĭhildren ( TaskArray r/o).Returns a location refering to position just before this project.īeginning ( Task.ChildInsertionLocation r/o).An array of FileWrapper objects representing the attachments associated with the Project’s root Task.īefore ( Folder.ChildInsertionLocation r/o).

Returns a location refering to position just after this project.Īttachments (Array of FileWrapper).

Here are the properties of a project:Īfter ( Folder.ChildInsertionLocation r/o) Project PropertiesĪs with most scriptable objects, instances of the Project class have properties that define their use and purpose. The Projects perspective displays all of your projects in a list, which can be grouped into folders to create hierarchy. Projects are typically more complex than individual action items, and can include several related actions. A project is a task made up of multiple items, referred to in OmniFocus as actions.

Omnifocus priorities