Clone module generates a draft class from an existing built-in module (for example Customers), so you can then adjust it in the class editor and Form Designer.

Clone a module

1. Open /admin/framework and click Clone module. The button appears only for platform administrators, and only when the server has FRAMEWORK_MODULE_CLONING=true (intended for dev environments).
2. Pick the Module to clone.
3. Set Name suffix (default V2), Sidebar group and Class label.
4. Click Preview to see the tables and fields that will be created, then Clone as draft.
5. A draft class named <source><Suffix> (for example customerV2) is created and opened in the class editor. Review it, then publish.

What is copied

• Structure only: the master table, lookups it uses (as Reference tables), child tables behind its detail tabs, and the form layout. Records are not copied; tables start empty.
• Internal names get the suffix; labels stay the same.
• An existing clone of a lookup is reused (Reuses existing clone).
• The dialog lists database columns not on the original form, which you can tick to include.

Class proposals

/admin/framework/proposals moves classes and layouts between environments: export a proposal file, load it in the other environment, review exactly what would change, then confirm or discard.

Deleting and inactive rules

Deleting a record in a class grid is a real delete, but it is blocked if other records reference it. You see a message and a Set Inactive action instead. Records owned by it (such as child lines) do not block.