Skip to content
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
wants to merge 22 commits into
base: 17.0
Choose a base branch
from

Conversation

yasp-odoo
Copy link

@yasp-odoo yasp-odoo commented Aug 14, 2024

  • 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.
@shag-odoo
Copy link

@yasp-odoo Could you please update your PR title as your module name is incorrect
and in PR description could you replace added with implemented.

Thanks 😇

@yasp-odoo 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 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 yasp-odoo force-pushed the 17.0-training-yasp branch 3 times, most recently from 9ef2d5b to edd5f07 Compare August 21, 2024 06:06
- 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.
- 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 yasp-odoo force-pushed the 17.0-training-yasp branch 2 times, most recently from 27fe108 to b16b19e Compare August 21, 2024 13:26
- 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.
- 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 yasp-odoo force-pushed the 17.0-training-yasp branch 4 times, most recently from 9a35853 to 7fb3561 Compare August 28, 2024 04:51
- Added an icon to the Estate main menu
…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.
- 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.
…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.
…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.
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 yasp-odoo force-pushed the 17.0-training-yasp branch 7 times, most recently from cfa3643 to f5573ca Compare September 10, 2024 11:05
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 yasp-odoo force-pushed the 17.0-training-yasp branch 2 times, most recently from b2bcbfb to 61a3332 Compare September 16, 2024 13:03
After this commit:
- implemented installment module
- added wizard button in subscription module
- implemented business logic
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 yasp-odoo force-pushed the 17.0-training-yasp branch 4 times, most recently from d841e67 to 60a23f3 Compare September 26, 2024 07:27
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants