What this form does
Use this form when you need to create a new casino sub-category or change an existing one. A sub-category belongs to one parent casino category and can carry translated names, translated descriptions, an active state, and, on the edit screen, icon settings.
Create and edit are one business workflow, but they are not identical:
- Create collects translated name and description values, parent category, and active/inactive state, then adds the new sub-category to the end of the selected parent category order.
- Edit loads an existing sub-category, lets you update the same content and settings, and also exposes system icon, custom icon, preview, and reset controls.
What operators can change
- Translated name and description values for every active CRM language.
- Parent casino category assignment.
- Active or inactive status.
- System icon on the edit flow.
- Custom icon on the edit flow. A custom icon overrides the selected system icon in the preview and saved configuration.
How create works
The create page builds one name value and one description value per active language. The operator chooses a parent category, decides whether the sub-category is active, and clicks Submit. After a successful create response, the portal returns to the sub-category list.
The save flow requires a name object and a parent category. It checks that the parent category exists, blocks a duplicate English name under the same parent category, and assigns the new sub-category the next order position within that parent category.
How edit works
The edit page opens from an existing sub-category id. It loads the current sub-category, active language list, parent category list, and category icon assets before the form is fully editable.
The left side contains the localized content tabs. Languages that already have a name value show a completion indicator. The right side contains general settings and icon settings.
When the operator clicks Save Changes, the portal sends the translated content, active state, parent category, selected system icon, and selected custom icon path. The update flow validates that the sub-category exists, validates category and duplicate rules when the English name or parent category changes, merges submitted names with existing stored names, and saves the update.
Icon behavior
On edit, the icon preview uses the custom icon when one is selected. If no custom icon is selected, it uses the selected system icon. The custom icon dropdown is populated from Core assets filtered for category icon assets.
Reset icon requests an icon reset for the current sub-category. The reset flow clears the custom icon and chooses a default system icon from the sub-category name pattern, falling back to the slots icon when no pattern matches.
Known caveats
- The create screen has a visible
-- Select --option, but the local default parent category value starts as1until the operator changes it. - The page does not enforce required translated name/description values before Submit; save validation requires the name object and duplicate checks focus on the English name.
- Reset icon is triggered from the edit page, but the portal clears the local custom icon after a short timeout instead of waiting for the reset response. Refresh the row or reopen the form if the reset result matters operationally.
- Reset icon chooses a pattern-based default from the stored name. If the stored language keys do not include lowercase
en, the reset flow falls back to the first available name value. - Permission handling differs by action: create and save are permission-checked; read and reset are authenticated admin actions.