[ADD] real_estate,* : complete real estate module and inherit the estate account #838
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
|
|
prbo-odoo
force-pushed
the
18.0-training-prbo
branch
10 times, most recently
from
f4fbabf to
c63782b
Compare
maad-odoo
reviewed
Jul 10, 2025
prbo-odoo
changed the title
prbo-odoo
force-pushed
the
18.0-training-prbo
branch
12 times, most recently
from
defa40a to
71c6f3b
Compare
- Reviewed Odoo server architecture and understood how addons and modules are structured - Created a new Odoo app and added app details in the manifest — now visible on the dashboard - Defined a basic model with fields, installed the module and tested it through the UI
…r the model - Defined security access rules to control user permissions for viewing, creating and editing model records. - Added a menu item and corresponding action in the UI to enable easy navigation to the model. - Defined basic list and form views for visualizing and managing records within the Odoo interface.
Implemented an onchange method. Added action buttons to mark a property as Cancelled or Sold, with validation to prevent switching between these states. Created Accept and Refuse buttons for property offers, where accepting an offer sets the buyer (using a many2one relation with res.partner) and the selling price on the property. Also added a check to ensure only one offer can be accepted per property.
…operty models - Added inline list view of properties inside the Property Type form with limited fields for quick reference. - Implemented statusbar widget on the property form to visually indicate state changes. - Introduced default and manual record ordering using '_order' and 'sequence' fields. - Used handle widget for drag-and-drop ordering of property types and also added search filter
…rnal module - Extended model using inheritance to add accounting-specific fields. - Integrated features from another external module to show how models from different modules can work together. - update the user interface by adding custom fields with filters. - created new module (estate_account) to view the generated invoices.
- Improved variable naming and removed unused code. - Updated security rules and access rights. - Refactored code structure.
- Applied record rules and security groups to restrict user access based on roles. - Users can only view or modify records they are permitted to. - Defined initial data (user roles, property types, permissions) for consistent module setup.
prbo-odoo
force-pushed
the
18.0-training-prbo
branch
from
71c6f3b to
e6b30d7
Compare
prbo-odoo
changed the title
prbo-odoo
force-pushed
the
18.0-training-prbo
branch
from
e6b30d7 to
19f87ad
Compare
- Implemented custom QWeb PDF reports for real estate properties and offers. - extract offers table into reusable sub-template. - inherit and extend property report to include invoice info for sold properties. - update report styling and layout formatting from wkhtmltopdf package.
prbo-odoo
force-pushed
the
18.0-training-prbo
branch
3 times, most recently
from
919f6ba to
c8a1ab4
Compare
…oggle - Prevented new offers from being submitted on properties that are already sold. - Fixed the garden toggle so that when it’s unchecked, related fields like area and orientation are cleared. - Added test cases to verify offer restrictions and garden field behavior.
prbo-odoo
force-pushed
the
18.0-training-prbo
branch
from
c8a1ab4 to
76bab01
Compare
*= awesome_dashboard - Implemented Owl components: counter, card with props validation and todo list. - Developed a complete Todo List application(add, remove, mark as completed). - Adhered to proper folder structure. - Built awesome_dashboard - Fetched and displayed stats via RPC (/statistics route) - Added PieChart with lazy-loaded Chart.js
prbo-odoo
force-pushed
the
18.0-training-prbo
branch
from
5c158c4 to
277a26a
Compare
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.
*= estate_account
This pull request includes set up of real_eastate module. Included relational fields for offers, property types, tags and properties. Such as accepting/rejecting offers, constraint checking and support for various property states ( new, sold, canceled) was added to simulate in the module. Applied access controls so that only specific users can view or change certain data. Also created custom views like List, Form and Search so users can easily interact with the system. Invoices are automatically created when a property is sold, by connecting this module with the estate_account module.