ENTRY POINTUnder review

F340ATLIS

User Function F340ATLIS()

Handles the title array displayed in the payable compensation listBox.

F340ATLISFINA340

01 · OVERVIEW

Overview

TDN documents returning aTitulos to change the listBox. The P12.2210 listing passes {aTitulos} and assigns the result in FA340COMP. The received array is the first outer context position; do not infer its inner layout from other entry points. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function F340ATLIS()

Parameters

PARAMIXB[1] / aTitulos

ArrayExecution context

Array observed in fourth argument {aTitulos}. Verify inner layout in the target release. (Refs. 1–2)

Return value

Title array returned to the caller. Do not return the entire outer PARAMIXB array or a logical value.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function F340ATLIS()
    // Editorial example: return documented by TDN; context observed in ref. 2.
    Local aTitles := AClone(PARAMIXB[1])
    // Keeps layout and values; row customization requires a verified contract.
Return aTitles

Expected result

Teaching proposal with behavior described in comments. Verify the context before compiling in a test environment. Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.

04 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA340.PRX - FA340COMP() -> ATITULOS := EXECBLOCK("F340ATLIS", .F., .F.,{ATITULOS})

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

The copy retains received content to demonstrate the contract without inventing inner positions. Check selection, totals and confirmation before modifying rows.
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.