# Service Design Specification - Object Design for pricingConfig
**aifitapp-subscription-service** documentation

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

## pricingConfig Data Object

### Object Overview
**Description:** Stores the current premium subscription pricing configuration. Admin-managed, single system-wide record.

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.


### Redis Entity Caching
This data object is configured for Redis entity caching, which improves data retrieval performance by storing frequently accessed data in Redis.
Each time a new instance is created, updated or deleted, the cache is updated accordingly. Any get requests by id will first check the cache before querying the database.
If you want to use the cache by other select criteria, you can configure any data property as a Redis cluster.











### Properties Schema


**Display Label Property:** `description` — This property is the default display label for records of this data object. Relation dropdowns and record references in the frontend will show the value of this property as the human-readable label.

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `currency` | String | Yes | Currency code for pricing (e.g., usd). |
| `description` | Text | No | Human-readable description of the subscription plan. |
| `price` | Integer | Yes | Current subscription price in cents (e.g., 999 = $9.99). |
| `type` | Enum | Yes |  |
* 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.

- **currency**: usd
- **description**: Premium Subscription - AI Fitness & Nutrition Coach
- **price**: 0
- **type**: subscription



### Auto Update Properties

`currency` `description` `price` `type`

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.

- **type**: [subscription, quota]


 

 

### Elastic Search Indexing

`currency` `description` `price` `type`

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

`type`

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.