UIWeb revenue batching usability really needs to be addressed. 1) The apply commitment window pops up any time a donor is entered. We only want it to pop us if the designation entered and the constituent is the same as the commitment they have. This causes performance issues because it checks for every donation as well as processing issues. 2) The performance on batch 'loading' is extremely cumbersome and you sometimes don't know when you need to wait. For example: after entering the first line of information and you go to the next line to enter the next gift, the system does not say loading and when you begin to enter the next id it only selects the last few digits you entered in. Then it becomes a loop so that you have to enter in the ID in the constituent search to get this to work. 3) We also noticed that when you do update status it doesn't save the batch and take you back to batch enter so you can commit the batch. It stays in the batch, this is different than 2.9 and that works better. Saves time.