gicha - Technical Training #1080
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This create a new module to handle estate property. It add a new Property model with its base fields.
This create the security/ir.model.access.csv file to give full access on the estate.property model for base.group_user group.
This create an action to display the form and list views for the property model and link it to a new menu. This also updates existing fields with attributes and adds new fields to the model.
…oup by. This will updates the form view, grouping field and adding a notebook with tabs, the list view, adding more field into the list, and the search view, allowing the search to be made using more fields. This will also create a new available filter, to only show properties that are still purchasable and a new group by postcode.
…esperson. This will allow for each property to select a property type, select a partner as buyer and a user as a salesperson.
This swill add the ability to create tags through the settings and link them to properties. It will also allow to create offers for a property directly from the property form. Each offer is linked to a partner, with a set price and a property.
This will add new computed fields in the models: - total_area in estate.property, computed as the sum of living_area and garden_area - best_price in estate.property, computed as the max price of the property offers (offer_ids) - date_deadline in estate.property.offer, computed as the sum of create_date and validity. As create_date is only set after creating the record, an alternative using fields.Date.today() function has been set to avoid crashes when creating an offer. This will also add an inverse function for date_deadline, allowing to set the deadline manually and computing the availibility value instead.
|
|
This will add a new onchange function to the estate.property model to set the garden_area and garden_orientation fields value when changing the value of the garden field.
…erty.offer list view. This will allow to quickly set a property as sold or cancelled, directly from the form view. The functions prevent to set a cancelled property as sold, and to set a sold property as cancelled by raising an UserError Exception. This will also allow to quickly set an offer as accepted or refused and update the linked property selling_price and buyer. The refuse action function will clear the selling_price and buyer of the property if it was in the accepted status before.
This will add constraints to the estate models to prevent user to encode inconsistent values. Here are the applied constraints : - The value of the expected price must be strictly positive - The value of on offer and selling_price must be positive - The name of property tags and property types must be unique - The selling_price must be at least 90% of the expected_price
This will : - add an inline list view of properties into the property type view. - add the state of a property as a widget in the property form view to allow user to easily visualize the field value. - add default ordering rules to property, offer and tag list views, and a manual reordering for the property types using a new sequence field (int). - allow the user to select a color for each tag, using the many2many_tags widget and a new color field. - make the "sold" and "cancel" button on the property view invisible when the property is marked as sold or cancelled. - make the garden related fields invisible in property form when the garden field is not selected. - make the date_availability optional and hidden by default on the property list view. - add the tag_ids field in the property list view, using the same widget and color option as in the form view. - make the offer editable in the list view to allow users to create or update offer without leaving the property form. - add conditional color into the property and offer list view to allow the user th easily visualize the state and status without accessing the form view or reading the field value - remove the status field from the offer list view, because the color code is enough for the users. - add automatic state update for the property : new on create or when there are no offers, offer_received after create one offer, offer_accepted when accepting an offer, sold when confirming the sale.
… view. This will add a new field to estate.property.type to store the number of offer. This value will be displayed as a smart button on the form view of the model. It will allow the user to display all offer related to a property type from the property tye form view. A domain was defined with the action to only display the offer related to the current type.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.