> For the complete documentation index, see [llms.txt](https://4wsplatform.gitbook.io/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://4wsplatform.gitbook.io/user-guide/modules/bpm/ee0-3-platform-integration/ee0-3-4-to-do-list.md).

# To-do list

This window contains the list of manual tasks potentially assignable to the current logged user and list of tasks already assigned to the user, but not completed yet.\
A user can move a manual task from the first list to the second one: in this way, the task will be assigned to the user and no more available to the users who were candidates to start it.\
Alternatively, the user can assign the task not yet started to another user, who is in the list of candidates for that task.\
Once assigned the task, the user has to complete it, at some point. Properties linked to the manual task are shown and the user has to fill them in, at least for the ones declared mandatory.

Once of the key points about the integration between Platform and Activiti is that properties binded to a manual task become input controls of a detail form in Platform.\
That means that it is possible to enrich the form content using the rich set of graphics components provided by Platform, such as code selectors, combo boxes, etc.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://4wsplatform.gitbook.io/user-guide/modules/bpm/ee0-3-platform-integration/ee0-3-4-to-do-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.