> Documentation index: https://www.gooddata.ai/docs/gooddata-ui/llms.txt lists every page of these docs as Markdown.

# DefaultAlertingDialog()

- Package: [@gooddata/sdk-ui-dashboard](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/index.md)
- Kind: function
- Stability: beta
- Source: https://github.com/gooddata/gooddata-ui-sdk/blob/rel/11.64/libs/sdk-ui-dashboard/src/presentation/automations/alerting/DefaultAlertingDialog/DefaultAlertingDialog.tsx
- Guides: [Customize the alert and scheduled email dialogs](https://www.gooddata.ai/docs/gooddata-ui/latest/dashboard-plugins/customize-automation-dialogs/index.md)

> **Beta API.** Mostly stable, but details may change in a minor release, outside SemVer. See [API maturity](https://www.gooddata.ai/docs/gooddata-ui/latest/integrations/platform/api-maturity/index.md).
> 

Default implementation of the alerting create/edit dialog.

**Signature:**

```typescript
export declare function DefaultAlertingDialog(props: IDefaultAlertingDialogProps): ReactElement;
```

## Parameters

| Parameter | Type | Description |
| --- | --- | --- |
| props | [IDefaultAlertingDialogProps](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.idefaultalertingdialogprops/index.md) |  |

**Returns:**

ReactElement

## Remarks

This component is a pure consumer of `AutomationsContext`, `AlertingDialogContext`, and the alerting dialog state contexts: it reads org/workspace data, per-dialog state, and the alert draft's state from those contexts rather than from the dashboard store. It must therefore be rendered within an `AutomationsContextProvider`, an `AlertingDialogContextProvider` (for the create/edit flow), and an `AlertingDialogStateProvider`. Inside a `Dashboard`, the alerting connector supplies the first two providers above the `AlertingDialogComponent` slot, and mounts `AlertingDialogStateProvider` around the resolved slot component — its state model establishes itself once `useAlertingDialogContext().isLoading` is false for the first time and stays mounted from then on — so the default component, and any wholesale slot replacement, inherit all three contexts automatically and require no extra wiring.

The providers are intentionally hoisted above the slot rather than built inside this component: that is what lets a wholesale replacement receive the same contexts. Rendering this component outside those providers throws at runtime.

The dialog is [AlertingDialogShell()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogshell/index.md) — the chrome: overlay, frame, header row, action bar, the dialog's messages, the stale-filters and delete confirmation steps, the loading skeleton — around the exported region renders ([DefaultAlertingDialogFilters()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.defaultalertingdialogfilters/index.md), [DefaultAlertingDialogDestination()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.defaultalertingdialogdestination/index.md), [DefaultAlertingDialogRecipients()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.defaultalertingdialogrecipients/index.md), fed by [useAlertingDialogFiltersProps()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.usealertingdialogfiltersprops/index.md) and siblings; the header and action bar are the shell's) and the connected field blocks — [AlertingDialogMeasure()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogmeasure/index.md), [AlertingDialogAttribute()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogattribute/index.md), [AlertingDialogComparisonOperator()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogcomparisonoperator/index.md), [AlertingDialogThreshold()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogthreshold/index.md), [AlertingDialogComparisonPeriod()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogcomparisonperiod/index.md), [AlertingDialogSensitivity()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogsensitivity/index.md), [AlertingDialogGranularity()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialoggranularity/index.md), [AlertingDialogTriggerMode()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogtriggermode/index.md), [AlertingDialogTriggerInterval()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogtriggerinterval/index.md) — grouped under the "When" and "Do" headings by [AlertingDialogFormFieldGroup()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogformfieldgroup/index.md); each field is a labelled [AutomationDialogFormField()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.automationdialogformfield/index.md) row and the conditional ones gate themselves on the draft. A custom `AlertingDialogComponent` that keeps this chrome but owns the arrangement renders [AlertingDialogShell()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.alertingdialogshell/index.md) around the blocks it wants (see its example); one that owns the chrome too places the blocks in its own markup and reads or writes the same draft through [useAlertDraft()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.usealertdraft/index.md) and [useAlertActions()](https://www.gooddata.ai/docs/gooddata-ui/latest/api-reference/sdk-ui-dashboard/sdk-ui-dashboard.usealertactions/index.md).

Slots render only in the fully rendered dialog: not while the dialog context reports loading, and not while the stale-filters confirmation step is shown.