[Achintya]

ANT is used as a building tool.

* Through this we can deploy all the changes we are making in one environment to another environment.
* We have to create the package.xml
* Had to make use of the command prompt for the retrieving and deploying from one to another environment.
* Advantage here is, once you create a package.xml, we can deploy it to any destination environment.
* We can make the backup of the complete package from both destination and source environment.

Apex integration development Services.

* It can be used for the downloading of the code and in creating/modifying the code components and then saving them to the server.
* It is used for comparing the components.
* It maintains the Local History, which is used for comparing or replacing it with an older copy.
* We can deploy to any other Salesforce org. But here we have to manually select the components. Also, it will be a little tough to deploy all config related changes using Eclipse.
* Option 'Deploy to Server' is available.

 

• This reply was modified 5 years, 3 months ago by  Achintya.

[Achintya]

You can find base Lightning components in the lightning namespace to complement the existing UI namespace components. In instances where there are matching UI and lightning namespace components, it is recommended to use the lightning namespace component. The lightning namespace components are optimized for common use cases. Beyond being equipped with the Lightning Design System styling, they handle accessibility, real-time interaction, and enhanced error messages.

[Achintya]

Apex classes and triggers run in system mode. Classes and triggers have no restrictions on dynamically looking up any sObject that is available in the org. You can generate a map of all the sObjects for your org regardless of the current user’s permission unless you are executing anonymous Apex.

User permissions matter when you execute describe calls in an anonymous block. As a result, not all sObjects and fields can be looked up if access is restricted for the running user. For example, if you describe account fields in an anonymous block and you don’t have access to all fields, not all fields are returned. However, all fields are returned for the same call in an Apex class.

[Achintya]

New features in Salesforce Spring ’19 are:

1. Sell more with Sales Cadences.

2. Build Quicker, Simpler, and More Intuitive Flows with Flow Builder.

3. Create Personalized Appointments with Lightning Scheduler.

4. Get the Most Important List View with Pinned Lists.

5. Organize Email Templates with Folders.

[Achintya]

To schedule, an Apex class from the user interface follow

1. Navigate to Setup, search for Apex in the Quick Find box, then select Apex Classes.
2. Click Schedule Apex.
3. Enter the job name, Example – Daily Account Update.
4. Click the lookup button to search Apex class and select the class.
5. Select Weekly or Monthly for the frequency and set options as needed.
6. Select the start and end dates, and also the preferred start time.
7. Click Save.

[Achintya]

Manual sharing allows users to grant one-off access to their individual records for users, roles, and public groups.

Manual sharing is available:
To the record owners, their managers in the role hierarchy, and administrators.
For objects set as public read-only or private in organization-wide defaults.
1. Click the "Sharing" button.

2. Click the "Add" button.

3. Select the users and access.

The users who can manually share records are

1. Record Owner.
2. Administrator.
3. The user above the role of the Record Owner's role.

[Achintya]

The Audit Trail helps you track the recent Setup changes that you and other administrators have made to your organization. This is especially useful in organizations with multiple administrators.

The setup Audit Trail history shows you the 20 most recent Setup changes made to your organization. It lists:

The date and time (with timezone) of the change.
Who made it (by username).
What the change was.

[Achintya]

Collections in Apex can be lists, sets, or maps.
There is no limit on the number of items a collection can hold. However, there is a general limit on heap size.
Lists
A list is an ordered collection of elements that are distinguished by their indices. List elements can be of any data type—primitive types, collections, sObjects, user-defined types, and built-in Apex types.
Sets
A set is an unordered collection of elements that do not contain any duplicates. Set elements can be of any data type—primitive types, collections, sObjects, user-defined types, and built-in Apex types.
Maps
A map is a collection of key-value pairs where each unique key maps to a single value. Keys and values can be any data type—primitive types, collections, sObjects, user-defined types, and built-in Apex types.
Parameterized Typing.

[Achintya]

I cross-posted this and  @Tamar Erlich(Atlassian) and @Jo Hetland had good ideas:
use a temporary object: https://success.salesforce.com/_ui/core/chatter/groups/GroupProfilePage?g=0F9300000001rzc&fId=0D53A00003W3Xk0
and use this Flow screen component: https://unofficialsf.com/datatablefsc-documentation/

[Achintya]

Static resources allow you to upload content that you can reference in a visual force page. Resources can be archives (such as .zip and .jar files), images, stylesheets, JavaScript, and other files.

You can use static resources in the ways but first of all, you have to upload these resources as a static resource in Salesforce view source print
<apex:image url="{!$Resource.TestImage}" width="50" height="50"/>
<apex:includeScript value="{!$Resource.MyJavascriptFile}"/>
<apex:image url="{!URLFOR($Resource.TestZip,'images/Bluehills.jpg')}" width="50"height="50"/>
<apex:includeScript value="{!URLFOR($Resource.LibraryJS, '/base/subdir/file.js')}"/>
<apex:stylesheet value="{!URLFOR($Resource.style_resources, 'styles.css')}"/>

[Achintya]

Testing is a key and critical component to successful long term software development process. Salesforce.com strongly recommends using a test-driven development process which occurs at the same time as code development. Salesforce has a very strong set of documentation. When I was learning salesforce unit testing, I realize that it is difficult to understand where to start reading. Therefore, I summarized the unit testing for salesforce beginners to understand the basic aspects of unit testing.

