Page 831 "Workflow Webhook Subscriptions"
Base Application · System.Automation
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · System.Automation · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | ‘workflowWebhookSubscriptions’, Locked = true |
| SourceTable | Workflow Webhook Subscription |
| PageType | List |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Group | notificationUrl | NotificationURLTxt |
Specifies the notification url to post to. |
| conditions | ConditionsTxt |
Specifies the workflow conditions. | |
| eventCode | Event Code | Specifies the event code for the workflow. | |
| clientType | Client Type | Specifies the client type | |
| clientId | Client Id | Specifies the id for the client from Power Automate. | |
| enabled | Enabled | Specifies if the subscription is enabled. | |
| id | Id | Specifies the unique identifier for a subscription. |
Triggers
OnAfterGetCurrRecord
Relations
- source table Table 469 “Workflow Webhook Subscription”
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Workflow Webhook Subscriptions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.