salesforce order of execution

salesforce order of execution

When you save a record with an insertupdate, or upsert statement, Salesforce performs the following events in order.

Before Salesforce executes these events on the server, the browser runs JavaScript validation if the record contains any dependent picklist fields. The validation limits each dependent picklist field to its available values. No other validation occurs on the client side.

On the salesforce server,

  1. Loads the original record from the database or initializes the record for an upsert statement.
  2. Loads the new record field values from the request and overwrites the old values.

    If the request came from a standard UI edit page, Salesforce runs system validation to check the record for:

    • Compliance with layout-specific rules
    • Required values at the layout level and field-definition level
    • Valid field formats
    • Maximum field length

    When the request comes from other sources, such as an Apex application or a SOAP API call, Salesforce validates only the foreign keys. Before executing a trigger, Salesforce verifies that any custom foreign keys do not refer to the object itself.

    Salesforce runs user-defined validation rules if multiline items were created, such as quote line items and opportunity line items.

  3. Executes all before triggers.
  4. Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any user-defined validation rules. The only system validation that Salesforce doesn’t run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
  5. Executes duplicate rules. If the duplicate rule identifies the record as a duplicate and uses the block action, the record is not saved and no further steps, such as after triggers and workflow rules, are taken.
  6. Saves the record to the database, but doesn’t commit yet.
  7. Executes all after triggers.
  8. Executes assignment rules.
  9. Executes auto-response rules.
  10. Executes workflow rules.
  11. If there are workflow field updates, updates the record again.
  12. If the record was updated with workflow field updates, fires before update triggers and after update triggers one more time (and only one more time), in addition to standard validations. Custom validation rules, duplicate rules, and escalation rules are not run again.
  13. Executes processes and flows launched via processes and flow trigger workflow actions.

    When a process or flow executes a DML operation, the affected record goes through the save procedure.

  14. Executes escalation rules.
  15. Executes entitlement rules.
  16. If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.
  17. If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.
  18. Executes Criteria Based Sharing evaluation.
  19. Commits all DML operations to the database.
  20. Executes post-commit logic, such as sending email.

Additional Considerations

Note the following when working with triggers.

The order of execution isn’t guaranteed when having multiple triggers for the same object due to the same event. For example, if you have two before insert triggers for Case, and a new Case record is inserted that fires the two triggers, the order in which these triggers fire isn’t guaranteed.

Please refer to below official link for more details:

Trigger and Order of Execution

For interview questions related to trigger, refer to below link:

Salesforce Interview Questions on Triggers

Permanent link to this article: http://www.sfdcpoint.com/salesforce/salesforce-order-of-execution/

Trigger context variables in salesforce

Trigger context variables in salesforce

What is Trigger context variables in salesforce?

All triggers define implicit variables that allow developers to access run-time context. These variables are contained in the System.Trigger class.

Following are the context variable available in triggers. Please note variable availability in trigger varies according to the type of trigger events.

  • isExecuting: Returns true if the current context for the Apex code is a trigger, not a Visualforce page, a Web service, or an executeanonymous() API call.
  • isInsert: Returns true if this trigger was fired due to an insert operation, from the Salesforce user interface, Apex, or the API.
  • isUpdate: Returns true if this trigger was fired due to an update operation, from the Salesforce user interface, Apex, or the API.
  • isDelete: Returns true if this trigger was fired due to a delete operation, from the Salesforce user interface, Apex, or the API.
  • isBefore: Returns true if this trigger was fired before any record was saved.
  • isAfter: Returns true if this trigger was fired after all records were saved.
  • isUndelete: Returns true if this trigger was fired after a record is recovered from the Recycle Bin (that is, after an undelete operation from the Salesforce user interface, Apex, or the API.)
  • new: Returns a list of the new versions of the sObject records. This sObject list is only available in insert, update, and undelete triggers, and the records can only be modified in before triggers.
  • newMap: A map of IDs to the new versions of the sObject records. This map is only available in before update, after insert, after update, and after undelete triggers.
  • old : Returns a list of the old versions of the sObject records. This sObject list is only available in update and delete triggers.
  • oldMap: A map of IDs to the old versions of the sObject records. This map is only available in update and delete triggers.
  • size: The total number of records in a trigger invocation, both old and new.

 

