Blog

  • Home
  • Salesforce
  • SalesForce Integration and Environment in Cloud Computing

SalesForce Integration and Environment in Cloud Computing

  • (4.0)
  • | 2245 Ratings
SalesForce Integration and Environment in Cloud Computing

Sales Force Environment

An environment in Force.com lets you develop and test your cloud computing application immediately without any delay and without touching even a single server. So an environment lets you deploy or create applications with different features depending on its configuration.
Few significant characteristics of an environment:

  • Used for development, testing and production.
  • Contains data and customizations.
  • All environments can be accessed through a web browser.
  • Each environment is based on an edition.

Domain Name:
Custom Domain names lets you run your own website on a platform.

             Choosing Custom Domain

We perform all these through point & click mechanism

  • Sales force provides a special type of test
  • Developer’s responsibility is to test ‘test method’

     ↓→   It Governs the  limits and based on this, execution  works from the starting till the ending
We must write and select the test method
     ↓→  Must practice best only (we have to work on all these test methods).

  • We can have ’n’ number of test methods in a single program
  • Every test method will work in system mode and not in user mode as they work against the govern limits

G .L worst work -> Ajax  -> test the code -> G.L will work love

       ↑
               VF

  • We can convert the test mode from system mode to user mode

To achieve this,

  1. We use test method
  2. System. Run As (user 1)

        The  ↓→    Special method is used to run at user mode

                   {
                         System. Run
                   }

 By default apex & VF will execute in system mode only, if we want to execute apex & VF in user mode then perform the operation again back to the system mode

  • In the sales force, there is a standard class termed as ‘user’

       → System. runs AS    (user) ↑   ↑→    S object
User clerk = [select  an ID from the user where,  first name = ‘OSEARIT’ limit 1]
System. runs As [clerk] {

  • The limit will restrict the records
  • We can share the limit b/w statements
  • The run As method will work inside the test method only
Public test method static void main (){
      System. run As (clerk) {
       }

Annotation

An Apex annotation adapts the manner in which a method is used.
Annotations are used to give additional information to the compilers at the run time. Annotations illustrated with an initial @symbol followed by a certain appropriate keyword. @isTest annotation defines a method that contains the code used for the application.

  • @ is Test → annotation
  • @ is Test → to test the performance of  a single test

Test annotation

Eg:   

Global class annot {
         @is test
         Public static void test me (){
         System. Debug (‘hello, hi’);
         }
         Test method {
         Test. Start test ()   ]
         |   →   Write inside the test method only
         Test. Stop test ()    ]
           }

In this, we can double the governor limits

  • In each test method, we shall only perform this once and not more than it
  • Apex provides batch apex, where we can work up to 15 million records
  • We can run multiple batch Apex’s at a time
  • Schedule apex:- executes at a specific time
  • We can get the features of the OS through interfaces
  • Apex provides interfaces
  • Apex utilizes the OS features

Checkout SalesForce Sample Resumes

Salesforce Integration

Integration between several related apps helps the organization to achieve efficiency, consistency, and quality in real-time.

      ↓→  Different app’s

Distinct App's

Package:-
Collection of resources to serve these applications

                                          Package

Managed: We can add new features even after release
Un-Named: Develops and provides

SandBox:

Salesforce creates copies of your organization in separate environments. It uses them for development and testing. Different types of sales force.com sandbox support different activities. SandBox is completely isolated from the Salesforce production organization.  Its types are:

  • Full Sandbox
  • Partial copy Sandbox
  • Developer Pro Sandbox
  • Developer Sandbox

There are two kinds of sales force.com environments

  • Production environment
  • Sandbox environment

SandBox:
The Sandbox is an environment stored by sales force.com for the testing and the development purpose and is mostly used by developers and testers

Checkout Salesforce Interview Questions

Production:
Production is an environment where the actual users work with the actual data and are maintained by administrators

  • Migration from sandbox to production environment can happen via ellipse tall or SFDC, where changesets eclipse toll is a much more recommended approach
  • There are three kinds of sandboxes in SFDC and the difference lies at the limit of data storage

Developer SandBox:
This is the most basic sandbox provided by SFDC. This comes as free and can be created by a single developer. Multi-users can log in and share this single developer Sandbox.
It can store 10 MB of data and can be refreshed every day (features of winter 11 release), this sandbox can be created from PRD environment

Configuration Only SandBox:
This is a paid sandbox and costs around 10% of the production environment, this is mostly used when the system needs to be tested with a good check of the data
This sandbox can be created directly from the production environment and can be refreshed every day. This sandbox has the data limit up to 500mb.

Checkout SalesForce Tutorial

Full SandBox:
This is also a paid sandbox and costs around 15% to 20% of the PRD environment. The full copy sandbox of SFDC is an exact replica of the production environment and even stores the actual business data.
This sandbox can be created from the SFDC Prd environment and can be refreshed after every 28 days. The full copy sandbox has same data limit as the PRD environment has.

  • From sandbox, the project will move to PRD

            Sandbox  →  PRD

            ↓→    This process is called deployment

Deployment:

Deployment is a connection between two salesforce environments to move, changesets from one environment to the other environment.

  • PASS

                 Force.com  (development environment)
                 IDE
                 Eclipse
→ Eclipse IDE provides an environment, where we write the code, test and deploy the code

  • While sharing, it executes an Apex programming as per the profiles and page layouts
  • Whereas without sharing, it works in system mode

Annotations:-
Annotations are used as additional information to the compilers at the run time

  • @ is test à annotation

                Are used to test the performance of a single test

                Test annotation

Eg:           

Global class all  {
                @ is test
                Public static void test me () {
                System.debug (‘hello, hai Ashok’);
                }

Related Articles:
An Overview of SalesForce Security
An Introduction to Visualforce – SalesForce
Access Specifiers in SalesForce Cloud Computing - Salesforce

Mindmajix offers different Salesforce certification training according to your desire with hands-on experience on Salesforce concepts

Subscribe For Free Demo

Free Demo for Corporate & Online Trainings.

Arogyalokesh
About The Author

Arogyalokesh is a Technical Content Writer and manages content creation on various IT platforms at Mindmajix. He is dedicated to creating useful and engaging content on Salesforce, Blockchain, Docker, SQL Server, Tangle, Jira, and few other technologies. Get in touch with him on LinkedIn and Twitter.


DMCA.com Protection Status

Close
Close