[Neha]

Hi Anjali,

Whenever we enable Re-evaluate Workflow Rules after Field Change checkbox in the Field Update of a workflow rule, due to this field update other workflow rules on the same object will be fired if the entry criteria of those workflow rules satisfied.

In case, in other workflow rules also if we enable Re-evaluate Workflow Rules after Field Change checkbox in the Field Update recursive workflow rules will come in some scenarios.

We can take two steps to avoid recursive workflow rules –

For the workflow Evaluation Criteria, if you choose created, and any time it’s edited to subsequently meet criteria option, we can avoid recursive workflow rules.
If you don’t enable Re-evaluate Workflow Rules after Field Change checkbox in the Field Update of a workflow rule we can avoid.

[Neha]

Hi Anjali,

Once logged into the Data Loader, the first thing you need to do is go into Setting and click the box “Insert Null Values.” If you do not, your “Update” function will only change a field from one value to a new value, OR, if the field was blank initially, you can populate a blank (or null) field to have a value. Unless that box is checked, you can’t delete an existing field value (erase it) with the Update command.

[Neha]

Hi Anjali,

A joined report consists of up to five report blocks, which you add to the report to create multiple views of your data. For each block, you can add regular and summary fields, create standard and cross-block custom summary formulas, apply filters, and sort columns.

Hope this may help you..!!

[Neha]

Hi Madhulika,

If we want to show more records than 50,000 then we have the following two options:

1. We can enable readOnly attribute value as true
2. Or we can implement pagination in our pages

Example: Retrieving Data in Apex to Paginate with the StandardSetController
public class opportunityList {
public ApexPages.StandardSetController setCon {
get {
if(setCon == null) {
setCon = new ApexPages.StandardSetController(Database.getQueryLocator(
[SELECT Name, StageName, Amount, Account.Name, Account.Named_Account__c FROM Opportunity where Account.BillingState = ‘California’ and Status__c = ‘Open’]));
}
return setCon;
}
set;
}

// Initialize setCon and return a list of records
public List getOpportunities() {
return (List) setCon.getRecords();
}
}

Note: we can also do pagination using offset caluse in SOQL query.

[Neha]

Hi Shradha,

The following information may help you.

apex:actionPoller
A timer that sends an AJAX request to the server according to a time interval that you specify. Each request can result in a full or partial page update.

An <apex:actionPoller> must be within the region it acts upon. For example, to use an <apex:actionPoller> with an <apex:actionRegion>, the <apex:actionPoller> must be within the <apex:actionRegion>.

Considerations When Using <apex:actionPoller>

• Action methods used by <apex:actionPoller> should be lightweight. It's a best practice to avoid performing DML, external service calls, and other resource-intensive operations in action methods called by an <apex:actionPoller>. Consider carefully the effect of your action method being called repeatedly by an <apex:actionPoller> at the interval you specify, especially if it's used on a page that will be widely distributed, or left open for long periods.
• <apex:actionPoller> refreshes the connection regularly, keeping login sessions alive. A page with <apex:actionPoller>on it won't time out due to inactivity.
• If an <apex:actionPoller> is ever re-rendered as the result of another action, it resets itself.
  Avoid using this component with enhanced lists.

Example:

<!-- Page -->

<apex:page controller="exampleCon">
<apex:form>
<apex:outputText value="Watch this counter: {!count}" id="counter"/>
<apex:actionPoller action="{!incrementCounter}" reRender="counter" interval="15"/>
</apex:form>
</apex:page>

/*** Controller: ***/

public class exampleCon {
Integer count = 0;

public PageReference incrementCounter() {
count++;
return null;
}

public Integer getCount() {
return count;
}
}

[Neha]

Hi Jos,

Here's the code! Maybe it's helpful for others
VF page:

<apex:outputLabel value="Postcode"></apex:outputLabel><br><apex:inputText styleClass="{!classInputPostalCode}" value="{!postalCode}"/><br><apex:outputText value="{!errorMessage}" styleClass="errorMsg" rendered="{!LEN(errorMessage)>0}"/>

 Controller code:

