# Player Entity Limits

### **1. Display and Table Scenarios** <a href="#id-1.-display-and-table-scenarios" id="id-1.-display-and-table-scenarios"></a>

Each row in the limits table represents a specific limit and reflects only the relevant entity data based on its level:

#### **Scenario 1 – Sport Level Limit** <a href="#scenario-1-sport-level-limit" id="scenario-1-sport-level-limit"></a>

* Display Columns: `Entity Limit (Sport)` | `Type (Inplay/Prematch)` | `Sport`
* Other fields (Location, Competition, Fixture) are empty.

#### **Scenario 2 – Location Level Limit** <a href="#scenario-2-location-level-limit" id="scenario-2-location-level-limit"></a>

* Display Columns: `Entity Limit (Location)` | `Type` | `Sport` | `Location`
* Competition and Fixture are empty.

#### **Scenario 3 – Competition Level Limit** <a href="#scenario-3-competition-level-limit" id="scenario-3-competition-level-limit"></a>

* Display Columns: `Entity Limit (Competition)` | `Type` | `Sport` | `Location` | `Competition`
* Fixture is empty.

#### **Scenario 4 – Fixture Level Limit** <a href="#scenario-4-fixture-level-limit" id="scenario-4-fixture-level-limit"></a>

* Display Columns: `Entity Limit (Fixture)` | `Type` | `Sport` | `Location` | `Competition` | `Fixture Name & Date`

### **2. Table Actions** <a href="#id-2.-table-actions" id="id-2.-table-actions"></a>

#### **Search Functionality** <a href="#search-functionality" id="search-functionality"></a>

* Search by: Amount, Action, Type, Entity Limit, Sport, Location, Competition, Fixture.

#### **Filters** <a href="#filters" id="filters"></a>

* Entity Limit: Dropdown (defaulted to “Sport” level only in first phase)
* Sport: Dropdown with all sport types (from DB)
* Location: Dropdown with all location types (from DB)
* Competition: Disabled
* Action: Check / Reject

**Create a New Limit**

* Opens a new row on top of the limits table to create a new limit.
* **Type**: `<Prematch>` or `<Inplay>` (PreMatch is default)
* **Sport**: Dropdown with search
* **Location**: Dropdown based on selected sport
* **Competition**: Dropdown based on selected location
* **Fixture**: Dropdown based on selected competition (fixture name + ID)

**Field Enablement:** You must fill in fields from top to bottom (Type → Sport → Location → Competition → Fixture)

* **Max Winning**: Numeric value
  * **Range**: 1 – 100,000,000
  * **Validation**: Must not exceed the limit set at a higher level
  * **Error Message**: *"Value exceeds max limit of higher hierarchy"*
* **Action**: `Check` or `Reject` (Reject is default. Check action will be activated in Q4)

**Action Button**\
\\

#### **Cancel** <a href="#cancel" id="cancel"></a>

* Resets all form inputs to their previous state.

#### **Delete Limit** *(Visible when editing an existing limit)* <a href="#delete-limit-visible-when-editing-an-existing-limit" id="delete-limit-visible-when-editing-an-existing-limit"></a>

* Confirmation Message: *"Deleting this limit will revert all affected events to the platform's default limits."*
* Options: `<Delete>` / `<Cancel>`
* On delete:
  * Limit is removed.
  * Reverts affected scopes to default platform limits.
  * Display for 0.5 seconds: *"Limit deleted successfully"* in the configuration panel.

#### **Save Limit** <a href="#save-limit" id="save-limit"></a>

* Enabled once any value changes.
* Saves data to backend and updates table.
* The saved limit remains selected in edit mode.

### **Editing a Limit** <a href="#editing-a-limit" id="editing-a-limit"></a>

* Clicking a row in the table opens that limit on the right in **Edit Mode**.
* You can make changes only for the \<max winning amount> and for the action \<check> or \<reject>

### **Exit Without Saving** <a href="#exit-without-saving" id="exit-without-saving"></a>

If the user tries to leave edit mode (either during new or existing limit editing) without saving:

* Display popup:\
  \&#xNAN;*“You Have Unsaved Changes”*\
  \&#xNAN;*“You are about to exit the sport limit editing without saving.”*
* Options:
  * `<Discard Changes>`
  * `<Continue Editing>`