Operator guideEN

Casino / Collections / Reorder

Drag-and-drop ordering screen for casino collections loaded into the reorder table.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this page does

This page lets operators reorder casino collections in a drag-and-drop table. The page loads the first collection page, sorts the loaded rows by stored order, and lets the operator drag rows into a new visible sequence before saving.

When to use it

  • change collection ordering after creating, deleting, or editing collections
  • review the curated sequence before saving
  • correct visible collection order when the list appears out of sequence

How to use it

  1. Drag collection rows into the intended order.
  2. Review the visible Position values.
  3. Click Save Order.

Cancel returns to the main Collections list without saving the current drag state.

What changes when saved

Save Order persists the submitted visible sequence. The save flow rewrites the stored order value for each submitted collection starting from 1.

Known caveats

  • The page reads the first 100 collections, then sorts those loaded rows by stored order. If there are more than 100 collections, omitted rows are not submitted by this page.
  • The save flow validates that submitted ids exist, but it does not verify that the submitted list contains every collection in the system.
  • The table header says Order ID, but the rendered row value is the current visible Position, not the stored order id.
  • Dragging rows changes the browser-side sequence only. Nothing is persisted until Save Order succeeds.
  • Leaving the page or pressing Cancel before saving discards unsaved drag movement.
More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Calculations8 topicsOpen details

Reorder list read

The table is built from the first loaded collection page, not from an unlimited full export.

Inputs
collection list query
Formula
The page reads collections with `limit = 100` and `pageNo = 1`; other list query defaults still apply.
Caveats
If there are more than 100 collections, omitted rows are not part of this page's submitted order.

Initial visible order

The first sequence the operator sees is based on stored collection order values for the loaded rows.

Inputs
loaded collection rows, stored order id
Formula
After the read completes, the page sorts loaded rows by `orderId` ascending before putting them into the draggable list.

Local drag order

Dragging changes the visible order in the browser but does not persist anything until Save Order succeeds.

Inputs
current row array, drag source index, drag destination index
Formula
Drag-and-drop copies the current row array, removes the dragged row from the source index, and inserts it at the destination index.

Displayed position

The value shown under the Order ID header is the current visible position.

Inputs
row index in draggable list
Formula
Displayed Position = current row index + 1.
Caveats
This is not the raw stored `orderId` value from the source response.

Save Order payload

Save Order sends the current visible sequence as the new order for submitted collections.

Inputs
current draggable row sequence
Formula
Payload = `{ order: current rows mapped to collection id }`.

Save order validation

The save only proves that submitted rows exist; it does not prove that every collection in the system was included.

Inputs
submitted ordered collection ids, existing collection records
Formula
The save flow de-duplicates the submitted id list, loads matching collections, and rejects the save when any submitted id does not map to an existing collection.
Caveats
Duplicate ids are removed before the existence comparison., A partial list can still pass validation when every submitted id exists.

Persisted order values

The first submitted row becomes order 1, the second becomes order 2, and so on.

Inputs
submitted order array, matching collection rows
Formula
For each matching collection id in the submitted order array, the save flow writes `orderId = index in submitted order + 1`.
Caveats
Operators should refresh and verify after any save error because the update loop is sequential and not wrapped in a documented transaction.

Cancel behavior

Unsaved drag movements are discarded when leaving through Cancel.

Inputs
current local drag state
Formula
Cancel navigates back to the main Collections list without calling the save-order mutation.
Fields10 topicsOpen details

Reorder Collections

Page heading for the collection ordering workflow.

Data Type
text
Editable
false

Error alert

Error message shown when the list read or save-order request fails.

Data Type
feedback-state
Editable
false

Success alert

Success message shown after the save-order request is accepted.

Data Type
feedback-state
Editable
false

Drag handle

Row handle used to move a collection to a different visible position.

Data Type
ui-control
Editable
true

ID

Internal collection id submitted in the saved order array.

Data Type
integer
Editable
false

Name

English collection name shown in the draggable row.

Data Type
string
Editable
false

Status

Shows Active when the collection active flag is true and Inactive when false.

Data Type
status
Editable
false

Order ID / Position

Current visible row position after sorting and any local drag movement.

Data Type
integer
Editable
true
Caveats
The table header says Order ID, but the rendered row value is current Position., Stored order id is used to build the initial sequence and is rewritten only after Save Order succeeds.

Save Order

Persists the current visible row sequence for submitted collection rows.

Data Type
action
Editable
true

Cancel

Returns to the Collections list without saving unsaved drag changes.

Data Type
action
Editable
true
More help

Related pages

Casino / Collections

Operator guide for casino collection catalog maintenance, including list, create or edit, reorder, and add-games relation flow.

Casino / Collections / Add Games

Relation workflow for assigning, removing, ordering, or bulk-loading games in a collection.

Casino / Collections / Form

Create and edit one collection, including translations, image, active state, portrait-preview preference, and manual preview games.

Casino / Collections / List

Searchable collection grid with status filter, page-level summary cards, game counts, image reset maintenance, and row-level collection actions.

Auto Tags Manager / Order

Manual drag-and-drop ordering screen for valid auto-tag rules, with a single save action that rewrites sort positions.

Casino / Aggregators

Operator overview for the casino-side aggregator registry, pagination, and activation workflow.