I1521

// Generated display declaration:
I1521 = 1521

// Effective Pascal Script type and value:
const I1521: String = '1521';

Example

procedure ScriptEvent(var Value: variant);
var
  IssueCode: string;
  IssueNum: integer;
begin
  IssueCode := I1521;               // '1521'
  IssueNum := StrToInt(IssueCode); // identifies the result; creates nothing
  Value := IssueCode + ':' + IntToStr(IssueNum);
end;

Usage

I1521 is the script-visible String code '1521' for Issue 1521 (Product Auto Created).

Meaning and evidence boundary

This definition names Product auto-creation, while the route points to /Administration/ProductParty. That route reflects the product/party administration context and does not mean the constant creates either record.

The text Auto Created describes the intended event represented by the Issue row. It is not an instruction and is not evidence on its own. A caller should emit this code only after the relevant creation path reports success and should add the new record key, supplied code, creation scope and any defaults that were applied.

The family is sparse. Missing numbers correspond to entities for which no named auto-created member is exposed; gaps are not reserved callable values. Do not calculate I1521 from another issue family or invent constants for absent members.

String versus integer issue parameters

GetIssueLevel, InvoiceIssue and the reusable Scriptlet's local CreateIssue take integer issue numbers even though this constant is String.

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

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

Additional Technical Info

I1521 is the script-visible String constant '1521' for the fresh-build VxData Issue definition Product Auto Created. It records a diagnostic identity for a creation outcome; evaluating or assigning the constant does not create product/party mapping master data.

The generated index displays I1521 = 1521 without quotes. Native source and the Pascal Script import supply digit text. The example was source-reviewed and not executed against VxData or any creation helper.

Declaration and fresh-build definition

Property	Default/source value
Script type/value	String / '1521'
Integer Issue.Num after conversion	1521
Fresh-build Issue.Code	1521
Fresh-build description	Product Auto Created
Fresh-build Issue.Status	1 — Status_Success
Fresh-build AdminUrl	/Administration/ProductParty
Reported entity/outcome	Product / auto-created

Severity discrepancy and live configuration

The introducing v1.15 upgrade inserts Issue 1521 with status 2/Warning. The current fresh-build Table_Issue.sql defines it as status 1/Success. Source history therefore does not guarantee a customer's live value: upgraded, fresh-built and customised databases can differ. Query or inspect the live Issue row when severity affects map behavior.

GetIssueLevel(1521) reads live Issue.Status and returns 6/Error if the row is absent. That fallback does not recreate the definition or prove the described record was created. The issue queue compares numeric levels; status 1 can be numerically displaced by higher values even though its label is Success.

Creation, logging and persistence boundaries

No representative runtime consumer of this named constant was found at the reviewed product baseline beyond declaration and script registration. Product helpers may create master data through other code paths, but the constant itself contains no function reference or payload.

The reusable Scriptlet's local CreateIssue always calls LogIssue and optionally inserts the supplied number/description into DIssue; it does not query configured severity. The separate InvoiceIssue lifecycle queries severity, queues data and persists later with transaction-status and notification-event effects. Neither API creates product/party mapping data merely because 1521 is supplied.

Usage guidance

• Emit I1521 only after confirmed Product creation, not when creation is merely requested or attempted.
• Use the String for exact text serialization; use 1521 or explicit conversion for integer issue APIs.
• Include the created record key, source code, application/partner scope and applied defaults in the description.
• Check idempotency and duplicate-detection behavior in the actual creation helper; this constant says nothing about either.
• Confirm the live Issue severity on systems upgraded from v1.15.
• Avoid credentials, tokens and unnecessary personal data in diagnostics.

Related entries

• GetIssueLevel documents live severity and the missing-row fallback.
• InvoiceIssue documents one issue persistence lifecycle.
• Status_Success is the current fresh-build status value 1.

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

Created 2026-07-15