Overview #
When working with LeadSquared forms, users may encounter a situation where a rule that works perfectly on the Web does not behave the same way on the Mobile App. This article explains the difference in rule execution behavior between Web and Mobile, particularly when combining On Load conditions with dependent fields, and provides clear guidance on how to troubleshoot and resolve the issue.
Problem Statement #
You have created a form rule with:
“On Load” condition enabled
Dependent fields below
The rule works on the Web platform, but it does not execute on Mobile as expected.
Key Insight #
There is a functional difference between how form rules execute on Web and Mobile:
| Web: | Executes On Load rules based on configuration and field dependencies |
| Mobile: | Executes all rules whose conditions are already met at the time of form load, regardless of On Load setting |
Mobile executes all matching rules automatically on form launch. Adding an explicit “On Load” condition can interfere with this behavior.
Resolution Steps #
If a form rule involving dependent fields is not working on Mobile, follow these steps:
Open the Form Rule Configuration in the LeadSquared platform.
Identify rules that have both:
Dependent fields
“Execute On Load” condition enabled
Example rule given below:
Remove the “On Load” condition from these rules.
Save and publish the changes.
Test the form again on Mobile.
By removing the “On Load” condition, Mobile will execute the rule automatically at the time of form load, provided the condition is already satisfied
