ENTRY POINTUnder review

F460BOT

User Function F460BOT()

Legacy settlement buttons; documented migration to BUTTONBAR.

F460BOTFINA460

01 · OVERVIEW

Overview

TOTVS lists F460BOT among legacy hooks removed from 12.1.17 and maps it to BUTTONBAR in the FINA460A MVC hook. The old public copy passes {aButtons}, clones the result and replaces buttons. This explains that caller without making F460BOT active in MVC. The MVC customization file must not be named FINA460A.prw. (Refs. 1 and 3)

02 · SYNTAX

Syntax

User Function F460BOT()

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

Array consumed by AClone in the legacy copy; the MVC event has its own contract.

03 · PRACTICAL EXAMPLE

Observed call and context

// Analysis of a legacy caller published on GitHub (ref. 3); not a hook implementation.
// If ExistBlock("F460BOT")
//     aButtons := AClone(ExecBlock("F460BOT",.F.,.F.,{aButtons}))
// EndIf

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 GitHub copy does not identify a validated release and is not an official distribution. Check the caller in the target environment; this example analyzes legacy flow rather than providing a deployable function.
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.