creating-diva-entity

Orchestrates end-to-end creation of DIVA business entities with human validation checkpoints.

6|Updated May 11, 2026
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill creating-diva-entity-divalto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-diva-entity
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/creating-diva-entity
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill creating-diva-entity-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jinja2, and includes scripts (resource) and references (resource) components.

What problem does it solve? Creating a complete business entity in the Divalto DIVA ERP requires coordinating many interdependent artifacts — RecordSql views, Module Check files, Zoom SQL screens, screen masks, dictionary entries, aliases, ISAM records, and menu entries — each with strict naming conventions and cross-file consistency rules. This Skill orchestrates that entire workflow collaboratively, pausing at 13 checkpoints so a human can validate each stage before proceeding. ## Core Features & Use Cases - End-to-end entity generation: Chains naming token computation, RecordSql/Module Check/Zoom SQL generation, screen mask creation, alias block generation, dictionary insertion, compilation, SQL sync, and menu registration. - Cross-file validation: Runs 7 consistency rules (XV01–XV07) across generated files and detects foreign keys automatically with confidence scoring. - Human-in-the-loop orchestration: 13 checkpoints (CP1–CP11) where the assistant explains choices, shows validation results, and waits for approval. - Use Case: Ask to create a 'FamRglt' entity in the Retail domain with table RtlFamRglt; the Skill generates all five source files, validates coherence, compiles via a standalone harness, and registers the zoom in the ERP menu. ## Quick Start Ask the assistant to create a complete DIVA entity by providing the domain, entity name, SQL table, key field, and description, then approve each checkpoint as the workflow progresses.

Frequently Asked Questions about creating-diva-entity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a complete business entity in Divalto DIVA?

Provide the domain, entity name, SQL table, key field, and description. The workflow computes naming tokens, generates RecordSql, Module Check, Zoom SQL, screen mask, and alias files, then validates, compiles, syncs SQL, and registers the zoom in the ERP menu across 13 approval checkpoints.

What files are generated when creating a DIVA entity?

Five artifacts are generated: a RecordSql source (.dhsq), a Module Check (.dhsp), a Zoom SQL (.dhsp), a screen mask (.dhsf), and a block of 16 aliases for the domain's pmficsql file. Each is individually validated before cross-file coherence checks run.

How does foreign key detection work in the DIVA entity workflow?

The suggest_nature.py script analyzes candidate field names and returns fk_target metadata with confidence scores. FKs at 90% confidence or higher are proposed automatically, ambiguous ones are flagged for clarification, and validated FKs propagate to Module Check and screen mask generation via --fk parameters.

Why is my zoom invisible via F7 after creating a DIVA entity?

Writing the M4 zoom record alone is insufficient. You must also insert one M1 record (Ce=5) in a5f.dhfi per visibility domain, copying ZoomNum, Ap, Reg, and Ordre from M4 with Applic set to each target domain.

What are the limitations of the DIVA entity creation workflow?

The pre-check against the ERP standard uses a snapshot that may not reflect recent changes and is advisory only. Compilation of gttcficsql.dhsp triggers a cascade of roughly 2000 files taking about 30 minutes, and ISAM writes to menu files require the ERP to be closed.