Context Variable Considerations

  • trigger.new and trigger.old cannot be used in Apex DML operations.
  • You can use an object to change its own field values using trigger.new, but only in before triggers. In all after triggers, trigger.new is not saved, so a runtime exception is thrown.
  • trigger.old is always read-only.
  • You cannot delete trigger.new.

 

For interview questions related to trigger, refer to below link:

Salesforce Interview Questions on Triggers

For more details about context variable, please refer to below official link:

Trigger Context Variable

 

Permanent link to this article: http://www.sfdcpoint.com/salesforce/trigger-context-variables-in-salesforce/

Salesforce Interview Questions on Triggers

Salesforce Interview Questions on Triggers

In this post I am going to share Salesforce Interview Questions on Triggers

What is a Trigger?

Apex triggers enable you to perform custom actions before or after events to records in Salesforce, such as insertions, updates, or deletions. Just like database systems support triggers, Apex provides trigger support for managing records.

Use triggers to perform tasks that can’t be done by using the point-and-click tools in the Salesforce user interface. For example, if validating a field value or updating a field on a record, use validation rules and workflow rules instead.

What is Trigger Syntax?

trigger TriggerName on ObjectName (trigger_events) {
   code_block
}

What are the various event on which a trigger can fire?

A trigger is a set of statement which can be executed on the following events. In above trigger events one or more of below events can be used with comma separated.

  • before insert
  • before update
  • before delete
  • after insert
  • after update
  • after delete
  • after undelete

What are different type of Triggers?

There are two types of triggers:

  • Before triggers are used to perform a task before a record is inserted or updated or deleted. These are used to update or validate record values before they are saved to the database.
  • After triggers are used if we want to use the information set by Salesforce system and to make changes in the other records. are used to access field values that are set by the system (such as a record’s Id or LastModifiedDate field), and to affect changes in other records. The records that fire the after trigger are read-only.

What are the considerations while implementing the Triggers?

Consider the following before implementing the triggers.

  • Upsert trigger fires on 4 different events :- before(insert, update), after (insert, update)
  • Merge trigger are fired on both events on delete
  • Field history is updated after the trigger has successfully finished processing data.
  • Any callout should be asynchronous so that trigger does not have to wait for the response.
  • A trigger cannot have a static keyword in its code.
  • If a trigger completes successfully the changes are committed to the database and if it fails the transaction is rolled back.

Read the Apex Developer Guide for more detailed considerations.

What are context variables in triggers?

All triggers define implicit variables that allow developers to access run-time context. These variables are contained in the System.Trigger class.

Following are the context variable available in triggers. Please note variable availability in trigger varies according to the type of trigger events.

  • isExecuting: Returns true if the current context for the Apex code is a trigger, not a Visualforce page, a Web service, or an executeanonymous() API call.
  • isInsert: Returns true if this trigger was fired due to an insert operation, from the Salesforce user interface, Apex, or the API.
  • isUpdate: Returns true if this trigger was fired due to an update operation, from the Salesforce user interface, Apex, or the API.
  • isDelete: Returns true if this trigger was fired due to a delete operation, from the Salesforce user interface, Apex, or the API.
  • isBefore: Returns true if this trigger was fired before any record was saved.
  • isAfter: Returns true if this trigger was fired after all records were saved.
  • isUndelete: Returns true if this trigger was fired after a record is recovered from the Recycle Bin (that is, after an undelete operation from the Salesforce user interface, Apex, or the API.)
  • new: Returns a list of the new versions of the sObject records. This sObject list is only available in insert, update, and undelete triggers, and the records can only be modified in before triggers.
  • newMap: A map of IDs to the new versions of the sObject records. This map is only available in before update, after insert, after update, and after undelete triggers.
  • old : Returns a list of the old versions of the sObject records. This sObject list is only available in update and delete triggers.
  • oldMap: A map of IDs to the old versions of the sObject records. This map is only available in update and delete triggers.
  • size: The total number of records in a trigger invocation, both old and new.

Refer to Trigger context variables in salesforce link for more details.

How is Trigger.New Different from Trigger.newMap?

Trigger.New variable returns the list of sObject which has invoked the trigger and Trigger.NewMap returns the map of ID’s with the newly entered records. NewMap is only available in after insert, before and after the update and after undelete.

