soneta-form-xml

Create and validate enova365 form.xml UI definitions for Soneta layouts.

9|6|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/soneta/soneta-erp-skills --skill soneta-form-xml
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: soneta-form-xml
Source: https://github.com/soneta/soneta-erp-skills/tree/main/soneta-form-xml
Command: npx skills add https://github.com/soneta/soneta-erp-skills --skill soneta-form-xml

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill provides in-depth knowledge of the proprietary enova365/Soneta form.xml UI format to help users create valid UI fragments (pageform.xml, viewform.xml, form.xml, lookupform.xml, gridform.xml) and avoid generating XML with non-existent elements.

Core Features & Use Cases

  • Comprehensive guidance on form.xml structure and UI elements (DataForm, Page, Group, Grid, Field, Include, Appearance, GroupBy) and binding syntax (EditValue, DataContext, CaptionHtml, RowCondition).
  • Practical examples and templates for creating and extending shared UI fragments (form.xml includes) and layout constructs (Stack, Row, Flow, Grid).
  • Use Case: design a complete pageform.xml for a domain object or modify an existing UI form without breaking the UI schema.

Quick Start

Provide a ready-to-use form.xml snippet for enova365 according to the defined schema.

Frequently Asked Questions about soneta-form-xml

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

FAQPage Schema
How do I create a valid pageform.xml for a custom domain object in enova365?

To create a valid pageform.xml in enova365, define the UI structure using DataForm elements like Page, Group, Grid, and Field with correct binding syntax such as EditValue and DataContext to prevent generating invalid XML.

What enova365 form.xml elements are available for designing UI layouts?

Available enova365 form.xml elements include DataForm, Page, Group, Grid, Field, Row, Stack, Flow, Command, Include, Appearance, and GroupBy for structuring UI layouts and binding data.

How do I use binding syntax like EditValue and RowCondition in viewform.xml?

Use EditValue, DataContext, CaptionHtml, and RowCondition binding syntax within viewform.xml elements to connect data sources and control UI behavior dynamically.

Can I include shared form.xml fragments in an enova365 UI definition?

Yes, you can use the Include element to embed shared form.xml fragments within pageform.xml or viewform.xml files, allowing for reusable UI components across enova365 modules.

Why does my enova365 gridform.xml break the UI schema?

A gridform.xml breaks the UI schema when it contains non-existent XML elements or incorrect binding syntax, so validate the structure against supported DataForm, Grid, and GroupBy definitions.

When should I use lookupform.xml instead of form.xml in enova365?

Use lookupform.xml for selection interfaces and form.xml for standard data entry, ensuring each uses appropriate DataForm, Field, and Stack layout constructs for its specific purpose.