The 6-Step Generation Workflow

Step 1 — Receive User Request

The user provides:

• The target Form Group ID (e.g., guard-rails)
• A description of the new form's purpose (e.g., "A property form for editing IP allowlist rules")
• Optional: a list of specific fields required

// Example invocation
Generate a new form in the guard-rails group.
Purpose: Edit an IP allowlist rule (allow/block specific IP ranges).
Fields required:
  - Rule name (text, required)
  - IP range (text, required, CIDR format)
  - Action (select: Allow / Block)
  - Expiry date (date, optional)
  - Notes (textarea, optional)

Step 2 — Read the Group Definition

The AI reads the group's FormGroupDefinition to obtain:

• formGroupId, categoryId, ownerApp
• formIdRange — to constrain FormID selection
• aiGenerationEnabled — abort if false
• defaultPrimaryUsage — pre-fill PrimaryUsage on the new form

Step 3 — Scan Existing SQL Files

The AI reads all .data.sql files in the group's folder. It extracts:

• All FormIDs already in use — to pick the next available one
• All FormCodes — to follow the naming pattern
• All SchemaJson values — to learn the group's control and section patterns

// Folder scanned
BizFirstFiV3DB/dbo/Data/AtlasForms/GuardRails/
  GuardRails_Category.data.sql
  Atlas_Forms_13000_GuardRail_List.data.sql
  Atlas_Forms_13001_GuardRail_Edit.data.sql
  Atlas_Forms_13002_GuardRail_View.data.sql
  ...
  Atlas_Forms_13006_GuardRail_AccessControl_Edit.data.sql

Step 4 — Learn Patterns

From the scanned schemas the AI extracts:

• Section IDs and titles used by peer property forms
• Control types used for similar field purposes across the group
• Binding path patterns ($json.fieldName vs $context.pathName)
• Action block configuration (Save action name, payload structure, navigation target)
• Validation rule patterns (required fields, common format validators)

Step 5 — Generate the Form Schema and Assign FormID

Using the patterns learned, the AI constructs:

1. The metadata block: next FormID, FormCode, title
2. Sections matching peer forms
3. Controls: one per field requirement, using the group's established control types
4. Actions block: cloned from the group's property form template
5. Validation rules: applied to each field per the user's requirements

Step 6 — Write the SQL File

The AI writes a .data.sql file containing the form INSERT with IF NOT EXISTS guard and IDENTITY_INSERT blocks. See SQL File Pattern for the exact format.

Workflow Summary