Posts tagged force.com

Dependent picklists in Salesforce

Virtually every site I’ve worked with in recent years has had need for dependent drop downs of some nature.
Usually implementing a dependent drop down consists one of two options: Outputting every option into a JavaScript method, or invoking an Ajax call to get the next set of options. The disadvantage to both of these options is usually a bulky mechanism the developer must write in order to provide a simple UI component.

Salesforce provides a dependent picklist feature, which in keeping with their no-software mantra, eliminates any need for a custom ajax or javascript solution. Define a dependent picklist and reference it in your page layout or Visualforce page. Salesforce takes care of everything else under the covers.

More >

Our heads are in the cloud: Dreamforce 2010

Salesforce.com’s annual Dreamforce conference was held in San Francisco the week of December 6-9, 2010. EDL, a gold sponsor for the second year. The booth included contortionists dressed in cloud morph suits which drew continuous large crowds. At the booth, EDL representatives were discucssing and demonstrating the new CloudCraze 2.0 and Service Cloud 2 integration for prospective customers. We attracted many conference attendees to our booth and had the opportunity to “WOW”them with our eCommerce and customer service offerings.

The energy of the event was immense and intense and the convention center was packed with both current salesforce.com customers and prospects who were eager to learn more about taking full advantage of their CRM system and learning about the power of saleforce.com’s Force.com development platform. The attendees at this conference were truly eager to learn all that there was to know about salesforce.com and cloud computing. While  talking to and observing many of the attendees, I  found that there were basically two types of attendees at this event:

Group A: This group represents the customers who view saleforce.com solely as a CRM system, with their company utilizing it strictly to communicate and manage their customer information. After speaking with numerous customers in this group, I found that many of them still shared a common need – to have visibility between their leads and their sales and support centers.

Group B: These are the customers who truly want understand all that salesforce.com offers and are excitedly looking for what they can “DO next” in terms of applications and sales force optimization.

When people from Group B approached the booth and I would demonstrate CloudCraze 2.0 or Service Cloud 2 integration for them, they were in awe. They truly understood the benefit of having one “repository” for all pertinent aspects for their company from lead generation to order fulfillment and then onto the service center, with the Service Cloud 2 offering. The enterprise-class customers were shocked with the short time required to build, having experienced how long it took to build solutions this robust with an on-premise solution.

As I dive deeper into solution architecture, it is easy to understand why one would want a single portal to control all of a company’s information since the integration of information is often difficult and trying. It is also problematic to maintain so many moving parts, which must all be working together toward a common end goal. It becomes apparent that it is also quite costly and inefficient to train employees on so many different platforms.

Another common theme that I noticed as I began to truly ponder CloudCraze, EDL Consulting’s eCommerce solution built natively on Force.com, was that many companies which are product companies by nature, were beginning to develop “light” versions of their own product on Force.com as well. However, they were not prepared to take the plunge and holistically develop their product on the platform in its entirety, but instead were developing smaller versions for the AppExchange. What this suggests is customer interest in native Force.com applications. Each company that I spoke with who had developed this lighter version of their product, discussed the road map for their AppExchange product and in essence, how it would/could become as robust as an enterprise-class product.

It seems most logical to me that a consulting company with ten years of deep eCommerce experience be the ones to develop a product to derive the benefits in both development and implementation. The need for natively built applications is continuing to grow and as other eCommerce solutions begin to develop their “shopping carts” into more robust solutions, CloudCraze will continue to develop strategically, remaining ahead of the curve.

Template for Global Configuration Variables in Apex

Richard Vanhook

Richard Vanhook

 

 

Summary: This article discusses a pattern or template for enabling and customizing features in an application developed upon the Force.com platform.

 

 

Force.com and “configurability”: new expecations for developers

A great thing about developing on the Force.com platform is how configurable the product is out of the box. Need a new field on a screen? Easy, find the right page layout and modify it. Want a field to be required? Go find the field and make it required. It’s crazy easy. So easy in fact, that more and more folks can contribute to the solution of a system. Even folks without an IT background that 5-10 years ago would never make these types of configuration changes are doing it. Can you imagine Joe the BA adding an Oracle constraint to make a field required? Of course not.

The downside to this amazing “configurability” of the Force.com platform however, is it creates a disconnect between developers who are not used to including this level of configurability, and salesforce users who have grown to love this type of configuration and now expect it in anything associated with salesforce. Below I discuss a “global configuration variable” pattern that makes adding configurability to your solution simple, clean and reliable.

More >