How is Trigger.new different from Trigger.old?

Trigger.New variable returns the list of sObject which has invoked the trigger and Trigger.old returns a list of the older versions of the records which have invoked the trigger. Trigger.Old is only available in update and delete events

Can a trigger call a batch class?

Yes, we can call a batch class in the trigger as we do in the normal apex code.

Can a trigger make a call to Apex callout method?

we can call a callout method in Apex Trigger but the only condition is that it has to be an asynchronous callout because the trigger flow cannot wait on the response received by the callout method.

Define Recursive Trigger and how to avoid it?

There is a possibility that the result of the trigger can end up calling the same trigger again and can run in a loop, this is known as a recursive trigger. To avoid this scenario we should create a static variable and check the value of this variable before we execute anything in the trigger. For more details refer to below link:

Avoid recursive trigger in salesforce

What do you mean by the bulkifying trigger?

A trigger should be able to handle single record and thousands of record. There are two important point for it:

  • Write triggers that operate on collections of sObjects.
  • Write triggers that perform efficient SOQL and DML operations.

If we will not follow above point we may hit governor limit when records are created/updated/deleted in mass using data loader or other tool.

Bulk Apex Trigger trailhead

Is there any limit on number of triggers define on an object?

We can define as many triggers on an object as we want but it is recommended to have one trigger per object because the order of execution of different trigger is not guaranteed and any trigger can fire first.

Can you explain the order of execution in Triggers?

Following is the order of execution of events which Salesforce perform before a DML Event.

  1. The record is loaded from the database or is initialized in case of upset statement.
  2. New record’s field values are overwriting the old values, now depending on the origin of the request this flow varies: if the request is from a UI page then the following validations are performed by Salesforce:
    1. Any layout specific rules are checked
    2. All the required values are checked at layout and field level
    3. All the field formats are validated along with the maximum length of field values

If the request originates other than UI then Salesforce only checks for Validation of foreign keys.

  1. Now all the before triggers are executed at the database.
  2. Most of the validations are performed again to verify that all the required fields are holding some values and are not null, at this step user defined validations are also executed and the only validation which is not repeated in this step are the rules specific to the layout.
  3. After the success of the previous step, the record is reviewed for duplicate records, by running the duplicate rule. If a duplicate is found the flow is stopped and no further actions performed.
  4. In this step, record is saved to the database but it not committed yet.
  5. Now all the after Triggers are executed.
  6. In this step, assignment rules are executed.
  7. Now if there is any auto-response rule is present then they are executed.
  8. Next in the queues are the workflow, they are executed after the auto response.
  9. If the workflow was updating a field, then the fields updated in this step and the flow after this step varies if this was the case.
  10. If a field was updated then the before and after update triggers are fired once more and standard validation are also executed again. Custom validation escalation rule and duplicate rules are not required to run again.
  11. Once the execution has reached this stage, then process is fired if there are any declared on the object.
  12. Now the escalation rules are executed.
  13. Entitlement rules are executed if any.
  14. If there are any roll-up summary field, then they are calculated at this step and the parent object go through the save process.
  15. Now the sharing rules are executed.
  16. If we reach this stage, then that means no error has occurred and the data is ready to be committed to the database and is committed now.
  17. Now if there is any post-commit logic like email, then that is executed.

 

For more details about trigger please refer below links

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers.htm

Trailhead get started with Triggers

Other posts related to interview questions

Salesforce lightning interview questions

I will keep adding more questions to Salesforce Interview Questions on Triggers.

Permanent link to this article: http://www.sfdcpoint.com/salesforce/salesforce-interview-questions-on-triggers/

Organization Wide Defaults(OWD) in salesforce

Organization Wide Defaults(OWD) in salesforce

Organization Wide Defaults(OWD) in salesforce is the baseline level of access that the most restricted user should have. Organizational Wide Defaults are used to restrict access. You grant access through other means like(sharing rules, Role Hierarchy, Sales Teams and Account teams, manual sharing, Apex Sharing ). In simple words Organization Wide Defaults(OWD) specify the default level of access users have to each other’s records.

Object permissions determine the baseline level of access for all the records in an object. Org-wide defaults modify those permissions for records a users doesn’t own. Org-wide sharing settings can be set separately for each type of object.

