Hello Everyone 
We hope you’re all doing well.
We’ve just released a new version of WME v2.305 
Below you can find a summary of the release.
New features/enhancements:
1. Suggest an Edit on House numbers: We introduced an improvement that ensures all relevant objects in an edit suggestion are visible when panning to it. From now on, we calculate the highest minimum zoom level required to display all entities included in the suggestion.
2. Upcoming A/B Testing Heads up: We are building infrastructure for A/B testing to be able to carefully evaluate how new features perform with various groups of editors. This infrastructure will likely be utilized later on for features, we’ll keep you updated regarding such instances.
3. Performance: We’d like to share that since the end of May, we’ve observed a 10–15% improvement in loading times, following a recent change in the Frontend client code.
4. Alignment of Suggest an edit (SAE) and On Segment suggestions (OSS): We’re introducing a new process to simplify and unify the suggestion submission experience. As our sources and system complexity have grown, the current setup has become inconsistent and difficult to maintain. The new phased approach will start by aligning OSS and SAE workflows to improve clarity and reduce support overhead. As part of the mentioned process, we’ve added some changes in this release. You can read about them in this document.
5. House numbers (HN) revamp: Previously, in both the add and edit flows, clicking the drag handle immediately after entering a number caused the marker to lose focus, interrupting the dragging action. Editors had to click the marker again before they could reposition it. This has been improved so editors can now type a number and immediately drag the marker without any extra clicks.
6. SDK improvements: please refer to the change log to check the SDK additions.
Bug fixes:
We released 10 bug fixes:
1. Suggest an Edit:
- We resolved an issue that a refresh was required in order to remove the lamp icon after suggestion acceptance.
- We fixed an issue where the House Number and Segment layers were turned off while reviewing suggestions — both layers will now be automatically enabled to ensure proper visibility. The snackbar will include all layer names that were toggled.
- Resolved an issue where, after changing a house number, the existing number was still displayed. Now, the suggested number is shown on hover.
- We made a change in order to prevent confusion: the top info alert ‘You can make changes to your edit…’ will no longer appear for editors who don’t have permission to apply suggestions (i.e., when the Apply button is hidden). This removes guidance that isn’t actionable or relevant.
2. House numbers (HN) revamp: We resolved an issue where house numbers could not be saved if they were added twice and then corrected during editing.
3. Junction nodes: Resolved an issue where segments could not be connected upon dragging nodes.
4. Map Events Filtering / Duplicating: Resolved an issue where the app crashed after undoing the duplication of a ‘Local Driving Advisory’ category event (this category is only visible to Waze Partners).
5. Suggestions on Turns: Addressed the issue where submitting a suggestion to enable a U-turn caused a crash.
6. Permanent hazards: Fixed an issue where moving a segment with a permanent hazard did not activate the Permanent Hazard layer.
7. Segment: Creating a segment from node to node fails with client side error - fixed.
Known issues:
-
Alignment of Suggest an edit (SAE) and On Segment suggestions (OSS):
- In case changes already applied to the map both ‘Apply’ and ‘Reject’ buttons are enabled
- In case the user opens Accepted card from the history the body will be old
-
Suggest an Edit on House numbers (HN): already added suggestions are added to the save stack.
We look forward to hearing your feedback! 
Thank you,
Olesya
