-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
17.0 training koye #152
Draft
koye-odoo
wants to merge
11
commits into
odoo:18.0
Choose a base branch
from
odoo-dev:17.0-training-koye
base: 18.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.
Draft
17.0 training koye #152
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
…iews - created a new estate module -defined init and manifest -created an estate_property model with the below fields and methods: -postcode,date_availability,selling_price,bed_rooms,facades.garden, orientation -compute_total,on_change,action_sold,action_cancel -created estate_property_type,tags,offers models and their corresponding views
…plates Added new features to the estate module, including the ability to generate comprehensive reports and the option to add dummy data for testing purposes. These enhancements improve the module's functionality and usability, allowing for better data visualization and easier testing scenarios.
- Created 'security.xml'`to define security groups for Real Estate users. - Added 'category' field to the `__manifest.py with value 'Real Estate/ Brokerage'. - Created security groups: - `estate_group_user` (Agent) with category ` base.module_category_real_estate_brokerage`. - `estate_group_manager` (Manager) which implies `estate_group_user`. - Configured user roles so real estate agents only have access to the Real Estate app. - Tested access control by logging in with a real estate agent user and verifying limited access.
- Implemented rule limiting agents to view/modify only properties with no salesperson or where they are the assigned salesperson. - Ensured real estate managers retain access to all properties. - Verified estate_group_manager inherits permissions from estate_group_user as required.
- Restricted the creation of Property Types and Tags to agents by updating access control rules. - Made the Settings menu only visible to estate managers and another group by adding group-based restrictions. - Applied multi-company rules to silo data access between different companies/agencies in the estate module.
…operties. - Added 'Add Offer' button in the estate property tree view header. - Enabled selection of multiple properties for offer creation. - Created wizard with fields for price, offer status, and buyer. - Included 'Make an Offer' button to handle business logic and 'Cancel' button for form cancellation.
[ADD] Warranty Configuration: - Inherited `product.template` to add `is_warranty_available` field. - Created warranty configuration model for managing product warranties. - Added wizard for showing add warranty button on relevant products.
- Created AddWarranty button to open a wizard for warranty management. - Implemented a wizard with an Add button to apply warranty to order lines if available. - Computed warranty price based on a percentage defined in the warranty configuration. - Integrated warranty product into the warranty configuration for better management.
- Created Add Warranty button to open a wizard for warranty management. - Implemented a wizard with an Add button to apply warranty to order lines if available. - Computed warranty price based on a percentage defined in the warranty configuration. - Integrated warranty product into the warranty configuration for better management.
- Created Add Warranty button to open a wizard for warranty management. - Implemented a wizard with an Add button to apply warranty to order lines if available. - Computed warranty price based on a percentage defined in the warranty configuration. - Integrated warranty product into the warranty configuration for better management.
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