I5000

I5000 = 5000
const I5000: String = '5000';

Example

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

Usage

I5000 is the script-visible String code '5000' for Issue 5000 (System Error).

Operational boundary

Capture the originating exception class, operation and correlation identifiers. Do not use it to hide a more specific database, file or transport category.

Fresh-build and v1.9 definitions agree. GetIssueLevel still queries the live row and returns 6 when absent; the same numeric result does not prove that the definition exists.

The constant carries no exception, stack trace, record key, file, SQL, endpoint, retry count or correlation ID. The caller must add actionable context and decide rollback/retry/escalation based on the actual operation.

Additional Technical Info

I5000 is the script-visible String constant '5000' for the VxData Issue definition System Error. It classifies a general unexpected product/system failure; it does not detect, catch, log, recover from or retry the failure.

Native/import source supplies digit text although the generated index omits quotes. The example was source-reviewed and not executed.

Definition

Property	Source value
Script type/value	String / '5000'
Integer Issue number	5000
Description	System Error
Status	6 — Status_Error
AdminUrl	/Administration/SystemErrors

Issue lifecycle and safe diagnostics

Integer APIs require 5000 or explicit StrToInt(I5000). The local Scriptlet CreateIssue logs and optionally inserts without querying severity; InvoiceIssue uses configured severity and deferred persistence. Neither catches the underlying failure.

• Prefer the most specific of 5001-5003; use 5000 only when evidence does not support a narrower category.
• Preserve original exception details in governed logs while keeping user-facing issue text concise.
• Retry only where the operation is idempotent or compensation is defined.
• Include safe identifiers, timestamps and correlation data; exclude passwords, tokens, connection strings and sensitive payloads.
• Do not claim recovery merely because an Issue was logged.

Related entries

• GetIssueLevel documents live severity.
• InvoiceIssue documents deferred issue persistence.
• Status_Error is current status 6.

No Delphi/Free Pascal equivalent exists; this is Velox-owned.

Created 2026-07-15