I1660

// Generated display declaration:
I1660 = 1660

// Effective Pascal Script type and value:
const I1660: String = '1660';

Example

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

Usage

I1660 is the script-visible String code '1660' for Issue 1660 (Remittance Line Auto Created).

• Emit I1660 only after confirmed Remittance Line creation, not before an attempted write or commit.
• Use I1660 for text; use 1660 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 child-record outcome. Its diagnostic must include both the created child key and enough parent scope to locate it.

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 1660 as status 2/Warning with route /Transaction/Remittance. A live upgraded or customised row can still differ. GetIssueLevel(1660) 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

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

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

Declaration and fresh-build definition

Property	Default/source value
Script type/value	String / '1660'
Integer Issue.Num after conversion	1660
Fresh-build description	Remittance Line Auto Created
Fresh-build Issue.Status	2 — Status_Warning
Fresh-build AdminUrl	/Transaction/Remittance
Record scope	Remittance Line / child

String versus integer issue APIs

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

TextCode := I1660;                      // exact text '1660'
Level := GetIssueLevel(1660);            // integer API, preferred literal
Level := GetIssueLevel(StrToInt(I1660)); // 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 Remittance Line merely because issue 1660 is supplied.

Related entries

• GetIssueLevel documents live severity and missing-row fallback.
• InvoiceIssue documents one deferred issue lifecycle.
• Status_Warning is the fresh-build status value 2.

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

Created 2026-07-15