aVars / PARAMIXBArrayContext to confirm
aVars: initial filter data array, direct PARAMIXB in the example.
ENTRY POINTUnder review
F240GAVE
Initial filter data.
Overview
The support article lists this identifier among payment batch and SISPAG entry points. (TOTVS, 2022, ref. 1) The specific TDN reference was read for this review. (TOTVS, n.d., ref. 2)
Parameters
Return value
Array of adjusted filter data. The page states that defining this entry point suppresses the standard initial screen.
Documentary record
// Research record; not an executable implementation.
// F240GAVE: https://tdn.totvs.com/pages/releaseview.action?pageId=6071420Expected result
This record identifies the source; it does not demonstrate execution or effects in Protheus.
- Documentary review; examples were neither compiled nor executed in Protheus.
- After recording does not mean after commit. Transaction placement and target-release compatibility require confirmation.
- The reference is historical (older Protheus versions); validate availability and contract in the release in use.
- Do not transfer a PARAMIXB or return contract between different entry points.
- The documented aVars order is: cNumBor, dVenIni240, dVenFim240, nLimite, cPort240, cAgen240, cConta240, cContrato, cMoeda240, aMoedas, cModPgto, cTipoPag, nOpc. The example does not demonstrate a nested array.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.