Question : What are the Declarative Application building blocks of the User Interface? 1. Visualforce Pages 2. Applications 3. Access Mostly Uused Products by 50000+ Subscribers 4. Workflow 5. Page Layouts 6. Record Types 7. Declarative Interface
Visualforce Pages : A developer creates Visualforce pages by composing components, HTML, and optional styling elements on the Force.com platform. Just like HTML, Visualforce can integrate with any standard web technology or JavaScript framework to allow for a more animated and rich user interface. Each page is then accessible by a unique URL. When someone accesses a page, the server renders the page.
Tabs: If you're familiar with the Force.com platform, you know that clicking tabs is how you navigate around an app. Every tab serves as the starting point for viewing, editing, and entering information for a particular object. When you click a tab at the top of the page, the corresponding home page for that object appears. For example, if you click the Accounts tab, the Accounts tab home page appears, giving you access to all of the account records that are defined in your organization. Click the name of a particular account record and you'll view all of the record's information in its associated detail page.
Workflow and approval processes allow us to create business logic based on rules: o Workflow rules can assign tasks to users, update fields, or send email alerts. o Approval processes allow users to submit sensitive records like new contracts or purchase orders to other users for approval.
A page layout controls the position and organization of the fields and related lists that are visible to users when viewing a record. Page layouts also help us control the visibility and editability of the fields on a record. We can set fields as read-only or hidden, and we can also control which fields require users to enter a value and which don't.
Explanation: The declarative development also follows the MVC architecture in development. The MVC components in declarative development using Force.com are:
Model : Objects, Fields, Relationships View : Applications, Tabs, Page layouts, Record types
Logic as a service : o Formulae o Validation rules o Assignment rules o Workflows o Approval process
There are different types of rules used in different areas. They are as follows: o Validation rules: Validation rules are used to validate the data populated in the field of a record. They can be used to provide a user-friendly error message in case of data discrepancy. For example, to check if the discount is not greater than 35 percent. o Workflow rules: Workflow rules are used to automate a process that is usually done manually. They can trigger an action when the rule is set true. For example, setting the checkbox to true if the value of X is Y. o Approval process entry rules: The rules here ensure that only a particular set of records enter this approval step. For example, if the amount is greater than 50,000 it should only go to the head of the finance department for approval.
Explanation: A rule syntax consists of the following components: o Literal value: A literal value can be any string or a numeric component. For example, 0 in the above formula. o Field values: These are references to the existing fields on the object. For standard fields we use the API name as the reference, for custom fields we append a __c to the API name. o Global values: These refer to the value of a system or environment variable, such as information about the logged in user or the organization settings. o Function and operators: Force.com provides us with functions to operate on the data. There are different sets of functions provided by Force.com for different sets of operations.