# Service Design Specification - Object Design for dispute
**airbnb-bookingmanagement-service** documentation

## Document Overview
This document outlines the object design for the `dispute` model in our application. It includes details about the model's attributes, relationships, and any specific validation or business logic that applies.

## dispute Data Object

### Object Overview
**Description:** Represents a dispute, refund request, or booking issue reported by guest/host/admin for a reservation. Flows to admin for handling, resolves with resolutionStatus and reference to any refund/payment involved.

This object represents a core data structure within the service and acts as the blueprint for database interaction, API generation, and business logic enforcement. 
It is defined using the `ObjectSettings` pattern, which governs its behavior, access control, caching strategy, and integration points with other systems such as Stripe and Redis.

### Core Configuration
- **Soft Delete:** Enabled — Determines whether records are marked inactive (`isActive = false`) instead of being physically deleted.
- **Public Access:** accessProtected — If enabled, anonymous users may access this object’s data depending on API-level rules.








### Properties Schema


| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `reportedAt` | Date | Yes | - |
| `reservationId` | ID | Yes | - |
| `raisedBy` | ID | Yes | - |
| `adminId` | ID | No | - |
| `issueType` | String | Yes | - |
| `description` | Text | Yes | - |
| `relatedPaymentId` | ID | No | - |
| `resolutionStatus` | Enum | Yes | - |
| `resolvedAt` | Date | No | - |
| `refundApproved` | Boolean | No | - |
* Required properties are mandatory for creating objects and must be provided in the request body if no default value is set.



### Default Values
Default values are automatically assigned to properties when a new object is created, if no value is provided in the request body.
Since default values are applied on db level, they should be literal values, not expressions.If you want to use expressions, you can use transposed parameters in any business API to set default values dynamically.

- **reportedAt**: new Date()
- **reservationId**: '00000000-0000-0000-0000-000000000000'
- **raisedBy**: '00000000-0000-0000-0000-000000000000'
- **issueType**: 'default'
- **description**: 'text'
- **resolutionStatus**: pending


### Constant Properties

`reportedAt` `reservationId` `raisedBy` `relatedPaymentId`

Constant properties are defined to be immutable after creation, meaning they cannot be updated or changed once set. They are typically used for properties that should remain constant throughout the object's lifecycle.
A property is set to be constant if the `Allow Update` option is set to `false`.


### Auto Update Properties

`reportedAt` `reservationId` `raisedBy` `adminId` `issueType` `description` `relatedPaymentId` `resolutionStatus` `resolvedAt` `refundApproved`

An update crud API created with the option `Auto Params` enabled will automatically update these properties with the provided values in the request body. 
If you want to update any property in your own business logic not by user input, you can set the `Allow Auto Update` option to false.
These properties will be added to the update API's body parameters and can be updated by the user if any value is provided in the request body.

 


### Enum Properties
Enum properties are defined with a set of allowed values, ensuring that only valid options can be assigned to them. 
The enum options value will be stored as strings in the database, 
but when a data object is created an addtional property with the same name plus an idx suffix will be created, which will hold the index of the selected enum option.
You can use the index property to sort by the enum value or when your enum options represent a sequence of values.

- **resolutionStatus**: [pending, reviewing, resolved, rejected]


 

 

### Elastic Search Indexing

`reportedAt` `reservationId` `raisedBy` `adminId` `issueType` `description` `resolutionStatus` `resolvedAt`

Properties that are indexed in Elastic Search will be searchable via the Elastic Search API. 
While all properties are stored in the elastic search index of the data object, only those marked for Elastic Search indexing will be available for search queries.


### Database Indexing

`reservationId` `resolutionStatus`

Properties that are indexed in the database will be optimized for query performance, allowing for faster data retrieval.
Make a property indexed in the database if you want to use it frequently in query filters or sorting.





### Secondary Key Properties

`reservationId`

Secondary key properties are used to create an additional indexed identifiers for the data object, allowing for alternative access patterns.
Different than normal indexed properties, secondary keys will act as primary keys and Mindbricks will provide automatic secondary key db utility functions to access the data object by the secondary key.


### Relation Properties

`reservationId` `raisedBy` `adminId` `relatedPaymentId`

Mindbricks supports relations between data objects, allowing you to define how objects are linked together.
You can define relations in the data object properties, which will be used to create foreign key constraints in the database.
For complex joins operations, Mindbricks supportsa BFF pattern, where you can view dynamic and static views based on Elastic Search Indexes.
Use db level relations for simple one-to-one or one-to-many relationships, and use BFF views for complex joins that require multiple data objects to be joined together.

- **reservationId**: ID
Relation to `reservation`.id

The target object is a parent object, meaning that the relation is a one-to-many relationship from target to this object.

On Delete: Set Null
Required: Yes

- **raisedBy**: ID
Relation to `user`.id

The target object is a parent object, meaning that the relation is a one-to-many relationship from target to this object.

On Delete: Set Null
Required: Yes

- **adminId**: ID
Relation to `user`.id

The target object is a parent object, meaning that the relation is a one-to-many relationship from target to this object.

On Delete: Set Null
Required: No

- **relatedPaymentId**: ID
Relation to `paymentRecord`.id

The target object is a parent object, meaning that the relation is a one-to-many relationship from target to this object.

On Delete: Set Null
Required: No