Mock HTTP callouts in a Managed Package

In this blog, I will show you how to mock callout response which is in a managed package.

I found out that many developers are using Test.IsRunningTest() in their Apex classes to avoid writing Mock responses for http callouts and if the callout comes from a Managed Package, they are stuck with this message "Methods defined as TestMethod do not support Web service callouts".

As per Salesforce Documentation, "To mock a callout if the code that performs the callout is in a managed package, call Test.setMock from a test method in the same package with the same namespace."

So to be able to mock callout which is performed in a managed package, the line doing "Test.setMock" should be called from the managed package itself.

So what we did in the SharinPix (ISV) managed package, we added a global class which take a HttpCalloutMock class as parameter and execute the Test.setMock from within the package.

@isTest
global class HttpCalloutSimulator {
    global static void setMock(HttpCalloutMock mock) {
        Test.setMock(HttpCalloutMock.class, mock);
    }
}

By adding the above class in your package and making it global so that it ca be called outside the managed package make it easy to mock code which are doing callout in your package without getting error messages.

You will just need to call it as below:

[namespace].HttpCalloutSimulator.setMock(mock);

Example on how to use it:

sharinpix.HttpCalloutSimulator.setMock(HttpCalloutMock mock);  

//where the variable mock is the instance of your HttpCalloutMock class

Links: 

• Salesforce documentation for test classes: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_restful_http_testing_httpcalloutmock.htm
• Trailhead tutorial for test classes: https://trailhead.salesforce.com/en/content/learn/modules/apex_testing/apex_testing_intro
• SharinPix AppExchange: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3000000Dq45IEAR

What is Remote Action in Salesforce?

In this blog, we will learn how to use Remote Actions in Visualforce Page.

But what is a Remote Action? 

Remote Action is a way to access Apex method using Javascript in your Visualforce page.
It allows you to create pages with complex, dynamic behavior that isn’t possible with the standard Visualforce AJAX components.

Remote action method should always have the @RemoteAction annotation and it should be Static.

Let's take an example where we need to retrieve the first five Cases with Status to New.



Output:

Point to remember:

• @RemoteAction annotation is mandatory
• Remote Action methods should always be static
• If you are using the Visualforce Page inline in a Page Layout, then the method should be declared as global instead of public

Rendering Visualforce as PDF with Header and Footer

In my last post, I explain about how to customize the page size format of a generated pdf through Visualforce page.

In this new post, I shall illustrate how to add a header and footer to a generated pdf through CSS.

We get started by using the Visualforce template below:


Now, let's add the code for the header and footer and see the output.

Output of the header and footer in pdf

Visualforce renderAs pdf in different page format

Over the years, I found that there are so many people struggling with rendering pdf using visualforce, specially when they are required to set a custom page size, page break, margin, adding custom styling.

Today I shall give an example on how to print a contact address on an envelope using a pdf generated from a pdf upon the click of a button from the page layout.

First of all, to be able to generate a pdf from a Visualforce page, you need to use the renderAs attribute on the apex:page tag. See code below:

The above code will generate a pdf but you will notice that the page size will be in an A4 or letter document format. We want to achieve an envelope page size as mentioned early. This can be easily be achieved using some css in the code.

The following attribute are required on the apex:page tag: applyHtmlTag="false" and showHeader="false". To specify a size for the rendered pdf, the following style need to be added to the page:

<style>
@page {
    size: 6.4in 4.5in;
}
</style>

The size is customizable depending on the desired print layout:

• size: A4;
• size: A5 landscape;
• size: 9in 5in;

When the @page is not specified, a full document format pdf is created. 

When no size specified (default to A4)

Now with a size specified.

Envelope size (6.4in x 4.5in)

Here is the full code for the above output.

Additional and helpful resources:

• https://www.smashingmagazine.com/2015/01/designing-for-print-with-css/
• CSS_for_print.pdf

Enjoy ;)

<apex:page standardController="Contact"
	applyHtmlTag="false"
	showHeader="false"
	renderAs="pdf">
	<html>
	<head>
	<style>
	@page {
	size: 6.4in 4.5in;
	}
	.center {
	margin: auto;
	width: 60%;
	padding: 20px;
	}
	</style>
	</head>
	<body>
	<div>
	<img src="https://kevan-dev-ed--c.eu15.content.force.com/servlet/servlet.ImageServer?id=0151p000004v4JH&oid=00D24000000e1d4&lastMod=1518775947000" />
	</div>
	<apex:outputPanel layout="block" styleClass="center">
	<apex:outputText value="{! Contact.Name }"></apex:outputText>
	<br/>
	<apex:outputText value="{! Contact.MailingStreet }"></apex:outputText>
	<br/>
	<apex:outputText value="{! Contact.MailingCity }"></apex:outputText>
	, &nbsp;
	<apex:outputText value="{! Contact.MailingState }"></apex:outputText>
	&nbsp;
	<apex:outputText value="{! Contact.MailingPostalCode }"></apex:outputText>
	<br/>
	<apex:outputText value="{! Contact.MailingCountry }"></apex:outputText>
	<br/>
	<apex:outputText value="{! Contact.Phone }"></apex:outputText>
	</apex:outputPanel>
	</body>
	</html>
	</apex:page>

Disabling Lightning Component Caching while developing in Lightning

Most of the time, developers has to refresh their page multiple times until they see the changes on their Lightning component. This is due because Salesforce enable caching of its client-side component to optimize performance on production. 

This can be bypass easily by disabling browser cache from Salesforce configuration. 

Here are the steps for disabling Browser cache:

Go to Setup > Security > Session Settings

Scroll to the section Caching

Uncheck Enable secure and persistent browser caching to improve performance

Session Settings (Browser caching)

Note: THIS option should be enabled in production environment to avoid performance issues.

Additional resources:

• https://developer.salesforce.com/blogs/developer-relations/2017/04/lightning-components-performance-best-practices.html#rendering