August, 2018 Release
This month's release of fixes in our HOC applicaiton for Salesforce fixes some annoying bugs and behaviors that occasionally crop up. We also have an administrative update that System Administrators of organizations using lightning should take action on. (It'll improve your lightning experience, as we bring you the first two HandsOn Connect Lightning Components! Read on!
More and more HOC users are using Salesforce's new lightning interface, and many others are testing it out and learning how to take advantage of the new interface. For those users who have switched to lightning, we strongly urge you ask for the upgrade to the Lightning Native version of HandsOn Connect (a $100 upgrade that replaces the "classic' version used in lightning with a Lightning native version.)
This release offers a fix for those users who have run into the problem wherein editing an occurrence and saving it does not close the occurrence editing window. Administrators should also add new HOC Lightning components included in this release, to fix two small issues with the Occurrence and Lightning Page layouts.
This is easy to do - and a good way for you administrators new to lightning to get under the hood and get some Lightning administrator Experience. If on the other hand this isn't something you're comfortable with - come to a lab and we'll walk you through the steps - or just open a support ticket and say "Please update my occurrences and recurrences" and we'll take care of it for you. But I bet you're eager to try this one yourself :-)
If you are not experiencing the problem of the edit window in occurrences not closing - Skip steps 1 - 4. Go directly to Step 5.
UPDATE THE OCCURRENCE OBJECT
1. Go to Setup Object Manager and select the occurrence object. Select "Buttons, Links, and Actions"
2. Select the button "Edit" and clicking the triangle to the right, select 'edit". to
3. Update the override properties changing the Salesforce Classic Override to "No Override" and the Lightning Experience Override to "Use the Salesforce Classic Override". (this part may have already been done for you by support when setting up lightning for you.
4. Also edit the buttons for NEW, VIEW, and CLONE if needed. All should have as 'content source" Standard Page.
Note: By turning off the redirect and fixing this in lightning, you will be removing a warning in classic that alerts users that editing an occurrence that's part of a recurrence will remove its relation to that recurrence. No big deal, but it is a handy alert to have. By making this change, we're going to stop this alert in classic but add it Lightning. (So don't make the change above yet if you're only dabbling in lightning).
5. Now we are going to add a new HOC lightning component to the Lightning Page Layout. To do so, click on Lightning Record Pages and select the page HOC 3.1 Occurrence Page Lightning. After selecting it, click on the Edit Button.
6. In the left column of the lightning page are all the available lightning components. In this release we've added two HOC lightning components: "OccuirrenceEditWarning" and "RecurrenceOverview". You'll find them at the bottom under 'custom - managed'. For the Occurrence lightning page we're going to add the component "OccurrenceEditWarning".
Not seeing the Custom Lightning components? Make sure you've activated "My Domain" as part of your initial lightning activation process. If you haven't done so yet, we strongly urge you to do so now :-). My Domain is required for certain lightning features, like custom components to be used.
7. Drag the component and place it on the page. We recommend placing it right under "Related List Quick Links". Then SAVE the Lightning record page.
Why are you doing this? Good question. Here's what this component does. In Classic, a VisualForce redirect page was used whenever you edited an occurrence, that checked if the occurrence was part of a recurrence, and gave a friendly warning that editing the occurrence would remove the occurrence from its recurrence. (Obvious yes, but nice to be warned, right?). The VF redirect page was what was causing the awkward behavior of the edit window in Lightning. So for lightning users, you'll want to turn off that redirect (Steps 1 -4 above), and this new Lightning component will display that warning message when you view an occurrence that's connected to a recurrence! If its not connected to a recurrence, then the warning won't be displayed!
UPDATING THE RECURRENCE LIGHTNING PAGE LAYOUT:
Another annoying thing we found in lightning is that the "Recurrence Overview" was not visible when VIEWING a recurrence. You had to click on edit to see the overview and publish it. You'll fix this with another lightning component!
1. Go to Object Manager and select the recurrences object. Select Lightning Record Page and select the page "HOC 3.1 Recurrence Record Page", and then click on Edit when you get to the next screen.
2. Drag the lightning component "Recurrence Overview" onto the page layout. (Place it just about the record detail section). Then click Save.
Voila! Now when you 'view' a recurrence - the recurrence overview IS visible and you can publish a recurrence without clicking on edit :-)
OK. Admit it. Lightning is fun, right? And its the future of Salesforce. So if you haven't tried out lightning, now's the time to give it a whirl and decide if your organization is ready to switch over to lightning!
If you ARE going to use lightning, we strongly urge you to request the $100 upgrade (a bargain!) for us to install the native lightning version of HandsOn Connect. It will save you a ton of setup headaches!
Just want to learn more about lightning? We're here to help. Drop into any lab and we can show you the ropes of using lightning!
When updating a contact's email address, all related records in which that contact's email address has been brought over must also be updated. In isolated cases, a single contact (like an Opportunity Coordinator for many opportunities and occurrences), Salesforce was not able to perform the update due to the number of records. Instead you got a delightful error message like this:
Error:Apex trigger HOC.contactTrigger caused an unexpected exception, contact your administrator: HOC.contactTrigger: System.LimitException: Apex CPU time limit exceeded
The apex code that manages these mass updates has been improved, and the contact trigger will now be able to handle as many records as it needs to update as a result of a change to the email address or contact name.
Add your comment