-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ADD] estate: initial setup of models, views, and constraints #114
Open
yasp-odoo
wants to merge
22
commits into
odoo:17.0
Choose a base branch
from
odoo-dev:17.0-training-yasp
base: 17.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
yasp-odoo
commented
Aug 14, 2024
•
edited
Loading
edited
- Implemented models for estate.property.offer and estate.property.type.
- Implemented views for managing property offers and types, including forms and lists.
- Established core logic for handling property offers, including validation and status management.
- Set up initial data integrity constraints and default behaviors.
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.
@yasp-odoo Could you please update your PR title as your module name is incorrect Thanks 😇 |
yasp-odoo
changed the title
[ADD] estate_module: Initial setup of models, views, and constraints
[ADD] estate: Initial setup of models, views, and constraints
Aug 14, 2024
yasp-odoo
changed the title
[ADD] estate: Initial setup of models, views, and constraints
[ADD] estate: initial setup of models, views, and constraints
Aug 14, 2024
…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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
3 times, most recently
from
August 21, 2024 06:06
9ef2d5b
to
edd5f07
Compare
- 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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
August 21, 2024 06:08
edd5f07
to
a88922e
Compare
- 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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
2 times, most recently
from
August 21, 2024 13:26
27fe108
to
b16b19e
Compare
- 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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
August 22, 2024 10:46
65d87c6
to
ede8d3e
Compare
- 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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
4 times, most recently
from
August 28, 2024 04:51
9a35853
to
7fb3561
Compare
- Added an icon to the Estate main menu
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
August 28, 2024 04:57
7fb3561
to
644cd99
Compare
…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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
August 30, 2024 09:25
18a81e5
to
ca2a277
Compare
- 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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
September 3, 2024 05:48
96192d0
to
6768402
Compare
…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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
September 3, 2024 05:52
6768402
to
458794c
Compare
…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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
September 3, 2024 12:24
d571d82
to
1cd5df5
Compare
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
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
7 times, most recently
from
September 10, 2024 11:05
cfa3643
to
f5573ca
Compare
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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
2 times, most recently
from
September 16, 2024 13:03
b2bcbfb
to
61a3332
Compare
After this commit: - implemented installment module - added wizard button in subscription module - implemented business logic
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
September 17, 2024 09:16
61a3332
to
b7e46d2
Compare
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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
4 times, most recently
from
September 26, 2024 07:27
d841e67
to
60a23f3
Compare
…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.
yasp-odoo
force-pushed
the
17.0-training-yasp
branch
from
September 26, 2024 07:50
60a23f3
to
a7c8e66
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.