ENTRY POINTUnder review

FA080BTN

User Function FA080BTN()

Customizes buttons in the manual payable-settlement screen.

FA080BTNFINA080

01 · OVERVIEW

Overview

Support identifies button addition and P12.2210 passes {aButtons}, replacing aButtons with the return. The 2012 GitHub example creates a virtual history field in oPanel2, initializes public _cE2HIST from E2_HIST and returns an empty array. Its comment names later FA080PE use, not analyzed here. This custom screen does not establish automatic history persistence. (Refs. 1–4) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function FA080BTN()

Parameters

Entry point context

UnconfirmedContext to confirm

The complete technical contract remains unconfirmed. Do not assume types, PARAMIXB positions or aliases beyond the evidence described.

Return value

Result replaces aButtons; the example’s empty array is not a universal neutral baseline.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA080.PRX - FA080TIT*/() -> ABUTTONS:= EXECBLOCK("FA080BTN",.F.,.F.,{ABUTTONS})

Expected result

The record shows arguments and immediate return use where present. It omits the full caller body and does not establish commit timing.

BEST PRACTICES

Do not copy fixed coordinates, a public variable or oPanel2 dependence into arbitrary screens. Verify lifecycle, UI context and received buttons. The isolated example depends on FA080PE customization for its full flow.
A call without a fourth argument does not document a PARAMIXB layout. Preserve caller identifiers and do not invent fields or positions.
Test plan: compare standard and customized flows, exercise success, rejection and repetition, and inspect balances, movements and accounting as applicable.
Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.