Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| api:api_applications_id_tasks [2015/07/31 15:40] – Lauri | api:api_applications_id_tasks [2024/07/30 11:50] (current) – external edit 127.0.0.1 |
|---|
| Content-Length: 1234 | Content-Length: 1234 |
| X-Count: 4 | X-Count: 4 |
| | |
| | ==== Response values ==== |
| | |
| | ^ Name ^ Notes ^ |
| | | ''created'' | Date when the task was created | |
| | | ''reminded'' | Date when the applicant was last reminded. If ''null'' then no reminders yet. | |
| | | ''committed'' | Date when the task was last saved by the applicant or admin (last modified). If ''null'' then has not yet been touched by anybody and is in it initial status. | |
| | | ''resolved'' | Date when the task was finally resolved. If ''null'', then the task is still not resolved - a suffiently advanced status has not been assigned. | |
| | | ''class'' | This is essentially the type of the task. | |
| | | ''status'' | The status that is currently assigned to the task. Note that this is the name of the status and should be a reliable identifier. In some cases, the title (as opposed to the name) of the status that is actually displayed, may be different. Name of the status (here) should be as concise as possible, title may be much more verbose, along with an even more verbose description. So you may think of name as a 'slug'. | |
| | | ''notes'' | Notes made by applicant or admin, separately. | |
| |
| ==== Response example ==== | ==== Response example ==== |