ENTRY POINTUnder review

FA330MNU

User Function FA330MNU()

Adds menu functionality before the browse is shown.

FA330MNUFINA330

01 · OVERVIEW

Overview

The current page documents required return of aRotina and shows adding an action. P12.2210 receives {aRotina} and replaces aRotina with the return. The official example depends on U_TESTE(), which must exist; a menu row implements neither the action nor authorization. No useful GitHub implementation was found. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function FA330MNU()

Parameters

PARAMIXB[1]

ArrayExecution context

aRotina in the P12.2210 call; the page also demonstrates caller-scoped aRotina. (Refs. 1–2)

Return value

Array of menu items, preserving required standard actions.

03 · PRACTICAL EXAMPLE

Adding a demonstration action

#Include "Protheus.ch"

User Function FA330MNU()
    // Adapt the TOTVS addition and provide the demonstration routine.
    Local aMenu := AClone(PARAMIXB[1])
    AAdd(aMenu,{"Diagnostic", "U_Ed330Info", 0, 0, 0, .F.})
Return aMenu

User Function Ed330Info()
    // Teaching action without changing titles.
    MsgInfo("FINA330 editorial menu")
Return Nil

Expected result

Adds an action with its own routine included in the sample. Verify menu layout and compile in testing; not tested in Protheus.

04 · PRACTICAL EXAMPLE

Observed call and context

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

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

Verify each item structure in the target release. Create and test the called routine before adding it. Distinguish adding actions in FA330MNU from selecting buttons in FA330LIB.
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.