Important to note that Org-wide defaults can never grant users more access than they have through their object permission.

There are mainly four levels of access :

  • Public Read/Write/Transfer (only available of Leads and Cases)
  • Public Read/Write : All users can view, edit, and report on all records(Given that they have object level permission).
  • Public Read/Only : All users can view and report on records, but only the owner, and users above that role in the hierarchy, can edit them.
  • Private : Only the record owner, and users above that role in the hierarchy, can view, edit, and report on those records.

 

How to determine OWD for your org:

To determine the org-wide defaults you need for your app, ask yourself these questions about each object:

  1. Who is the most restricted user of this object?
  2. Is there ever going to be an instance of this object that this user shouldn’t be allowed to see?
  3. Is there ever going to be an instance of this object that this user shouldn’t be allowed to edit?
Organization Wide Defaults(OWD) in salesforce

Deciding owd in Salesforce

For more detail check this trailhead module.

Setting owd in Salesforce

  1. In Setup, use the Quick Find box to find Sharing Settings.
  2. Click Edit in the Organization-Wide Defaults area.
  3. For each object, select the default access you want to give everyone.
  4. To disable automatic access using your hierarchies, deselect Grant Access Using Hierarchies for any custom object that does not have a default access of Controlled by Parent.

 

owd in salesforce

owd in salesforce

 

 

Permanent link to this article: http://www.sfdcpoint.com/salesforce/organization-wide-defaults-owd-in-salesforce/

Salesforce Lightning Interview Questions

Salesforce Lightning Interview Questions

In this post I am going to share Salesforce Lightning Interview Questions

What is Lightning?

Lightning is the collection of tools and technologies behind a significant upgrade to the Salesforce platform. Lightning includes:

  • Experience: A set of modern user interfaces optimized for speed. This includes the Lightning Experience, Salesforce1 Mobile app and template-based communities.
  • Lightning Component Framework: A JavaScript framework and set of standard components that allow you to build reusable components to customize the Lightning Experience, Salesforce1 Mobile app and template-based communities and build your own standalone apps.
  • Visual Building Tools: Drag-and-drop technologies for fast and easy app building & customizations. Use the Lightning App Builder to customize the Lightning Experience and Salesforce1 Mobile app. Use the Community Builder to customize template-based communities.
  • Lightning Exchange: A section of the AppExchange where you can find 70+ partner components to jumpstart your development.
  • Lightning Design System: Style guides and modern enterprise UX best practices to build pixel perfect apps that match the look and feel of the Lightning Experience and Salesforce1 Mobile app.
Salesforce Lightning Interview Questions

Salesforce Lightning Interview Questions

What are the tools included in lightning ?

  • Lightning Component Framework – Components and extensions that allow you to build reusable components, customize the Salesforce1 Mobile App, and build standalone apps.
  • Lightning App Builder – A new UI tool that lets you build apps lightning fast, using components provided by Salesforce and platform developers.
  • Lightning Connect – An integration tool that makes it easier for your Force.com app to consume data from any external source that conforms to the OData spec.
  • Lightning Process Builder – A UI tool for visualizing and creating automated business processes.
  • Lightning Schema Builder – A UI tool for viewing and creating objects, fields, and relationships.

What is Aura? Why do I see the aura: namespace in the code?

Aura is the open source technology that powers Lightning Components. The aura: namespace contains all of the basic building blocks for defining components and applications.

Is Lightning an MVC framework?

No, it’s a component-based framework.

What is difference between Visualforce Components and Lightning Components?

Visualforce components are page-centric and most of the work is done on the server. Lightning is designed from the component up, rather than having the concept of a page as its fundamental unit. Lightning Components are client-side centric, which makes them more dynamic and mobile-friendly.

Where we can display lightning component?

