1. From Setup, enter API in the Quick Find box, then select API.
2. Click Generate Enterprise WSDL.
3. Select the Package Version for each of your installed managed packages. If you are unsure which package version to select, you should leave the default, which is the latest package version.
4. Click Generate.
5. Use the File menu in your browser to save the WSDL to your computer.
6. On your computer, import the local copy of the WSDL document into your development environment.

---

1. From Setup, enter External Data Sources in the QuickFind box, then select External Data Sources.
2. Click New External Data Source, or clickEdit to modify an existing external data source.
3. Complete the fields.FieldDescriptionLabelA user-friendly name for theexternal data source. The label is displayed in the Salesforceuser interface, such as in list views.If you set Identity Type to Per User, this label appears when your users view or edit their authentication settings for external systems.NameA unique identifier that’sused to refer to this external data source definition throughthe API.The name can contain only underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.TypeSelect Salesforce Connect: Custom—.If you change and save a DataSource.Connection class, resave thecorresponding DataSource.Providerclass. Otherwise, when you define the external data source, the customadapter doesn’t appear as an option for the Type field.URLURL of the external system.Available only when the DataSource.Provider class declares theREQUIRE_ENDPOINT capability. If the class also declares the REQUIRE_HTTPS capability, the URL must begin with https://.If the endpoint is defined in a named credential, enter the named credential URL. A named credential URL contains the scheme callout:, the name of the named credential, and an optional path. For example: callout:My_Named_Credential/some_path.You can append a query string to a named credential URL. Use a question mark (?) as the separator between the named credential URL and the query string. For example: callout:My_Named_Credential/some_path?format=json.Writable External ObjectsLets the Lightningplatform and users in this org create, update, and deleterecords for external objects associated with the external datasource. The external object data is stored outside the org. Bydefault, external objects are read only.High Data VolumeSalesforce enforcesrate limits for retrieving and viewing data from externalsystems. If your org hits rate limits when accessing external objects, consider selecting the High Data Volume option on the associated external data sources. Doing so bypasses most rate limits, but some special behaviors and limitations apply. See High Data Volume Considerations for Salesforce Connect—CustomAdapters.CertificateIf you specify acertificate, your Salesforce org supplies it when establishingeach two-way SSL connection with the external system. The certificate is used for digital signatures, which verify that requests are coming from your Salesforce org.Available only when the DataSource.Provider class declares the CERTIFICATE authentication capability.Identity TypeDetermines whetheryou're using one set or multiple sets of credentials to accessthe external system. See Identity Type for External Data Sources.Available only when the DataSource.Provider class declares theBASIC or OAUTH authentication capability.
4. Select the authentication protocol.If you select Password Authentication, enter the username and password for accessing the external system.Password authentication is available only when the DataSource.Provider class declares the BASIC authentication capability.If you select OAuth2.0, complete the following fields.OAuth 2.0 is available only when the DataSource.Provider class declares theOAUTH authentication capability.FieldDescriptionAuthenticationProviderChoose theprovider. See External Authentication Providers.ScopeSpecifies the scope ofpermissions to request for the access token.Your authentication provider determines the allowed values. See Use the Scope Parameter.NoteThe value that you enter replaces the DefaultScopes value that’s defined in the specified authentication provider.Whether scopes are defined can affect whether each OAuth flow prompts the user with a consent screen.We recommend that you request a refresh token or offline access. Otherwise, when the token expires, you lose access to the external system.StartAuthentication Flow on SaveToauthenticate to the external system and obtain an OAuth token,select this checkbox.This authentication process is called an OAuth flow.When you click Save, the external system prompts you to log in. After successful login, the external system grants you an OAuth token for accessing its data from this org.Redo the OAuth flow when you need a new token—for example, if the token expires—or if you edit the Scope or AuthenticationProvider fields.
5. If you select Password Authentication, enter the username and password for accessing the external system.Password authentication is available only when the DataSource.Provider class declares the BASIC authentication capability.
6. If you select OAuth2.0, complete the following fields.OAuth 2.0 is available only when the DataSource.Provider class declares theOAUTH authentication capability.FieldDescriptionAuthenticationProviderChoose theprovider. See External Authentication Providers.ScopeSpecifies the scope ofpermissions to request for the access token.Your authentication provider determines the allowed values. See Use the Scope Parameter.NoteThe value that you enter replaces the DefaultScopes value that’s defined in the specified authentication provider.Whether scopes are defined can affect whether each OAuth flow prompts the user with a consent screen.We recommend that you request a refresh token or offline access. Otherwise, when the token expires, you lose access to the external system.StartAuthentication Flow on SaveToauthenticate to the external system and obtain an OAuth token,select this checkbox.This authentication process is called an OAuth flow.When you click Save, the external system prompts you to log in. After successful login, the external system grants you an OAuth token for accessing its data from this org.Redo the OAuth flow when you need a new token—for example, if the token expires—or if you edit the Scope or AuthenticationProvider fields.
7. The value that you enter replaces the DefaultScopes value that’s defined in the specified authentication provider.
8. Whether scopes are defined can affect whether each OAuth flow prompts the user with a consent screen.
9. We recommend that you request a refresh token or offline access. Otherwise, when the token expires, you lose access to the external system.
10. Click Save.
11. Click Validate and Sync, and confirm that the connection issuccessful.This step also invokes the sync() method on the DataSource.Connection class to obtain the list of tables that you can sync to create external objects and their fields.
12. Optionally, select tables and click Sync to do the following for each selected table.Automatically create aSalesforce external object.Automatically create a customfield for each table column that’s compatible with a Salesforcemetadata field type.Note Before you sync, make sure that you understand the considerations that are described in these topics.Sync Considerations for Salesforce Connect—All AdaptersSync Considerations for Salesforce Connect—Custom AdapterYou can instead choose to manually create the external objects and custom fields that map to the external data. Doing so lets you customize the external object names, decide which table columns to create custom fields for, and customize the custom field names. However, this approach takes longer and requires manual maintenance.
13. Automatically create aSalesforce external object.
14. Automatically create a customfield for each table column that’s compatible with a Salesforcemetadata field type.
15. Sync Considerations for Salesforce Connect—All Adapters
16. Sync Considerations for Salesforce Connect—Custom Adapter

