It is important to understand how approval email notifications work in Salesforce.com, particularly when you are mass submitting/re-assigning approval requests. You might want to avoid unpleasant situations wherein users are flooded with email notifications in their inbox. This article tries to point out the various options available to avoid such situations.

How does Salesforce send an email to the approver when a request is submitted?

How to stop email notifications while mass submitting/reassigning approval requests?

There might be situations wherein System Administrators are required to mass transfer pending approval requests. This article is aimed at providing the various options available.

As a word of advice, please be CAREFUL before you do the mass reassignment as this will trigger EMAIL NOTIFICATIONS to the new assignee's.

Option 1: Transfer to a User

This is straightforward as shown below. Note that you can mass recall approval requests from this page as well. Also, you do not have the option to transfer to a Queue.


Option 2: Transfer to a Queue

In a bid to combine all posts of this blog into one single space, I am starting to put these together in a e-book format. You can enroll and see the complete course here https://www.openlearning.com/courses/salesforceforall as it progresses. It's FREE.

Feel free to leave feedback, and any topics you think should be included. Any feedback is greatly appreciated!

***********************************************************************************

Salesforce for All - Chapter One : Introduction

Today, Salesforce unveiled the NEW.

Here is a sneak peak of the features first hand.

Video Credits: Brian Kwong
                             

Report & Dashboards:

Opportunity:

Account:

And there is a whole lot NEW for developers. Lightning components is the NEW world.

This article is out of the blue and not related to the technical stuff i usually write about. I am writing this hoping that it might help someone make a informed decision.

A real estate company in Bangalore, Dreamz Infra Pvt Ltd (http://www.dreamzinfra.com/) promises to sell apartment homes for very cheap prizes. If you are considering buying an apartment from them, I would suggest you ponder over these points before you make a decision. I hope that this post will attract honest reviews from those who purchased/tried to purchase with the company.

The prices of the apartment are unbelievably cheap. Compare with the market rates and you will notice that there is a sharp difference.

There is an unbelievable large number of positive reviews for Dreamz Infra. There are even blogs created by employees of Dreamz Infra like this one.

Note that all comments are positive reviews.

Now, the contrasting part is that their Facebook page (https://www.facebook.com/DreamzInfra?fref=ts) is nothing but filled with negative reviews. Note that customer support hasn't responded to any negative review, whereas positive reviews are liked or commented at.

I used https://web.archive.org to see what content they had on their website historically. I was surprised to see that the projects listed in 2012 in Electronics city are neither seen in the completed list nor do they show up in the current projects list.

Dreamz Infra projects today in Electronics city

STEP 1:

STEP 2:

STEP 3:

STEP 4:  

STEP 5:

 STEP 9:

STEP 10:

STEP 11:

STEP 12:

STEP 13:

STEP 14:

STEP 15:

      1. Place package.xml in the folder 'Retrieve Package'
      2. from CMD run 'ant retrieve'
      3. Folder 'deploy' is created.
      4. To validate change edit build.xml and make 'checkonly = true'.
      5. To deploy make checkonly = 'false' and from CMD run 'ant deploy'
      6. Rename the 'deploy' folder and copy to 'completed' folder for history tracking.
      7. Delete the 'deploy' folder

You might get this Error fairly frequently when developing complex Apex Triggers. In this article, we will look at the causes and possible solutions to address the issue.

What?

This error message typically means that the Apex Trigger is taking too long to execute. The maximum CPU time for a trigger is 10,000 milliseconds or 10 seconds. Note that the time taken for DML and SOQL operations does not fall into this category. 

Why?

When you get this error, it DOES NOT mean that you have too many DML operations or large SOQL queries. Rather, it means that there is a problem in the way you handle the result of those operations.

Things to check

1. Try using a MAP instead of a LIST. A MAP is always much efficient to use.
2. Try to avoid iterations or FOR loops wherever possible.
3. Check your nested FOR Loops. This is one MAJOR area which consume too much time. Try to minimize the iterations.