You are here: Building with agents › The kits › HumanRequests.Processes
Summary#
Osysharp.HumanRequests.Processes is the bridge between requests and processes: each request a workflow's run puts to a person — a question, an approval, a form, a link sent to somebody outside — is a line of that run, in the state that put it.
Nothing is written at the call: a request records the run it was put in by itself. What became of it is told too — who answered and after how long, that its date passed and whom it went on to, that nobody did — and each line opens the request, as whoever is looking may read it.
| Package | Osysharp.HumanRequests.Processes, version 1.1.0 |
| You add it with | Nothing. It arrives by itself in an app that uses [[agent-kit-human-requests|HumanRequests]] and [[agent-kit-processes|Processes]]; osy lock says so. without Osysharp.HumanRequests.Processes; in the manifest keeps it out. |
| It sits on | [[agent-kit-human-requests|HumanRequests]], [[agent-kit-processes|Processes]], [[agent-kit-work-queues|WorkQueues]] |
| It also uses | Identity, Ui — parts of the platform's own library |
| Its own test app | An engineering consultancy hiring a senior implementation consultant — kits/human-requests-processes/tests |
Description#
What do you get without writing anything?#
- A line on the run for each request: who was asked, by an account, a link or a queue.
- A line for what became of it: answered, passed on, run out, called off.
- The request opened in place on the run's page.
- A state that waits for a person no longer reads "Nothing was recorded here."
When do you need it?#
Processes and HumanRequests together. It arrives by itself; you write nothing.
What does it expose?#
The tables below are generated from the kit itself, not written by hand: osy kits Osysharp.HumanRequests.Processes --surface lists each of
them with the code of the kit's own test app that uses it, and the tests that show it working.
Functions you call, those its own tests show most first.
| Function | What it does | Tests that show it |
|---|---|---|
RequestSubject() | What a line of a run that is about a request says its subject is — ProcessMoment.SubjectKind. | 7 |
Screens and components you mount — each is one line in a page of yours.
| Component | What it draws |
|---|---|
RequestOpened(kind, subject) | A line of a run that is about a request opens the request in place — the question, what is known, and what came back — as whoever is looking may read it. |
What to read next#
- Osysharp.Processes — every run of a business process, findable and readable — every run of a business process, findable and readable
- Osysharp.HumanRequests — something put to a person, and their answer coming back — something put to a person, and their answer coming back
- Shape 3 — agents inside a business process — Shape 3 — agents inside a business process
Go deeper#
- People in business processes — what a run asks of people, told on the run (HumanRequests.Processes kit) — what a run asks of people, told on the run
- Requests to people — a question, an approval, a form, and the answer coming back (HumanRequests kit) — requests to people
- Processes — every run of a business process, listed and read from start to now (Processes kit) — the Processes kit