Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1. MVC architecture
2. Sandboxes
3. Custom objects and standard objects
4. Tabs
5. Custom fields
6. standard fields
7. datatypes
8. relationships
9. Pagelayouts
10. formula fields
11. cross object formula fields
12. junction objects
13. workflows
14. validation rules
15. roll up summary
16. process builder
17. record types
18. apex
19. vf pages
20. developer consoler
21. soql
22. sosl
23. relationship query
24. DML operations and associated query limits
25. handle errors
26. Apex triggers
27. trigger context variables
28. order of execution
29. apex classes
30. sharing/access to classes
31. life cycle of apex transaction
32. static varaibles
33. create test data
34. run apex test
35. code coverage
36. test classes
37. batch apex
38. controllers
39. Custom setting
40. Access modifiers of test classes, importance of @istest, @istestvisible, startTest and stopTest
methods.
41. page references
42. stdlist controllerz
43. governor limits
44. Approval processes
45. Visualflows
46. Appexchange
47. Managed and unmanaged packages
48. Data import wizard
49. Data loader
50. Lighting components
51. Dynamic soql
52. Exception handling
53. With sharing and without sharing
54. Usage of normal DML operations/Database DML operations
55. Debug Logs
56. Schema methods
57. Dynamic apex
1.MVC architecture
2.Sandboxes.
4.Tabs
Tab is user interface to create records for object and to view the records in objects.
We have three types of tabs
Custom object tab-display data of ur custom object
Web tab- display any external web-based application or web page
Vf tab- display data from a Visualforce page.
Lighting component tabs-Lighting componets available in salesforce app.
Not supported in salesforce classic
Lighting page tabs-
5.Custom fields-
Add custom field on custom object or standard object to enter data whatever u wanted and
optionally control security at the field level.
6.Standard fields-
System fields.
Id-15 digits-case sensitive
ID-18 digit-Case insensitive
Audit fields like CreatedbyID,Createddate,lastmodifiedby,etc.
7.Data types-all variables and expression has data type like primitive,Sobject,enum.
A primitive-integer,Double,Long,date,datetime,String ID,Boolean
Field data types-picklist,multiselect
picklist,Formula,Curreny,Phone,email,Url,Relationship,text,textarea etc.
sObject like account,contact,mycustomobject__c
Collections like List,set,Map.
8.Relationship
9.Page Layouts-
Control the layout and organization of buttons, fields, s-controls, Visualforce, custom links,
and related lists on object record pages.
Used to organize UI pages for ur users.-Fields,Related lists,custom links,
Can set field properties-Visible,Read only,and required.
Page section customizations.
MINI Pagelayout-Within pagelayout u can access a mini page layout.
The mini pagelayout defines the hover details that display when u mouse over a field on as
objects detail page.
Page layout assignments are specified in profiles onlytheyre not available in permission
sets.
10.Formula fields-
You cant use long text area, encrypted, or Description fields in formulas.
Cross object formula always works from child to parent means you can create formula on
child to reference parent only and if parent has to refer children then it might be roll up
summary field
Cross-object formulas can reference merge fields from a master (parent) object if an
object is on the detail side of a master-detail relationship.
Cross-object formulas also work with lookup relationships
If cross object formula field is created with reference to another object and displayed on
page layout, even if user doesnt have access to that object can see the data.Eg;If Cross
object formula filed is created on case that reference to account field, and displayed on case
page layout then user who doesnt have access to account object can also see this field.
CROSS OBJECT FORMULA ALWAYS WORKS FROM CHILD TO PARENT MEANING YOU CAN
CREATE FORMULA ON CHILD AND REFERENCE FIELDS FROM IT'S PARENT.
Cross-Object formula referencing Currency field converts the currency value as per the
record where the formula field is added.
You cant reference cross-object formulas in roll-up summary fields.
Important - Cross-Object formula is all about getting information of Parent object
in Child object. So in the exam, if you are getting questions where you need to
fetch child information in parent record, then it should be roll-up summary field.
Formula fields Cross object formula field
Can be created on one single object Span two related objects
On same record. You can reference fields from objects that
are up to ten relationships away
are used except when creating default Cross-object formulas are available
values anywhere
13. Workflows
Are automated process to send email alerts,assign task,update fields,send out bound
messages.
Format of outbound messages-XML
14.Validation rules
Validation rules verify that data entered by users in records meet the standards you
specify before they can save it.
You can create validation rules for objects, fields, campaign members, or case
milestones.
A validation rule can contain a formula or expression that evaluates the data in one
or more fields and returns a value of True or False.
Vlookup only works in validation rule.
15.Roll up summary
Roll-up summary fields are only available on the master object in a master-detail
relationship.
Created on parent object to child object to do some calucation on child record.
SUM,AVG,MIN,MAX,COUNT.
Can create 25 roll up summary fields for an object.
IF A PARENT HAS TO REFER TO CHILDREN THEN IT MIGHT BE A ROLL-UP SUMMARY FIELD IF
THERE IS A MASTER-DETAIL RELATION OR OTHERWISE A TRIGGER FOR MORE COMPLEX
LOGIC.
17.record types
Record types let you offer different business processes, picklist values, and page layouts to
different users.
You can assign record types to users in their profile or permission sets, or a combination of both.
18.apex https://www.tutorialspoint.com/apex/
19.vf pages
20.developer consoler
21.soql
22.sosl
23.relationship query
24.DML operations and associated query limits
25.handle errors
26.Apex triggers
Trigger can invoke apex code to perform some custom task just b4 or after record
created,deletd.
Fires on dml actions-insert,update,delete,undelete,upsert,merge.
Before triggers-perform task before a record is inserted,updated or dleted.
After triggers-
isExecuting
isInsert
isUpdate
isDelete
isBefore
isAfter
isUndelete
new
newMap
old (update and delete only)
oldMap (update and delete only)
size
28.order of execution
29.apex classes
30.sharing/access to classes
36.code coverage
37.test classes
38.batch apex
39.controllers
40.Custom setting
41.Access modifiers of test classes, importance of @istest, @istestvisible, startTest and stopTest
methods.
42.page references
43.stdlist controllerz
44.governor limits
45.Approval processes
46.Visualflows
47.Appexchange
50.Data loader
51.Lighting components
52.Dynamic soql
53.Exception handling