There are a number of possibilities for display lightning component..

  •  Lightning Experience: We can display component in the Lightning Experience using the App Builder. We can edit the home page, edit a record detail page or create/edit a new app page to include it.
  •  Salesforce1 Mobile app: We can display component in the Salesforce1 Mobile app by creating a custom Lightning tab that references it and adding that tab in mobile navigation.
  • Standalone Lightning app: By create a standalone Lightning app (e.g. myapp.app) and include component in this app. Access Lightning app by URL.
  • Add Apps to the Lightning Experience App Launcher: Your Lightning Components apps and custom tabs are available from the App Launcher.
  • Add Apps to Lightning Experience and Salesforce App Navigation:  You can add Lightning components tabs to an app and they display as items in the app’s navigation bar.
  • Lightning App Builder and Community Builder : We can display component in template-based (e.g. Napili) community using the Community Builder. Build custom user interfaces using your own Lightning components, or those you install from AppExchange, for desktop and mobile devices.
  • Add Lightning Components to Lightning Pages: A Lightning Page is a custom layout that lets you design pages for use in the Salesforce mobile app or in Lightning Experience. You can use a Lightning Page to create an app home page and add your favorite Lightning component, such as the Expenses app we’ll be creating in this module, to it.
  • Add Lightning Components to Lightning Experience Record Pages: You can customize Lightning Experience record pages by adding a Lightning Component.
  • Launch a Lightning Component as a Quick Action: Create actions using a Lightning component, and then add the action to an object’s page layout to make it instantly accessible from a record page.
  • Create Stand-Alone Apps: A standalone app comprises components that use your Salesforce data and can be used independently from the standard Salesforce environment.
  • Run Lightning Components Apps Inside Visualforce Pages: Add Lightning components to your Visualforce pages to combine features you’ve built using both solutions. Implement new functionality using Lightning components and then use it with existing Visualforce pages.
  • Run Lightning Components Apps on Other Platforms with Lightning Out: Lightning Out is a feature that extends Lightning apps. It acts as a bridge to surface Lightning components in any remote web container. This means you can use your Lightning components inside of an external site (for example, Sharepoint or SAP), or even elsewhere on the platform such as on Heroku.
  • Customize Flow Screens: Create a flow to guide your users through a business process. By default, you can add simple fields like inputs or radio buttons to a flow screen. But with a custom Lightning component, you can fully customize the look-and-feel and functionality of your screen.

What are the different Lightning component bundles?

  • Component :UI for lightning component
  • Controller: Contains client-side controller methods to handle events in the component.
  • Helper: JavaScript functions that can be called from any JavaScript code in a component’s bundle
  • Style: Contains styles for the component.
  • Document: A description, sample code, and one or multiple references to example components
  • Design: File required for components used in Lightning App Builder, Lightning pages, or Community Builder.
  • SVG: Custom icon resource for components used in the Lightning App Builder or Community Builder.
  • Renderer: Client-side renderer to override default rendering for a component.

Click Here for official Salesforce documentation.

What is Lightning Experience?

Lightning Experience is the name for the all new Salesforce desktop app, with new features, built with a modern user interface and optimized for speed.

What is Lightning Design System?

Style guides and modern enterprise UX best practices to build pixel perfect apps that match the look and feel of the Lightning Experience and Salesforce1 Mobile app. Click Here for official link.

What happens to my existing Visualforce Pages?

They’ll continue to be supported in the current UI and Lightning Experience. See the Trailhead module on this topic.

What are the type of events into Salesforce Lightning component?

  • Application Event – Scope of this event is throughout the lightning App and any component which has registered for this event would get a notification.
  • Component Event– Scope of this event is within itself or the parent component of this event, all the components declared within the parent component would get notified of this event.
  • System Event- these are the events fired by Salesforce’s system during the lifecycle of the lightning app.

 

What is the basic difference between Application Event and Component Event?

Component events are used to do communication between child and parent. They use bubbling and capture same as used in DOM events. A change in a child component can be communicated to the parent component via component event.

Application events are used to communicate any change in the component to a broader audience. Any component who has registered for this event will get a notified.

Which interface we are supposed to implement so that a lightning component can be used as a Tab?

We need to implement the following “force:appHostable” so that we can use the component as a Tab.

Which interface we are supposed to implement so that a lightning component can be used as quick action?

We need to implement the following “force: lightningQuickAction” so that we can use the component as a Quick Action.

Can we Include One Lightning component to another ?

Yes we can include one Lightning component inside another Lightning component

How can we use Lightning Components with the Salesforce1 Mobile App ?

We can create a custom Lightning tab that points to our component and include that tab in our Salesforce1 Mobile navigation.

