[Satyakam]

Namespace prefixes are used in managed Force.com AppExchange packages to differentiate custom object and field names from those in use by other organizations. After a developer registers a globally unique namespace prefix and registers it with AppExchange registry, external references to custom object and field names in the developer's managed packages take on the following long format:

namespace_prefix__obj_or_field_name__c

Setup -> Build -> Create -> Packages -> Developer Setting -> Edit

Before giving namespace prefix create your packages.

Thanks

[Satyakam]

Hi Vikas,

Field History Tracking
You can select certain fields to track and display the field history in the History related list of an object. The field history data is retained for up to 18 months.

• You can track the field history of custom objects and the following standard objects.
  Accounts
  Articles
  Assets
  Cases
  Contacts
  Contracts
  Contract line items
  Entitlements
  Leads
  Opportunities
  Orders
  Order Products
  Products
  Service Contracts
  Solutions
• You can enable field history tracking for custom objects in the object’s management settings.
• You can turn off field history tracking from the object’s management settings.

Feed Tracking

Using Feed Tracking, users can see updates for records they follow in their Chatter feed.We can track only up to 20 fields per object.

• The following standard field types can't be tracked:
  Auto-number, formula, and roll-up summary fields
  Encrypted and read-only system fields
  The Expected Revenue field on opportunities
  The Solution Title and Solution Details fields on solutions

 

•    It won't show modified values and old values for Multi-Picklist and Long Textarea fields.                             History tracking shows the following:

  Prior value - old value.
  Current value - value.
  Who has done the changes - person who modified it.
  When it was changed - date and time of modification.

 

• Go to Setup --> Build --> Customize --> Chatter --> Feed Tracking.

Thanks

[Satyakam]

Hi Kumar,

Span-

While a span allows you to separate things from the other elements around them on a page or within a document, it does not cause a line break. This is why it is perfect for in-line styling, like coloring a single word in a sentence to draw more attention to it.

Div-

But a div, by default, creates a line break because it is used to make separate containers or boxes within a page or document, hence the name division. So the proper way to use a div is as a containing element, rather than an inline styling element.

Thanks

[Satyakam]

Hi Sushant,

You can delete your component and create one new component,because to rename a component is not allowed yet in lightning.

https://success.salesforce.com/ideaView?id=0873A000000cLiqQAE

Thanks,

[Satyakam]

Hi Vikas,

Go through the following link,this will help you.

https://www.forcetalks.com/salesforce-topic/how-to-use-salesforce-lightning-component-in-visualforce/

 

Thanks,

[Satyakam]

Hi Sushant,

This event is automatically fired when an app or component is initialized, prior to rendering.

Component-

<aura:component>

<aura:handler name="init" value="{!this}" action="{!c.doInit}"/>

</aura:component>

jsController-

({
doInit: function(cmp) {
// Set the attribute value.
// You could also fire an event here instead.
alert('test');
}
})

Thanks

[Satyakam]

Hi Kumar,

If you have added your static resource named as 'SLDS' than you can use this in your component like:

<ltng:require styles="{!$Resource.SLDS +'/assets/styles/salesforce-lightning-design-system.css'}"/>

Thanks

[Satyakam]

Hi Sushant,

Component-

<aura:component controller="HomeApexController">

<ui:button label="New Account" class="btn btn-block btn-lg btn-info col-sm-5 " press="{!c.NewAccount}" />

<aura:attribute name="AccAttr" type="Account" default="{'sobjectType':'Account',
'Name':'',
'Phone':'',
'BillingAddress':'',
'Fax':'',
'Website':'',
'Description':''
}"/>

<div class="input-group col-sm-5" id="test">
<ui:inputText aura:id="AccName" class="form-control" placeholder="Write your name" label="Account Name" value="{!v.AccAttr.Name}"/>
<ui:inputText aura:id="AccPhone" class="form-control" placeholder="Phone Number" label="Phone" value="{!v.AccAttr.Phone}"/>
<ui:inputText aura:id="AccBaddress" class="form-control" placeholder="Billing Address" label="Address" value="{!v.AccAttr.BillingAddress}"/>
<ui:inputText aura:id="AccFax" class="form-control" placeholder="Fax" label="Fax" value="{!v.AccAttr.Fax}"/>
<ui:inputText aura:id="AccWebsite" class="form-control" placeholder="Website" label="Website" value="{!v.AccAttr.Website}"/>
<ui:inputText aura:id="AccDes" class="form-control" placeholder="Description" label="Description" value="{!v.AccAttr.Description}"/>
<div class="btn-group">
<ui:button label="Save" class="btn btn-block btn-success" press="{!c.SaveAccount}"/>
<ui:button label="Cancel" class="btn btn-block btn-danger" press="{!c.CancelAccount}"/>
</div>
</div>

