ENTRY POINTUnder review

F460TOK

User Function F460TOK()

Legacy validator officially mapped to MODELPOS.

F460TOKFINA460

01 · OVERVIEW

Overview

TOTVS removes F460TOK from 12.1.17 and maps it to MODELPOS in FINA460A MVC. The legacy caller assigns its result to lRet. Another file in that GitHub repository, F460SE1.prw, actively declares F460TOK and returns a field array: filename, active function and observed logical consumption diverge. Do not adopt it as a valid F460TOK contract. (Refs. 1, 3 and 4)

02 · SYNTAX

Syntax

User Function F460TOK()

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

Validation result in lRet in the legacy caller; 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("F460TOK")
//     lRet := ExecBlock("F460TOK",.F.,.F.)
// 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.