Open ERP

Preview & Generation

Review the complete proposal, save an immutable version, generate it and verify the deployed runtime.

Preview before saving

Preview gives a consolidated view of the proposed module. Use it to catch missing fields, poor form order, internal list columns, incomplete mappings or unbalanced posting before generation.

  • Confirm module identity and enabled capabilities.
  • Review all fields and lookup sources.
  • Review create/edit form rows and child placement.
  • Review view columns, search filters and actions.
  • Review accounting, stock, GST and print sections that are enabled.

Draft, version and generation job

  1. 01
    Save Draft

    Persist the current definition without changing the tenant runtime.

  2. 02
    Create the definition version

    Generation uses an immutable snapshot so the job is traceable and repeatable.

  3. 03
    Generate

    The backend validates metadata, updates the tenant schema safely and creates runtime/frontend artifacts.

  4. 04
    Deploy and health-check

    Queued frontend artifacts appear in ERP only after the scheduled deployment and health checks succeed.

Ready does not always mean deployed

A successful generation may finish before the next batched frontend deployment. The user-facing status should show the next deployment slot and keep existing ERP features available.

Editing a generated module

Use the action that matches the changed tab. Jhapu can regenerate Forms, Runtime & Forms, Runtime & List, Print Page, or Schema/Runtime/Forms for supported column changes.

  • Properties/DB changes may alter the physical table and regenerate the model/runtime.
  • View Page changes require list regeneration.
  • Print Studio changes require print-page regeneration.
  • Form Designer changes require form regeneration.
  • Primary/unique key corrections are restricted once the table contains data.

Runtime acceptance test

  • Open the module through its ERP menu and verify access permissions.
  • Create at least two realistic records.
  • Search, sort, paginate, view and export where enabled.
  • Edit and confirm lookup selections, calculations and child rows reload.
  • Inspect vouchers, stock reports and GST reports where enabled.
  • Print a saved record where enabled.
  • Delete a test record and verify reversals/files/dependencies where deletion is allowed.
Generated code is isolated

If one generated frontend module fails to load, Jhapu shows a module-level error while the base ERP and other modules remain available.

Next guideReport Configuration