</aura:component>

jsController-

NewAccount : function(component, event, helper){
document.getElementById('test').style.display = 'block';

},
CancelAccount : function(component, event, helper){
document.getElementById('test').style.display = 'none';
}

Hope this may help you.

Thanks

[Satyakam]

Updating the Salesforce icons was a huge priority for us as we embarked upon this work. Let’s face it, the existing “clip art” was looking a bit haggard and 90’s. Hence we are very excited to offer this set of exciting Technicolor icons covering a wide range of use cases for you to use in your own apps.

The Design System includes a varied supply of new icons divided into five categories:

1. Custom - These icons represent Custom Salesforce objects in our UI. They are the icons we make available to Salesforce Administrators when they are creating their Custom objects
   2. Doctype - Common document and file formats
   3. Standard - These icons cover all the Standard Salesforce objects in our UI
   4. Utility - We use these icons to represent interactions that the user can engage with in the UI - things like closing a modal, going back to a previous page, or opening a dropdown menu
   5. Action - And last, but not least, the good ol’ action category. We utilize these icons for a fairly specific use case within our mobile UI. You’ll notice some duplication here with the Standard and Custom sets - don’t panic, you’re not going crazy. It’s likely you can ignore this category altogether and still have enough icons for any use case you can dream up.

<span class="slds-icon_container slds-icon-standard-account" title="description of icon when needed">
<svg aria-hidden="true" class="slds-icon">
<use xlink:href="{!URLFOR($Resource.REPLACE_WITH_NAME_OF_SLDS_STATIC_RESOURCE,
'assets/icons/standard-sprite/svg/symbols.svg#account')}"></use>
</svg>
<span class="slds-assistive-text">Account Icon</span>
</span>

[Satyakam]

Hi Kumar,

if you want to use lightning component in your visualforce page,you have to follow below steps:

1-Create your component.

2-Create your App.

3-Create Vf page to put your App and Component.

Component-

<aura:component>

// Code Here

</aura:component>

App-

<aura:application access="GLOBAL" extends="ltng:outApp">
</aura:application>

Vf page-

<apex:page standardController="Account" sidebar="false" showHeader="false">
<apex:includeLightning />
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js"></script>
<div id="vf-app">

</div>
<script>
var accountId = "{!$CurrentPage.parameters.id}";
console.log('::::'+accountId);
$Lightning.use("c:YourApp", function() {
$Lightning.createComponent(
"c:YourComponent",
{ "AccountId" : accountId },
"vf-app",
function(cmp) {
console.log("Component created!");
console.log(cmp)
});
});
</script>
</apex:page>

Hope this will help you.

Thanks

[Satyakam]

Yes

[Satyakam]

Hi Kumar,

To validate field in salesforce lightning,go through the following code:

Component:

<aura:component >

<aura:attribute name="AccountAtt" type="Account" default="{'sobjectType':'Account',
'Name':''}"/>
<ui:inputText aura:id="AccName" value="{!v.AccountAtt.Name}"/>
<ui:button label="Submit" press="{!c.SubmitButton}"/>

</aura:component>

jsController:

({
SubmitButton : function(component, event, helper) {
var name=component.find("AccName");
var AccName=name.get("v.value");
if($A.util.isEmpty(AccName)){
name.set("v.errors", [{message:"Input not valid: " + AccName}]);

}
}
})

Hope this will help you,

Thanks

[Satyakam]

Hi Sushant,

In lightning,SLDS stands for 'Salesforce Lightning Design System'.With the Design System you can build custom applications with a look and feel that is consistent with Salesforce core features - without reverse engineering our styles! Simply download our platform-agnostic CSS framework.

To use SLDS in your org,you have to upload .zip file using static resource and you may use classes given in slds.

To start with lightning slds go through following link:

https://www.lightningdesignsystem.com/getting-started/

Thanks

[Satyakam]

Hi Sushant,

placeholder text displays only when the date picker is not available, when displayDatePicker"false". To assist with user input, the placeholder text displays based on the browser locale, such as MM dd, yyyy.

[Satyakam]

Hi Vikas Kumar,

Yes,you can include external javascript libraries in your component and application.To reference a JavaScript library  you’ve to upload as a static resource, use a <ltng:require> tag in your .cmp or .app markup.

<ltng:require scripts="{!$Resource.***YourresourceName***}"
afterScriptsLoaded="{!c.afterScriptsLoaded}" />

Thanks

[Satyakam]

Hi Vikas Kumar,

Please go through following blog,this may helpful for you:

https://www.forcetalks.com/blog/custom-visualforce-lookup/

Thanks

• This reply was modified 7 years, 4 months ago by  Satyakam.

[Satyakam]

Hi sushant,

Features of SoapUI is following:

