pageAdministration & Setupofficial - Microsoftderived - from the source, no model text

Page 1870 "Credit Limit Notification"

Base Application · System.Environment.Configuration

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Table 18 "Customer" (relates to)Customer

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Credit Limit Notification
SourceTable Customer

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
Content Control4 label Specifies the main message of the notification.
CreditLimitDetails part Page 1871 “Credit Limit Details” —

Actions

Group Action ToolTip Runs
Manage Customer View or edit detailed information about the customer. Page 21 “Customer Card”
Create Finance Charge Memo Create a new finance charge memo. Page 446 “Finance Charge Memo”
Report Customer - Balance to Date View a list with customers’ payment history up until a certain date. You can use the report to extract your total sales income at the close of an accounting period or fiscal year.

Procedures

  • SetHeading(Value: Text[250])
  • InitializeFromNotificationVar(CreditLimitNotification: Notification)

Relations

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: "Credit Limit Notification"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources