# Focus on Operational Process

Where information is requested from external resources (users not having logins to Enate) then there is no need to model this request in the flow. The way to think about the workflow is from the perspective of the resource communicating with the external contact. Their activity is to GAIN approval, or GET additional info.

![](/files/-MWj_e7J7A6DD1d2JJjr)

In this example, there is no need to model the “exceptional” flow. The user should validate the paperwork and that might entail getting additional information from a third party.

This, again, simplifies how the process is mapped. It also defines the process from an operational point-of-view. If someone is responsible for gaining information from an external party then the responsibility is on them, not the external party.

![](/files/-MWj_jiG1U6Lp89Db7OB)


---

# Agent Instructions: 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:

```
GET https://docs.enate.net/enate-help/implementation/enate-implementations-2/solutioning-in-enate/focus-on-operational-process.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.