Presentation for Salesforce Summer'14 Release Notes by Astrea IT Services

1. 1
By:
Mohit Gupta
Sagar Pareek
Priyanshi Agrawal
ASTREA IT SERVICES

2. Sales Enhancements
Force.com Development Enhancements
Force.com Customization Enhancements
Hands-on exercises
2

3. Sagar Pareek
Software Developer
Astrea IT Services

4. Generally Available Features
Enhancements to Activity
Opportunity Splits
Enhancements to Price Book
New Fields on Sales Cloud Objects
Pilot Features
Generate Orders from Opportunity or Quotes
Territory Management 2.0
4

5. Generally Available Features
5

6. Global Action New Event on publisher added.
Use Date and Date/Time Fields in Formulas
6

7. Opportunity Team Selling must be activated before using this feature.
Two types of splits
a. Revenue : direct split and total of all must be 100%
b. Overlay : indirect split and can be more than 100%
New flow UI with Summer‟14
Users can view these splits in tabs.
7

8. With Summer‟ 14 release users can create and edit custom fields, page layouts, validation rules and field level security for Price Book Entries .
8

9. New field Contract on Opportunity and Quote objects
New fields Opportunity and Quote on Order object.
New field Quote Line Item on Order Product object. 9

10. Pilot Features
10

11. Pilot feature.
Standard button on the Opportunity or Quotes. 11

12. Now you can model your sales territories into a logical and flexible structure that connects your sales reps to accounts they sell to.
Now you can model Territory Management based upon territory types, territory models and territory model states. 12

13. Priyanshi Agrawal
Astrea IT Services

14. Sandbox
Change Sets and Deployment Tools
Force.com Canvas
Developer Console
VisualForce
Apex Code
ISVForce 14

15.  Sandbox copy and refresh now support connected apps installed using a package installation, such as connected apps installed from the AppExchange.
 You can match provisioned licenses in production to your sandbox organization without having to refresh your sandbox.
◦Company Profile > Company Information > Match Production Licenses. 15

16. You can now monitor the status of all deployments in one place. Change sets, the Metadata API, and tools- based deployments all show on the Deployment Status page.
The Force.com Migration Tool now accepts the rollbackOnError parameter in build.xml for deployment targets and no longer ignores this value. 16

17. entityFields attribute added to <apex:canvasapp>
◦Asterisk “*” to return all fields from the associated object.
◦Eg. <apex:canvasApp applicationName="MyApp" entityFields=“*“/> 17

18. SDK Object and Field Changes
◦The Environment object contains a new Record object (a JSON-formatted object that contains information about the object on which the canvas app appears).
◦The Environment object contains two new values for displayLocation.
MobileNav—The canvas app was called from the navigation menu in Salesforce1.
 PageLayout—The canvas app was called from an element within a page layout.
18

19. The orientation event enables you to handle changes in orientation when your canvas app appears on a mobile device.
Now you can directly embed Canvas Apps on your Page Layouts and in S1 Mobile Cards without having to use a Visualforce wrapper.
19

20. By providing a custom Apex class, you can control the context information that is sent to your canvas app and add custom behavior when your app is rendered. 20

21. Set your own Canvas App icon for your apps in S1 Mobile Navigation menu.
21

22. The new Edit menu in the Developer Console allows you to quickly access search and edit functionality.
Search for files by name using the new Open Resource dialog in the Developer Console.
◦File > Open Resource or press SHIFT+CTRL+O.
◦Prefix with “re:” for regular expressions 22

23. Use the Query Plan tool to optimize and speed up queries done over large volumes.
The Change Log Levels dialog in the Developer Console now includes a color-coded Expiration field that displays the current logging status. 23

24.  Visualforce Remote Objects has been improved with new features
◦remote method overrides
◦an upsert() operation
◦the orderby query condition for specifying sort order
◦new query operators for where conditions
ne: not equals
lte: less than or equals
gte: greater than or equals
◦supports geolocation fields, which removes a limitation of the prior release. 24

