Page 6752 "Reminder Automation Card"
Base Application · Microsoft.Sales.Reminder
Across versions
- BC23not present
- BC24added
- BC25-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Reminder · captioned “Reminder Automation” · BC24-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Reminder Automation |
| SourceTable | Reminder Action Group |
| PageType | Card |
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 |
|---|---|---|---|
| General | Code | Code | Specifies a unique code for the reminder action group. |
| Description | Description | Specifies a description for the reminder action group. from the table field | |
| Blocked | Blocked | Specifies whether the reminder action group is blocked. Blocked reminder action groups cannot be used in the system. from the table field | |
| Reminder Terms Filter | ReminderTermsText |
Specifies the reminder terms that can be used by this reminder action group. This filter is always used, regardless of the action specific filters. | |
| Status | StatusTxt |
Specifies the status of the reminder action group. | |
| ErrorMessageGroup | Error Message | ErrorMessage |
Specifies the error message that has stopped the automation job from running. For specific error messages you need to open the details card. |
| ErrorNumbersGroup | Number of errors | NumberOfActiveErrors |
Specifies the number of errors that occurred when running the reminder action group. |
| NextStartDateGroup | Expected start | NextStartDateTxt |
Specifies the expected start date and time of the next automation job. The job should start at the specified time or shortly after. If the job does not start, you need to check the job queue entries. |
| LastRunStatusGroup | Last run | LastRunStatus |
Specifies the status of the last automation job. |
| Scheduling | Cadence | Schedule | Specifies the cadence of the automation job. The cadence determines how often the automation job is run. from the table field |
| StartDate | Start Date | Start DateTime | Specifies the date and time when the automation job is started for the first time. from the table field |
| NextSchedule | Next Run Date formula | Next Run Date Formula | Specifies the formula that is used to calculate the date and time when the automation job is run next time. from the table field |
| Content | Actions | part Page 6755 “Reminder Actions Part” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Start | Start the backround job that will perform the actions defined. | |
| Pause | Pause the backround job. | ||
| Refresh | Refresh the status. | ||
| Log entries | See the history and log entries for the reminder actions. | ||
| Job queue entry | Access the job queue entry. | ||
| Reminders | Open the Reminders page. | Page 436 “Reminder List” | |
| Issued Reminders | Open the Issued Reminders page. | Page 440 “Issued Reminder List” |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetRecord, OnAfterGetCurrRecord, OnOpenPage
Relations
- card page Page 6752 “Reminder Automation Card”
- source table Table 6751 “Reminder Action Group”
Pages and codeunits on this table
- Page 6752 “Reminder Automation Card” (card page)
- Page 6753 “Reminder Automation List” (card page)
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 8703 “Feature Telemetry” (1 call:
OnOpenPage → LogUptake)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Reminder Automation Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.