Two metadata gaps spotted when the user couldn't see Shira entities in
Admin → Layout Manager and got console 404s on /#CaseMemory:
* AssistantRule.json (scopes/) was missing `customizable: true` and
`importable: false`. Without `customizable: true` EspoCRM hides the
entity from Admin → Entity Manager → Layouts. Other Shira entities
already had it; this one was the outlier.
* CaseMemory.json (clientDefs/) didn't exist at all. The Metadata
endpoint returned an empty object, so the frontend fell through to
default convention `client/custom/modules/smart-assistant/src/controllers/case-memory.js`
which doesn't exist → 404 in browser console. Adding clientDefs with
`controller: controllers/record` + icon + filters lets the standard
record controller handle the entity without any custom JS file.
Verified on prod after hot-patch:
- Metadata?key=scopes.AssistantRule.customizable → "true"
- Metadata?key=clientDefs.CaseMemory → full object
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
chaim
97f7607b2b