public String classInputPostalCode {get;set;}<br>public String postalCode {get;set;}<br>public String errorMessage {get;set;}<br><br>public void validate() {<br> if (error) {<br> classInputPostalCode = 'error'; // put the errorclass, red borders<br> errorMessage = 'Postal code not found';<br> } else {<br> classInputPostalCode = '';<br> errorMessage = '';<br> }<br>}

 

[Neha]

Hi Ravi,

In this case, you need to give Edit access to order object on customer service profile. From this, you are giving access at metadata level.

Since your OWD setting is set to control by parent and user has read access at record level then you need to provide edit access to users those are associated with customer service profile at the record level. For this, you need to add the users to the group and create sharing rules to give edit access to them on order object.

[Neha]

Thanks for your suggestion Pranav,

We will do that, but I just only ask for guide relevant to the discussion.

[Neha]

Thanks for your suggestion,

But I am asking for the guide for the same discussion that is relevant here to ask.

[Neha]

Thanks for your suggestion. I will do that.

[Neha]

Hi Pranav,

My question is related to the same issue, still, I am confused about "Send Email" checkbox functionality related to Adarsh explanation. My question is totally relevant this discussion.

Thanks for your suggestion

[Neha]

Can anybody provide me the appropriate link o document guide for the output types?

[Neha]

Hi Rahul,

Here we are discussing Congo Composer.

[Neha]

If my comment is helpful to you, Please like it.

[Neha]

Yes, It really helpful for me too.

[Neha]

Hi Archit,

You can also post the separate question for same for faster response.

[Neha]

Can you please provide the support doc for Congo and Nintex to confirm the same thing?

[Neha]

Is there is a way to insert unique Nickname user at every time when the user is inserted into my code without using timestamp function?

[Neha]

Hi Adarsh,

It means we can not overwrite the "Send email"checkbox functionality of Community Welcome mail?

• This reply was modified 6 years, 8 months ago by  Neha.
• This reply was modified 6 years, 8 months ago by  Neha.
• This reply was modified 6 years, 8 months ago by  Neha.

[Neha]

Thanks all for confirming the output types for Webmerge, Congo, and Nintex.

[Neha]

Hi Ankit,

Here are the more details related to Callback URL:

Callback URL (endpoint) that Salesforce calls back to your application during OAuth. It’s the OAuth redirect URI.Depending on which OAuth flow you use, the URL is typically the one that a user’s browser is redirected to after successful authentication. Because this URL is used for some OAuth flows to pass an access token, the URL must use secure HTTPS or a custom URI scheme. If you enter multiple callback URLs, at run time Salesforce matches the callback URL value specified by the app with one of the values in Callback URL. It must match one of the values to pass validation. Separate multiple callback URLs with line breaks.

The callback URL field has a limit of 2000 characters, cumulatively. If you enter several URLs and they exceed this limit, create another connected app to manage more callback URLs.

Hope this helps you..!

[Neha]

Hi Archit,

Thanks for your response.

Can you please provide me limitation guide for Congo and Nintex related to mapping limitations only?

[Neha]

Hi Amresh,

Do you want to calculate the no. of days between the start date and end date of date time type? If yes, then from calendar you can get and start date and end date in variable

If the total duration is less than 24 hours, the following code works in javascript

var now = "04/09/2013 15:00:00";
var then = "04/09/2013 14:20:30";

moment.utc(moment(now,"DD/MM/YYYY HH:mm:ss").diff(moment(then,"DD/MM/YYYY HH:mm:ss"))).format("HH:mm:ss")
This approach will work ONLY when the total duration is less than 24 hours:

var now = "04/09/2013 15:00:00";
var then = "04/09/2013 14:20:30";

moment.utc(moment(now,"DD/MM/YYYY HH:mm:ss").diff(moment(then,"DD/MM/YYYY HH:mm:ss"))).format("HH:mm:ss")

// outputs: "00:39:30"

If the response for durations of 24 hours or greater, then following code works in javascript

var now = "04/09/2013 15:00:00";
var then = "02/09/2013 14:20:30";

var ms = moment(now,"DD/MM/YYYY HH:mm:ss").diff(moment(then,"DD/MM/YYYY HH:mm:ss"));
var d = moment.duration(ms);
var s = Math.floor(d.asHours()) + moment.utc(ms).format(":mm:ss");

// outputs: "48:39:30"

[Neha]

Hi Amresh,

You can post the code and UI screenshot so that it is better to understand the exact issue.

Thanks..!

• This reply was modified 6 years, 8 months ago by  Neha.

[Neha]

Large page sizes directly affect load times. To improve Visualforce page load times:

• Cache any data that is frequently accessed, such as icon graphics.
• Avoid SOQL queries in your Apex controller getter methods.
• Reduce the number of records displayed on a page by:
• Limiting the data coming back from SOQL calls in your Apex controllers. For example, using AND statements in your WHERE clause, or removing null results
• Taking advantage of pagination with a list controller to present fewer records per page
• “Lazy load” Apex objects to reduce request times.
• Consider moving any JavaScript outside of the <apex:includeScript> tag and placing it into a <script> tag right before your closing <apex:page> tag. The <apex:includeScript> tag places JavaScript right before the closing <head> element; thus, Visualforce attempts to load the JavaScript before any other content on the page. However, you should only move JavaScript to the bottom of the page if you’re certain it doesn’t have any adverse effects to your page. For example, JavaScript code snippets requiring document.write or event handlers should remain in the <head> element.

Hope this helps you..!