---

1. From Setup, enter Permission Sets in the Quick Find box, then select Permission Sets.
2. Click an existing permission set or create one.
3. In the System Permissions section, click Edit.
4. Select the edit feed post permissions you want to enable.Select Edit My Own Posts to allow users that are assigned this custom profile to edit their own posts and comments.Select Edit Posts on Records I Own to allow users that are assigned this custom profile to edit posts and comments on records they own, including posts and comments made by other users.Select Can Approve Feed Post and Comment to allow users that are assigned this custom profile to edit or delete posts and comments, including posts and comments made by others, in any feed they have access to.
5. Select Edit My Own Posts to allow users that are assigned this custom profile to edit their own posts and comments.
6. Select Edit Posts on Records I Own to allow users that are assigned this custom profile to edit posts and comments on records they own, including posts and comments made by other users.
7. Select Can Approve Feed Post and Comment to allow users that are assigned this custom profile to edit or delete posts and comments, including posts and comments made by others, in any feed they have access to.
8. Click Save.
9. Assign the permission set to the users who need the permissions.

---

1. Select the data extension to link.
2. Click Continue.
3. Follow the How to Link Data Extensions procedures to link the data extensions.

---

1. From Setup, enter Public Groups in the Quick Find box, then select Public Groups.
2. Click New, or click Edit next to the group you want to edit.
3. Enter the following information:FieldDescriptionLabelThe name used to refer to the group in any user interfacepages.Group Name (public groups only)The unique name used by the API and managed packages.Grant Access Using Hierarchies (public groupsonly)Select Grant Access Using Hierarchiesto allow automatic access to records using your role hierarchies.When selected, any records shared with users in this group are alsoshared with users higher in the hierarchy. DeselectGrant Access Using Hierarchies ifyou’re creating a public group with All Internal Users asmembers, which optimizes performance for sharing records withgroups.Note If Grant Access UsingHierarchies is deselected, users that are higher inthe role hierarchy don’t receive automatic access. However,some users—such as those with the “View All”and “Modify All” object permissions and the“View All Data” and “Modify All Data”system permissions—can still access records theydon’t own.SearchFrom the Search drop-down list,select the type of member to add.If you don’t see the member you want to add,enter keywords in the search box and click Find.Note Foraccount owners to see child records owned by high-volume portalusers, they must be members of any portal share groups with accessto the portal users' data.Selected MembersSelect members from the Available Members box, andclick Add to add them to the group.Selected Delegated GroupsIn this list, specify any delegated administration groups whosemembers can add or remove members from this public group. Selectgroups from the Available Delegated Groups box, and then clickAdd. This list appears only in publicgroups.
4. Click Save.Note When you edit groups, sharing rules are automatically reevaluated to add or removeaccess as needed. If these changes affect too many records at once, a message appearswarning that the sharing rules aren’t automatically reevaluated, and you must manuallyrecalculate them.