How can we use a lightning component in a VisaulForce Page?

A Lightning component can be embed in any webpage using a very powerful and flexible feature, Lighting out. When used with Visualforce some complexity becomes simpler.
Lightning component can be added to Visualforce page in three steps:

1. We have to first Add the Lightning Components for Visualforce JavaScript library to your targetted Visualforce page using the tag.

2. Next we have to create and refer a Lightning app which is used to the component dependencies.

3. Lastly we need to write a JavaScript function which will finally create the the component on the page using $Lightning.createComponent()

 How to ensure FLS while working with Lightning Component?

FLS and CRUD are not automatically enforced in the lightning component whenever any object is referenced in the Apex Controller and the component will display the fields and records for which the users do not have access. Therefore we should manually enforce the FLS and CRUD in the Apex Controller. Also when we use Lightning Data service  it takes care of FLS and CRUD for us.

Please refer to below links for more detail about lightning:

Lightning FAQ

Lightning Design System

Lightning Experience Rollout Specialist

Lightning Component Framework Specialist

Lightning Experience Specialist

Lightning Components Developer Guide

I will keep adding more questions to Salesforce Lightning Interview Questions.

Permanent link to this article: http://www.sfdcpoint.com/salesforce/salesforce-lightning-interview-questions/

Salesforce Certified Community Cloud Consultant Exam

Salesforce Certified Community Cloud Consultant Exam Tips

How to pass Salesforce Certified Community Cloud Consultant Exam

My Experience

Salesforce Certified Community Cloud Consultant Exam is part of architect journey. But this is optional exam. But I will strongly recommend everyone to appear for his exam if you want to be Salesforce Certified Technical Architect(CTA). Communities management is very important topic from business prospective.

Credential Overview

The Salesforce Certified Community Cloud Consultant credential is designed for those who have experience implementing and consulting on the Salesforce Communities applications in a customer-facing role. Candidates should also be able to troubleshoot and solve platform issues.

Here are some examples of the concepts you should understand to pass the exam:

  • Enable, create, configure, manage membership, and deploy communities
  • Differentiate between the capabilities of different license types
  • Configure the community management console
  • Describe the infrastructure of communities
  • Employ build options

The Salesforce Certified Community Cloud Consultant candidate has the experience, skills, knowledge, and ability to:

  • Enable, Create, Configure, Manage Membership, and Deploy Communities.
  • Employ architecture design options.
  • Configure the community management console.
  • Describe the infrastructure of communities.
  • Employ build options.
  • Describe the capabilities of different deployment types.
  • Differentiate between the capabilities of different license types.
  • Exercise the capabilities of the Community Workspaces (Dashboards, Recommendations, Reputation, Moderation, Insights, Topics, etc.).
  • Exercise the capabilities of the Community Builder and Visualforce (Modify templates, Create new pages, Add / Remove Components, Custom Objects, Custom navigation, Branding, Articles/Knowledge).
  • Implement the appropriate security model for a given use case (Sharing & Users, Person Accounts, Profiles, etc.).
  • Determine if a community is SEO-enabled.
  • Employ fundamental best practices for adoption and engagement.
  • Invest time in studying the resources listed in this Exam Guide and the additional required study materials provided by Salesforce.

Official Study Materials

Official Exam page
Official Exam Guide contains full exam outline
free self-directed resource guides which contains all important links

Important Topics

Expand Your Reach with Communities Trail
Salesforce Communities Overview
My Domain
Communities User Licenses
How to share files in Chatter across communities
Grant Super User Access to Customer Users in Your Community
Share Records Owned By High-Volume Community Users
Grant High-Volume Community Users Access to Records Important
Using Templates to Build Communities
Communities Containers: Options for Building Salesforce Communities
Access Communities in the Salesforce App
Add Authenticated Site.com Pages to Community Tabs
How to Provision Salesforce Communities Users
salesforceben blog Quiz
salesforceben blog guide
proprofs quiz
automationchampion blog

Good Luck for exam 🙂

Permanent link to this article: http://www.sfdcpoint.com/salesforce/salesforce-certified-community-cloud-consultant-exam/

Salesforce Certified Mobile Solutions Architecture Designer Exam

Salesforce Certified Mobile Solutions Architecture Designer Exam Tips

