We're very excited to announce Update 12 for Vision which launches 1st July 2019. Vision will be taken offline at 8 PM (BST) and will remain offline for up to two hours while we complete the update. We'll notify all users when services are back online.
A new simpler way of sharing
Sharing areas with people outside of your business was over-complicated and as a result, took far longer than it should with the majority of users staying away from the feature altogether. Clearly, this was not what we wanted and therefore Update 12 brings a complete overhaul of the sharing feature as well as a redesigned viewing platform for recipients.
To share an area in Update 12, simply click it and enable sharing from the action menu. Once you've done that, you can either copy the unique link or send an email directly from within Vision. It literally takes seconds!
What will happen to existing reports?
During the update, any shared reports that are active and have at least one specified user at the time of the update will be migrated into the new sharing platform.
Within each such report, an email will be automatically sent to each specified user providing a new link for each area within the report. Therefore, if a report contains 3 areas and 2 specified users, both users will receive 3 emails, one for each area providing them with continued access in the new sharing platform.
Unfortunately, we are unable to migrate any public reports automatically and as such these will need to be recreated manually after the update. We will be working with heavily affected users to give them as much information as we can and apologise for any inconvenience.
What will people I've shared an area with see?
When you share an area with someone in Vision, they'll automatically get access to that area, broken down by every level in your layer hierarchy. They'll also have access to demographic information - the demographics shown will be those you've chosen to show at the lowest level of geography.
So, for example, imagine you have created Territory A, Territory B, and Territory C out of Postcodes and then created Region 1 out of Territory A and Territory B. If you share a Territory (A, B, or C), they will be able to view that territory's boundary and they will be able to view the Postcodes within that territory's boundary. If, however, you share Region 1, they will be able to view the boundary for Region 1, and then also the boundaries for both Territory A and Territory B, as well as the boundaries for the Postcodes in both territories. They will be able to view demographic information at all levels. The demographics shown to them will be the ones chosen for display at the shared area level.
We're really excited about the new share viewer, and you can view an example we've created here.
A new demographic dashboard
Feature Pack 2 and above
The new demographic dashboard makes its exciting debut in Update 12 for Vision. Unlike, the demographic summary and demographic report which display only the chosen demographics for the layer, the demographic dashboard provides a detailed market report on an area you've created for all available demographics within your subscription in a format that's easy to view and simple to digest.
Improvements and Bug fixes
- We've noticed that the flashing notifications icon doesn't attract enough attention from our users. As the notifications are designed to bring you important information about Vision and your subscription, we've ensured that the notifications window will display by default when you log in and have unread notifications.
- We've fixed an issue where clicking on a multilocation icon or overlapping areas in a custom boundary layer before anything else would cause an error.
- We've fixed an issue which prevented the information window from closing if the user turned off a location layer and only results from a multilocation within that layer were displayed.
- We've fixed an issue which prevented the information window from closing if the user turned off an area layer and only results from an overlap of two or more areas within that layer were displayed.
Comments
0 comments
Article is closed for comments.