Introduced V2 API to Fetch Opportunity by Lead Unique Fields
What’s the benefit?
This enhancement simplifies API calls, improves performance, and makes it easier to retrieve opportunities using the lead’s contact detail.
What’s new?
We’ve now introduced a dedicated v2 API to fetch opportunities directly using a lead’s unique field such as phone number, email address, etc.,
Object Type Enhancements
What’s the benefit?
Now you have full visibility into where an object type or field is in use (across Automations, Forms, Email Campaigns, Landing Pages, Lists, and more) so you can cleanly remove dependencies before proceeding. It prevents errors and keeps your CRM setup clean and reliable.
What’s new?
View Associations Before Unpublishing an Object Type
When you attempt to unpublish an object type, a popup message will now display the details of its associations. To proceed, you must first unpublish the associated work area before unpublishing the object type itself.
For example, if the Student object type is used in an Email Campaign, you must first delete the associated Email Campaign before you can unpublish the Student object type.
Areas where the Object Type may be associated:
- Automation
- Dynamic Forms
- Email Campaigns
- Landing Pages
View Field Usage Before Dissociating an Object Field
When you attempt to dissociate an object field from an object type configuration, a popup message will now display all the areas where the field is currently in use. To proceed, you must first remove the field from each associated work area before dissociating it from the object type.
For example, if the Date of Birth field is used in a Dynamic Form, you must remove it from the form before you can dissociate it from the object type.
Associated work areas could be:
- Object Details View
- Selected Automation Cards
- System and Dynamic Forms
- Lists (as the field will be available in advanced search)
- Quick Filter (as the field will be available in advanced search)
- Mobile App Object Card
- Email Campaigns
- Landing Pages
Enforce Object Type Compatibility in Sub-Automations
What’s the benefit?
This enhancement ensures consistent data handling and prevents object type mismatches in automation flows.
What’s new?
Sub-automations now inherit and enforce object type compatibility from their parent automations. Only sub-automations with the same object type can be linked, and visibility/usage restrictions for modules and fields now extend to sub-automations based on the configured trigger.
For example, if you create a primary automation for the Customer object type, you can link only a Customer sub‑automation to it—and only the activities and opportunity types associated with Customer will be available in the sub-automation.
Optimize Field Context for Call Lapp and Webhook Cards
What’s the benefit?
Optimized field context improves automation performance and reduces unnecessary field load.
What’s new?
Previously, all fields were brought into context of trigger cards of automation when Call Lapp or Webhook cards were included in automation. Now, if customization is enabled on your account for these cards, only default fields and specific fields configured within the cards will be brought into context.
Faster Login Experience on Marvin/NextGen
What’s the Benefit?
The OTP verification flow has been streamlined for a smoother user experience. This reduces login friction.
What’s new?
Now, when users enter their Email or SMS OTP, the system will automatically detect completion and proceed without requiring a manual submit. This is only applicable to Marvin and NextGen on the web application.
Enhanced Call Log Activity on Opportunities
What’s the benefit?
Streamlines call logging by automatically linking calls to opportunities, improving tracking and reducing manual effort in sales workflows.
What’s new?
This enhancement ensures that the call log activity is posted directly on the opportunity rather than just on the lead. This applies only to opportunity-enabled accounts; to enable this feature contact support@leadsquared.com.
| Scenario | Existing Behavior | New Behavior (if enabled) |
| Lead does not exist | Creates lead and logs activity on lead | Creates lead and opportunity, and logs activity on opportunity type if VN-IVR mapping resolves |
| Lead exists, but Opportunity Type doesn’t | Logs activity on lead | Creates opportunity and logs activity on it if VN-IVR mapping resolves to a particular type |
| Lead exists with one matching Opportunity Type | Logs activity on lead | Post the activity on the opportunity provided the VN-IVR mapping resolves to a particular type which has only one open opportunity. Otherwise, it will be posted on the lead. |
Edit Restrictions on User-Agent Mapping
What’s the benefit?
Prevents accidental misconfigurations by allowing only one admin to edit User-Agent settings at a time, ensuring consistent and reliable setup.
What’s new?
Users can no longer make simultaneous edits to the User-Agent Mapping configuration in UTC. This update prevents multiple users from overwriting each other’s changes at the same time.
Manage Team-Based Agent Panel Access
What’s the benefit?
Enables admins to quickly set up team-based agent panel access without backend support, streamlining configuration and control in telephony workflows.
What’s new?
The RestrictAgentPanelByTeams setting, previously available only via backend APIs, is now available in the Telephony General Settings page. Admins can toggle it directly from the Telephony configuration panel.
Security – Core Platform
Implemented strict cache control headers across all LeadSquared V2 REST API endpoints to prevent caching by browsers, proxies, and CDNs, ensuring data privacy and real-time accuracy.
Bug Fixes
Core Platform
- Fixed an issue where system fields like Last Activity and Last Activity Date were not appearing in the Advanced Search for Object Types.
- Fixed an issue where the calendar field configured on the Landing Page was not functioning when the page was exported as HTML using the “Export Form HTML” option.
- Fixed an issue where the GetOpptyCardCustomization V1 API was returning a partial response.
- Fixed an intermittent issue where users at the top of the Reporting Hierarchy were unable to view all leads assigned to users under them.
- Fixed an issue where the Opportunity Assignment Quota was visible to Sales Users, even though it is intended only for Admin Users.
- Fixed an issue with opportunity field sorting where fields with sorting disabled by default were still appearing as sortable in the mobile app.
- Fixed an issue where the “Service Role” was not visible in the role options while editing a Light User Role from the “Manage Permission” section in User Management.
Automation
- Resolved an issue where an invalid validation and incorrect rule naming (“Rule 3” instead of “Rule 2”) occurred when adding a second rule to a second Distribute card within an automation. The validation now correctly triggers on save.
Telephony
- Response bodies are now logged in failure logs for the following APIs:
- V1 LogCall
- V2 ShowPopup
- V2 LogCall
- V2 LogHybridCall
- The [IC V1] Svc/GetOpportunitiesByLeadId API was not returning all opportunities under a lead. This issue has now been resolved.
