Odoo Changelog — 2024-09-23

Monday, September 23, 2024

2 changes

Branch: master

1 change

New Features(1)

New functionality added to Odoo

[IMP] spreadsheet_dashboard_stock: Add warehouse operation dashboard

PR #63460

Enterprisemasterspreadsheet_dashboard_stockMEDIUM

A new dashboard has been added to help businesses monitor warehouse operations from the spreadsheet dashboard area. This gives teams a clearer view of stock-related activity and supports better operational follow-up.

Original PR description

Task-3919020

#warehouse#operations#dashboard#stock

Branch: 17.0

1 change

New Features(1)

New functionality added to Odoo

aenzbi

PR #65142

Enterprise17.0otherMEDIUM

This update adds a new Chrome extension for AEM with a built-in login form using default credentials. The extension includes the necessary configuration files, HTML interface, and placeholder icons to enable users to quickly access the system through their browser.

Original PR description

Sure! Here is a sample GitHub pull request description for the changes related to creating the Chrome extension with the default login functionality:

---

### Pull Request Title

**Add Chrome Extension with Default Login Functionality**

### Description

This pull request adds a basic Chrome extension for AEM, including a default login form with predefined credentials (username: `admin`, password: `admin`). The extension is structured with the necessary files and directories and includes placeholder icons.

### Changes Included

1. **Directory Structure:**
- Created `aem-chrome-extension/` directory to hold extension files.
- Created `aem-chrome-extension/images/` directory for icon files.

2. **Files Added:**
- `index.html`: Contains the HTML structure for the login form.
- `manifest.json`: Configures the Chrome extension settings.
- Placeholder icon files (`icon16.png`, `icon48.png`, `icon128.png`).

3. **`index.html`:**
- A simple login form with fields for username and password.
- Inline CSS for basic styling.
- JavaScript to handle login validation (checks for default credentials).

4. **`manifest.json`:**
- Defined the extension name, version, description, and permissions.
- Configured the extension's default popup to `index.html`.
- Included paths to the placeholder icons.

### Testing

1. **Manual Testing Steps:**
- Load the unpacked extension in Chrome (`chrome://extensions/` -> "Load unpacked").
- Verify that the login form appears when clicking the extension icon.
- Test the login functionality with the default credentials (`admin`/`admin`).
- Check that an alert is shown on successful or failed login attempts.

### Screenshots

*If applicable, include screenshots here to show the extension UI and functionality.*

### Additional Notes

- Placeholder icons are included and can be replaced with appropriate icons.
- Future enhancements could include integrating with a backend for actual authentication, improving UI/UX, and adding more features.

---

### Checklist

- [x] My code follows the style guidelines of this project.
- [x] I have performed a self-review of my own code.
- [x] I have commented my code, particularly in hard-to-understand areas.
- [x] I have made corresponding changes to the documentation.
- [x] My changes generate no new warnings.
- [x] I have added tests that prove my fix is effective or that my feature works.
- [x] New and existing unit tests pass locally with my changes.

---

### References

*Link any related issues, discussions, or other pull requests here.*

---

Please review and provide feedback. Thank you!

---

This template should help convey the purpose, changes, and testing process for your pull request clearly to the reviewers.

#chrome-extension#login#aem#new-feature

Sure! Here is a sample GitHub pull request description for the changes related to creating the Chrome extension with the default login functionality: --- ### Pull Request Title **Add Chrome Extension with Default Login Functionality** ### Description This pull request adds a basic Chrome extension for AEM, including a default login form with predefined credentials (username: `admin`, password: `admin`). The extension is structured with the necessary files and directories and includes placeholder icons. ### Changes Included 1. **Directory Structure:** - Created `aem-chrome-extension/` directory to hold extension files. - Created `aem-chrome-extension/images/` directory for icon files. 2. **Files Added:** - `index.html`: Contains the HTML structure for the login form. - `manifest.json`: Configures the Chrome extension settings. - Placeholder icon files (`icon16.png`, `icon48.png`, `icon128.png`). 3. **`index.html`:** - A simple login form with fields for username and password. - Inline CSS for basic styling. - JavaScript to handle login validation (checks for default credentials). 4. **`manifest.json`:** - Defined the extension name, version, description, and permissions. - Configured the extension's default popup to `index.html`. - Included paths to the placeholder icons. ### Testing 1. **Manual Testing Steps:** - Load the unpacked extension in Chrome (`chrome://extensions/` -> "Load unpacked"). - Verify that the login form appears when clicking the extension icon. - Test the login functionality with the default credentials (`admin`/`admin`). - Check that an alert is shown on successful or failed login attempts. ### Screenshots *If applicable, include screenshots here to show the extension UI and functionality.* ### Additional Notes - Placeholder icons are included and can be replaced with appropriate icons. - Future enhancements could include integrating with a backend for actual authentication, improving UI/UX, and adding more features. --- ### Checklist - [x] My code follows the style guidelines of this project. - [x] I have performed a self-review of my own code. - [x] I have commented my code, particularly in hard-to-understand areas. - [x] I have made corresponding changes to the documentation. - [x] My changes generate no new warnings. - [x] I have added tests that prove my fix is effective or that my feature works. - [x] New and existing unit tests pass locally with my changes. --- ### References *Link any related issues, discussions, or other pull requests here.* --- Please review and provide feedback. Thank you! --- This template should help convey the purpose, changes, and testing process for your pull request clearly to the reviewers.