How to pass Salesforce Certified Mobile Solutions Architecture Designer Exam

My Experience

This is one of easier exam from all architect exam. This is optional from Architect journey. I did not had any previous experience in building mobile app. But I had experience in using and customizing Salesforce 1 mobile app(Now its Salesforce App). I had never used Mobile SDK. So i decided to go through trailhead modules which were very helpful in understanding concept. I strongly recommend Develop with Mobile SDK trail if you do not have previous experience in using Mobile SDK. This trail will cover 50% of exam.

Credential Overview

The Salesforce Certified Mobile Solutions Architecture Designer credential is designed for those who assess the architecture environment and requirements and design and implement sound and scalable mobile solutions on the Force.com platform that meet those requirements. Candidates should have experience communicating solutions and design trade-offs to businesses and IT stakeholders.

Here are some examples of the concepts you should understand to pass the exam:

  • Describing the differences between Salesforce1, Native, HTML5 and Hybrid mobile architectures
  • Defining how a customer can choose between Salesforce1 solution and a Customer Mobile Solution
  • Understanding the Salesforce1 app and its configuration/customization options
  • Describing how mobile solution capabilities can be enhanced via connected devices (e.g., Wearables, iBeacons)

Official Study Materials

Official Exam page
Official Exam Guide contains full exam outline
free self-directed resource guides which contains all important links

Important Topics

Native, HTML5, or Hybrid: Understanding Your Mobile Application Development Options
Multi-Device Strategy
Develop with Mobile SDK Trail
Visualforce Mobile
Developing Offline Apps with Salesforce Mobile Services
Building Beautiful Apps With the Salesforce Mobile SDK
Mobile SDK Development Guide
Customize Your My Domain Login Page with Your Brand
MAR 20, 2014 BY STUART LEUNG 5 Ways the Internet of Things Will Make Marketing Smarter
Salesforce Wear Developer Pack
Salesforce Mobile App Security Guide
Salesforce Mobile Push Notifications Implementation Guide
Work Offline with the Salesforce App
Using SmartStore to Securely Store Offline Data

Good Luck for exam 🙂

Permanent link to this article: http://www.sfdcpoint.com/salesforce/salesforce-certified-mobile-solutions-architecture-designer-exam/

Permanent link to this article: http://www.sfdcpoint.com/salesforce/get-started-with-salesforce-dx/

Salesforce Certified Identity and Access Management Designer Exam

Salesforce Certified Identity and Access Management Designer Exam Tips

How to pass Salesforce Certified Identity and Access Management Designer Exam

My Experience

This was my fifth architect exam. I was searching online for this exam. In every post it was written that this is toughest exam from all architect exam. I too agree with all other posts that this is tougher as compare to other architect exam. Some of my friends also failed in this exam in first attempt. But still with good preparation you can crack this exam. Luckily and Credits to salesforce documentation I passed this exam in first attempt with very good score. I studied almost all links mentioned in resource guides. I will cover important topics at end of this post. My advice: Don’t get scared by this exam. Study all important topics, you can crack this exam easily.

Credential Overview

The Salesforce Certified Identity and Access Management Designer credential is designed for those who assess the architecture environment and requirements and design sound, scalable and high-performing solutions on the Force.com platform that meet the Single Sign-on (SSO) requirements. Candidates should have experience communicating solutions and design trade-offs to businesses and IT stakeholders.

Here are some examples of the concepts you should understand to pass the exam:

  • Understanding Configuration requirements of delegated authentication
  • Understanding configuration requirements of SAML
  • Knowledge of when to use IDP initiated vs. service provider initiated
  • Describing provisioning and de-provisioning related to SAML, Oauth, and OpenID Connect

Official Study Materials

Official Exam page
Official Exam Guide contains full exam outline
free self-directed resource guides which contains all important links

Important Topics

