Save time managing your picklists. You can now delete, activate, deactivate, or replace multiple custom picklist field values at once. Previously, you modified them one at a time. This feature is available in production and in sandbox orgs.

Where: This change applies to Lightning Experience and Salesforce Classic in all editions.

How: Opt in to Advanced Picklist Values Management (beta) from the Picklist Settings page. Then navigate to the custom field definition page. The Values and Inactive Values sections show a checkbox next to each picklist value. You can select multiple values and use one of the new buttons: Delete Selected, Deactivate Selected, Replace Selected, or Activate Selected. This feature is available only for custom picklists with predefined values.

Bulk Manage Picklist Values (Beta) (salesforce.com)

Manage your inactive picklist values and enforce limits on inactive values for custom picklists to improve system performance and overall health. You can now bulk delete inactive unused picklist values. Previously, custom picklists with many inactive values were difficult to maintain because you deleted inactive values one at a time.

Where: This change applies to Lightning Experience and Salesforce Classic in all editions.

How: Opt in to Bulk Delete Inactive Picklist Values (beta) from the Picklist Settings page. From the Inactive Values section of the picklist field, click Delete Unused Values. This feature is available only for custom picklists with predefined values.

After you delete unused values, if a picklist is unbound and the total number of inactive values falls below the limit, the picklist is set to bound.

Clean Up Inactive Picklist Values (Beta) (salesforce.com)

Improve address data accuracy and your users’ experience with Custom Address Fields. For example, add a Warehouse Address field to a standard or custom object. Your users can enter a custom address, or they can use the Google lookup to search for an address. Then you can access each address that’s stored in a custom address field, either as a structured compound data type or as individual address components. This feature, now generally available, includes some changes since the last release.

Where: This change applies to Lightning Experience and Salesforce Classic in all editions.

Why: There are several changes in this release. Custom address fields are now supported for dynamic forms for Flows. If the end user’s personal language is a fully supported or end-user language in Salesforce, the labels for the components of a custom address now appear in that language. You can add a state in the State and Country picklist with a name and code that match the name and code of an existing state in another country. And the documentation now clarifies expected behavior for address fields around marking fields as required and load times.

The beta process uncovered some new limitations. Custom address fields aren’t supported for Lead Conversion, Approval Process, or the address component of Flows. And Salesforce hasn’t validated custom address fields in Community Profile or Data Export.

How: Before you enable custom address fields, review Custom Address Fields Requirements and Limitations. Custom address fields use the State and Country picklists. By default, all countries, territories, and their states and provinces are visible to users. To specify the available picklist values in Salesforce, configure State and Country/Territory Picklists before you enable custom address fields.

Deliver to Your Customers with Custom Address Fields (Generally Available) (salesforce.com)

Create custom fields that mimic the behavior of standard address fields. Manage your inactive picklist values and enforce limits on inactive values for custom picklists to improve system performance and overall health. Bulk delete all the inactive values for a picklist field. Save more time managing your picklists with the ability to delete, activate, deactivate, or replace multiple custom picklist field values at once in sandboxes and in production.

• Deliver to Your Customers with Custom Address Fields (Generally Available)
  Improve address data accuracy and your users’ experience with Custom Address Fields. For example, add a Warehouse Address field to a standard or custom object. Your users can enter a custom address, or they can use the Google lookup to search for an address. Then you can access each address that’s stored in a custom address field, either as a structured compound data type or as individual address components. This feature, now generally available, includes some changes since the last release.
• Clean Up Inactive Picklist Values (Beta)
  Manage your inactive picklist values and enforce limits on inactive values for custom picklists to improve system performance and overall health. You can now bulk delete inactive unused picklist values. Previously, custom picklists with many inactive values were difficult to maintain because you deleted inactive values one at a time.
• Bulk Manage Picklist Values (Beta)
  Save time managing your picklists. You can now delete, activate, deactivate, or replace multiple custom picklist field values at once. Previously, you modified them one at a time. This feature is available in production and in sandbox orgs.

Fields (salesforce.com)