Loading
Sales Productivity
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Manage Version Settings for Visualforce Email Templates in Salesforce Classic

            You are here:

            1. Salesforce Help
            2. Docs
            3. Seller Productivity

            Manage Version Settings for Visualforce Email Templates in Salesforce Classic

            To aid backwards-compatibility, each Visualforce email template is saved with version settings for the specified version of Visualforce and the API. If the Visualforce email template references installed managed packages, the version settings for each managed package referenced by the Visualforce component are saved too. Saving version settings ensures that as Visualforce, the API, and the components in managed packages evolve in subsequent versions, a Visualforce email template is still bound to versions with specific, known behavior.

            Required Editions

            Available in: Salesforce Classic

            Available in: Group, Enterprise, Performance, Unlimited, Developer, and Contact Manager Editions

            Mass email not available in: Personal, Contact Manager, and Group Editions

            User Permissions Needed
            To set version settings for Visualforce email templates: Customize Application

            A package version is a number that identifies the set of components uploaded in a package. The version number has the format majorNumber.minorNumber.patchNumber (for example, 2.1.3). The major and minor numbers increase to a chosen value during every major release. The patchNumber is generated and updated only for a patch release. Publishers can use package versions to evolve the components in their managed packages gracefully by releasing subsequent package versions without breaking existing customer integrations using the package.

            1. Choose one of these options.
              • If you have permission to edit public templates, from Setup, enter Email Templates in the Quick Find box, then select Classic Email Templates.
              • If you don’t have permission to edit public templates, go to your personal settings. Enter Templates in the Quick Find box, then select Email Templates or My Templates—whichever one appears.
            2. Click the Email Template Name for the Visualforce email template.
            3. Click Edit Template and then click Version Settings.
            4. To specify the Salesforce API and Visualforce version for the template, select the Version of the Salesforce API.
              The API version is also the version of Visualforce used with this template.
            5. To configure the package version settings for the template, select a Version for each managed package referenced by the Visualforce email template. This version of the managed package is used by the Visualforce email template if later versions of the managed package are installed, unless you manually update the version setting. To add an installed managed package to the settings list, select a package from the list of available packages. The list is only displayed if you have an installed managed package that is not already associated with the Visualforce email template.
            6. Click Save.

            Note the following when working with package version settings:

            • If you save a Visualforce email template that references a managed package without specifying a version of the managed package, the Visualforce email template is automatically associated with the latest installed version of the managed package.
            • If a Visualforce email template references a managed package, you can’t remove the email template's version setting for the managed package.

            See Also

             
            Loading
            Salesforce Help | Article