[Shweta]

Follow these steps to use the lightning style in the Visualforce page:
1. Go to SetUp -> Enter Visualforce in the quick find box -> select visualforce page -> click edit.
2. Add the lightningStyleSheets="true" to initial <apex:page> component in the visualforce markup.
e.g.: <apex:page standardController="Account" lightningStyleSheets="true" >
3. Save the above changes.

1. <div>
   </div>

[Shweta]

Trigger factory is a pattern that avoids multiple bad practices such as multiple triggers on an object and Repetitive SOQL queries that can exceed governer limit.

[Shweta]

TLS stands for “Transport Layer Security.” It is a protocol that provides privacy and data integrity between two communicating applications. It’s the most widely deployed security protocol used today, and is used for web browsers and other applications that require data to be securely exchanged over a network. TLS ensures that a connection to a remote endpoint is the intended endpoint through encryption and endpoint identity verification.

[Shweta]

After Undelete: It is available in Salesforce but for limited set of objects. The after undelete trigger events only run on top object. e.g. if you delete an Account, an Opportunity may also be deleted. When you recover the Account from the Recycle Bin, the Opportunity is also recovered.
After Update: A runtime error is thrown, as trigger.new is already saved. And the updates are saved before the object is deleted, so if the object is undeleted, the updates become visible.

[Shweta]

The first insights you see are What Happened insights, which are descriptive insights that tell you more about what happened according to the data in the dataset.

[Shweta]

<div>In data loader, we can loads up to 5 million records. we can't load more than 5 million records.</div>

[Shweta]

Support can increase the API limit temporarily only when a customer's business is impacted critically.

[Shweta]

An event can be handled by the component that fired the event or by a component in the containment hierarchy that receives the event. The name attribute in <aura:handler> must match the name attribute in the <aura:registerEvent> tag in the component that fires the event.

[Shweta]

Batch apex can have 5 simultaneous jobs running in parallel.

[Shweta]

You can't update the LinkedEntityId field of ContentDocumentLink object because the field is not writeable. But you can delete the previous ContentDocumentLink and insert a new ContentDocumentLink with updated ContentDocumentId & LinkedEntityID.

[Shweta]

Locker Console is used to check your JavaScript code’s compatibility with Lightning Locker, and compare how it runs with Lightning Locker enabled and disabled.

[Shweta]

<div>We can use the Virtual keyword to indicates that this class can be extended and overrides are allowed. If the methods need to be overridden, then the <b style="font-family: inherit; font-size: inherit;">classes should be declared with the virtual keyword.</div>

[Shweta]

Component.get(): It returns the Aura.Component instance(s) by its local ID. If the Aura.Component local ID is unique, it returns the component, and if there are multiple Aura.Component with the same local ID, it returns an array of the components.Component.find(): It is associated with Component attributes and returns the referenced component attribute value.

[Shweta]

Listings are the primary marketing tool for promoting your app or consulting service on the AppExchange. The more information you add to your listing, the more likely it is that users can find it. To create a listing on the AppExchange, you must log in to the publishing console of the site.

[Shweta]

Article Manager that includes the permissions to create, edit, publish and assign articles. We can then create a Knowledge Base Manager profile with permission to archive and delete articles.

[Shweta]

We can query Custom Settings using the following Methods :
List Custom Setting Methods: The following are instance methods for list custom settings.getAll(): Returns a map of the data sets defined for the custom setting.getInstance(dataSetName): Returns the custom setting data set record for the specified data set name. This method returns the exact same object as getValues(dataSetName).getValues(dataSetName): Returns the custom setting data set record for the specified data set name. This method returns the exact same object as getInstance(dataSetName).

[Shweta]

Analytics apps can help you turn that data into smarter actions to accelerate new business. Sales Analytics brings the power of Analytics to Sales Cloud on any device that supports Analytics. With intuitive visualizations based on your Salesforce data, Sales Analytics lets you move from insight to action quickly and helps you turn data into smarter sales.

[Shweta]

Bubbling is also known as the Bubble phase. In this, the Event is first captured and handled by the source component and then propagated by application root.

[Shweta]

A/B testing works by random split once you define the test distribution. Which customer enters which grouping is not in our control. We can choose the test distribution of audience for an A/B Test by:

1. Number of subscribers
2. Percentage of subscribers

[Shweta]

A Wait Activity is a period of time that contacts are held between other activities. There are types of wait activity:

1. Wait by Duration: waits for specified hours, days, etc
2. Wait Until Date: waits until the specified end day and time
3. Wait by Attribute: waits until the day and time stored in a date field is reached

[Shweta]

Journey Builder at SFMC helps in designing customer-centric cross-channel automated marketing campaigns. These are the data source for Journey builder:

1. Data Extension
2. Lists or Audience: like a MobileConnect list.
3. salesforce Data: Contact in Salesforce database.
4. API: by configuring an integration to admit contacts into a journey
5. Events

[Shweta]

<div>Dynamic dashboard: It enables each user to see the data they have access to. With this, you can control data visibility without having to create a separate dashboard, with its own running user and folder, for each level of data access.</div>Dynamic dashboard always shows data integrated with real-time so we can not schedule a dynamic dashboard.

[Shweta]

You can get logged-in user id by using this,
User users = [select id, name from user where id =: UserInfo.getUserId()];

[Shweta]

This is the valid Permission of permission set: Access Sales Cloud Analytics Templates and Apps.

[Shweta]

We can't query this directly, but we can do it by means of Process.... sObjects.
ProcessInstance, processInstanceStep etc.