After this commit:
-read the file structure
-created model given in exercise
-given the access right

After this commit:
- Added actions and menus to access estate_property model
- Created custom list, form, and search views
- Defined default attributes and fields behavior for estate_property model

- Added 'Cancel' and 'Sold' buttons to estate.property
- Added 'Accept' and 'Refuse' buttons to estate.property.offer
- Ensure business logic updates property state and details

- Added SQL constraints for positive expected price, selling price, and offer
  price.
- Enforced unique names for property types and tags using SQL constraints.
- Implemented a Python constraint to prevent selling price from being lower than
  90% of the expected price.

- Add inline views for property types linked to properties.
- Implement statusbar widget for property state representation.
- Set default model ordering for consistent list views.
- Enable manual ordering for property types using sequence fields.
- Apply conditional visibility for buttons and fields based on property and
  offer states.
- Restrict property type creation and editing from the property form view.
- Introduce color tags for property types and conditional button display.

…al display

- Implemented inline list view for properties in property types form.
- Applied statusbar widget to display property state.
- Set default model ordering for properties, offers, tags, and types.
- Added manual ordering for property types with sequence field.
- Implemented conditional display of fields and buttons in property form.
- Enabled inline editing for offers and tags in list views.
- Applied decorations to distinguish offers and properties in list views.
- Updated search view with default 'Available' filter and optimized area search.

- Implemented `property_type_id` to `estate.property.offer` as a related field.
- Implemented `offer_ids` and `offer_count` to `estate.property.type` to track
  related offers.
- Implemented a stat button on `estate.property.type` to view related offers
  with a filtered domain.

- Added `property_ids` field to the `res.users` model, showing properties linked
  to the salesperson.
- Applied a domain on `property_ids` to only list properties that are available
  (not sold or canceled).
- Extended the user form view to include the `property_ids` field in a new
  notebook page.

- Created estate_account module to link estate and account modules.
- In estate_property.py, inherited estate.property model.
- Overrode action_sold method to return the super call.

- Added functionality to create a customer invoice when a property is marked as
 'Sold'.
- Set `partner_id` from the estate property and invoice type to 'Customer
  Invoice'.
- Included two invoice lines: 6% of selling price and an additional 100.00 in
  fees.
- Enhanced Kanban view to display expected price, best price, selling price, and
  tags.
- Applied conditional logic and default grouping by property type; disabled
  drag-and-drop.

- Added an icon to the Estate main menu

…ners

- Added demo data for the estate module:
- Created property records with valid details, including pricing and
  availability.
- Added property offers linked to existing partner records to demonstrate
  functionality.
- Ensured that the demo data complies with data integrity constraints.

- Added offers with dates relative to module installation using eval.
- Validated one demo offer using the Accept Offer button and refused others
  with function.
- Created a new property with associated offers using Command in the
  One2many field.

…ails

- Added a minimal property offers report template using QWeb.
- Integrated the report into the Print menu of the Property views.
- Enhanced the report with additional property data and conditional logic for
  offers.
- Created a sub-template for property offers and reused it in a new report for
  salesmen's properties.
- Inherited the property report in the estate_account module to include invoice
  details for sold properties.

…access rule

- Added security groups for Real Estate Agents and Managers.
- Defined access rights for agents and managers for properties, types, and tags.
- Implemented a rule to restrict property access for agents based on assigned
  salesperson.
- Updated estate_account to bypass access rights in action_sold.

- Added a 'Properties' menu on the website to display available properties in a
  grid.
- Implemented image display for properties on the front-end.
- Added a pager with a maximum of 6 properties per page.
- Created a dedicated, mobile-friendly page for each property using Bootstrap
  components.

After this commit
- added different menus and sub-menus
- Implemented corresponding views

After this commit
- added controller so that dental will be visible in my account
- implemented invoice in dental

After this commit

- Created a DentalPortal to manage dental records on the portal.
- Added routes for viewing patient details, medical history,
  medical aid information, and dental history via the portal.
- Extended the portal_my_home template to include a Dental section for
  easy access.
- Implemented templates for viewing and managing dental records on the portal,
  providing a user-friendly interface for patients to view their details and
  history.

After this commit:
- implemented installment module
- added wizard button in subscription module
- implemented business logic

After this commit:

- Create models for account move, sale order, and res config settings.
- Implemented wizard for adding EMI with corresponding views.
- Update security access controls.
- Implemented views for res config settings and sale order.
- Implemented necessary data files for product setup.

…tory

After this commit:

- Added warranty configuration model and settings.
- Extended sale order and sale order line models to include warranty fields.
- Implemented warranty wizard for adding warranties to sale orders.
- Created views for managing warranty settings and applying warranties to
  products.
- Added security rules to control access to warranty features.