> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/workflow-template-administration/managing-tasks-adding-tasks-to-the-dependency-diagram/task-types-in-the-task-palette/defining-request-start-details.md).

# Defining Request Start Details

1. On the dependency diagram, double-click the **Request Start** task iconto view the **Request Start Task Details** window.
2. Complete the fields in this window.
3. In the **Request Information** section, the **Request Title**, **Ref** and **Description** are populated automatically from the request and cannot be edited.
4. Expand the **Task Information** section if necessary, and complete the details.
5. Expand the **Task Description** section and in the text area, type some details about this task.
6. Save the changes.

This is a system-defined task, and therefore cannot be deleted. For email messages to be sent for the tasks in a workflow, the **Request Start** task must be authorized through the request.


---

# 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://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/workflow-template-administration/managing-tasks-adding-tasks-to-the-dependency-diagram/task-types-in-the-task-palette/defining-request-start-details.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.