pageFinanceofficial - Microsoftderived - from the source, no model text

Page 1060 "Payment Services"

Base Application · Microsoft.Bank.Setup

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 1060 "Payment Service Setup" (relates to)Payment Service SetupTable 1060 "Payment Service Setup" (calls)Payment Service Setup

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 · Microsoft.Bank.Setup · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Payment Services
SourceTable Payment Service Setup
PageType List
UsageCategory Administration
ApplicationArea Basic, Suite

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
Control2 Name Name Specifies the name of the payment service. from the table field
Description Description Specifies the description of the payment service. from the table field
Enabled Enabled Specifies that the payment service is enabled. from the table field
Always Include on Documents Always Include on Documents Specifies that the payment service is always available in the Payment Service field on outgoing sales documents. from the table field
Terms of Service Terms of Service Specifies a link to the Terms of Service page for the payment service. from the table field

Actions

Group Action ToolTip Runs
Processing New Add a payment service (such as PayPal) on the application that lets customers make online payments for sales orders and invoices.
Setup Change the payment service setup.

Procedures

1 local procedures, no public ones.

Triggers

OnAfterGetCurrRecord, OnDeleteRecord, OnOpenPage

Relations

Called by

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.

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

Evidence 1 sources