# `mix ash_workflow.gen.acknowledgement`
[🔗](https://github.com/team-alembic/ash_workflow/blob/v0.12.0/lib/mix/tasks/ash_workflow.gen.acknowledgement.ex#L53)

Adds an acknowledgement workflow to a resource

Generates an acknowledgement resource with one row per person asked to
acknowledge a subject. Only the row's own person may acknowledge it.
The subject gains `has_many :acknowledgements` and an
`acknowledged_by_actor?` calculation. When the subject does not exist, it
is created with `mix ash.gen.resource` first.

Nobody may open a request until the application defines who can, in the
generated `Checks.CanRequest` module.

## Example

```bash
mix ash_workflow.gen.acknowledgement MyApp.Policies.Policy --person MyApp.Accounts.User --overdue-after 14d
```

## Options

* `--person` - required. The actor resource. Each acknowledgement belongs
  to one person.
* `--module` - the acknowledgement resource's module name. Defaults to
  the subject's name with `Acknowledgement` appended.
* `--domain` - the domain for a subject the task creates. Required only
  when the subject does not exist.
* `--overdue-after` - moves an unacknowledged request to `:overdue` this
  long after it was requested, given as `30m`, `12h`, `2d` or `2w`. A
  duration under a minute needs `AshWorkflow.Scheduler.Precise`. Without
  it, no `:overdue` step is generated.
* `--transition-log` - also generates a transition log for the
  acknowledgement with `mix ash_workflow.gen.transition_log`. Defaults to
  `true`.

---

*Consult [api-reference.md](api-reference.md) for complete listing*
