[MOHIT]

The software development lifecycle (SDLC) is a framework that development teams use to produce high-quality software in a systematic and cost-effective way. The SDLC methodology is used by both large and small software organizations. These teams follow development models ranging from agile to lean to waterfall and others.
The software development lifecycle gives organizations a methodical, step-by-step approach to developing successful software. From gathering the initial requirements for a new product, through maintaining a mature product on the market, we’ll teach you how to employ SDLC.
Origins of the Software Development LifecycleSDLC actually began as the “systems development lifecycle” in the 1960s. As Geoffrey Elliott explains in his book, Global Business Information Technology, large corporations developed the model to help manage complex business systems that required a lot of data processing and analysis.
Over time, variations of the framework have been adopted for the development of hardware and software technology products and other complex projects.

[MOHIT]

The two main development methodologies are agile and waterfall. They are commonly applied to software development, and thus, project management as well. The main difference between agile and waterfall is that waterfall projects are completed sequentially whereas agile projects are completed iteratively in a cycle.
Both the agile and waterfall methodologies carry their own set of advantages and disadvantages. Overall, both can be beneficial to a software development team. Which one to choose is highly dependent on the project type and circumstances.

[MOHIT]

Salesforce Development Lifecycle is like a software developed on cloud, tested on cloud and deployed on the cloud environment.
Force.com is the Salesforce Development Environment. It is built using Eclipse hence it can be effortlessly integrated by using a plugin. It is strongly equipped with Apex, Visualforce and metadata components making it eligible for developing Force.com Apps. Data is saved on local file system and the developers migrate the files to source control repository makes the changes and it is fed into the system again. For source control most developers use Git or SVN.

The following steps will very clearly demonstrate the entire Salesforce Development Lifecycle:
1. Setting Up Source Control Repository: It is always beneficial in the long run from a development point of view to have a separate Git repository for every project, with a default branch acting as the Master branch. It is will be more suited to the purpose of storing the production metadata in the master branch.
As discussed above there are a number of actors involved during the entire lifecycle of the development. Release Manager helps to create entirely different branches for different features which are supposedly handled by different developers. He/She also helps in creating package.xml manifest while also using the same to populate the Master Branch with Metadata and very rightfully uses Force.com Migration to migrate all the data.
2. Development Phase: There is this concept of sandboxes in Salesforce. Sandboxes are totally isolated from your Salesforce production, so it implies that the operations that you perform in your sandboxes don’t affect your main Salesforce production enterprise, and vice versa. The developers start coding in their own sandboxes.
They use Force.com IDE to make connection with their sandboxes and thereby retrieve the matadata from sandbox to the IDE. They do the necessary coding and after performing initial level of unit testing they commit the code to the Git repository.
For subsequent development this fresh code that has been committed is migrated to their sandboxes and they continue with further development. After completion commit the latest development to the repository.
But there can be a possibility that two or more people are working on the same code, hence they definitely have to check for any possible conflicts before committing their code.
3. Testing: As the normal software development lifecycle flows, so is this here in this case. After the development is over it is time for testing. Similar to the developers the testers or QAs also create their own sandboxes and migrate the code to be tested from the repository to their sandboxes.
Sometimes the QA might be assigned with the task of testing only a particular feature. In such a case they use Partial Copy Sandboxes. They deploy only selected features and allows specialized testing of the app features.
QA members can also share their sandboxes if situation demands for a more thorough testing of vital and crucial features but it largely depends on the organization’s workflow pattern.However any changes suggested at this level would take it back to the prior phase of development.
4. Acceptance Testing: After this level of testing is completed it goes for further user acceptance testing. Apart from the QAs and tester the developers, product manager and other parties concerned will perform the final level of testing.
The release manager at first creates partial sandboxes for testing and the same are used by the product managers to carry out the ad hoc testing. And then he/she prepares the final presentation for the end users or clients. These sandboxes can also be used by the trainers of the company to prepare manuals for the trainees. Again in this phase if any further changes are suggested it goes back to the development phase to inculcate the necessary changes.
5. Product Release: The last phase is all about performance testing. This testing is performed on intermediate sandboxes which unlike partial sandboxes has all the features of the app.The testing team performs rigorous testing and regression testing. After it passes all levels of testing then it is successfully deployed in the production environment.
However it is always expected that some or the other important changes will definitely crop up after the final deployment. These end moment changes are handled in the patch releases. Patch cycle has a lifecycle of it’s own but it is quite faster process than the normal development cycle.

[MOHIT]

Use the <samp>with sharing</samp> or <samp>without sharing</samp> keywords on a class to specify whether sharing rules must be enforced. Use the <samp>inherited sharing</samp> keyword on an Apex class to run the class in the sharing mode of the class that called it.
With Sharing
The <samp>with sharing</samp> keyword allows you to specify that the sharing rules for the current user are considered for the class. You have to explicitly set this keyword for the class because Apex code runs in system context. In system context, Apex code has access to all objects and fields— object permissions, field-level security, sharing rules aren’t applied for the current user. This strategy ensures that code doesn’t fail to run because of hidden fields or objects for a user. The only exceptions to this rule are Apex code that is executed with the <samp>executeAnonymous</samp> call and Connect in Apex. <samp>executeAnonymous</samp> always executes using the full permissions of the current user. For more information on <samp>executeAnonymous</samp>, see Anonymous Blocks.
Use the <samp>with sharing</samp> keywords when declaring a class to enforce the sharing rules that apply to the current user.

[MOHIT]

Salesforce is a cloud computing service as a software (SaaS) company that specializes in customer relationship management (CRM). Salesforce's services allow businesses to use cloud technology to better connect with customers, partners and potential customers.

[MOHIT]

