|
| 1 | +--- |
| 2 | +title: Create events from the Admin |
| 3 | +description: Learn about managing events subscriptions through the admin in Commerce Cloud Service. |
| 4 | +keywords: |
| 5 | + - Events |
| 6 | + - Extensibility |
| 7 | +--- |
| 8 | + |
| 9 | +# Create events from the Admin |
| 10 | + |
| 11 | +<InlineAlert variant="info" slots="text1" /> |
| 12 | + |
| 13 | +This feature is available only in Adobe Commerce as a Cloud Service (ACCS). |
| 14 | + |
| 15 | +In addition to the available [REST endpoints for event subscriptions](./api.md), Adobe Commerce as a Cloud Service also supports managing events through the Admin. |
| 16 | + |
| 17 | +## View event subscriptions |
| 18 | + |
| 19 | +In the Admin, select **System** > **Events** > **Events Subscriptions** to display the _Events Subscriptions_ grid page. |
| 20 | + |
| 21 | + |
| 22 | + |
| 23 | +The rows of this grid show configuration settings for all event subscriptions, both enabled and disabled. |
| 24 | + |
| 25 | +## Create a new event subscription |
| 26 | + |
| 27 | +Click **Add New Subscription** from the grid page to display the form for creating a new event subscription. |
| 28 | + |
| 29 | + |
| 30 | + |
| 31 | +The **Event subscription settings** configuration panel contains the following fields: |
| 32 | + |
| 33 | +Field | Description |
| 34 | +--- | --- |
| 35 | +**Event Name** | Select one of the supported Commerce event names from the dropdown. |
| 36 | +**Event Name Alias** | A unique alias name for the event. An alias is required for events that have rules configured. |
| 37 | +**Event Provider** | Select the event provider to which the event should be delivered. If a workspace configuration is set for the provider, event metadata will be created and linked to the provider when the event subscription is saved. |
| 38 | +**Is Enabled** | Indicates whether the event is enabled. Commerce does not emit disabled events. |
| 39 | +**Priority** | Indicates whether the event has priority status. Priority events are sent within a second, whereas non-priority events can take up to 59 seconds to send. |
| 40 | + |
| 41 | +### Configure event subscription fields |
| 42 | + |
| 43 | +The **Event Subscription Fields** configuration panel allows you to define the fields of the event payload to transmit from Commerce. The name provides the path to the field in the event payload. See [Register events](./module-development.md#register-events) for details on specifying event field names. |
| 44 | + |
| 45 | +### Configure event subscription rules |
| 46 | + |
| 47 | +The **Event Subscription Rules** configuration panel allows you to define rules that determine when an event with a name alias is triggered. [Create conditional events](./conditional-events.md) describes how to configure rules. |
| 48 | + |
| 49 | +Field | Description |
| 50 | +--- | --- |
| 51 | +**Field** | The name of the event field to be evaluated. |
| 52 | +**Value** | The value to be compared. |
| 53 | +**Operator** | Defines which comparison operator to use. Examples include `lessThan`, `regex`, and `equal`. |
| 54 | + |
| 55 | +## Events Subscriptions grid actions |
| 56 | + |
| 57 | +Click **Select** > **Edit** in the **Action** column of an event subscription's row to display a form for editing the subscription. |
| 58 | + |
| 59 | + |
| 60 | + |
| 61 | +Click **Select** > **Delete** in the **Action** column to delete an event subscription. |
0 commit comments