25. Deferred Creation of Dynamic Components
◦A dynamic component can now wait for page actions to be completed before the method that creates the dynamic component runs
◦Set invokeafteraction = true
The topics widget lets users see, add, and remove topics on a record so it‟s easy to tag and categorize records. Use the renderStyle attribute to specify whether the widget appears with a basic (simple) or an advanced (enhanced) user interface.
The markerFill and fillColor attributes of the <apex:lineSeries> charting component weren‟t defaulting to match the component‟s strokeColor as documented. This behavior has been corrected for pages that are set to API versions 31.0 and later.
25

26. Limits for all Apex describe calls have been removed for all API versions. Describe calls include describes for sObjects, fields, field sets, child relationships, picklists, and record types.
The Limits methods for script statements have been removed but are available and deprecated in API version 30.0 and earlier. Because the script statement limit is no longer enforced in any API version since Winter ‟14, the associated Limits methods are no longer needed.
◦getScriptStatements()
◦getLimitScriptStatements() 26

27. You can access the Standard Price Book in your apex tests when SeeAllData=FALSE and create your own test data.
◦Test.getStandardPricebookId()
You can submit more batch jobs simultaneously and actively manage the order of the queued jobs (Pilot)
◦AsyncApexJob has new status field value of Holding
Run Future Methods with Higher Limits (Pilot)
◦@future(limits='2x|3xlimitName')
27

28. The new Partner Community at is now the primary resource for all ISVs.
◦https://partners.salesforce.com
Simplified installer makes app installation possible in just one step.
28

29. You can collect detailed Usage Metrics from each organization in which your managed package is installed, giving you valuable insights into the utilization and performance of your app across your entire customer base.
◦Custom Objects
◦Visualforce pages
The Usage Metrics Visualization package, available from Salesforce Labs on the AppExchange, enables you to visualize trends in usage metrics data for your app.
29

30. 30

31.  The License Management App now generates licenses and leads for package installation in sandbox organizations, in addition to production organizations.
Administrators can now use the API to assign or revoke licenses for any managed package installed in their organization.
◦License information for a package is stored in two objects: PackageLicense and UserPackageLicense.
31

32. You can now create partner organizations directly from the Environment Hub, instead of having to visit the Partner Portal.
Mobile packaging is now available to all customers for free, solving the app distribution problem for customers building mobile apps on the Salesforce platform by providing an easy mechanism for distributing those apps to employees or partners
32

33. Mohit Gupta
Astrea IT Services

34. Setup Enhancements
General Administration Enhancements
Permission Enhancements
Security Enhancements
Business Logic & Process Automation Enhancements
Sharing Enhancements
Additional Force.com Customization Enhancements 34

36. With Advanced Setup Search, we can now search for Setup menu items, custom fields, custom objects, custom profiles, permission sets, public groups, roles, and users from the sidebar in Setup.
To enable Advanced Setup Search for your organization, in Setup, click Customize > User Interface, then scroll to Enable Advanced Setup Search (Beta).
36

37. Once advanced setup search is enabled, a tooltip will appear in your Setup search window. 37

38. To find setup items, enter at least two consecutive characters of the item that you want in the Setup Search box, and then press Enter. 38

39. 39

41. When setting the Login IP Ranges for a profile or your organization, you can now also enter a description for each range to help identify the purpose of the range setting.
From Setup, click Security Controls > Network Access. 41

42. Expand the feed horizontally and automatically collapse the publisher when it‟s not in use so users can see more information at a glance when they work with records.
Two new settings for feed-based page layouts let you customize feed views so users can see more information without having to scroll.
42

43. Use the Auto-Collapse Publisher setting to collapse the publisher when it‟s not in use. The publisher expands to its regular height when a user clicks inside it.
43

44. Enable the Use Full-Width Feed setting to expand the feed horizontally to take up all available space on the page. 44

45. To enable either of these settings, click Feed View in the top menu of the page layout editor when you‟re editing a feed-based page layout, and then choose the setting you want. 45

