Salesforce Training Institute & Courses Pune | SFDC Training PCMC

1. Cloud Computing victoriousdigital.in/salesforce-certification-training-institute-pune

2. What is Cloud Computing? • Paradigm/model that allows On Demand network Access to Shared Computing Resources • Managing, Storing, Processing Data Online via Internet victoriousdigital.in/salesforce-certification-training-institute-pune

3. Characteristics • On Demand Service • Network Access • Shared Resources • More scalability victoriousdigital.in/salesforce-certification-training-institute-pune

4. Delivery Models • SAAS (Software as a Service) • PAAS (Platform as a Service) • IAAS (Infrastructure as a Service) victoriousdigital.in/salesforce-certification-training-institute-pune

5. SAAS • On Demand Service Pay per use of application software to users • Independent of platform Dont require anything to be installed in PC • Runs in a single instance of Software Available for multiple end users • Cheap Resources maintained by vendor • Accessible via web browser victoriousdigital.in/salesforce-certification-training-institute-pune

6. Examples • Who uses-end users • Gmail • Office 365 • Google drive • CRM – Salesforce.com victoriousdigital.in/salesforce-certification-training-institute-pune

7. PROS and CONS • Accessible from any platform • No need to commute (we can work from anywhere) • Allows Multi tenancy • Best for collaborative working • Browsers issues • Internet performance victoriousdigital.in/salesforce-certification-training-institute-pune

8. PAAS • Service made with programming lanuage,webserver,database • Like Salesforce Force.com (use of apex language similar to java) • Build,Compile,Run programs without worrying about Infrastructure • Manage data,Application Resources victoriousdigital.in/salesforce-certification-training-institute-pune

9. Examples • Who uses- developers • AWS • Heroku • Force.com

10. PROS and CONS • Cost effective • Faster market for developers • Easy deployment • Private Public deployment possible (use of managed package) • Limited developers • Migration issues victoriousdigital.in/salesforce-certification-training-institute-pune

11. IAAS • Computing Architecture , Infrastructure,but all in virtual environment • Data storage,Virtualization,Servers,Networking • Mainly handle application,data,runtime,Middleware victoriousdigital.in/salesforce-certification-training-institute-pune

12. Examples • Who uses – Sys Admins • AWSEC2 • Rackspace.com • Gogrid victoriousdigital.in/salesforce-certification-training-institute-pune

13. PROS and CONS • Cloud provides the Infra • Scalability • Flexible • Security Issues • Network & Service delays victoriousdigital.in/salesforce-certification-training-institute-pune

14. Database • collection of related data and its metadata organized in a structured format • Database Management System (DBMS) • is a software that enables easy creation, access, and modification of databases victoriousdigital.in/salesforce-certification-training-institute-pune

15. Salesforce.com Database  • organized collection of objects.  • database tables to collect (or store) the information  •  information as object in Salesforce.com • table is presented with rows and columns • Salesforce its maintained as Record and Field. victoriousdigital.in/salesforce-certification-training-institute-pune

16. Database Structure • In Salesforce.com objects are of three types: • Standard Objects: These are the objects that are pre defined by the salesforce and readily available. • Custom Objects: These are the objects created by user according to their need .Each custom object has five standard fields (refer Note 2.2.1) • External Objects: These are the custom objects which are used to map the data stored outside your organization. victoriousdigital.in/salesforce-certification-training-institute-pune

17. Default Standard fields • ID: This is an index allocated to each object. This value is unique. ID can be of 15 digit (Case sensitive) and 18 digits (Case insensitive) • Name • Owner • Created Date/ Created By • Last Modified Date/ Last Modified By victoriousdigital.in/salesforce-certification-training-institute-pune

18. Normal excel based vs Relational database • Relationships define the connection between two objects, and objects are related to each other through the use of common fields. victoriousdigital.in/salesforce-certification-training-institute-pune

19. Types of Relationship • Relationships associate one object with other object. •  Relationship is always defined on the child object. • The child object has complete access of the parent. Based on the handling of data deletion, record, ownership, security victoriousdigital.in/salesforce-certification-training-institute-pune

20. Introduction of Primary-Keys & Foreign-Keys (Conceptual Knowledge) • APrimary keyis a column or set of columns that uniquely identifies the record in the table. When a primary key is defined using multiple columns, the data from each column is used to determine whether a record/row is unique. When we defined any column or columns as primary key, there are some constrains which should be satisfied by primary key that is column value should not be null (Null Constrains) and data should be unique (Unique Constrains.) • A Foreign key is a set of one or more columns in a table that refers to the primary key in another table. Foreign key does not necessary  to be always point to primary key, but the basic idea behind foreign key is that any column which is unique to identify that record/row. victoriousdigital.in/salesforce-certification-training-institute-pune

