Spring ’17 Customization

Approvals:

1.) Review Pending Approval Requests from Lightning Experience:

  •  Lightning Experience can review their pending approval requests in one place. This change applies to Lightning Experience only.
  • Edit the appropriate home pages in Lightning App Builder to add the Items to Approve component or app navigation bar.

approvals_tab

2.) Don’t Worry About That Submit Button:

  • Automatically add the button to all the associated page layouts when you activate an approval process. This change applies to both Lightning Experience and Salesforce Classic.
  • When you create an approval process, look for this setting: Add the Submit for Approval button and Approval History related list to all Object page layouts. Previously, the setting added only the Approval History related list to the object’s page layouts, and it was disabled by default. It now includes the Submit for Approval button and is enabled by default.

  • This setting is available only when you create an approval process. When the setting is enabled, Salesforce adds the Submit for Approval button to the Standard Buttons section of that object’s page layouts.

Process Builder

1.) Process Builder Has Updated Icons:

Winter 17—->>pb_icons_list_before

Spring 17—->> pb_icons_list_after

2.) Access Encrypted Data in Process Builder:

  • Process Builder now supports encrypted fields, except in filters, like in the Update Records action. This change applies to both Lightning Experience and Salesforce Classic.
  • If you’re an existing pilot customer, nothing has changed since the last release.

Ex: If you’ve encrypted Account Name, you can update that field’s value, but you can’t filter based on that field.

Picklist Administration:

1.) Global Picklist Fields Now Have Their Own Record Type:

All global picklist fields that use the same global value set now have individual record types. This change gives you more flexibility than having only one record type for all fields.

2.) Value Labels Are No Longer Tied to API Names:

  • picklist value has a display label and an API name.
  • change the label without the API name changing.
  • You can also edit the API name.
  • you can disable the ability to change API names.

    prevent users from changing a picklist value’s API name:

  1.   Setup in Salesforce Classic, enter Picklist Settings in the Quick Find box.
  2.   Select Disable editing picklist values’ API names.

3.) Access Picklists with the Tooling API:

Standard and global value sets are now available in the Tooling API and Metadata API.

       New Tooling API items are:

  • StandardValueSet—Represents the set of values in a standard picklist field.
  • GlobalValueSet—Represents the definition of a value used in a global value set or local custom picklist.

Note:

This feature isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. We can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s