46. Every custom object is now classified based on whether you can use a private sharing model, Bulk API, or Streaming API with it.
When you create custom objects, you can classify the object as a Light Application object or an Enterprise Application object by enabling or disabling the following settings.
• Allow Sharing
• Allow Bulk API Access
• Allow Streaming API Access
46

47. If these settings are enabled on an object, it‟s an Enterprise Application object. If these settings are disabled on an object, it‟s a Light Application object. The settings must all be enabled or all be disabled.
Objects created before Summer ‟14 automatically have these settings enabled and are classified as Enterprise Application objects.
47

48. To keep track of how many custom objects your users are assigned to, we can create a custom report type with the User Licenses and Custom Object Usage by User License Metrics objects.
Create > Report Types > Create New Report Type 48

49. 49

51. Custom permissions enables developers to easily create custom permissions on profiles and permission sets that Administrators can easily assign to users.
Custom permissions let you define access checks that can be assigned to users via permission sets or profiles, similar to how you assign user permissions and other access settings.
For example, you can define access checks in Apex that make a button on a Visualforce page available only if a user has the appropriate custom permission.
51

52. To Create Custom Permissions : Setup> Develop > Custom Permissions.
Note : Custom permissions are currently available as a developer preview; they‟re available only in Developer Edition organizations.
52

53. Custom permissions give you a way to provide access to custom processes or apps. After you‟ve created a custom permission and associated it with a process or app, you can enable the permission in permission sets and Profiles.
53

55. Previously, administrators could limit user password reuse by selecting an option of up to 15 passwords remembered in an organization‟s history. Now administrators can select up to 24 passwords remembered.
Administrators could previously require minimum password lengths of up to 10 characters but can now require a 12 character minimum length. (The default remains 8 characters.)
55

56. Now, administrators can also require that passwords include both uppercase and lowercase letters. More complex passwords improve organizational security.
To reset the password polices, from Setup, click Security Controls > Password Policies and select a value for Enforce password history.
Use the Force logout on session timeout setting in Security Controls > Session Settings to require that when sessions time out for inactive users, current sessions become invalid. Browsers are automatically refreshed and return to the login page. To access the organization again when this occurs, users must log in again.
56

57. The Salesforce login page includes a link, Log in to a custom domain, so users of organizations that implemented My Domain or Communities can easily get to their organization.
57

59. Workflow email alerts for the User object can now reference fields from the user record that triggered the workflow rule.
When creating or editing email templates in Salesforce, the Select Field Type drop-down list now contains the Workflow Target User option.
{!Target_User.field_name} return values from the user record that was created or updated to trigger the workflow rule.
59

60. When workflow email alerts approach or exceed certain limits, now Salesforce will send a warning email to the default workflow user or—if the default workflow user isn't set—to an active system administrator.
(Pilot) A new value is available for setting a flow‟s sObject variable from a flow trigger workflow action. Enter {!old} to use the most recent previous values of the record that was edited to cause the workflow rule to fire.
60

61. We can now launch a trigger-ready flow with these new methods.
• A custom button or link
• The flow URL
• The Run button in the Cloud Flow Designer
Flow trigger workflow actions are currently available through a pilot program.
61

62. (Pilot) We can now submit records for approval from a flow.
If a flow submits a record for approval, the user who launched the flow is the submitter.
If a workflow rule triggers a flow that submits a record for approval, the user who triggered the workflow rule (by creating or editing a record) is the submitter.
When the record is approved or rejected, the user who launched the flow or triggered the workflow rule is notified.
62

63. We can now run reports on completed and in- progress approval processes and their steps.
Previously, reports were available only for pending approval requests.
We can now create a custom report type with primary object Process Instance and related object Process Instance Node.
63

65. User Sharing controls who sees whom in the organization.
User Sharing controls the visibility of internal users and external users within your organization, communities, and portals.
Previously, User Sharing was automatically enabled only for new organizations that were provisioned after Winter ‟14.
With Summer ‟14, User Sharing is now automatically enabled for all organizations. 65

