Summary:
This article highlights key limitations and edge cases of the VMF Engine, including dependencies on configuration, formatting, and system processes. It covers scenarios where automation may be limited—such as scheduled job timing, mixed line‑level requirements, regional differences, and API behavior—helping users understand potential gaps and how they may impact order validation and processing.
Question: What are the known limitations and edge cases of the VMF Engine?
Answer:
Automation Scope:
Supports all DSMFs and Capture Codes set up in IMPulse; It also allows the creation of new capture codes.
Comment Line Format:
Requires FieldName:Value separators for Jarvis AI to parse correctly.
Scheduler Dependency:
Auto-release occurs only after scheduled jobs run.
Multi-Line Orders:
Mixed VMF requirements may result in partial release (line-level vs header-level).
Invalid SKUs & Field-Kill Accounts:
VMF validation does not override rejection logic; invalid SKUs are rejected before VMF checks.
Regional Variations:
EMEA uses Order Type flag (S/D/A) for DSMF applicability.
API Behavior:
Orders are accepted even if VMFs are missing; status changes to VR hold. No error codes returned to customer.