Project date fields
Here we explain the purpose of each date field in tiny+ for projects.
This information is most useful to advanced administrators and system-integrators.
Name | Field Type | Purpose | Access |
Created Date
| DateTime | The datetime the record was first created. | Read-only |
Modified Date
| DateTime | The datetime the record was most recently updated. | Read-only |
Start Year
| Integer | An optional field which can hold the calendar year (eg 2019) that the project started. | Read/Write |
Start Date
| DateTime | An optional field that you can populate with the date the project began. | Read/Write |
End Date
| DateTime | An optional field that you can populate with the date the project concluded. | Read/Write |
Close Date
| DateTime | This field is autopopulated with the datetime stamp a project is marked as Won, Active, Lost or Cancelled. It can be manually overridden. | Read/Write |
Completed Date
| DateTime | This field is autopopulated with the datetime stamp a project is marked as Completed. It can be manually overridden. | Read/Write |
Expected Start Date
| Date | A user-entered date for when the project is expected to commence. This field, combined with | Read/Write |
Expected Duration
| String (ISO 8601 Duration-only format) | A user provided period identifying the expected length of time this project will run for. (eg. P4M for 4 months, P14D for 2 weeks, P40D for 40 days). This is parsed input so the user just selects days/weeks/months and enters a number. | Read/Write |
Expected Finish Date
| Date | A user provided date for when the project is expected to conclude. | Read/Write |
Proposal Received Date
| Date | A user provided date for managing proposals. This tracks when a fee proposal is received. | Read/Write |
Proposal Due Date
| Date | A user provided date for managing proposals. This tracks when a fee proposal is due. | Read/Write |
Last updated