I1210

// Generated display declaration:
I1210 = 1210

// Effective Pascal Script type and value:
const I1210: String = '1210';

Example

procedure ScriptEvent(var Value: variant);
var
  IssueCode: string;
  IssueNum: integer;
begin
  IssueCode := I1210;               // '1210'
  IssueNum := StrToInt(IssueCode); // 1210 for integer issue APIs
  Value := IssueCode + ':' + IntToStr(IssueNum);
end;

Usage

I1210 is the script-visible String code '1210' for Issue 1210 (Booking Missing Required Value).

• Use I1210 for text serialisation or comparison; use 1210 or explicit conversion for an integer parameter.
• Validate the exact required-value rule before creating the issue; the constant does not perform the test.
• Include the missing field, transaction key, source scope and expected rule in the description.

Transaction-family scope

This code means that a required value is missing in Booking processing. The generic description does not identify the missing field, row, partner, mapping rule or source value. Supply those facts in the separate issue description so an operator can locate and correct the failure.

The fourteen I1201–I1214 members are fixed per-family identifiers. Do not calculate one by adding an offset, and do not substitute a nearby member merely because all fresh-build descriptions are the same. Use I1210 only when the validation belongs to the Booking family.

The constant itself:

• does not test null, blank, whitespace, Unassigned, Null or Empty values;
• does not determine which field is required under a particular partner or message profile;
• does not call LogIssue, insert an issue row, change transaction status or navigate to /Transaction/Booking; and
• carries no transaction Num, record key, field name, source application or partner context.

Additional Technical Info

I1210 is the script-visible String constant '1210' for the fresh-build VxData Issue definition Missing Required Value in the Booking transaction family. It identifies a validation result; reading or assigning the constant does not inspect a record or create an issue.

The generated index displays I1210 = 1210 without quotes. Product source registers the member as String and supplies digit text. The example was source-reviewed and not executed against VxData.

Declaration and fresh-build definition

Property	Default/source value
Script type/value	String / '1210'
Integer Issue.Num after conversion	1210
Fresh-build Issue.Code	1210
Fresh-build description	Missing Required Value
Fresh-build Issue.Status	6 — Status_Error
Fresh-build AdminUrl	/Transaction/Booking

String versus integer issue parameters

The native declaration deliberately exposes a String. GetIssueLevel, InvoiceIssue and the reusable Scriptlet's local CreateIssue accept integer issue numbers.

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

Do not depend on implicit String-to-integer coercion. StrToInt(I1210) is deterministic for this compiled constant, while arbitrary data still needs normal conversion-error handling.

Live definition and severity

The table above describes the current fresh-build database. GetIssueLevel(1210) queries the live Issue.Status each time. Administrators can change the row, and an older or customised database can differ. If the row is absent, GetIssueLevel returns 6 (Error), which happens to equal the fresh-build severity here but does not prove that the definition exists.

A level of 6 is configuration data, not behavior embedded in I1210. The transaction issue queue retains the greatest numeric configured level among newly queued issues for one record; that numeric comparison must not be reinterpreted as a general semantic priority table.

Creation and persistence boundaries

No representative reusable helper call using 1210 was found at the reviewed product baseline. A map must both detect the missing value and pass the correct code and diagnostic context to its chosen issue API.

The reusable Scriptlet's local CreateIssue always calls LogIssue and optionally inserts the supplied number and description into DIssue; it does not query Issue.Status. The separate InvoiceIssue path queries configured severity, queues issue data, and persists it later with header-status and notification-event effects. Its deferred-save, rollback, queue-retention and multi-record quirks apply only when that lifecycle is used.

Related entries

• GetIssueLevel documents live severity lookup and missing-row fallback.
• InvoiceIssue documents one integer issue-consumer lifecycle.
• Status_Error is the fresh-build status value 6 used by this definition.

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

Created 2026-07-15