Standard and custom object records in Salesforce map to their sObject types in Apex. Here are some common sObject type names in Apex used for standard objects.

[MOHIT]

please follow the below link-
https://help.nintex.com/en-us/docgen/docservices/docgen-sfdc/Services/setup/InstallApp.htm

[MOHIT]

Use Streaming API to receive near-real-time streams of data that are based on changes in Salesforce records or custom payloads.

[MOHIT]

SOAP will communicate through WSDL file.REST will communicate through HTTP protocol.

[MOHIT]

It will return true if the variable is empty on which it is applied

[MOHIT]

An approval process automates how Salesforce records are approved in your org. In an approval process, you specify:

• The steps necessary for a record to be approved and who approves it at each step. For example, when an employee creates a time-off request, have Salesforce automatically send an approval request to the employee’s manager.
• The actions to take based on what happens during the approval process. For example, if a time-off request is approved, update fields on the employee’s record. But if the request is rejected, send a notification to the employee.

[MOHIT]

Render: – Is used to show/hide the particular block, output panel or input/output fields based on the condition. Example: – You have 2 fields one is visible and second is hidden, you want the second field to be visible when the first field is filled then use render.

[MOHIT]

Start
the wizard.

1. From
   Setup, enter Data Import Wizard in the Quick Find box, then select Data
   Import Wizard.
2. Review
   the information provided on the welcome page, then click Launch
   Wizard!

Choose
the data that you want to import.

1. To
   import accounts, contacts, leads, solutions, person accounts, or campaign
   members, click Standard Objects. To import custom objects,
   click Custom Objects.
2. Specify
   whether you want to add new records to Salesforce, update existing
   records, or add and update records simultaneously.
3. Specify
   matching and other criteria as necessary. Hover over the question marks
   for more information about each option.
4. Specify
   the file that contains your data. You can specify your data file by
   dragging the CSV to the upload area of the page or by clicking the CSV
   category you’re using and then navigating to and selecting the file.
5. Choose
   a character encoding method for your file. Most users can accept the
   default character encoding.
6. Click Next.

Map
your data fields to Salesforce data fields. The Data Import Wizard tries
to map as many of your data fields as possible to standard Salesforce data
fields. If Salesforce can’t automatically map fields, however, you do it
manually. Unmapped fields are not imported into Salesforce. To see a list
of standard Salesforce data fields, from Setup, at the top of the page,
click Object Manager. Click the object whose fields you’re
interested in, and click Fields & Relationships. For
example, if you want to see a list of standard Salesforce fields for
leads, click Object Manager | Lead | Fields
& Relationships.

1. Scan
   the list of mapped data fields and locate any unmapped fields.
2. Click Map to
   the left of each unmapped field.
3. In
   the Map Your Field dialog box, choose the Salesforce fields you want to
   map to and click Map. The Map Your Field dialog box also
   gives you the option of saving data from unmapped fields in a general
   notes field for accounts and contacts. To do so, choose Account Note or
   Contact Note from the Map To drop-down list and click Map.
4. To
   change mappings that Salesforce performed automatically, click Change to
   the left of the appropriate field, then choose the Salesforce fields you
   want to map to and click Map.
5. Click Next.

Review
and start your import.

1. Review
   your import information on the Review page. If you still have unmapped
   fields that you want to import, click Previous to return
   to the previous page and specify your mappings.
2. Click Start
   Import.

Check
import status. From Setup, enter “Bulk Data Load Jobs” in the Quick
Find box, then select Bulk Data Load Jobs. The user who
starts the data import receives a status email when the import is
completed.

[MOHIT]

connectedCallback()
This callback method called when the element is inserted into a document.
This method lifecycle flows from Parent to Child Component.
we can’t access child elements in the component body because they don’t exist yet.

You can access the host element with this.template.

• This reply was modified 4 years, 3 months ago by  MOHIT.

[MOHIT]

Apex allows you to use the private, protected, public, and global access modifiers when defining methods and variables.

While triggers and anonymous blocks can also use these access modifiers, they are not as useful in smaller portions of Apex. For example, declaring a method as global in an anonymous block does not enable you to call it from outside of that code.

• This reply was modified 4 years, 3 months ago by  MOHIT.

[MOHIT]

Custom Notification is customized notification where admin can add recipients, subject and content. Admin can be sent a custom notification when any important event occurs.

[MOHIT]

Future method jobs

[MOHIT]

Validation rules -- throwing error message while someone is trying to edit,Permission Sets -- To assign these permission sets to users,triggers -- in apex you can lock() and unlock() records (Approval.lock(accts, false);) functions,Approval Process -- to lock records.

[MOHIT]

Profiles: A collection of settings and permissions that define how a user accesses records. Profiles Control a user’s permissions to perform different functions in Salesforce.

• A Profile can have many users, but a user can have only one profiles.

Roles : Controls the level of visibility that users have yo an organization’s data.

[MOHIT]

No, because while creating the user, selection of profiles is mandatory thing.

[MOHIT]

There are three ways to make a filed required. They are:

1. While creating a filed.
2. Using Page Layout and using Validation Rules.
3. FLS(doubt).

[MOHIT]

There are two ways to create a visualforce page. They are

1. By using the URL.
2. By using the path setup=> Develop=> Pages.

[MOHIT]

Assignment Rules are used to automate organization’s lead generation and support processes.

• Lead Assignment Rules specify how leads are assigned to users or queues as they are created manually, captured from the web, or imported via the lead import wizard.
• Case Assignment Rules determine how cases are assigned to users or put into queues as they are created manually, using Web-to-Case.

[MOHIT]

1. Master- Detail.
2. Lookup.
3. Many to Many.
4. Hierarchical.

[MOHIT]

As per now, Salesforce does not allow to delete any user, how ever we can deactivate the user.