Trailhead
Create a Connected App
Digging Deeper into OAuth 2.0 in Salesforce
Enabling Single Sign-On with the Force.com Platform
Identity Provider Values
Salesforce Communities Licenses
Configure a Salesforce Authentication Provider
Best Practices and Tips for Implementing Single Sign-On
Single Sign-On with SAML on Force.com
My Domain
Scope Parameter Values
Single Sign-On
Inside OpenID Connect on Force.com
Configure SSO Across Multiple Salesforce Orgs
Secure Coding Single Sign On
Modify Session Security Settings
Configure SSO to Salesforce Using Microsoft Active Directory Federation Services as the Identity Provider
Setting Up the App Launcher (Salesforce Classic)
Social Single Sign-On with OpenID Connect
Configuring SSO for Mobile and Desktop Apps Using SAML and OAuth
Social Single Sign-On with OpenID Connect
OAuth Authentication
SAML Single Sign-On for Canvas Apps
Configuring SAML SSO for a Canvas App
Two-Factor Authentication
Seamless Authentication with Force.com Canvas
Customizing User Authentication with Login Flows
Deploying Single Sign-On and Identity for Employees, Customers, and Partners
How to Provision Salesforce Communities Users
About Just-in-Time Provisioning for SAML
Integrating Active Directory with Salesforce using Identity Connect
Salesforce memo Blog
Quizlet
alwaysablezard blog

Good Luck for exam 🙂

Permanent link to this article: http://www.sfdcpoint.com/salesforce/salesforce-certified-identity-and-access-management-designer-exam/

Salesforce Certified Development Lifecycle and Deployment Designer Exam

Salesforce Certified Development Lifecycle and Deployment Designer Exam Tips

Salesforce Certified Development Lifecycle and Deployment Designer Exam

My Experience

This was my third architect exam. I will rate this one also easier to crack. Most of people who are working in Salesforce development get chance to practically work in most of topics which are required for this exam. It requires good knowledge about development & deployment lifecycle and all tools which are required for development & deployment. I had used most of tools and features in my project. So it was easy for me. But if you have not worked on it, don’t worry this exam preparation will be good opportunity for you to learn so many good things. Go through all topics mentioned in resource guides. I will list down most important topics at end of this post.One more important point to mention that most of questions in this exam were scenario based.

Credential Overview

The Salesforce Certified Development Lifecycle and Deployment Designer credential is designed for those who assess their architecture environment and requirements and then implement management solutions on the Force.com platform that meet those requirements. Candidates should have experience communicating solutions and design trade-offs to businesses and IT stakeholders.

Here are some examples of the concepts you should understand to pass the exam:

  • Experience with project and development lifecycle methodologies
  • Experience providing requirements traceability through the project’s lifecycle
  • Awareness of Salesforce and third-party application development lifecycle tools
  • Understanding test plan design and evaluating effectiveness

The Salesforce Certified Development Lifecycle and Deployment Designer candidate has the experience, skills, knowledge, and ability to:

  • Communicate development methodologies and trade-offs.
  • Provide alternatives to development methodologies.
  • Ensure Governance through change management and release management.
  • Ensure Governance in environment management.
  • Develop and execute effective deployment strategies.
  • Use technical tools to execute deployment strategies and environmental approaches.
  • Describe the capabilities and characteristics of metadata API.
  • Describe the capabilities and constraints of the tools available for accessing the Metadata API (Force.com Migration Tool, Force.com IDE, and Change Sets).
  • Describe source control and continuous integration, how they are used, and when they should be recommended.
  • Utilize testing methodologies.
  • Describe strategies to restore and back up.
  • Understand deployment KPIs.
  • Follow Salesforce release schedules and know how they may impact deployments and projects.

A candidate for this exam will likely need assistance with:

  • Environment configuration.
  • Code development.
  • Test execution.
  • Code migration.
  • Configuring continuous integration/development architectures.
  • Setting up a governance process.

Study Materials

Official Exam page
Official Exam Guide contains full exam outline
Free self-directed resource guides which contains all important links

Important Topics

Development Lifecycle Guide
An Introduction to Environments
Application Lifecycle Management Trailhead
Fifteen Things to Consider Before Your Next Data Migration
A Guide to Application Performance Profiling in Force.com
9 Steps to Effective Change Management
Change Management Trailhead
Change Sets
Sandbox Setup Considerations
Change Sets Best Practices
Force.com IDE
Understanding Metadata API
Bestpractices:Continuous Integration Techniques
Agile Development Through Salesforce

Good Luck for exam 🙂

Permanent link to this article: http://www.sfdcpoint.com/salesforce/salesforce-certified-development-lifecycle-and-deployment-designer-exam/