Salesforce lead Queues

In Salesforce, Queues think about the board and relationship of records in Leads, Cases, and custom things. Lead Queues are particularly helpful in light of the fact that they license you to channel a social occasion Leads into a line reliant on a particular principles whereby customers in that line can ensure obligation regarding Leads. For example, you can make a Lead Queue to fitting as of late made Leads or those got from web by region/a territory (West Coast, North Pacific…etc) Today, I’ll be giving an associate on how with make a Leads Queue.

CREATION OF  TERRITORIES OR REGIONS:

First, we’re going to create a queue for each region.

To get started, go to Setup> Administration Setup> Manage Users> Queues and click New.

Name the Queue and on the other hand, you can assign an email address unequivocal for the line; customers in that line will get invigorates on exercises.

Next, pick the thing you have to make the line in.

Next, assign users to the queue. Alternatively, you can assign a Group of users to a queue. Then click Save.

ASSIGNING RULES FOR LEAD QUEUES

Now that you’ve built the queue, it’s time to create rules to automatically assign users to the appropriate region/territory queue. Go to Setup> Customize> Leads> Assigning Rules and click “New”. In Assignment Rules, you can prioritize the order of rules.Assigning Rules will run on an ascending order.

First, set the order of the rule.

Enter the criteria on which you want the Assignment Rule to apply
If you have multiple rules and depending on the logic, you can modify the logic of the rules right under the list.

Finally, enter the name of the queue you want the records with the above criteria to go to. click Save.

And now, users assigned to the queue can have a list view of all records in that queue where they can assign ownership accordingly. Only those users and users of higher hierarchy will have access to that list view.

Chandra V [11/26/2018]

Force Refresh on Lightning Component

To Force Refresh on a Lightning Component this code can be used:

refresh : function(component, event, helper) {
var action = cmp.get(‘c.myController’;);
action.setCallback(cmp,
function(response) {
var state = response.getState();
if (state === ‘SUCCESS’){
$A.get(‘e.force:refreshView’;).fire();
} else {
//do something
}
}
);
$A.enqueueAction(action);
}

Reloads the view.

To refresh a view, run $A.get(“e.force:refreshView”;).fire();, which reloads all data for the view.

This example refreshes the view after an action is successfully completed

Yeshas [11/10/18]

How to Speed Up Internal Approval Processes in Salesforce

Without a standard procedure for inside endorsements, individuals may convey statements and agreements without approving the substance and what is being offered – from cost to the capacity to convey the proposed arrangement. Also, with no power over what statements and agreements are being conveyed, it is hard to oversee related dangers and vulnerabilities. Without appropriate procedures, making deals records requires a ton of manual work which is inclined to mistakes – and will require rounds of manual checking on for acknowledgment. So how might you accelerate inward endorsement forms? We take a gander at a couple of approaches to assist you with getting that green light quicker inside.

Implement thresholds

Before you can fabricate a normalized procedure for inward endorsements, you ought to consider the limits that really require an endorsement. So decide when things over a specific limit need more marks or approvers and assemble your procedure around these. By making limits for things over an edge you’ll wipe out bottlenecks that can back off citing and contracting. In addition you can give more opportunity to your groups to carry out their responsibility viably.

Speed up the flow of a document in an organisation

At the point when you have to get an endorsement for a statement or agreement, the speed of which you can get the archive through the different phases of endorsements is vital. Dealing with the coordinations of getting the report to the perfect individuals is significant and how you do this has an enormous ramifications on the speed.

Messages, gatherings and calls are on the whole legitimate methods of getting an endorsement yet some agony can be brought about by the following side of these. How would you make a point to keep track on who’s endorsed and what? At the point when you spare messages and meeting notes, it might be hard to locate these later on and sharing these may bring considerably more difficulties.

So what can you do to speed up the flow of a document in an organisation? The answer is a well-thought workflow. It will streamline the time it takes to coordinate the approval process by managing and tracking the different stages of the process. You can use workflows to send reminders, track responses, request changes and create a record of the entire internal approval process for future reference.

Setting up quote and contract approvals

Construct your work processes as indicated by the business rules. A case of an agreement endorsement process is one where any agreement must be affirmed by the top of a division before it moves onto the monetary group and from that point to the lawful group for audit. The archive moves along the procedure, and as and when each gathering favors or updates it, the report is put away halfway in for instance contract database and consequently refreshed with the goal that just a single variant of the agreement is accessible and that it is consistently state-of-the-art. When all gatherings have affirmed the archive, it is come back to the first proprietor of the report and is currently fit to be conveyed.

-Chandra V [11/04/2018]

Field History Tracking on Custom Components

There is a limitation on the Field Tracking on the Quote Standard object in Salesforce.

This functionality is used when a custom application is built and want to track the history of the fields that are created
on the component.

In this scenario, I am tracking the Field History based on these criteria:

Date / Field / Original value / New Value / Type / Modified By

In the below scenario, Tracking the Custom Component Fields Based on two objects – Quote and Quote Line Item.

Lightning Component for Field History Tracking:

<aura:component controller=”QuoteAndQuoteLineItemHistory” implements=”force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId,forceCommunity:availableForAllPageTypes,force:lightningQuickAction” access=”global” >
<!– HANDLERS –>
<aura:handler name=”init” action=”{!c.doInit}” value=”{!this}” />
<!– ATTRIBUTES –>
<aura:attribute name=”componentHistory” type=”List” />
<aura:attribute name=”componentHistoryFinalList” type=”List” />
<aura:attribute name=”searchText” type=”String”/>
<aura:attribute name=”headers” type=”List”/>
<aura:attribute type=”Boolean” name=”sortType” />

<aura:attribute name=”recordId” type=”Id” />
<aura:attribute name=”sortedBy” type=”String” default=”Name”/>
<aura:attribute name=”sortedDirection” type=”String” default=”asc”/>
<div class=”slds”>
<div class=”slds-grid slds-gutters”>
<div class=”slds-col slds-size_9-of-12″></div>
<div class=”slds-col slds-size_3-of-12″>
<lightning:input type=”text” name=”searchInput” onkeyup=”{!c.filterSelection}” value=”{!v.searchText}” aura:id=”searchInput” label=”Type here to search” />
<br/>
</div>
</div>

<lightning:datatable data=”{!v.componentHistory}”
columns=”{!v.headers}”
keyField=”Id”
hideCheckboxColumn=”true”
onsort=”{!c.updateColumnSorting}”
sortedBy=”{!v.sortedBy}”
sortedDirection=”{!v.sortedDirection}”/>
</div>
</aura:component>

This component also has the functionality of Sorting and Search feature.

Please comment and reach out for the Apex Class and related java scripts.

Chandra V [11/3/2018]