AI Model · 0.8.1

First AI model: describe, refine and review

Create RELATED_ENTITY_NAME and ENTITY_NAME through a conversation, then check their fields and relationships before Apply.

On this page

This example adds a small product catalogue to a project. Start with a project that does not already contain RELATED_ENTITY_NAME or ENTITY_NAME: the assistant can only create new entities and refine unapplied additions.

1. Prepare the project

Open your project and save or discard unfinished changes in other generator forms. AI uses a specific saved model revision. It cannot combine a request with a half-filled Content form or silently overwrite changes made while it was working.

Open Account, sign in and check that AI assistant is Available. Then return to AI Model.

2. Describe the result

Enter a request in Describe new entities. Name the records, fields and relationships that matter. Separate a product requirement from an implementation suggestion when you are unsure.

For example:

Create a new Catalog module with RELATED_ENTITY_NAME and ENTITY_NAME persistent entities. RELATED_ENTITY_NAME needs a required name. ENTITY_NAME needs a required name, a text description, a price and a belongsTo category relationship. Create the related structures together. Keep all existing entities and modules unchanged.

Click Send. The panel shows the current processing phase. You can continue reading the model while waiting; the result is not applied automatically.

3. Refine before saving

Read the assistant's explanation and inspect the proposed cards. A name or field type that looks plausible may still be wrong for your application.

You can continue with a follow-up before Apply:

In this proposal, add a published boolean to ENTITY_NAME and make its description localizable in English and Russian. Keep RELATED_ENTITY_NAME as proposed.

The new reply replaces the pending proposal. It still needs review and validation. Ask for a smaller change if the request or conversation becomes too large.

4. Inspect relationships carefully

Check which entity owns a reference, whether the field is required and whether a reverse collection is needed. Admingen's regular relationship rules still apply.

If a saved entity needs a new inverse field, create that field manually in Content / Relationships. The assistant cannot modify the saved entity to finish the relationship for you. A rejected proposal does not change your model.

5. Apply and generate separately

Follow Review, Apply and Undo to accept the complete proposal. After Apply, the additions appear in Content. Open Generate, inspect its plan and diff, and generate when you are ready.

For later changes to an applied ENTITY_NAME, use Content. AI can help create another new entity, but it cannot keep revising ENTITY_NAME once ENTITY_NAME is saved.