2.2.8.8 release notes
2.2.8.8 Issue 2426 - In Apex, it's technically valid to dereference System.Map.values() as a single instance of the map's value type, though only when the value type is some type of SObject , e.g., accountsByName.values()?.AccountNumber , and only when the map has exactly one entry. To be blunt, I don't like that allowed idiom for a few reasons. It feels unnecessary and unsafe—pay specific attention to the use of the safe navigation operator before accessing fields of the one-and-only map entry's value—and in order to provide proper support, it muddies the variant code completions offered for the values() method to include both instance methods of System.List and fields of the map's value type. Having said that, it is allowed and valid, so I've added support for it in IC2's expression type evaluator. Issue 2449 - Added support for email templates created and managed via the Lightning a...