Page 838 "Reminder Terms Setup"
Base Application · Microsoft.Sales.Reminder
Across versions
- BC23not present
- BC24added
- BC25-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Sales.Reminder · BC24-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Reminder Terms Setup |
| SourceTable | Reminder Terms |
| PageType | Document |
| UsageCategory | None |
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 | Reminder Terms Code | Code | Specifies a code to identify this set of reminder terms. from the table field |
| Description | Description | Specifies a description of the reminder terms. from the table field | |
| Maximum Number of Reminders | Max. No. of Reminders | Specifies the maximum number of reminders that can be created for an invoice. from the table field | |
| Post Interest | Post Interest | Specifies whether to post any interest listed on the reminder to the general ledger and customer accounts. from the table field | |
| Post Additional Fee | Post Additional Fee | Specifies whether to post any additional fee listed on the reminder to the general ledger and customer accounts from the table field | |
| Post Additional Fee per Line | Post Add. Fee per Line | Specifies whether to post any additional fee listed on the finance charge memo to the general ledger and customer accounts when the memo is issued. from the table field | |
| Minimum Amount (LCY) | Minimum Amount (LCY) | Specifies the minimum amount for which a reminder will be created. | |
| LanguagesCustomerCommunicationsGroup | Languages with customer communications | LanguagesCustomerCommunications |
Specifies the languages with customer communications for this reminder. The list of languages with attachment texts and email texts is displayed in the format Attachments:
|
| Content | ReminderLevelSetup | part Page 1896 “Reminder Level Setup” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Customer Communication | View or edit customer communications for this reminder. Customer communications include texts added to the reminders document and email texts. | Page 1897 “Reminder Term Communication” |
Triggers
OnAfterGetRecord, OnQueryClosePage
Relations
- source table Table 292 “Reminder Terms”
Pages and codeunits on this table
- Page 837 “Reminder Terms 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 1890 “Reminder Communication” (2 calls:
OnAfterGetRecord → ExtractAttachmentAndEmailLanguages,OnQueryClosePage → CheckMissMatchBetweenLanguages)
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 Terms Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.