Skip to main content

I1611

// Generated display declaration:
I1611 = 1611

// Effective Pascal Script type and value:
const I1611: String = '1611';

Example​

procedure ScriptEvent(var Value: variant);
var
  IssueCode: string;
  IssueNum: integer;
begin
  IssueCode := I1611;               // '1611'
  IssueNum := StrToInt(IssueCode); // identifies an outcome; creates nothing
  Value := IssueCode + ':' + IntToStr(IssueNum);
end;

Usage​

I1611 is the script-visible String code '1611' for Issue 1611 (POD Auto Created).

  • Emit I1611 only after confirmed POD creation, not before an attempted write or commit.
  • Use I1611 for text; use 1611 or explicit conversion for integer issue APIs.
  • Include created keys and parent scope so the result can be audited.

Header/child scope and route

This member represents a transaction header outcome. Do not substitute a later child-row code for it, even when both belong to the same transaction family.

The issue detail should state the new Num or business code, its parent transaction where applicable, source/application/partner context, and any defaults or transformations used. The four-digit identifier carries none of that context.

Family offsets are sparse fixed source choices. Do not derive a child code by adding to a header code, and do not treat an unlisted number as supported.

Live Issue definition

Fresh-build and v1.15 upgrade sources both define 1611 as status 2/Warning with route /Transaction/POD. A live upgraded or customised row can still differ. GetIssueLevel(1611) queries that live status and returns fallback 6/Error when the row is absent; fallback does not recreate the definition or prove creation.

The transaction issue queue retains the greatest numeric configured level among new issues for a record. That numeric comparison can displace status 2 when higher values are present and should not be treated as a separately governed semantic priority table.

Additional Technical Info​

I1611 is the script-visible String constant '1611' for the VxData Issue definition POD Auto Created. It identifies a configured transaction-creation outcome; evaluating the constant does not create a POD record or verify that one was committed.

Native source and the Pascal Script import supply digit text, although the generated index displays I1611 = 1611 without quotes. The example was source-reviewed and not executed against transaction data.

Declaration and fresh-build definition

PropertyDefault/source value
Script type/valueString / '1611'
Integer Issue.Num after conversion1611
Fresh-build descriptionPOD Auto Created
Fresh-build Issue.Status2 — Status_Warning
Fresh-build AdminUrl/Transaction/POD
Record scopePOD / header

String versus integer issue APIs

GetIssueLevel, InvoiceIssue and the reusable Scriptlet's local CreateIssue take integer issue numbers.

TextCode := I1611;                      // exact text '1611'
Level := GetIssueLevel(1611);            // integer API, preferred literal
Level := GetIssueLevel(StrToInt(I1611)); // explicit shared conversion

Do not depend on implicit String-to-integer coercion. The compiled digits convert deterministically; external text needs normal error handling.

Creation and persistence boundaries

No representative runtime consumer of this named constant was found at the reviewed baseline beyond declaration and script registration. A creation helper's return value, dataset state, transaction/commit boundary and duplicate behavior remain the actual evidence of creation.

The reusable Scriptlet's local CreateIssue always calls LogIssue and optionally inserts into DIssue; it does not query configured severity. The separate InvoiceIssue path queries severity, queues issue data and persists later with header-status and notification-event effects. Neither path creates POD merely because issue 1611 is supplied.

Related entries

No Delphi or Free Pascal standard-library equivalent exists; this is a Velox-owned scripting identifier.

Created 2026-07-15