1.Web services inspection
2.Web services invoking
3.Web services development
4.Web services simulation and mocking
5.Web services functional, load, compliance and security testing

Thanks

• This reply was modified 7 years, 4 months ago by  Satyakam.

[Satyakam]

Hi Kumar,

You may deactivate user using workflow.follow the below steps-

https://success.salesforce.com/servlet/rtaImage?eid=90730000000DunB&feoid=Body&refid=0EM300000004ytj

I hope this will help you very much,if you are getting any problem,than please let me know.

thanks

[Satyakam]

Hi Kumar,

Follow below step,

Right click on project->Right click on Force.com->select Work Online.

i hope you eclipse will work fine.

[Satyakam]

Hi Vikas Kumar,

Try below code in controller to redirect from one vf page to another.

PageReference FirstPage = Page.SecondPageName;
FirstPage.setRedirect(false);
return FirstPage;

Thanks

[Satyakam]

Hi sushant,

Another tool is Git bywhich you can sync your salesforce org metadata.

for more detail you may go through following link:

https://developer.salesforce.com/page/Syncing_Salesforce_Org_Metadata_to_Github

[Satyakam]

Hi Vikas Kumar,

You may understand relation between Opportunity,Product,OpportunityLineItem,PricebookEntry and Pricebook.

Opportunity:
Opportunity object stores data of potential sales and pending sales.
One opportunity can only have one pricebook.
One opportunity can contain one or many line items.
Product:
Product object is a catalogue of items or services for sales.
A product may contain one or more different sets of prices (PriceBookEntry).
OpportunityLineItem:
List of products that link with opportunity containing data on types of products and respective prices.
One opportunity line item can only be linked to one opportunity.
One opportunity line item can only be linked to one price book entry.
PricebookEntry:
PricebookEntry object is a product entry in a pricebook.
This object allows products to be linked to standard price book or custom price book.
One price book entry is linked to only one product.
One price book entry can only appear in one pricebook.
One price book entry can be used in multiple line items. This also further creates flexibility for users to set their own prices.
Pricebook:
Pricebook object store a list of products and services for sale.
A pricebook can be used in one or more different opportunities.
A pricebook has one or more different price entries.

• This reply was modified 7 years, 4 months ago by  Satyakam.

[Satyakam]

Hi Kumar,

Following is the difference between public group and queues.

Public Group:

If you want to share some information in your organization among some users, so we make public Group.Public Group is the group of some selected users,then we can share information or we assign some work to group.

Queues:

In our daily life we can take example of Call Centre to understand Queues.There are many Customer Care Executive in a call centre and many customers call at a time and one executive can talk to one customer at one time,so other customer's calls are kept in queues.Same thing is there in salesforce like:

Each user should assigned to at least one lead and same number of leads.
That means user need to handle assigned lead individually and all users in organization should assigned with same number of leads, in this case we can define users in organization as Queue and assign them one by one and in same number using round robin lead assignment.

i hope this will help you to understand differences.

Thanks

[Satyakam]

Hi Sushant,

We use scheduler class to schedule batch class.

Example of a batch class:
global class BatchClass implements Database.Batchable<sObject>
{
global ExampleBatchClass(){
// Batch Constructor
}

// Start Method
global Database.QueryLocator start(Database.BatchableContext BC){
return Database.getQueryLocator(query);
}

// Execute Logic
global void execute(Database.BatchableContext BC, List<sObject> scope){
// Logic to be Executed batch wise
}

global void finish(Database.BatchableContext BC){
}

}

Example of a Scheduled Apex:

global class scheduledBatchable implements Schedulable{
global void execute(SchedulableContext sc) {
// Implement any logic to be scheduled

// We now call the batch class to be scheduled
ExampleBatchClass b = new ExampleBatchClass();

//Parameters of ExecuteBatch(context,BatchSize)
database.executebatch(b,10);
}
}

Schedule the class by executing anonymous

Finally now we can schedule the batch class, there are two ways by which we can schedule the batch class
1.From Setup—> Apex Classes –> Schedule Apex : but, here the minimum is one day/ 24 hours
By executing anonymous code from either developer console or apex, here the minimum is 1 hour

Code to be executed

// Cron EXP for hourly schedule
String CRON_EXP = '0 0 * * * ?';
SheduledBatchable sch = new scheduledBatchable();
system.schedule('Hourly Example Batch Schedule job', CRON_EXP, sch);

this may help you.

Thanks

[Satyakam]

Hi Sushant,

you can use more than one controller on vf page using 'extensions' like:

<apex:page standardController="Account" extensions="yourCustomController1,yourCustomController2">

 

Apex Controller 1:

public class yourCustomController1 {

}

Apex Controller 2:

public class yourCustomController2 {
}

For more details you may go through following Visualforce Developer Guide:

https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_controller_extension.htm