FUNCTIONUnder review

CONFIRMSXE()

ConfirmSxe( <lVerifica> )

Confirms pending numbering under the documented historical contract.

CONFIRMSXE()AdvPL

01 · OVERVIEW

Overview

The CONFIRMSXE() page describes confirming the number obtained by the latest GetSxeNum; true lVerifica requests checking whether it exists in the database. It is not a generic record commit. Documentation formalizes neither a return nor every current availability context. Daniel Atilio’s community example reports using ConfirmSX8 in his environment rather than ConfirmSxe: check the release API instead of silently replacing names. The example prepares an action without confirming or reserving numbers. (TOTVS, 2012, ref. 1; ATILIO, 2023, ref. 2)

02 · SYNTAX

Syntax

ConfirmSxe( <lVerifica> )

Parameters

lVerifica

LogicalRequired

True checks number existence in the database; false does not.

Return value

Unspecified in the consulted page.

03 · PRACTICAL EXAMPLE

Commented example

#Include "Protheus.ch"

User Function Ed310()
    Local bConfirm
    // Invoke only in the lifecycle of an already validated own reservation.
    bConfirm := {|| ConfirmSxe(.T.)}
Return Nil

Expected result

Callback created; no numbering changed. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.

BEST PRACTICES

Do not consume numbering merely for a demonstration. Confirm, cancel and handle errors under the process contract; a visual choice does not prove a write.
Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.