[ADD] estate: add the real estate module #173
Draft
Conversation
This file contains 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
sahm-odoo
force-pushed
the
17.0-training-sahm-odoo
branch
from
edbe754
to
5f895b2
Compare
…Models) Completed the first three chapters of the Odoo developer tutorials. Set up the development environment. Created the real estate module and model with various fields. Established access rights for the model. Developed initial XML views for the module. Added relational models for estate properties, offers, tags, and types: Implemented One2many, Many2many, and Many2one relationships in models () Created basic views (search, list, form) for these models Implemented filters, groupby, and domain functionalities.
- Added computed fields for total area and best offer in estate property model. - Implemented inverse method for offer validity date computation. - Created onchange method to auto-fill garden area and orientation based on garden field.
…property - Added 'Cancel' and 'Sold' buttons to estate.property model with business logic. - Ensured canceled properties cannot be sold and sold properties cannot be canceled. - Added 'Accept' and 'Refuse' buttons to estate.property.offer model. - Set buyer and selling price when an offer is accepted. - Added SQL constraints to enforce unique property tag and type names. - Ensured property expected price, selling price, and offer price are strictly positive using SQL constraints. - Added Python constraint to validate selling price is at least 90% of the expected price.
Chapter 11 - Added inline list view for property types to display offers. - Implemented statusbar widget to show property states. - Established default sorting for property and offer models. - Introduced manual ordering for property types using a sequence field. - Enabled conditional display of buttons based on property state. - Applied color decorations to property and offer list views. - Made estate.property.offer and estate.property.tag list views editable. - Set default filter for 'Available' properties in the action. - Improved search functionality for living area filtering. - Added stat button to property type form to view related offers.
- Prevent deletion of properties unless their state is 'New' or 'Canceled'. - Ensure that new offers cannot be created with a price lower than existing offers and setting the state to 'Offer Received' upon creation. - Introduce a property_ids field in the res.users model, establishing a one-to-many relationship with properties, and applying a domain filter to show only properties in states 'New' or 'Offer Received'. - Extend the user form view to include the property_ids in a new notebook page. - Created a new module to connect the real estate and invoicing. - Modified the property sold action to automatically create a customer invoice with two line items. - Created a basic Kanban view to display property names in clickable cards. - Added fields for expected price, best price, selling price, and tags, with conditional visibility for prices. - Grouped properties by type by default and disabled drag-and-drop functionality.
- Added standard Real Estate Property Types: Residential, Commercial, Industrial, and Land. - Created demo data for the estate module with properties like Big Villa and Trailer Home. - Created demo data offers for properties, using partners (use ref) defined in base. - Set Property Type to Residential for both demo properties (use ref). - Validated one demo offer and refused the others using the function and eval. - Created a new Property with offers added directly to the One2many field using Command methods.
…odule - Added groups for real estate agents and managers. - Defined access rights: agents can read types/tags but cannot delete properties - Created record rules to restrict agents to only see/manage their own properties. - Updated estate_account to bypass security for confirming sales without full invoicing access.
sahm-odoo
force-pushed
the
17.0-training-sahm-odoo
branch
from
5f895b2
to
0cd5a6d
Compare
- Added a template to show property offers. - Enhanced the template to display a message if there are no offers. - Created a sub-template specifically for the offers table. - Built a report listing all properties for a user. - Used an inherited template and added a condition to display about invoice
…rties - Implemented 'Add Offer' wizard for adding offers on multiple properties - Added button in estate property tree view header to open wizard - Wizard includes fields for price, buyer selection - Added 'Make an Offer' button to execute offer creation and 'Cancel' button to exit
- Added a Properties menu to display unsold properties in a grid format. - Integrated image display for each property on the front-end. - Implemented pagination to display a maximum of 6 properties per page. - Ensured only properties that are not canceled or archived are listed. - Implement dedicated property page accessible via View Details link from property grid
…inventory - Developed the stock_transport module to establish a connection between fleet management and batch transfers within the inventory system. - Introduced max_weight and max_volume fields in fleet categories to specify capacity limits. - Modified the fleet vehicle model's display_name to include maximum weight and volume values (max_w, max_v). - Added computed fields weight and volume in stock batch picking to calculate the cumulative weight and volume of items within each batch. - Created the stock_install module to handle the installation of stock_transport through inventory settings.
- Added a Graph View to visualize key measures, including volume, weight, transfers, and lines. - Introduced a customized Gantt View - Modified the display name to provide better batch identification. - Set default grouping by Dock and Fleet together. - Included visual indicators such as decoration-success, decoration-info, and decoration-warning based on the batch’s status.
…fields - Made Print Label button visible only to Michell admin (user_admin). - Restricted visibility of fields in stock_transport module (category, vehicle, progress bar, dock, max_volume, max_weight, volume column) to Michell admin (user_admin).
- Added is_kit boolean field to identify kit products. - Added button to allow adding sub-products under main products. - Created wizard view to display sub-products. - Enabled addition of sub-products in order line, with automatic recalculation of unit price for main product. - Restricted editing of sub-product lines in order. - Implemented automatic deletion of sub-products when main product is deleted. - Added print_in_report boolean field to control display of sub-products in sale order, preview, and invoice reports.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
training