Numerous 'Save' ui actions for Demand table.Issue Upgrade to London added new actions to existing tables like Demand [dmn_demand] like 'Save'.ReleaseALLCauseExpected behavior.ResolutionFrom reviewing these UI actions further, this appears to be working as expected. Notice of the 6 save ui actions there are only two different action names being used 'sysverb_update_and_stay' and 'sysverb_insert_and_stay'. Since these ui actions share the same action name, these will override each other depending on the conditions set. From reviewing the comments/scripts for each ui action, it can be determined that these are not duplicate records, but each created for a particular circumstance. As mentioned, this is also seen in an out of box instance starting in Kingston. From testing these do not appear to be causing any unexpected/incorrect behavior.