L1 can now force HNs

Map Editors Community WME Production Bugs
1

Hi @maiapas
Just a quick note regarding the new feature allowing users to suggest “forced” HNs.

Before this update, forcing a HN was restricted to L4 editors and above. However, we’ve noticed today that editors of any level (even L1) can now force HNs, as long as the segment is locked at their level or lower.

This seems unintended, as forcing HNs bypasses important validation rules and could affect data quality.
Could you please confirm if this is expected behavior or something that needs to be reviewed?

Thanks!

2 Likes
2

Thank you daviaraujo93 for the report.

Do you have an example PL I could share with the team? Are you referring to directly adding forced HNs or suggesting them?

Thank you in advance for your insights!

1 Like
3

Here you are, an example where an L1 editor directly forced the HN 320 on segment.

As I noticed, this happens for all segments that are locked at or below their level. If the segment is locked at a higher level than the editor’s, it creates a suggestion, as it should be for all editors from L1 to L3 in Brazil. I don’t know what the default lock level is abroad.

1 Like
5

Thank you! I’ve opened an internal issue to investigate this case. I’ve also moved this to the Production Bugs forum so we can follow up here.

2 Likes