21. different types of relationships are categorized in to following ways: • Master Detail • Lookup relationship victoriousdigital.in/salesforce-certification-training-institute-pune

22. Using 2 relationship we can build various relationships in SFDC • Many to One (Many child objects but one Parent Object)E.g. many metro cities are associated to One Country. This kind of relationship is represented in four different forms like • Master-detail • LookUp (Loosely Coupled Relationship) • Self • Hierarchical (only available on User object) victoriousdigital.in/salesforce-certification-training-institute-pune

23. Master-Detail (1: n) — (One Parent Object and Many Child Objects) • The record of child object gets automatically deleted when we delete the master object. • To create a child object parent object reference field is required. • Child object does not have separate sharing but it derives from Parent object, the detail records inherits the sharing and security settings of respective master record. • The Owner field is automatically set to the owner of its associated master record as owner field is not available at detail side (child object). victoriousdigital.in/salesforce-certification-training-institute-pune

24. The detail record must have the master detail relationship field on its page layout. • Administrators select Allow reprinting option in the master-detail relationship definition to represent child records in master-detail relationship on custom objects. • Master-detail relationships can be defined on two custom objects. • One can define this relationship between one custom object and one standard object but in such relationship the standard object cannot be on the detail side of a relationship with a custom object. The data of custom object is displayed on page layout. • master-detail relationship can’t be created on objects where the User or Lead objects are the master. victoriousdigital.in/salesforce-certification-training-institute-pune

25. Lookup (1: n)  • Lookup is also one-to-many relationship but in this relationship two objects has no effect on deletion or security. • Child objects are independent • Child object have separate setting • If we delete parent object child object will remain in system. • Child may or may not have parent. victoriousdigital.in/salesforce-certification-training-institute-pune

26. Self •  In this relationship the object is self-referred. E.g. Add on Card on your credit card • an object has a lookup with itself, it is a self-relationship. A self relationship creates a tree diagram of the objects. For example, the account has a lookup on himself, called Parent Account. victoriousdigital.in/salesforce-certification-training-institute-pune

27. Hierarchical • This is also (1: N) Lookup relationship • But can only be defined on User object. In this we can use lookup field to associate one user with other user. • relationship is a special lookup relationship available only for the user object. It allows users to use a lookup field to associate one user with another that does not directly or indirectly refer to itself. For example, you can create a custom hierarchical relationship field to store each user's direct manager. victoriousdigital.in/salesforce-certification-training-institute-pune

28.  Many-to-many Very Very IMP • master-detail relationships can be used to model many-to-many relationships between any two objects. • In many-to-many relationship each record of one object is linked with multiple records from another objects and vice versa.  • We need to create custom junction object to create a many-to-many relationship and then master-detail relationship fields, are linked with this objects. victoriousdigital.in/salesforce-certification-training-institute-pune

29. Junction object • This object is used to create Many-to-Many relationship. • Salesforce support two relationship master detail and Lookup but both are 1:n that is one-to-many. • To define many-to-many relationship we need third object and that is called junction object. victoriousdigital.in/salesforce-certification-training-institute-pune

30. Example • Classroom and Courses • Can have multiple courses in 1 classroom on different time • Can have 1 course in multiple classroom • To understand this we need a junction object Course offerings victoriousdigital.in/salesforce-certification-training-institute-pune

31. Junction object Example • Create 3 custom objects • Classroom fields seats • Course field Name • Junction Course offerings • Fields start date, enddate,current occupancy • One formula field later • On course offering have 2 master detail relationship one to classroom and other to Course victoriousdigital.in/salesforce-certification-training-institute-pune

32. victoriousdigital.in/salesforce-certification-training-institute-punevictoriousdigital.in/salesforce-certification-training-institute-pune

33. victoriousdigital.in/salesforce-certification-training-institute-punevictoriousdigital.in/salesforce-certification-training-institute-pune

34. victoriousdigital.in/salesforce-certification-training-institute-punevictoriousdigital.in/salesforce-certification-training-institute-pune

35. victoriousdigital.in/salesforce-certification-training-institute-punevictoriousdigital.in/salesforce-certification-training-institute-pune

36. victoriousdigital.in/salesforce-certification-training-institute-punevictoriousdigital.in/salesforce-certification-training-institute-pune

37. victoriousdigital.in/salesforce-certification-training-institute-punevictoriousdigital.in/salesforce-certification-training-institute-pune

38. victoriousdigital.in/salesforce-certification-training-institute-punevictoriousdigital.in/salesforce-certification-training-institute-pune

