401 Dumps Part - 9

• Custom fields are stored for 45 days after deletion
  
  
• Two types of custom tabs 
  –
• Custom object tabs-displays the data of your custom object in UI tab
  
  
• Web tab-display any external web-based application or web page in UI tab
  
  
• Blank spaces created with the enhanced page layout editor will be respected by the original page layout editor-you cannot edit them around in the original editor.
  
  
• Queue-
  
  
• Queues allow groups of users to manage a shared workload more effectively
  
  
• A queue is a location where records can be routed to await processing by a group member
  
  
• Records remain in the queue until a user accepts them for processing or they are transferred to another queue
  .
• Developers can specify the set of objects that are supported by each queue,as well as set of users are allowed to retrieve records from the queue.
  
  
• Any member of a queue has the same access to all records in the queue that an owner would have.
  
  
• Workflow rule configuration-

Entry criteria:which records

-object type

-evaluation criteria

-rule criteria

Timing:whwn to execute action

-immediately

Time dependent

actions:what to do

-Assign task

-Send Email alert(1.from current user’s email address 2.From organization wide email)

-update field

-post outbound SOAP message

• Record type name and ID can be formlula merge fields
  
  
• Standard and custom users merge fields for the current user are also available,allowing user and profile specific validation rule
  
  
• IsChanged(field) function allows validation to be conditional based on whether a specific value has changed.
  
  
• PriorValue(field) allows access to previous value of a field.
  
  
• IsNew() allows different validation rules for create vs. update actions.
  
  
• License type-
  
  
• Each user must have a user license
  
  
• Different type of user license allow different levels of access
  
  
• Feature licensedetermine wheather users have acces to additional features like mobile or content.
  
  
• Profile-
  
  
• Every user has only one profile.
  
  
• We can group the things that profile controls in 3 categories-
  permission,access to data and user interface.
  
  
• Permissions:general user permission,administrative permission,standard/custom object CRUD
  
  
• Access to data:field level security,object CRUD,login hours and IP ranges
  
  
• User interface:page layouts,record types,tabs,application.
  
  
• Profile controls-
  
  
• Tab settings determines which tabs a user sees when he logs in
  
  
• Permissions determine what users can do to records to which they have access
  
  
• Sets the hours when users with a particular profile can use the system
  
  
• Sets the IP address from which users with a particular profile can log in.
  
  
• There are 6 standard profiles.permissions on standard profiles cannot be customized.
  
  
• Each profile is associated with a license type.
  
  
• Typically,organizations will have one profile for each actor.
  
  
• Levels of record access
  
  
• Full access privileges:

-view

-edit

-transfer ownership

-delete

-share

• Read/write privilege:

-View

-Edit

• Read only privilege

-view

• Ways to obtain access
• Full access-

-owner field-user.queue number

-above user(who has ownership in role hierarchy)

-profile permission:”modify all data”

-object permission:”modify all”

• Read/write or read only access-

-org wide default

-above user(who has read/write or read only access) in role hierarchy

-manual sharing

-apex sharing

-sharing rules

-profile permission:”view all data”

-object permission:”view all”

• Child records in master details relationship inherit their org wide default from parent
  
  
• Child records in lookup relationship have independent org wide default from their parent.
  
  
• With standard object,access to records rolls up through the role hierarchy
  
  
• With custom object,developers choose whether or not access should roll up through the role hierarchy.
  
  
• Apex sharing reasons are defined for custom objects only.
  
  
• Establishing apex sharing reasons allow developers to define the reason that a user or group of users might have access to a record.
  
  
• Debug logs record error and system processes thet occur in the org.debug log contain information about-database change,automated workflow processes such as workflow rule,assignment rule,approval process,validation rule etc.
  
  
• Time dependent workflow can’t be used when a rule is set to be evaluated ‘every time a record is created or updated’.