ENTRY POINTUnder review

F460LQOK

User Function F460LQOK()

Validates title-selection confirmation in the inspected flow.

F460LQOKFINA460

01 · OVERVIEW

Overview

The public copy executes the hook only when lRet is already true and the block exists, assigning the result back to lRet. It passes no explicit parameters. This chaining preserves an earlier failure and does not provide the selection layout. Do not assume other FINA460 validators share the same parameters. (Refs. 1 and 3) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function F460LQOK()

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

Logical validation result propagated through lRet in the legacy caller.

03 · PRACTICAL EXAMPLE

Observed call and context

// Analysis of a legacy caller published on GitHub (ref. 3); not a hook implementation.
// If lRet .And. ExistBlock("F460LQOK")
//     lRet := ExecBlock("F460LQOK")
// 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.