Sugar Market 25.12.0 has been released!

Feature Enhancements

• Search across all lists in Email Builder: You can now search across all lists at once within Email Builder when selecting recipients, making it easier to find the people you wish to send to.
  
• Email template type consolidation: The three email template types have been merged into a single view, with a Type field added to accurately reflect each template type.
  
• All unsubscribes shown in the Buyer’s Journey: When viewing a contact or lead, the Buyer’s Journey now shows all unsubscribes, regardless of how the customer unsubscribed.
• Additional support added for Email Builder 2.0 Advanced Testing: Email Builder 2.0 Advanced Testing now supports the following clients: Android 13 Gmail App, Apple Mail 16, iPhone 16 Gmail App, iPhone 16, iPad (10th generation), Gmail App for iOS, Outlook 365, Outlook for Mac, and Outlook for Windows.
• Legacy modules use new email templates: Forms, listeners, and scoring actions now use Email Builder 2.0 email templates to support the ongoing modernization of Sugar Market.

Fixed Issues

• 98126: Email Builder 2.0 Advanced Testing support has been discontinued for the following clients: Android 6, Apple Mail 15, Gmail App for iOS, iPad (Retina), iPhone 11, iPhone 12, iPhone SE, Outlook for iOS, and Windows 10 Mail.
• 98125: The Market iframe in SugarCRM did not properly respect the ordering of nurtures a contact has participated in by nurture name, status, and created date. This has been corrected by removing the legacy nurture endpoints, and results now return as expected.
• 98121: Access to the legacy Nurture Builder has been removed to support the deprecation of older technology stacks and encourage usage of the modern Nurture Builder.
• 98115: The terminology in Email Builder 2.0 was inconsistent with the rest of the product. Minor edits have been made to labels to ensure clarity and consistency across the application.
• 98112: When a user added a list to either the Include or Exclude section, the same list still appeared in the Lists search results. This has been fixed so that once a list is added, it no longer appears in the search results.
• 98091: The captcha was not compliant with the General Data Protection Regulation (GDPR) in the European Union. This was changed, and now the captcha is compliant.
• 98090: When setting up the connector between Sugar and Sugar Market, the terminology between the two configuration pages was inconsistent. The field "Organization Name" has been removed to reduce confusion.
• 98087: Accounts created from anonymized web traffic data were only viewable to administrators because they were incorrectly marked as OwnerID = 0, which is invalid. This has been corrected so that accounts are viewable by users based on their roles, and records are assigned to OwnerID = 1 when no other user is set.
• 97968: When slider fields were marked as required, adding a slider to a form prevented response submissions. The Required option is not necessary and has been removed, and forms now submit as expected.
• 97383: Using a dynamic reply-to address showed the correct name but not the correct email address, resulting in replies going to the wrong inbox. This issue has been fixed, and the correct reply-to address is now used.
• 90436: When managing report subscriptions, Sugar Market users occasionally could not see their own subscriptions or see subscriptions from other users. This has been fixed to ensure the specific user’s ID is referenced when accessing subscriptions, and it now behaves as expected.

Happy Thursday!