Problem
---------
Users may want to cancel several houses and flats at once, currently
this is not possible; they have to do it one by one.

Objective
---------
Add a way to cancel several estates in one go.

Solution
---------
Add a server action in the demo data so that it is available for new
users. Old users can create the same server action on their database.

task-123456

Problem
---------
Users may want to see the total area after adding the garden area and the living area, as well as the best offer after adding multiple offers
to the property. They also might want to either enter a validity number of days or a deadline, and the other should be computed automatically.

Objective
---------
Add a field (total area) dependant on two fields (garden and living area). Add another field which is the maximum of all offer prices.
Add a relation between the validity date and the deadline fields (after creating them).

Solution
---------
Add a computed field for the total area depending on garden and living area fields. Add a computed field for the best price depending on the
offer prices, computing the maximum of them all. Add an computed field for the date deadline and add both a compute and inverse function for it.

task-xxxxxx

…de their actions.

Problem
---------
Users may want to modify the property status through buttons, and see their actions reflected in the data. Same applies to the offer status.

Objective
---------
Add a sold and cancel button for the property, modify the status based on their activity.
Add accept and refuse buttons for the offers, modify the status based on their activity.
Reflect the actions of offers on the property data.

Solution
---------
Add a sold and cancel button in the header part of the XML file, alongside their functions applied on press.
Add a accept and refuse button in the list view of the offers.
Based on which is clicked, modify the selling price and the buyer of the property as well as the status of the offer.

task-xxxxxx

Problem
---------
Users may enter incorrect data like a negative expected or offer price. Also, they may create multiple property types and tags
of the same name. The selling price of a property shouldn't be less than 90% of the expected price.

Objective
---------
Add constraints to the field boxes (expected, selling, and offer price). The property tags and types should have constraints too.
Add constraints to prevent selling prices from being lower than 90% of the expected price.

Solution
---------
Added an SQL constraint checking the expected, selling, and offer price to be positive.
Added an SQL constraint to check the uniqueness of the property tags and types.
Added a Python constraint checking the selling price to be not lower than 90% of the expected price.

…ties in the user form

…nk with invoicing