GoFiler Legato Script Reference
Legato v 1.5b Application v 5.24b
|
Table of Contents | < < Previous | Next >> |
Chapter Thirteen — Collaboration Functions (continued)
Like other collaboration items, tasks can be stored in up four locations: enterprise, user (local), project and project entry. The task functions allow tasks to be enumerated, added, deleted and altered.
Tasks can be referenced by location and index or by task ID. Task IDs consist of a location code, task designator and series number. For example, “UT0023” is a user task, 23rd serial item. Time stamps are used to assist in task sharing amongst multiple users. It indicates where the task has been altered since the last load.
When data elements must be referenced when retrieving or setting task properties, the following key names apply:
Name | Description | ||
ID | Task ID (set by the application). The ID can also be used to set the location and type of data when creating a task. The values after the location and type are not used when creating tasks. This is a read-only field. | ||
TimeStamp | Internal time stamp in ISO-8601 in UTC. This is a read-only field. | ||
Location | Location code (integer as a string). This can be the same as ID when setting tasks. This is a read-only field. | ||
Subject | Subject field. | ||
Status | Status field. | ||
PercentComplete | Percent complete. | ||
Priority | Priority (normally a percentage). | ||
Category | Category for user classification of the task. | ||
CategoryColor | Color for display purposes. | ||
Owner | The owner of the task (name). | ||
AssignedTo | Assigned to (name). | ||
BlockActions | Block actions by Function Code (multiples separated by spaces). | ||
Description | User description. | ||
DateCreated | Date created in ISO-8601 format in UTC. | ||
DateStarted | Date started in ISO-8601 format in UTC. | ||
DateDue | Date due in ISO-8601 format in UTC. | ||
DateCompleted | Date completed in ISO-8601 format in UTC. | ||
CompletedBy | Name of person completing. | ||
Notes | General notes. | ||
EmailEvents | Events resulting in an email notification. | ||
Email addresses for notifications. | |||
UserData | General user data. |
The total size of the data elements cannot exceed 4,096 bytes, including zero terminators.
The ID/location codes break down as follows:
l T nnnnn
Where:
l
Is the location as ‘E’ for enterprise, ‘U’ for user, ‘P’ for project, ‘F’ for project file and T for template.
T
Indicates this is a task.
nnnnn
Is a serial number used to uniquely identify the task.
Table of Contents | < < Previous | Next >> |
© 2012-2024 Novaworks, LLC. All rights reserved worldwide. Unauthorized use, duplication or transmission prohibited by law. Portions of the software are protected by US Patents 10,095,672, 10,706,221 and 11,210,456. GoFiler™ and Legato™ are trademarks of Novaworks, LLC. EDGAR® is a federally registered trademark of the U.S. Securities and Exchange Commission. Novaworks is not affiliated with or approved by the U.S. Securities and Exchange Commission. All other trademarks are property of their respective owners. Use of the features specified in this language are subject to terms, conditions and limitations of the Software License Agreement.