As we sat down to design MapWorks one of the ideas that we kept coming back to is that people, systems, and organizations are inevitably changing. What we are today isn’t what we were yesterday and isn’t what we will be tomorrow. (Because of this, we designed the features of our “Releases” module to allow you to keep track of the changes in your organization over time.) The MapWorks application itself isn’t immune to this notion. We will continually be enhancing and improving MapWorks to make it easier to use and more powerful. As we go along, we will keep you updated on what’s changing and how you can take advantage of these features.
So here’s what’s new in MapWorks in the 23 May 2017 release:
- A new Data Retention Period attribute was added to the Data Element to allow you to optionally collect and maintain information about how long data should be retained on the given Data Element.
- New attributes were added to the Mappings on Data Elements to allow you to capture the name of the job responsible for the movement of data, the system running that job and the frequency with which that job is run. These attributes are optional, so don’t worry if you don’t have this information.
- We improved the way deletions are handled on Systems and Tables. Previously, you had to remove all the Tables and Data Elements under the item being deleted before deleting the System or Table. Now, that is done in two clicks…one to request the deletion and one to confirm that you are sure (just in case).
- We also adjusted the way that MapWorks deals with potentially duplicate names. Now, MapWorks will allow you to add a new System, Table or Data Element with a duplicate name, but will add the word “duplicate” and a number to the new item to distinguish it from the original. This means you don’t have to think of a new name on the fly if the original name you had in mind is already being used. For example, if you try to name a new element CUSTOMER_NAME but you already have a CUSTOMER_NAME field in that table, MapWorks will automatically save the new element as CUSTOMER_NAME (duplicate 1). This way you don’t re-do your work or lose your train of thought while you are setting up the new element. Once you’ve saved it, you can go back and change CUSTOMER_NAME (duplicate 1) back to its proper name.
- Help links were added to the footer in MapWorks to make getting help if you get stuck even easier.
- We fixed a few minor formatting and layout bugs to make the application flow a little better.
Items #1 and #2 were improvements based on feedback we received at the TDWI conference in Chicago. We love getting this type of feedback and, as you can hopefully see, take it to heart. Once you’ve had a chance to try out our Free Trial , we would love to hear what you think and any suggestions you might have.