How to locate and test entry points
Investigates caller, contract and release before implementing an entry point.
Overview
Start from the routine and business event; locate the identifier in the official index, then find its specific page and release-specific caller. An ExecBlock listing does not establish parameters, return meaning or transaction placement. ExistBlock checks availability without explaining the contract. Test confirmation, cancellation, error and absence paths in a test environment; record versions and observed effects. The example only checks a fictional identifier without invoking an entry point or simulating a standard routine. (TOTVS, n.d., refs. 1–2)
Commented example
#Include "Protheus.ch"
User Function Ed306()
// Fictional name: checks availability, not purpose.
ConOut(cValToChar(ExistBlock("EDTESTPE")))
Return NilLogical according to repository and environment conditions; it does not validate the technical contract. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
- Keep customer data out of logs. Check aliases, PARAMIXB, return and transaction in the actual hook; do not transfer contracts between similar identifiers.
- Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.