Remember in the film 'Ghostbusters', there was a golden rule - Don't cross the streams? OK, i know, you're all too young to remember that film. So, no developer would expect to migrate to an upgraded platform and not find disparities and issues with their models as a result of improved functionality and added vital features. In the little time I've had to provisionally test BOARD 10.3.0 WEB on my own production models, I've picked up on one general issue that I hope will help other developers when planning their upgrade strategies and plans, which is:
OVERLAPPING OBJECTS ARE NOT ALLOWED
I've tested several of my production models and they all need some major screen layout re-working to function correctly due to labels overlapping objects or objects touching objects. In these occurrences, big blank white patches appear on the screen. Curiously, the size and shape of these voids do not relate to that of the objects causing the 'whiteout' patches; maybe the issue is caused by the preparation for mobile layout preferences and also due to the update to the functionality and/or upgraded behaviour of the SLIDING TOOLBAR in the top left of all objects?
I've tried to illustrate the issue with the following images - the data is 'fuzzy' as it has been deliberately pixellated:
Image 1: BOARD 10.1.4 WEB page as it originally was (I know there's an issue with 'Northern Ireland' and 'Offshore' Valuation Counts and the TOTAL of the bottom left Dataview too!).
Image 2: BOARD 10.1.4 mid-Data refresh - Looking closely, it can be seen that there are objects which overlap the pie chart array (middle left of the image)
Image 3: BOARD 10.3.0 outcome with a white patch where the Pie Charts should be. Also, the dataview bottom left has been affected as well as the Annual Rent Dataview, and last pie chart.
I can appreciate that BOARD Intl are transitioning us to BOARD 11 in steps with the strategy of releasing 10.3, 10.5 and finally 11.0 so that we can get used to the new features in a reasonable timeframe, prepare our teams for the changes and create solutions to development issues. To go from 10.1.4 to 11 and have to mitigate the design changes in one upgrade would be very hard.