Salesforce Nation

Hi Folks, Today I am writing about Objects in Force.com. In previous article we have discussed about various components of force.com applications with an overview of  the Salesforce data model so diving deep into it we are going to discuss objects in force.com. Basically, there are two types of objects in force.com. Table below is showing some main objects as example - Standard Objects Custom Objects MyCustomObject__c Account Contact Lead Opportunity Campaign Case Quote Note:- All Standard Objects are not mentioned. As we all know that Objects in Salesforce are the database tables and Standard Objects are predefined by Salesforce and those objects which are defined by us, are Custom Objects. So in the above table MyCustomObject__C is a custom object with a sample name. “__c” is a suffix, added by Salesforce to differentiate between Standard objects and Custom objects.

Hi Folks, Today I’m writing about the Force.com Applications for Salesforce.com. Developing an application on force.com has a defined process. This process goes as -  We can develop our application in Developer Edition Org. After being developed an application must be tested in a Sandbox. Since it’s a tested application it must be submitted for the Security Scanner reviews. Scanner scans our application for security, complexity and other issues. If our application gets a “No issues found” result then only it can be pushed on App Exchange. App Exchange is a marketplace for force.com applications. App Exchange is just like Google App Store. From the App Exchange we can download and install applications directly into our Salesforce.com CRM org. An application is a collection of different Kinds of Components as we see after logging into CRM. Components available in an application have a big picture behind it’s view and behavior so before understanding these components

Hi Folks, Today I’m writing about MVC the MODEL, VIEW, CONTROLLER in Force.com application development platform. MVC is basically an Architecture Pattern which has some separation of concerns, in a Software. Separation of Concerns means that classifying a Module in Sub-Modules which are integrated and interactive to each other. Components A Model basically manages data and enforces rules and validations on the data, currently in context. It’s a central component of the design pattern. A View is your HTML/Javascript based representation of your data pulled from your Model. It can be a chart or some tabular formatted page to view information. A Controller is a conveying medium between model and view which helps view to show data by pulling it from model. It basically accepts inputs and converts into instructions or commands to model or view. Working A model stores the data retrieved by the controller and displayed in the view. A view generates new ou