66. With User Sharing, you can:
• Set the organization-wide defaults for user records to Private or Public Read Only. The default is Public Read Only for internal users and Private for external users.
• Create user sharing rules that are based on group membership or other criteria.
• Create manual shares for user records to open access to individual users or groups.
66

67. Previously, the Sharing button was available on all user detail pages for organizations with User Sharing.
Now we can enable or disable the Sharing button for all users.
With Summer ‟14, organizations get the Sharing button hidden on all user detail pages by default.
67

68. We can now set different access levels to internal and external users.
The following objects support external organization-wide defaults.
• Accounts and their associated contracts and assets
• Cases
• Contacts
• Opportunities
• Custom Objects
• Users 68

69. Click the Enable External Sharing Model button to enable the feature. 69

70. When we create, update, or delete sharing rules, the resulting recalculation is now processed asynchronously and in parallel.
You‟ll receive an email notification upon completion.
Before the recalculation is completed, we can‟t run other sharing operations such as creating a sharing rule or updating the organization-wide defaults.
70

71. To view recent sharing operations, from Setup, click Security Controls > View Setup Audit Trail.
The View Setup Audit Trail page displays entries for when the recalculation is started and whether it‟s successful.
71

73. The maximum length for Long Text and Rich Text custom fields has been increased, from 32,768 characters (32 KB) to 131,072 characters (128 KB).
The maximum number of Relationship Fields per object has been increased, from 25 fields to 40 fields.
The maximum number of custom fields used as external IDs has been increased, from 3 fields per object to 7 fields per object
73

74. 74

75. Activity Exercises
In an organization the development team has decided to allow users to create new events from the Salesforce1 app, so that users can use their mobile devices to create new events instead of their workstations. How can you allow users to create events from Salesforce1 app?
75

76. Opportunity Splits Exercise
In an organization there are three users A, B and C. A is manager of B and C . There are two opportunities named Acme group and Delta that are closed won. Now user A wants to split Acme group opportunity as 50-50% among A and B and Delta Opportunity as 101% for B and 60% for C .
76

77. In an organization the users wants to know which of the events or tasks are upcoming or passed. How can you show on the detail page of the event or task whether it is passed or upcoming?
77

78. Create a new workflow rule that emails new employees when their user records are created. A new Email template should be created which should have names of both new employee and the person who created the user record.
Create a report showing object usage per User License.
78

79. Create a new test class called TestPriceBook.
◦Insert a new product called Test Product
◦Insert a new price book entry for standard price book (Product = testprod, isactive=true, unitprice=0)
◦Create a custom price book (Name= custom price book, isactive = true)
◦Insert a price book entry with a custom price.
79

80. @isTest public class TestPriceBook { static testmethod void addPricebookEntries() { // Insert a test product. Product2 prod = new Product2(Name = 'Test Product', Family = 'testing'); insert prod; // Get standard price book ID. Id pricebookId = Test.getStandardPricebookId(); // Insert a price book entry for the standard price book. // Standard price book entries require the standard price book ID we got earlier. PricebookEntry standardPrice = new PricebookEntry( Pricebook2Id = pricebookId, Product2Id = prod.Id, UnitPrice = 0, IsActive = true); insert standardPrice; // Create a custom price book Pricebook2 customPB = new Pricebook2(Name='Custom Pricebook', isActive=true); insert customPB; // Insert a price book entry with a custom price. PricebookEntry customPrice = new PricebookEntry( Pricebook2Id = customPB.Id, Product2Id = prod.Id, UnitPrice = 12000, IsActive = true); insert customPrice; } }
80

81. Given the code sample for Visualforce remote objects, make the following changes:
1.Create a new field location__c on Contact and display the longitude and latitude for each contact.
2.Sort the records by First Name (ascending) and Last Name (descending).
3.Create a new field age__c on Contact and add a where condition: age >= 20.
4.Add another condition that last name should not be equal to „test‟.
81

82. Create a dynamic component which displays the string „The controller is constructed.‟ if invokeafteraction = false. If set to true it should display „The page action method has been run.‟
82

83. QUESTIONS?
Contact Person: Naveen Gabrani
Email Id: ngabrani@astreait.com
83