The biggest problem of bulk changes or bulk updates is that it is easy at the same time - reviewing the changes is definitely time consuming. The crux of the problem lies in the fact that we may not exactly know how many records are updated. Right now we get an indicator saying 'X' records have been updated, but it may always be different from the number of records you wanted to update. Say you wanted to update 100 records, but the final toaster message says only 20 records have been updated, a common user may not know why this has happened. There can be many factors to this - such as records in review etc.. An estimate giving how many will be updated and a message saying why the other records will not be updated will be extremely useful to take appropriate actions.
This definitely reduce the complexity of maintaining the Content Repository.
Created date : 2023-02-15
Votes : 5
Comments for the idea :
