-Created a new app called Estate.
-Set up the estate addon with a proper manifest file.
-Added estate property model with all required fields.
-Access rights assigned to base groups.
-CH2 , CH3 Completed.

The tutorial uses base groups, giving all rights to every user. Instead,
Two dedicated groups are defined:

- Agent: read and write access only
- Manager: full CRUD access, implies Agent group
- Admin user is automatically assigned the Manager group
- CH4 Done

Add basic UI views for the estate.property model to allow
users to interact with property records.

- Add list view to display properties in a tabular format.
- Add form view to create, edit, and view individual properties.
- Chapter 6 partially done (list and form views).

Improve the estate.property views to make property browsing
more efficient for users.

- Add search view with filters for available properties
  and properties by current user.
- Add group by postcode option in search view.
- Apply domain filters on list and form views to refine
  displayed records.

Chapter 6 completed.

The estate module needed relational fields to link properties
to other records, demo data for easier development and testing,
and an app logo for better identification in the app list.

- Add Many2one fields for property type, buyer, and salesperson.
- Add Many2many field for property tags.
- Add One2many field for property offers.
- Add demo data with 5 sample properties for testing.
- Add app logo to identify the module in the app list.

Chapter 7 completed.

…line

Computed fields are needed to automatically calculate values
that depend on other fields, avoiding manual input errors.

- Add total area computed field combining living area and garden area.
- Add best price computed field to show the highest offer received.
- Add offer deadline computed field based on creation date and
  validity duration, with inverse to allow direct date editing.

Chapter 8 partially done (computed fields only).

When a user enables the garden option, the garden area and
orientation fields should be auto-filled with sensible defaults
to reduce manual input. When disabled, both fields should be
cleared to avoid stale data.

- Add onchange method on garden field to set default garden
  area and orientation when garden is enabled.
- Clear garden area and orientation when garden is disabled.

Chapter 8 completed.

- Add optional hide on living area, seller, and buyer columns
  in list view to reduce visual clutter.
- Add domain filters in search view to refine property results.
- Set default search to show properties with offers received.

Without proper checks, offers can lead to incorrect property states
and allow users to perform invalid actions.

Added logic to manage offers so that properties follow the correct flow
and only valid operations are performed.

- Accepting an offer updates the selling price, buyer,
  and sets the state to offer accepted.
- Other offers are automatically refused when one is accepted
- Prevents accepting offers on sold or cancelled properties
- Prevents refusing an already accepted offer
- Deleting an accepted offer resets the property state and selling price
- Added UserError validations to enforce business rules

CH9 completed

Without a default status, new offers had NULL in the database,
causing an ambiguous state. Buttons were also visible on terminal
states, leading to errors when clicked.

- Add default 'pending' status on offers to avoid NULL values.
- Add a computed field to hide action buttons when the offer status
  is already accepted or refused.
- Make the status field read-only so it can only be changed via buttons.

Property state was not reflecting the actual offer situation.
Creating an offer did not move the property out of 'new' state,
and deleting the last offer left the property stuck in
'offer_received'.

- Transition property to 'offer_received' when a new offer is added.
- Reset property to 'new' when the last remaining offer is deleted.
- Keep 'offer_received' if other offers still exist after deletion.

Invalid pricing entries such as negative amounts or selling prices
far below the expected price can compromise data integrity and
violate business rules. Constraints are needed to catch these errors
before they reach the database.

- Add SQL constraints to enforce strictly positive expected price
  and non-negative selling price at the database level.
- Add Python constraint to ensure selling price is not lower than
  90% of the expected price.

Chapter 10 completed.

Improve the estate module UI by adding widget options, conditional
field/button visibility, and a stat button on the property type form.

- Prevent creating property types directly from the property form
- Add color support to property tags
- Hide garden fields when there is no garden
- Show/hide offer buttons based on offer and property state
- Add a stat button on property type showing the number of linked offers

Chapter 11 completed

Without proper overrides, properties in active states could be
deleted, offers with lower prices could be created, and there was
no way to see a salesperson's properties directly from the user form.

- Prevent deletion of properties that are not in 'new' or
  'cancelled' state by overriding unlink.
- Prevent creation of offers with a price lower than existing
  offers by overriding create on estate.property.offer.
- Extend res.users model to add a One2many field linking a
  salesperson to their properties.
- Add view inheritance on res.users form to display the list
  of properties linked to the salesperson.

Chapter 12 completed.

Create a customer invoice automatically when a property gets marked as sold.
The invoice includes:
- 6% commission on the selling price
-  administrative fee

This links the real estate module to accounting so property sales are recorded
as invoices. Makes it easier to track finances.
-Chapter 13 completed

- Add kanban view with expected price, best price, selling price and tags
- Show best price only when offer received, selling price when accepted
- Group properties by type by default with drag and drop disabled

Chapter 14 completed