---

1. Navigate to the Lightning App Builder.In Lightning Experience:From Setup, in the Quick Find box, enterOutlook, and then select Lightning for Outlookand Sync. Click Let users access Salesforce records fromOutlook. Click New under Email Application Panes. Follow the steps until you reach the design window.If you‘re adding Inbox components, click New InboxBeta Pane. Follow the steps until you reach the design window. In Salesforce Classic:From Setup, in the Quick Find box, enter AppBuilder, and then select New under Lightning Pages. Select Email Application Pane. Follow the steps until you reach the design window.
2. In Lightning Experience:From Setup, in the Quick Find box, enterOutlook, and then select Lightning for Outlookand Sync. Click Let users access Salesforce records fromOutlook. Click New under Email Application Panes. Follow the steps until you reach the design window.If you‘re adding Inbox components, click New InboxBeta Pane. Follow the steps until you reach the design window.
3. In Salesforce Classic:From Setup, in the Quick Find box, enter AppBuilder, and then select New under Lightning Pages. Select Email Application Pane. Follow the steps until you reach the design window.
4. Drag components onto the pane, and arrange them in the order you want them to appear.
5. Click the empty area of the canvas to view the page properties, add a description, or create a filter with criteria that determines when a component is shown.Tip Some components are useful when reading emails or viewing events whileothers are useful when composing emails or editing events. Use a filter to determinewhen a particular component is shown.
6. Click Save.
7. You’re ready to activate the pane and assign it to user profiles. Go to the Lightning App Builder to activate. You can also assign the pane to user profiles using the Set Page Assignment options in the Lightning for Outlook and Sync setup page.

---

