Available in app.mworks.com May 18, 2023
This sprint saw noticeable improvements to Point of Interest (POI) Manager and Placecast, but the bulk of interest is the release of User Account Management (UAM) 2.0 to our production environment.
The final item includes a list of remaining “Known Issues” that are still being resolved.
Users will notice a new User Account Management screen when they login. This new screen has the major addition of adding Accounts. Going forward this will allow for more sharing of scenarios, place sets and other work that users do with other users inside of their organization. This will also allow for us to create things like different permission level of users and licensing of features so that an Account can have an admin that creates and assign other users permission or various tools and data sets are available to specific accounts as examples.
We’ve enhanced our data tables to more standardize headers across applications. This specifically includes making uniform header text where the header will always state Created By, Date Created, Last Modified By and Last Modified when referring to those fields in a data table. More work is in progress to standardize the Table experience and will be pushed in future releases.
In order to facilitate more data requests for locations we’ve added locations that have an Audit Status of “Approximate” to now display the data that we have. This isn’t our Gold Standard of fully audited, verified and approved data but it’s a best guess on what information we do have, and it will now be available to you.
We’ve added the ability to add and remove vertices in drawn polygons. This will allow for more streamlined creation and editing of polygons. You will no longer have to redraw the entire things because you need to add an additional corner or cut one off. You can edit the polygon by updating vertices on the drawn shape.
When editing the parameters of an existing Placecast you would commonly run into the initial load of the editing screen hung on loading the initial data. This was specifically an issue around the default load of Prizm Profiles. We’ve cleaned up this caching and added additional instructions around what to do.
It’s come to our attention that having easy access to the Place ID is useful, so we’ve added this Place ID to the Individual Insights Summary Report and the print version of this report.
IMXDEV-2650 & IMXDEV-2651
When creating or editing a POI we’ve cleaned up some additional helpful functionality that allows users to Search Google for information on a place or go directly to a Street View map of the location. Now these options are initially greyed out and once information has been added to the place where they can be of use then they become clickable to the user to help get this additional information to doublecheck their work.
*If a pin is not located in a location that we can gain access to a Street Map we open the user up to a Google Maps search of the location from the available information.
IMXDEV-2635 & IMXDEV-2637
In order to make POI Manager more usable we’ve added additional information fields to the data table. Specifically, we’ve added City, State, Postal Code, and Country. These fields are also going to be filterable depending on the data type. For example, City will be text but State will be a multi-picklist filter for example. We’ve made these fields visible by default and hidden Country as the majority of our places currently are US only.
The graphs in Placecast Individual Insight Reports were having issues where certain text was the same as the background color in the graph. We’ve cleaned this up by ensuring that they are always different now and bringing the percent data outside to the bulleted list of values so that the information can be viewed either way.
We’ve cleaned up a bug where after generating a Placecast report if you went back into editing the places and place sets that were part of the report were not shown checked and selected. We’ve made these selected to more align with what a user would expect to see and show what is actively part of the current report.
If a user creates a Placecast report that has Places that do not have data currently available, we have been notifying the user when they load the report the number of places that are still awaiting data. What we did not do was notify the user when that data on those places becomes available. Now we send out an email notification to the user that information is now available. This helps them know when to come back to the platform and get their requested data.
Known Outstanding Issues
- IMXDEV-2660 - POI Manager - When creating a new place, the user-entered location information was overwritten
- IMXDEV-2570 - Placecast - How could Airport locations have 100% Local Visits and no long distance traffic?
- IMXDEV-2413 - Placecast - Data inconsistencies noticed by Sales - Data Reporting Weeks Issue
- IMXDEV-2333 - Placecast - Locations in MW Places search have empty Address Information
- IMXDEV-2648 - Placecast - Sort appears to break when a row has a Null "-" value - Population Profile Visits
Article is closed for comments.