There are few things to consider before you deploy or upload the code or package;75% of your Apex code must be covered by unit tests
All the tests must complete successfully
Every trigger has some test coverage (1%)
All classes and triggers must compile successfully
When you are writing a test class, you have to write a test for Single Action, Bulk Action, Positive Behavior, Negative Behavior, and Restricted User.
Single Action: Test to verify that a single record produces the correct, expected result.
Bulk Action: Test not only the single record case but the bulk cases as well
Positive Behavior: Verify that the expected behavior occurs through every expected permutation
Negative Behavior: Verify that the error messages are correctly produced
Restricted User: Test whether a user with restricted access to the sobjects used in your code sees the expected behavior
Test Class can be defined as @isTest annotation. Before the Winter 12’ release we had only private test classes, but on Winter 12’ release salesforce has given the chance to write public test classes as well. Salesforce has released public test classes for exposing common methods for data creation. It can be used to set up data that the tests need to run against. Public test methods can be called from a running test but not from a non-test request.

[Achintya]

To customize a flow’s look and feel or enhance its functionality, embed it in a Visualforce page. If your org has flows enabled for sites and portals, use the Visualforce page to deliver the flow to your Salesforce site, portal, or community.

To add a flow to a Visualforce page, embed it using the <flow: interview> component.

1. Find the flow's API name. a) From Setup, enter Flows in the Quick Find box, then select Flows.
b) Click the name of the flow that you want to embed.
2. Define a new Visualforce page or open one that you want to edit.
3. Add the <flow:interview> component, somewhere between the <apex:page> tags.
4. Set the name attribute to the unique name of the flow.

For example <apex:page>
<flow:interview name="flowAPIName"/>
</apex:page>

5. Restrict which users can run the flow by setting the page security for the Visualforce page that contains it. To run the flow, external users (such as on a community) need access to the Visualforce page. To run the flow, internal users need access to the Visualforce page and either: a)The "Run Flows" permission.
b)The Flow User field enabled on their user detail page.

[Achintya]

Three types of bindings used in Salesforce are:-

1. Data bindings, which refer to the data set in the controller
2. Action bindings, which refer to action methods in the controller
3. Component bindings, which refer to other Visualforce components.

[Achintya]

An application that automates a business process by collecting data and doing something in your Salesforce org or an external system. Flow is a powerful business automation tool that can manipulate data in Salesforce in a variety of ways. Such an application can be created right from the org’s set up with just drag-drop/point-click. The ease of creating flows makes it the number one go-to tool when it comes to complex business requirements. It is not only easy to create but also it does not require any coding. Beware! That does not mean you don’t need to know the Salesforce platform’s object relationships and overall how Salesforce runs. You have got to have (at least) mid-level understanding of SFDC and its features in order properly use flows.

It is mainly used when you have to display or collect information through screens making it more visible to the users. Workflow on the other hand execute pre-defined rules behind the scenes. They are used to process information rather than collecting it.

[Achintya]

You can include up to 10 fields per related list.

[Achintya]

We need to first make a lightning tab which points to the lightning component we created and then we have to include that tab in the salesforce1 Mobile Navigation select list and the newly created tab to it.

[Achintya]

Lightning components can be deployed similar to any other component using changeset, ant migration tool, eclipse or any other migration tool.

[Achintya]

These are the following:

a. Component
b. Controller
c. Helper
d. Style
e. Document
f. Design
g. SVG
h. Rendre

[Achintya]

The Apex Scheduler lets you delay execution so that you can run Apex classes at a specified time. This is ideal for daily or weekly maintenance tasks using Batch Apex. To take advantage of the scheduler, write an Apex class that implements the Schedulable interface, and then schedule it for execution on a specific schedule. To invoke Apex classes to run at specific times, first implement the Schedulable interface for the class, then specify the schedule using either the Schedule Apex page in the Salesforce user interface, or the System.schedule method.

[Achintya]

Various Dashboard Components are:

1. Chart: Use a chart when you want to show data graphically.

2. Gauge: Use a gauge when you have a single value that you want to show within a range of custom values.

3. Metric: Use a metric when you have one key value to display.

Enter metric labels directly on components by clicking the empty text field next to the grand total.
Metric components placed directly above and below each other in a dashboard column are displayed together as a single component.
4. Table: Use a table to show a set of report data in column form.

5. Visualforce Page: Use a Visualforce page when you want to create a custom component or show information not available in another component type.

6. Custom S-Control: Custom S-Controls can contain any type of content that you can display or run in a browser, for example, a Java applet, an ActiveX control, an Excel file, or a custom HTML Web form

[Achintya]

An Aura.Action is a reference to an action in the framework. If a child component has an Aura.Action attribute, a parent component can pass in an action handler when it instantiates the child component in its markup.

[Achintya]

If you wanted to implement any business logic like how to render a component and many more things than component controllers are needed for custom components.

[Achintya]

They are able to manage multiple pages and state across each page that is not possible to manage by other simpler controllers in VisualForce. A VisualForce controller defines a complete set of instructions that specify what can happen when the user interacts with different components available on VisualForce pages. These components may be buttons, links, or any other action item. There are three popular types of Visual Force Controllers in Salesforce. These are Standard Controller, Custom Controller, and the Controller Extensions.

[Achintya]

You need to use position fixed and set the other attributes like top, right or left, like below:

<div class="slds-theme_default" style="position:fixed;top:7rem;right:2rem;">
some help text
</div>
You can put this in component and check.

Using a fixed position will make the element position itself with respect to window port so even while scrolling it will be in the same position.

[Achintya]

You cannot re-use the activities composer component in this way.

You can create a new page in the lightning app builder (app page, record page or home page) and place your component as well as the activities composer component on it if that suits your application.

If you want to create a new task at the same time as a new custom object via your custom 'new' button (in what I assume is a modal) you will need to place the fields to capture your task info on your page and save it via your controller.