39. Model • Themodel is your database objects in Salesforce. The include the standard Salesforce objects like Leads, Contacts, Accounts, Opportunities etc but it also includes any custom objects you've created. Think of it like this - the "model" represents your data model in terms of MVC. victoriousdigital.in/salesforce-certification-training-institute-pune

40. VIEW • The view represents the presentation of the data (i.e. the user interface). • Pages - While often just called "pages", what we are talking about is Visualforce pages. They are the building blocks of the user interface. Visualforce uses HTML to lay out the appearance of the application interface. Each page is referenced by a unique URL just like a regular webpage. The pages themselves also contain Visualforce Components which can be invoked by simple tags inside the page.  • Components - these are both standard and custom Visualforce Components. Think of them like widgets that you can add to your pages. Once you write the code once, you can reuse it on multiple pages. Components are important because they allow for this reuse. Components can be styled with CSS. victoriousdigital.in/salesforce-certification-training-institute-pune

41. CONTROLLER • Controllers are the building blocks of the actual application logic. The controllers are written in Apex code and they end up controlling and enforcing all the business logic. Remember that one of the key design elements of MVC is to separate the logic from the UI. The presentation layer (the view) shouldn't be mixed with a bunch of business logic. Pages interact with the controller through components which shuttle the data and specifies what happens when the user actually interacts with the UI. Salesforce has pre-built controllers for many of the standard actions like View, Edit, Save. If you want to add new behavior though you can extend or build new controllers (custom controllers) in Apex. victoriousdigital.in/salesforce-certification-training-institute-pune

42. Roll-up Summary Field • A roll-up summary field is custom object field which calculates values from related records child records detail records or the records in a related list. • Roll-up summary field is created to display a value in a master record based on the values of fields in a detail record. • Roll-up summary can be defined on Master-Detail relationship only. victoriousdigital.in/salesforce-certification-training-institute-pune

43. Types • Assumption child record has fees field of master • Count-count of all child records on master • Sum- field on child for aggregation referred sum of fees field on child • Min minimum value of fees in all child records • Max maximum value of fees in all child records • Go to App Setup | Create | Objects and click on New field and Select Roll up summary field. victoriousdigital.in/salesforce-certification-training-institute-pune

44. victoriousdigital.in/salesforce-certification-training-institute-punevictoriousdigital.in/salesforce-certification-training-institute-pune

45. Formula & Cross Object Formula Field in Salesforce: • Formula Field is a read only field whose value is evaluated from the formula or expression defined by us. We can define formula field on both standard as well as custom objects. Any change in expression or formula will automatically update the value of formula field. victoriousdigital.in/salesforce-certification-training-institute-pune

46. Return types of Formula Fields • We can define formula field for 7 types: • Number • Currency • Percent • Date • Date/Time • Checkbox • Text victoriousdigital.in/salesforce-certification-training-institute-pune

47. Cross Object Formula Field • Cross Object Formula Fields are the fields which are based on a Cross-object formulas. • The cross object formulas are defined on two related objects and reference merge fields on those objects. • This field is built on child object. It is also known as Reference formula. We can apply cross-object fields up to 10 levels.  Cross-object formulas can reference merge fields from a master object as well as if field is at detail side then it can merge field from a master-detail relationship. Cross Objects formula can also be defined on lookup relationships. victoriousdigital.in/salesforce-certification-training-institute-pune

48. Record types • Record types allow you to offer different business processes, picklist values, and page layouts to different users based on their profiles. Record types can be used in various ways, for example: • Create record types for Account to differentiate type of account for one business process with another and offer different picklist values for each. victoriousdigital.in/salesforce-certification-training-institute-pune

49. Record types allow you to associate different business processes and subset of pick list value to different users based on their user profile. • They are used to drive which page layouts users see when viewing records, based on their user profile. • Benefits of record types: • Tailors user interaction experience to specific business needs. • Allows for easier administration as there are fewer fields to maintain. • Creating Record Types: • Example to create record types: In this example I am creating record type for Case object. • Setup->Customize->Object(Account,case Contact)>Record Type victoriousdigital.in/salesforce-certification-training-institute-pune

50. Pagelayouts • Page Layout • The organization of fields, custom links, and related lists on an object detail or edit page. • Used to organize UI pages for your users: • –          Which fields, related lists, and Custom links a user’s sees. • –          Field properties – visible, read-only and required. • –          Page section customizations. • NOTE: Establish unique layouts for different business scenarios. • Creating Page Layout: • Following is example to create page layout for case object. • Set Up->Customize->Object(Account,Contact,case)>Page Layout->Click on New button • Fill Mandatory details • Drag and drop required to the layout and save page layout. victoriousdigital.in/salesforce-certification-training-institute-pune