1. From Setup, enter Transaction in the QuickFind box, select Transaction Security, and then click Create Policy in Transaction Security Policies.
2. First select what your policy monitors. Choose a category and then select an event or entity in that category.The categories are:Data Export—Notifies you when the selected object type has been exported. To trigger a policy, the export must be done using a default report type from the Report tab or with an API client like Data Loader or Workbench.Note You can’t create a Data Export event policy for joined reports, historical reports, or custom report types.Login—A user login. You can trigger your policy on many types of login events.Resource Access—Notifies you when the selected resource has been accessed. You can block access or require two-factor authentication before access is allowed.Note AccessResource event policies don't trigger when Dashboard Subscriptions send an email. These policies still trigger when users access resources directly from a dashboard.Entity—An object type.Note Lightning Experience supports only the Feed Comment and Feed Item resources, while Salesforce Classic supports all Chatter resources.
3. Data Export—Notifies you when the selected object type has been exported. To trigger a policy, the export must be done using a default report type from the Report tab or with an API client like Data Loader or Workbench.Note You can’t create a Data Export event policy for joined reports, historical reports, or custom report types.
4. Login—A user login. You can trigger your policy on many types of login events.
5. Resource Access—Notifies you when the selected resource has been accessed. You can block access or require two-factor authentication before access is allowed.Note AccessResource event policies don't trigger when Dashboard Subscriptions send an email. These policies still trigger when users access resources directly from a dashboard.
6. Entity—An object type.Note Lightning Experience supports only the Feed Comment and Feed Item resources, while Salesforce Classic supports all Chatter resources.
7. Select Generate Apex unless you have an existing policy condition to use.Transaction Security creates a stub, or placeholder, Apex policy condition. You’ll expand it after creating the policy.
8. Next select what the policy is to do when triggered, who is to be notified and how, and the user that the policy executes as. The user selected forExecute Policy As must have the System Administrator profile.The actions available vary depending on the event type. For login and resource events, you can also block the action or require a higher level of access control with two-factor authentication. For Chatter events, you can freeze the user or block the post. For Login events, you can require ending an existing session before continuing with the current session. You can set the default action for ending a session to always close the oldest session.Note Two-factorauthentication is not available in the Salesforce app or LightningExperience for the Resource Access event type. The Block action is usedinstead.Important If you create a policy requiring the two-factor authentication action, provide your users a way to get a time-based, one-time password. This password is their second authentication factor. Otherwise, if your users encounter a situation that requires a second authentication factor, they can’t finish their task, such as logging in or running a report.
9. Choose a descriptive name for your policy. The name and policy description help you identify and organize policies as they are created.
10. Click Save and then click Finish to confirm. The new policy appears at the bottom of the policy list.

---

1. Navigate to the email editor.
2. Hover over the content area and click the menu arrow.
3. Select Lock.
4. Share the email with business units.

---

1. Click Admin.
2. Click Send Management.
3. Click URL Expiration.
4. Enter the number of days after emails are sent to expire links. Some links may take up to 30 days past the set threshold to expire for emails sent before the March 2017 release.
5. To redirect subscribers to a custom URL, choose Custom Defined URL and enter a valid URL that includes http:// or https://.
6. Click Save.

---

1. Create a custom Promotion object with fields that store your promotional data: Start Date, End Date, Promo Code, and Discount (%). Start Date has a value of 4/1/2018, End Date has a value of 5/31/2018, Promo code has a value of Promo1, and Discount has a value of 10%.
2. Add a Promo Code text field to your quote. When your price rule is active, your sales reps can enter Promo1 on the quote to receive a 10% discount.
3. Create a price rule with the following fields.Evaluation Scope: CalculatorConditions Met: AllLookup Object: Promotion
4. Evaluation Scope: Calculator
5. Conditions Met: All
6. Lookup Object: Promotion
7. Create a price condition so that the price rule fires when your quote’s promo code field doesn’t have a blank value.
8. Create your lookup queries. Test whether the quote’s promo code matches the promotion’s promo code, and whether the quote expires before the promotion begins. Remember that the tested field refers to the quote field you’re evaluating, and lookup field refers to the Promotion object field that you’re testing against. Each lookup query should have the quote as the tested object. After that, set up each query as follows.Tested FieldOperatorLookup FieldPromoCode__cequalsPromoCode__cSBQQ__ExpirationDate__cgreater thanStart_Date__cSBQQ__ExpirationDate__cless thanEnd_Date__c
9. Create your price actions. Your price rule performs these actions when all its lookup queries are true. The first action sets your source lookup field to find the value of your quote line’s discount field and sends that value to your promotional discount field. The second action pulls the promotional discount into a formula to determine your quote line’s final listprice.This is your first price action.Target ObjectQuote LineTarget FieldPromotional Discount__cSource Lookup FieldDiscount__cThis is your second price action.Target ObjectQuote LineTarget FieldSBQQ__ListPrice__cFormulaSBQQ__OriginalPrice__c * (1 – Promotional_Discount__c)

---

Supported Editions - Winter ’16 and later