These changes were made in response to complaints that Recorder 6 was too lax in the way it allowed automatic matching and the creation of new names when there potentially already users in the database with the same name.   It isn't stopping users  from creating any names they wish, just that where the IW doesn't have  sufficient information to create a meaningful entry or where it would potentially create a duplicate entry then then it shoduln't be automatically making the entry.   

If you click on the search icon (Mag glass) in the notes column you will get a list of individuals who could potentially match, based not just on the exact matches, but looking at the name as a whole. From this list you can choose the match without the need to go through the laborious process of going into the individual hierarachy,  finding the name and returning it to the IW. In addition you get all the basic information to make a decision about which existing name is correct and the ability to find out more if you wish, like when they were recording and the groups recorded. It wasn't easy to get to this information before. If you do need to create a new individual then open then click in search  (Mag glass) in the Recorder matches column   which will open the Individual hierarchy where the name can be added and returned to the import wizard.

Clicking on the buttons at the top previously created new names with little consideration as to whether they already existed and with the minimum of information, allowing the creation of spurious names.  It is still  automatically adding names, but doesn't do so where the IW has insufficient information to choose the correct name ( ie there is potentially more than one) or where it seems that there isn't enough information about the individual to create a meaningful entry automatically. 

This approach seems right  for 'Make new Entries' where anything doubtful should not be created automatically. It isn't right  to apply this to 'Make New Entry' where the user  is in fact making the decision and this appears to have been a mistake, which will be treated as a bug. If it causes an immediate problem it can be fixed  by making a change to the stored procedure which does the matching. This would apply both to 'Make New Entries' and 'Make New Entry'. Treating the two differently is a  bit more complicated.