<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://sugarclub.sugarai.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide</link><pubDate>Mon, 07 Apr 2025 18:24:59 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Alex Nassi</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Current Revision posted to Dev Tutorials by Alex Nassi on 4/7/2025 6:24:59 PM&lt;br /&gt;
&lt;div class="content"&gt;
&lt;p&gt;The purpose of this document is to provide insight to Sugar Developers for upgrading custom Sugar code, extensions, and integrations to the Sugar 14.0 (Q2 2024) release. This guide focuses on changes in Sugar&amp;nbsp;&lt;span&gt;14.0 (Q&lt;/span&gt;&lt;span&gt;2&lt;/span&gt; 2024) that could cause an immediate impact on Sugar customizations and integrations built for earlier Sugar versions.&lt;/p&gt;
&lt;p&gt;Please check out the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/m/event-recaps/2740"&gt;Q2 2024 Developer Webinar recording&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for more developer highlights.&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;For Admin and End User release notes, please visit the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://support.sugarcrm.com/SmartLinks/Release_Notes/14.0.0_Release_Notes/"&gt;Sugar 14.0.0 Release Notes&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;h2 id="mcetoc_1ff80k9i32"&gt;User Experience Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1h8k0rdqt0"&gt;Predict Dashlets on Focus Drawers and Preview&lt;/h3&gt;
&lt;p&gt;In this release, we&amp;#39;ve added the capability for users to&amp;nbsp;view the Opportunity Close Prediction Dashlet and the Lead Conversion Prediction Dashlet directly from their Focus Dashboards and Dashlet Previews, eliminating the need to navigate to an Opportunity or Leads Record View. This enhancement streamlines the user experience, making it easier for users to access and manage their Leads and Opportunities data. By providing better lead and opportunity insights right in their Focus Dashboards and Dashlet preview, we&amp;rsquo;re enabling users to make more informed decisions and improve their overall productivity.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Comment Log in Quotes and all Preview Layouts&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;we are adding&amp;nbsp;Comment Log to the Quotes Module Record View and Preview allows for more efficient management of Quotes, as users can now easily access and update comments directly from their Record View and/or Preview Layout. Before 14.0, the Comment Log was only available for preview layouts in the Bugs module, in 14.0 we expanded the funcionalty to all preview layouts for modules where the Comment Log is available. We also added a scrollbar to the Comment Log making it easier for users to navigate through the comments without losing visibility of other relevant record information&lt;/span&gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Define Users Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;&lt;span class="TextRun SCXW208591049 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Admins can easily see at a glance the number of group users and drill into the drawer without having to navigate&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;away from the list view&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;This enhancement leverages the powerful functionality of&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Sugar&amp;#39;s&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;existing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;f&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ocus&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;d&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ashboards, providing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;users&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;with valuable information at their fingertips without having to drill into individual records or navigate away from other relevant information. This not only improves the efficiency of admins by reducing the time spent on navigation&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;,&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;but also enhances the overall user experience by providing quick access to important data.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW208591049 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;&lt;span class="TextRun SCXW159085114 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW159085114 BCX0" data-ccp-parastyle="heading 2"&gt;Role-based Report and Dashboard Templates&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release, w&lt;span class="TextRun SCXW30004081 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW30004081 BCX0"&gt;e introduce the role-based report and dashboard templates that will come with brand-new instance and will allow users to start working with data immediately, instead of spending time on setting up the reports and dashboards.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide role-based comprehensive templates, developed by our customer-facing departments (project webb). Users&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;Sales Reps or Sales Executives &amp;ndash; will have their dashboard and report available immediately. The reports and dashboards are read-only, but they can be duplicated and modified if needed.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide 6 role-based dashboard templates that can be accessed from left-hand home menu:&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;BDR Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Customer Success Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Executive Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Marketing Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Manager Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Rep Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;Also, we provide 166 report templates.&amp;nbsp;The templates are marked with the new filter visible in the list view. Stock reports were replaced by templates, the filters were replaced accordingly.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;New customer after his instance is set, access granted &amp;ndash; can start working. Sales Reps introduce the Opportunities and Leads to track &amp;ndash; next day can just open the dashboard where they have everything they need.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl10"&gt;&lt;code&gt;&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1givqvoho2"&gt;&lt;span&gt;&lt;span class="NormalTextRun SCXW249156672 BCX0"&gt;&lt;/span&gt;&lt;/span&gt;Sugar REST API updates&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;This Sugar release introduces REST&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;v11_24&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Admins to trigger a password reset in non-IDM mode&lt;/h3&gt;
&lt;p&gt;Allows an administrator of the Users module to trigger an email to be sent to a User requesting them to reset their password&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/password/adminRequest&lt;/pre&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Retrieve Related Activities API&lt;/h3&gt;
&lt;p&gt;The endpoint is used to load list of activities related to module/modules.&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/&amp;lt;module&amp;gt;/&amp;lt;record_id&amp;gt;/link/related_activities&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="mcetoc_1gj9pc6si0"&gt;Supported Platforms Update&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;In this release, we are updating Sugar&amp;rsquo;s Supported Platforms.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;We are dropping support for PHP 8.0 and adding support to PHP 8.3.&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;PHP&amp;nbsp;8.0 to PHP 8.1 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration81.php"&gt;https://www.php.net/manual/en/migration81.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration81.incompatible.php"&gt;https://www.php.net/manual/en/migration81.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.1&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.2 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration82.php"&gt;https://www.php.net/manual/en/migration82.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration82.incompatible.php"&gt;https://www.php.net/manual/en/migration82.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.2&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.3 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration83.php"&gt;https://www.php.net/manual/en/migration83.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration83.incompatible.php"&gt;https://www.php.net/manual/en/migration83.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There isn&amp;#39;t an upgrade path from 8.0 to 8.3, you must ensure it follows the upgrade path 7.4 -&amp;gt; 8.0 -&amp;gt; 8.1 -&amp;gt; 8.2 -&amp;gt; 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MySQL&amp;nbsp;5.4&amp;nbsp;and adding support for 8.1 and 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MSSQL&amp;nbsp;2017 and adding support for&amp;nbsp;2019 and 2022&lt;/li&gt;
&lt;li&gt;We are adding&amp;nbsp;support&amp;nbsp;for&amp;nbsp;Oracle&amp;nbsp;21c and 23c&lt;/li&gt;
&lt;li&gt;We are&amp;nbsp;dropping support for Windows Server 2019.&lt;/li&gt;
&lt;li&gt;We are adding support for&amp;nbsp;Amazon OpenSearch v2.7&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mcetoc_1ff80k9i33"&gt;Configurability&amp;nbsp;updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1f77psegv7"&gt;Sugar Config Settings&lt;/h3&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Setting Name&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Default&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Override Example&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.transport&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;https&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['transport'] = &amp;#39;https&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the protocol to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;full_text_engine.Elastic.username&lt;br /&gt;&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['username'] = &amp;#39;username&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;username to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.password&lt;br /&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config['full_text_engine']['Elastic']['password'] = &amp;#39;password&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;password to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;api.allowedClients&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;[]&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;span&gt;$sugar_config['api']['allowedClients'] =&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;#39;base&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;#39;chrome&amp;#39;, // allow only chrome browser&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;],&lt;br /&gt;&amp;nbsp; &amp;#39;mobile&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;#39;my_mobile_app_name&amp;#39;, // allow my_mobile_app_name custom app&lt;br /&gt;&amp;nbsp; &amp;nbsp; // ... add other custom apps ],&lt;br /&gt;&amp;nbsp; &amp;#39;portal&amp;#39; =&amp;gt; [], // allow anything&lt;br /&gt;];&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;Rules applied in the following order:&lt;br /&gt;- If the platform is not in the list - any client is allowed for it&lt;br /&gt;- If the platform is defined in the list, but the clients list is empty - any client is allowed&lt;br /&gt;- If the platform has one or more clients in the list - only they are allowed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcetoc_1f77psegvl"&gt;Platform Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable access to SugarCRM mobile application&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we&amp;#39;ve introduced a new configuration setting. This addition will empower you to define precisely which mobile clients are permitted to access your Sugar data/instance. It&amp;#39;s managed via a&amp;nbsp;sugar_config called&amp;nbsp;&lt;code&gt;$sugar_config['api'][&amp;#39;allowedClients&amp;#39;&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When you generate an SDK application you are asked to give that application a name. This new config, provides you the the ability to specify which app names can connect to a Sugar instance. For an existing application, in the app.json configuration file, you can see the name in the &amp;ldquo;appName&amp;rdquo; parameter. As an example, if you generated an app with an appName set to &amp;ldquo;my_app_name&amp;rdquo;, you would need to make a corresponding configuration change in Sugar.&lt;br /&gt;For example, to ensure that only the&amp;nbsp;your app_name client, created through the mobile SDK, is allowed, you&amp;#39;ll need to incorporate the following line into your Sugar Sell configuration:&amp;nbsp;&lt;code&gt;$sugar_config['api']['allowedClients'] = [&amp;#39;mobile&amp;#39; =&amp;gt; ['my_app_name']];&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Updates to&amp;nbsp;Forecast Commitment&lt;/h3&gt;
&lt;p&gt;Prior to this release, the Commitment value in the Commitment tab be calculated based on the Opportunities in the forecast before an initial manual commitment. When the user changes the value and clicks &amp;ldquo;Commit&amp;rdquo; the Commitment value is no longer calculated and only changes when the user manually changes.&amp;nbsp;This has caused some confusion amongst Forecast module users because they expect the system to continue to update the Commitment value after their manual changes. To avoid confusion, in this release, Sugar will initiate that value at 0 (zero) so users know they haven&amp;rsquo;t committed anything and the value will only change when they manually change it.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Default Value was removed from Calls and Meetings in the Studio UI&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are removing Default&lt;span&gt;&amp;nbsp;Value from Calls and Meetings in the Studio UI.&amp;nbsp;This option has been removed as it creates a false impression that admins can set reminders. Currently, Sugar uses what is in&amp;nbsp;the User Profile Settings.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On Upgrade, instances will no longer see that and it will not be avilable for new installs.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW113039343 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW113039343 BCX0" data-ccp-parastyle="heading 2"&gt;Additional List View Filters&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="TextRun SCXW80679206 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW80679206 BCX0" data-ccp-parastyle="heading 2"&gt;The addition of three new list view filters in version 14.0 significantly enhances the user experience by making it easier for users to filter and find information quickly. With the &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; operator now available for Textarea fields and the &amp;quot;&lt;code&gt;After today&lt;/code&gt;&amp;quot; and &amp;quot;&lt;code&gt;Before today&lt;/code&gt;&amp;quot; options for Date and Datetime fields, users can easily filter records without having to enter exact dates or build complex operators. &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; also works for custom fields now.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW165847498 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW165847498 BCX0" data-ccp-parastyle="heading 2"&gt;Improved CRM/Self-Service Center integration&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW165847498 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;Currently Self-Service Center(SSC) users are mapped as &amp;ldquo;External Users&amp;rdquo; in CRM. When a case or any other object is created by SSC user, it is linked to the &amp;ldquo;External Users&amp;rdquo; in the CRM. A SSC user can be a Prospect or a Lead or a Contact and currently can be linked to a Contact. The current problem is that the CRM users ( e.g. Sales or Service agents) have to look at two separate screens e.g. 1) External Users and 2) Contact records to see all the related activities for a Contact (depending on which system was used to create the interaction/activity).&lt;/p&gt;
&lt;p&gt;&lt;span class="TextRun SCXW110851170 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;In this release, we are bringing this&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;ne&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;w&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;enhancement&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;to&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ensure that all&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the related&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;activities whether initiated from the SSC by an External User or within the CRM by&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;s&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;are&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;shown&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in a single, c&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;onsolidated&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;view for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;Contact in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;CRM.&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;I.e. All related records of External Users are now also shown as related to the Contact when an External User is related to that C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW110851170 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Display SugarIdentity warning when user is trying to edit IDM fields&lt;/h3&gt;
&lt;p&gt;In this release, we are introducing a warning message when user is trying to edit a field that&amp;rsquo;s owned by Sugar IDM in the&amp;nbsp;User&amp;rsquo;s List View, User&amp;rsquo;s Preview, Dashboards and dashlets.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Enable Sales Stage and Expected close date editable for Sales Console&lt;/h3&gt;
&lt;p&gt;In this release,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Sales Stage&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Expected Close Date&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;were added as&amp;nbsp;editable in console multiline list views and they&amp;nbsp;will behave the same as list views.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Add Users List View to Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In our previous release, we moved Users from BWC to Sidecar but we missed this functionality, now in this release we have fixed it, so you can take advantage of adding Users List Views to your Dashboards&lt;/span&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Update Metric font size&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are&amp;nbsp;updating the font size for the metric total as follows:&lt;/p&gt;
&lt;ul class="ak-ul" data-indent-level="1"&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="171"&gt;Update preferred currency from&lt;strong data-renderer-mark="true"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;text-4xl&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&amp;rarr;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl (&lt;/strong&gt;&lt;code class="code css-1o5d2cw" data-renderer-mark="true"&gt;font-size: 1.875rem; /* 30px */ line-height: 2.25rem; /* 36px */&lt;/code&gt;&lt;strong data-renderer-mark="true"&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="292"&gt;Fix When preferred currency &amp;amp; system currency are turned on, use&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;for preferred currency as well. (today when preferred currency is on or off, they appear at different sizes)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Support for Amazon OpenSearch&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are concluding our efforts to support Amazon OpenSearch which could potentially be used by any admin on their instances.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;User Interface&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins have a new option to configure Full-text search options and use OpenSearch as their FTS engine&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;They can set&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;password&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Elastic search is still the engine and there&amp;#39;s no need to update to OpenSearch, it will be handled by Sugar when there&amp;#39;s handshake with the server&lt;/li&gt;
&lt;li&gt;&lt;span&gt;UI is not available for SugarCloud instances&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Configuration&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins can override config.php to add those configs (see Sugar&amp;nbsp;Config Settings)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Admins can use Environment Variables as a security protection for&amp;nbsp;&lt;span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;/span&gt;&amp;nbsp;&lt;span&gt;&lt;code&gt;password&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Note, the environment variables must be set before Apache server restarted.&lt;/li&gt;
&lt;li&gt;These are the env variables&lt;/li&gt;
&lt;li&gt;&amp;#39;es_username&amp;#39; ==&amp;gt; &amp;#39;username&amp;#39;&lt;/li&gt;
&lt;li&gt;&amp;lsquo;es_password&amp;#39; ==&amp;gt; &amp;#39;password&amp;rsquo;&lt;/li&gt;
&lt;li&gt;&amp;#39;es_transport&amp;#39; ==&amp;gt; &amp;#39;transport&amp;#39;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Note:&amp;nbsp;&lt;/strong&gt;It&amp;rsquo;s important to note that using Amazon OpenSearch requires careful evaluation, especially for on-site Sugar instances. This is due to the need of opening connections to Amazon&amp;rsquo;s cloud services, which may pose connectivity challenges or latency issues for some customers. We recommend that you evaluate Amazon OpenSearch on a case-by-case basis, taking into account these considerations.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Cookie Consent -&amp;nbsp;Remove &amp;quot;Accept Cookies&amp;quot; step from new user wizard&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are removing our cookie acceptance policy to ensure that we are only requiring users to accept required cookies and nothing else. At present, our cookie accept screen is a required field &amp;ndash; without accepting cookies, the application will not work. As this is not a meaningful choice for the user, Sugar is removing&amp;nbsp;the option and any required checks for this setting. Those fields are being hidden in Studio. Sugar&amp;nbsp;&lt;/span&gt;Portal is&amp;nbsp;also removing the cookie consent same as Sugar app.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable unlink option for records created by External Users&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are disabling the unlink option for records that are created by External Users but shown in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After creating a record as an external user, the unlink option is not available in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Sugar Core Security Updates&lt;/h3&gt;
&lt;p&gt;As part of our ongoing efforts to keep Sugar clean, fast, reliable, and most importantly secure, we have updated&amp;nbsp;Sugar Core code in different areas of the application such as Package Scanner, Module Installer, UI rendering, Handlebar templates, File Uploads and Imports.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Sugar Core PHP 8.2 compatibility&lt;/h3&gt;
&lt;p&gt;We are constantly monitoring issues in the code for PHP 8.2 compatibility and have hardened multiple core code In this release,&amp;nbsp;Most of those fixes are defensive coding following the steps described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/w/dev-tutorials/896/php-7-4-warnings-to-php8-2-errors"&gt;this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Sugar Q2 2024, Sugar 14&lt;/div&gt;
</description></item><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide/revision/8</link><pubDate>Mon, 21 Oct 2024 13:03:10 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Rafael Fernandes</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Revision 8 posted to Dev Tutorials by Rafael Fernandes on 10/21/2024 1:03:10 PM&lt;br /&gt;
&lt;div class="content"&gt;
&lt;p&gt;The purpose of this document is to provide insight to Sugar Developers for upgrading custom Sugar code, extensions, and integrations to the Sugar 14.0 (Q2 2024) release. This guide focuses on changes in Sugar&amp;nbsp;&lt;span&gt;14.0 (Q&lt;/span&gt;&lt;span&gt;2&lt;/span&gt; 2024) that could cause an immediate impact on Sugar customizations and integrations built for earlier Sugar versions.&lt;/p&gt;
&lt;p&gt;Please check out the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/m/event-recaps/2740"&gt;Q2 2024 Developer Webinar recording&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for more developer highlights.&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;For Admin and End User release notes, please visit the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://support.sugarcrm.com/SmartLinks/Release_Notes/14.0.0_Release_Notes/"&gt;Sugar 14.0.0 Release Notes&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;h2 id="mcetoc_1ff80k9i32"&gt;User Experience Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1h8k0rdqt0"&gt;Predict Dashlets on Focus Drawers and Preview&lt;/h3&gt;
&lt;p&gt;In this release, we&amp;#39;ve added the capability for users to&amp;nbsp;view the Opportunity Close Prediction Dashlet and the Lead Conversion Prediction Dashlet directly from their Focus Dashboards and Dashlet Previews, eliminating the need to navigate to an Opportunity or Leads Record View. This enhancement streamlines the user experience, making it easier for users to access and manage their Leads and Opportunities data. By providing better lead and opportunity insights right in their Focus Dashboards and Dashlet preview, we&amp;rsquo;re enabling users to make more informed decisions and improve their overall productivity.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Comment Log in Quotes and all Preview Layouts&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;we are adding&amp;nbsp;Comment Log to the Quotes Module Record View and Preview allows for more efficient management of Quotes, as users can now easily access and update comments directly from their Record View and/or Preview Layout. Before 14.0, the Comment Log was only available for preview layouts in the Bugs module, in 14.0 we expanded the funcionalty to all preview layouts for modules where the Comment Log is available. We also added a scrollbar to the Comment Log making it easier for users to navigate through the comments without losing visibility of other relevant record information&lt;/span&gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Define Users Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;&lt;span class="TextRun SCXW208591049 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Admins can easily see at a glance the number of group users and drill into the drawer without having to navigate&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;away from the list view&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;This enhancement leverages the powerful functionality of&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Sugar&amp;#39;s&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;existing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;f&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ocus&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;d&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ashboards, providing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;users&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;with valuable information at their fingertips without having to drill into individual records or navigate away from other relevant information. This not only improves the efficiency of admins by reducing the time spent on navigation&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;,&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;but also enhances the overall user experience by providing quick access to important data.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW208591049 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;&lt;span class="TextRun SCXW159085114 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW159085114 BCX0" data-ccp-parastyle="heading 2"&gt;Role-based Report and Dashboard Templates&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release, w&lt;span class="TextRun SCXW30004081 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW30004081 BCX0"&gt;e introduce the role-based report and dashboard templates that will come with brand-new instance and will allow users to start working with data immediately, instead of spending time on setting up the reports and dashboards.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide role-based comprehensive templates, developed by our customer-facing departments (project webb). Users&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;Sales Reps or Sales Executives &amp;ndash; will have their dashboard and report available immediately. The reports and dashboards are read-only, but they can be duplicated and modified if needed.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide 6 role-based dashboard templates that can be accessed from left-hand home menu:&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;BDR Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Customer Success Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Executive Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Marketing Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Manager Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Rep Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;Also, we provide 166 report templates.&amp;nbsp;The templates are marked with the new filter visible in the list view. Stock reports were replaced by templates, the filters were replaced accordingly.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;New customer after his instance is set, access granted &amp;ndash; can start working. Sales Reps introduce the Opportunities and Leads to track &amp;ndash; next day can just open the dashboard where they have everything they need.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl10"&gt;&lt;code&gt;&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1givqvoho2"&gt;&lt;span&gt;&lt;span class="NormalTextRun SCXW249156672 BCX0"&gt;&lt;/span&gt;&lt;/span&gt;Sugar REST API updates&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;This Sugar release introduces REST&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;v11_24&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Admins to trigger a password reset in non-IDM mode&lt;/h3&gt;
&lt;p&gt;Allows an administrator of the Users module to trigger an email to be sent to a User requesting them to reset their password&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/password/adminRequest&lt;/pre&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Retrieve Related Activities API&lt;/h3&gt;
&lt;p&gt;The endpoint is used to load list of activities related to module/modules.&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/&amp;lt;module&amp;gt;/&amp;lt;record_id&amp;gt;/link/related_activities&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="mcetoc_1gj9pc6si0"&gt;Supported Platforms Update&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;In this release, we are updating Sugar&amp;rsquo;s Supported Platforms.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;We are dropping support for PHP 8.0 and adding support to PHP 8.3.&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;PHP&amp;nbsp;8.0 to PHP 8.1 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration81.php"&gt;https://www.php.net/manual/en/migration81.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration81.incompatible.php"&gt;https://www.php.net/manual/en/migration81.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.1&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.2 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration82.php"&gt;https://www.php.net/manual/en/migration82.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration82.incompatible.php"&gt;https://www.php.net/manual/en/migration82.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.2&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.3 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration83.php"&gt;https://www.php.net/manual/en/migration83.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration83.incompatible.php"&gt;https://www.php.net/manual/en/migration83.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There isn&amp;#39;t an upgrade path from 8.0 to 8.3, you must ensure it follows the upgrade path 7.4 -&amp;gt; 8.0 -&amp;gt; 8.1 -&amp;gt; 8.2 -&amp;gt; 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MySQL&amp;nbsp;5.4&amp;nbsp;and adding support for 8.1 and 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MSSQL&amp;nbsp;2017 and adding support for&amp;nbsp;2019 and 2022&lt;/li&gt;
&lt;li&gt;We are adding&amp;nbsp;support&amp;nbsp;for&amp;nbsp;Oracle&amp;nbsp;21c and 23c&lt;/li&gt;
&lt;li&gt;We are&amp;nbsp;dropping support for Windows Server 2019.&lt;/li&gt;
&lt;li&gt;We are adding support for&amp;nbsp;Amazon OpenSearch v2.7&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mcetoc_1ff80k9i33"&gt;Configurability&amp;nbsp;updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1f77psegv7"&gt;Sugar Config Settings&lt;/h3&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Setting Name&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Default&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Override Example&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.transport&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;https&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['transport'] = &amp;#39;https&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the protocol to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;full_text_engine.Elastic.username&lt;br /&gt;&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['username'] = &amp;#39;username&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;username to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.password&lt;br /&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config['full_text_engine']['Elastic']['password'] = &amp;#39;password&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;password to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;api.allowedClients&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;[]&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;span&gt;$sugar_config['api']['allowedClients'] =&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;#39;base&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;#39;chrome&amp;#39;, // allow only chrome browser&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;],&lt;br /&gt;&amp;nbsp; &amp;#39;mobile&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;#39;my_mobile_app_name&amp;#39;, // allow my_mobile_app_name custom app&lt;br /&gt;&amp;nbsp; &amp;nbsp; // ... add other custom apps ],&lt;br /&gt;&amp;nbsp; &amp;#39;portal&amp;#39; =&amp;gt; [], // allow anything&lt;br /&gt;];&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;Rules applied in the following order:&lt;br /&gt;- If the platform is not in the list - any client is allowed for it&lt;br /&gt;- If the platform is defined in the list, but the clients list is empty - any client is allowed&lt;br /&gt;- If the platform has one or more clients in the list - only they are allowed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcetoc_1f77psegvl"&gt;Platform Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable access to SugarCRM mobile application&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we&amp;#39;ve introduced a new configuration setting. This addition will empower you to define precisely which mobile clients are permitted to access your Sugar data/instance. It&amp;#39;s managed via a&amp;nbsp;sugar_config called&amp;nbsp;&lt;code&gt;$sugar_config['api'][&amp;#39;allowedClients&amp;#39;&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When you generate an SDK application you are asked to give that application a name. This new config, provides you the the ability to specify which app names can connect to a Sugar instance. For an existing application, in the app.json configuration file, you can see the name in the &amp;ldquo;appName&amp;rdquo; parameter. As an example, if you generated an app with an appName set to &amp;ldquo;my_app_name&amp;rdquo;, you would need to make a corresponding configuration change in Sugar.&lt;br /&gt;For example, to ensure that only the&amp;nbsp;your app_name client, created through the mobile SDK, is allowed, you&amp;#39;ll need to incorporate the following line into your Sugar Sell configuration:&amp;nbsp;&lt;code&gt;$sugar_config['api']['allowedClients'] = [&amp;#39;mobile&amp;#39; =&amp;gt; ['my_app_name']];&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Updates to&amp;nbsp;Forecast Commitment&lt;/h3&gt;
&lt;p&gt;Prior to this release, the Commitment value in the Commitment tab be calculated based on the Opportunities in the forecast before an initial manual commitment. When the user changes the value and clicks &amp;ldquo;Commit&amp;rdquo; the Commitment value is no longer calculated and only changes when the user manually changes.&amp;nbsp;This has caused some confusion amongst Forecast module users because they expect the system to continue to update the Commitment value after their manual changes. To avoid confusion, in this release, Sugar will initiate that value at 0 (zero) so users know they haven&amp;rsquo;t committed anything and the value will only change when they manually change it.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Default Value was removed from Calls and Meetings in the Studio UI&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are removing Default&lt;span&gt;&amp;nbsp;Value from Calls and Meetings in the Studio UI.&amp;nbsp;This option has been removed as it creates a false impression that admins can set reminders. Currently, Sugar uses what is in&amp;nbsp;the User Profile Settings.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On Upgrade, instances will no longer see that and it will not be avilable for new installs.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW113039343 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW113039343 BCX0" data-ccp-parastyle="heading 2"&gt;Additional List View Filters&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="TextRun SCXW80679206 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW80679206 BCX0" data-ccp-parastyle="heading 2"&gt;The addition of three new list view filters in version 14.0 significantly enhances the user experience by making it easier for users to filter and find information quickly. With the &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; operator now available for Textarea fields and the &amp;quot;&lt;code&gt;After today&lt;/code&gt;&amp;quot; and &amp;quot;&lt;code&gt;Before today&lt;/code&gt;&amp;quot; options for Date and Datetime fields, users can easily filter records without having to enter exact dates or build complex operators. &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; also works for custom fields now.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW165847498 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW165847498 BCX0" data-ccp-parastyle="heading 2"&gt;Improved CRM/Self-Service Center integration&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW165847498 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;Currently Self-Service Center(SSC) users are mapped as &amp;ldquo;External Users&amp;rdquo; in CRM. When a case or any other object is created by SSC user, it is linked to the &amp;ldquo;External Users&amp;rdquo; in the CRM. A SSC user can be a Prospect or a Lead or a Contact and currently can be linked to a Contact. The current problem is that the CRM users ( e.g. Sales or Service agents) have to look at two separate screens e.g. 1) External Users and 2) Contact records to see all the related activities for a Contact (depending on which system was used to create the interaction/activity).&lt;/p&gt;
&lt;p&gt;&lt;span class="TextRun SCXW110851170 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;In this release, we are bringing this&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;ne&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;w&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;enhancement&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;to&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ensure that all&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the related&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;activities whether initiated from the SSC by an External User or within the CRM by&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;s&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;are&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;shown&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in a single, c&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;onsolidated&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;view for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;Contact in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;CRM.&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;I.e. All related records of External Users are now also shown as related to the Contact when an External User is related to that C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW110851170 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Display SugarIdentity warning when user is trying to edit IDM fields&lt;/h3&gt;
&lt;p&gt;In this release, we are introducing a warning message when user is trying to edit a field that&amp;rsquo;s owned by Sugar IDM in the&amp;nbsp;User&amp;rsquo;s List View, User&amp;rsquo;s Preview, Dashboards and dashlets.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Enable Sales Stage and Expected close date editable for Sales Console&lt;/h3&gt;
&lt;p&gt;In this release,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Sales Stage&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Expected Close Date&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;were added as&amp;nbsp;editable in console multiline list views and they&amp;nbsp;will behave the same as list views.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Add Users List View to Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In our previous release, we moved Users from BWC to Sidecar but we missed this functionality, now in this release we have fixed it, so you can take advantage of adding Users List Views to your Dashboards&lt;/span&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Update Metric font size&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are&amp;nbsp;updating the font size for the metric total as follows:&lt;/p&gt;
&lt;ul class="ak-ul" data-indent-level="1"&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="171"&gt;Update preferred currency from&lt;strong data-renderer-mark="true"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;text-4xl&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&amp;rarr;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl (&lt;/strong&gt;&lt;code class="code css-1o5d2cw" data-renderer-mark="true"&gt;font-size: 1.875rem; /* 30px */ line-height: 2.25rem; /* 36px */&lt;/code&gt;&lt;strong data-renderer-mark="true"&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="292"&gt;Fix When preferred currency &amp;amp; system currency are turned on, use&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;for preferred currency as well. (today when preferred currency is on or off, they appear at different sizes)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Support for Amazon OpenSearch&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are concluding our efforts to support Amazon OpenSearch which could potentially be used by any admin on their instances.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;User Interface&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins have a new option to configure Full-text search options and use OpenSearch as their FTS engine&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;They can set&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;password&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Elastic search is still the engine and there&amp;#39;s no need to update to OpenSearch, it will be handled by Sugar when there&amp;#39;s handshake with the server&lt;/li&gt;
&lt;li&gt;&lt;span&gt;UI is not available for SugarCloud instances&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Configuration&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins can override config.php to add those configs (see Sugar&amp;nbsp;Config Settings)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Admins can use Environment Variables as a security protection for&amp;nbsp;&lt;span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;/span&gt;&amp;nbsp;&lt;span&gt;&lt;code&gt;password&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Note, the environment variables must be set before Apache server restarted.&lt;/li&gt;
&lt;li&gt;These are the env variables&lt;/li&gt;
&lt;li&gt;&amp;#39;es_username&amp;#39; ==&amp;gt; &amp;#39;username&amp;#39;&lt;/li&gt;
&lt;li&gt;&amp;lsquo;es_password&amp;#39; ==&amp;gt; &amp;#39;password&amp;rsquo;&lt;/li&gt;
&lt;li&gt;&amp;#39;es_transport&amp;#39; ==&amp;gt; &amp;#39;transport&amp;#39;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Note:&amp;nbsp;&lt;/strong&gt;It&amp;rsquo;s important to note that using Amazon OpenSearch requires careful evaluation, especially for on-premise setups (can we say &amp;quot;on-site Sugar instances&amp;quot;?). This is due to the need of opening connections to Amazon&amp;rsquo;s cloud services, which may pose connectivity challenges or latency issues for some customers. We recommend that you evaluate Amazon OpenSearch on a case-by-case basis, taking into account these considerations.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Cookie Consent -&amp;nbsp;Remove &amp;quot;Accept Cookies&amp;quot; step from new user wizard&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are removing our cookie acceptance policy to ensure that we are only requiring users to accept required cookies and nothing else. At present, our cookie accept screen is a required field &amp;ndash; without accepting cookies, the application will not work. As this is not a meaningful choice for the user, Sugar is removing&amp;nbsp;the option and any required checks for this setting. Those fields are being hidden in Studio. Sugar&amp;nbsp;&lt;/span&gt;Portal is&amp;nbsp;also removing the cookie consent same as Sugar app.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable unlink option for records created by External Users&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are disabling the unlink option for records that are created by External Users but shown in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After creating a record as an external user, the unlink option is not available in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Sugar Core Security Updates&lt;/h3&gt;
&lt;p&gt;As part of our ongoing efforts to keep Sugar clean, fast, reliable, and most importantly secure, we have updated&amp;nbsp;Sugar Core code in different areas of the application such as Package Scanner, Module Installer, UI rendering, Handlebar templates, File Uploads and Imports.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Sugar Core PHP 8.2 compatibility&lt;/h3&gt;
&lt;p&gt;We are constantly monitoring issues in the code for PHP 8.2 compatibility and have hardened multiple core code In this release,&amp;nbsp;Most of those fixes are defensive coding following the steps described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/w/dev-tutorials/896/php-7-4-warnings-to-php8-2-errors"&gt;this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Sugar Q2 2024, Sugar 14&lt;/div&gt;
</description></item><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide/revision/7</link><pubDate>Mon, 15 Apr 2024 13:27:04 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Rafael Fernandes</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Revision 7 posted to Dev Tutorials by Rafael Fernandes on 4/15/2024 1:27:04 PM&lt;br /&gt;
&lt;div class="content"&gt;
&lt;p&gt;The purpose of this document is to provide insight to Sugar Developers for upgrading custom Sugar code, extensions, and integrations to the Sugar 14.0 (Q2 2024) release. This guide focuses on changes in Sugar&amp;nbsp;&lt;span&gt;14.0 (Q&lt;/span&gt;&lt;span&gt;2&lt;/span&gt; 2024) that could cause an immediate impact on Sugar customizations and integrations built for earlier Sugar versions.&lt;/p&gt;
&lt;p&gt;Please check out the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/m/event-recaps/2740"&gt;Q2 2024 Developer Webinar recording&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for more developer highlights.&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;For Admin and End User release notes, please visit the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://support.sugarcrm.com/SmartLinks/Release_Notes/14.0.0_Release_Notes/"&gt;Sugar 14.0.0 Release Notes&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;h2 id="mcetoc_1ff80k9i32"&gt;User Experience Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1h8k0rdqt0"&gt;Predict Dashlets on Focus Drawers and Preview&lt;/h3&gt;
&lt;p&gt;In this release, we&amp;#39;ve added the capability for users to&amp;nbsp;view the Opportunity Close Prediction Dashlet and the Lead Conversion Prediction Dashlet directly from their Focus Dashboards and Dashlet Previews, eliminating the need to navigate to an Opportunity or Leads Record View. This enhancement streamlines the user experience, making it easier for users to access and manage their Leads and Opportunities data. By providing better lead and opportunity insights right in their Focus Dashboards and Dashlet preview, we&amp;rsquo;re enabling users to make more informed decisions and improve their overall productivity.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Comment Log in Quotes and all Preview Layouts&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;we are adding&amp;nbsp;Comment Log to the Quotes Module Record View and Preview allows for more efficient management of Quotes, as users can now easily access and update comments directly from their Record View and/or Preview Layout. Before 14.0, the Comment Log was only available for preview layouts in the Bugs module, in 14.0 we expanded the funcionalty to all preview layouts for modules where the Comment Log is available. We also added a scrollbar to the Comment Log making it easier for users to navigate through the comments without losing visibility of other relevant record information&lt;/span&gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Define Users Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;&lt;span class="TextRun SCXW208591049 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Admins can easily see at a glance the number of group users and drill into the drawer without having to navigate&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;away from the list view&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;This enhancement leverages the powerful functionality of&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Sugar&amp;#39;s&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;existing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;f&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ocus&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;d&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ashboards, providing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;users&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;with valuable information at their fingertips without having to drill into individual records or navigate away from other relevant information. This not only improves the efficiency of admins by reducing the time spent on navigation&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;,&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;but also enhances the overall user experience by providing quick access to important data.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW208591049 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;&lt;span class="TextRun SCXW159085114 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW159085114 BCX0" data-ccp-parastyle="heading 2"&gt;Role-based Report and Dashboard Templates&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release, w&lt;span class="TextRun SCXW30004081 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW30004081 BCX0"&gt;e introduce the role-based report and dashboard templates that will come with brand-new instance and will allow users to start working with data immediately, instead of spending time on setting up the reports and dashboards.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide role-based comprehensive templates, developed by our customer-facing departments (project webb). Users&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;Sales Reps or Sales Executives &amp;ndash; will have their dashboard and report available immediately. The reports and dashboards are read-only, but they can be duplicated and modified if needed.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide 6 role-based dashboard templates that can be accessed from left-hand home menu:&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;BDR Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Customer Success Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Executive Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Marketing Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Manager Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Rep Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;Also, we provide 166 report templates.&amp;nbsp;The templates are marked with the new filter visible in the list view. Stock reports were replaced by templates, the filters were replaced accordingly.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;New customer after his instance is set, access granted &amp;ndash; can start working. Sales Reps introduce the Opportunities and Leads to track &amp;ndash; next day can just open the dashboard where they have everything they need.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl10"&gt;&lt;code&gt;&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1givqvoho2"&gt;&lt;span&gt;&lt;span class="NormalTextRun SCXW249156672 BCX0"&gt;&lt;/span&gt;&lt;/span&gt;Sugar REST API updates&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;This Sugar release introduces REST&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;v11_24&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Admins to trigger a password reset in non-IDM mode&lt;/h3&gt;
&lt;p&gt;Allows an administrator of the Users module to trigger an email to be sent to a User requesting them to reset their password&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/password/adminRequest&lt;/pre&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Retrieve Related Activities API&lt;/h3&gt;
&lt;p&gt;The endpoint is used to load list of activities related to module/modules.&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/&amp;lt;module&amp;gt;/&amp;lt;record_id&amp;gt;/link/related_activities&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="mcetoc_1gj9pc6si0"&gt;Supported Platforms Update&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;In this release, we are updating Sugar&amp;rsquo;s Supported Platforms.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;We are dropping support for PHP 8.0 and adding support to PHP 8.3.&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;PHP&amp;nbsp;8.0 to PHP 8.1 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration81.php"&gt;https://www.php.net/manual/en/migration81.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration81.incompatible.php"&gt;https://www.php.net/manual/en/migration81.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.1&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.2 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration82.php"&gt;https://www.php.net/manual/en/migration82.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration82.incompatible.php"&gt;https://www.php.net/manual/en/migration82.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.2&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.3 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration83.php"&gt;https://www.php.net/manual/en/migration83.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration83.incompatible.php"&gt;https://www.php.net/manual/en/migration83.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There isn&amp;#39;t an upgrade path from 8.0 to 8.3, you must ensure it follows the upgrade path 7.4 -&amp;gt; 8.0 -&amp;gt; 8.1 -&amp;gt; 8.2 -&amp;gt; 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MySQL&amp;nbsp;5.4&amp;nbsp;and adding support for 8.1 and 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MSSQL&amp;nbsp;2017 and adding support for&amp;nbsp;2019 and 2022&lt;/li&gt;
&lt;li&gt;We are adding&amp;nbsp;support&amp;nbsp;for&amp;nbsp;Oracle&amp;nbsp;21c and 23c&lt;/li&gt;
&lt;li&gt;We are&amp;nbsp;dropping support for Windows Server 2019.&lt;/li&gt;
&lt;li&gt;We are adding support for&amp;nbsp;Amazon OpenSearch 5.6&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mcetoc_1ff80k9i33"&gt;Configurability&amp;nbsp;updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1f77psegv7"&gt;Sugar Config Settings&lt;/h3&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Setting Name&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Default&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Override Example&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.transport&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;https&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['transport'] = &amp;#39;https&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the protocol to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;full_text_engine.Elastic.username&lt;br /&gt;&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['username'] = &amp;#39;username&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;username to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.password&lt;br /&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config['full_text_engine']['Elastic']['password'] = &amp;#39;password&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;password to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;api.allowedClients&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;[]&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;span&gt;$sugar_config['api']['allowedClients'] =&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;#39;base&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;#39;chrome&amp;#39;, // allow only chrome browser&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;],&lt;br /&gt;&amp;nbsp; &amp;#39;mobile&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;#39;my_mobile_app_name&amp;#39;, // allow my_mobile_app_name custom app&lt;br /&gt;&amp;nbsp; &amp;nbsp; // ... add other custom apps ],&lt;br /&gt;&amp;nbsp; &amp;#39;portal&amp;#39; =&amp;gt; [], // allow anything&lt;br /&gt;];&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;Rules applied in the following order:&lt;br /&gt;- If the platform is not in the list - any client is allowed for it&lt;br /&gt;- If the platform is defined in the list, but the clients list is empty - any client is allowed&lt;br /&gt;- If the platform has one or more clients in the list - only they are allowed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcetoc_1f77psegvl"&gt;Platform Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable access to SugarCRM mobile application&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we&amp;#39;ve introduced a new configuration setting. This addition will empower you to define precisely which mobile clients are permitted to access your Sugar data/instance. It&amp;#39;s managed via a&amp;nbsp;sugar_config called&amp;nbsp;&lt;code&gt;$sugar_config['api'][&amp;#39;allowedClients&amp;#39;&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When you generate an SDK application you are asked to give that application a name. This new config, provides you the the ability to specify which app names can connect to a Sugar instance. For an existing application, in the app.json configuration file, you can see the name in the &amp;ldquo;appName&amp;rdquo; parameter. As an example, if you generated an app with an appName set to &amp;ldquo;my_app_name&amp;rdquo;, you would need to make a corresponding configuration change in Sugar.&lt;br /&gt;For example, to ensure that only the&amp;nbsp;your app_name client, created through the mobile SDK, is allowed, you&amp;#39;ll need to incorporate the following line into your Sugar Sell configuration:&amp;nbsp;&lt;code&gt;$sugar_config['api']['allowedClients'] = [&amp;#39;mobile&amp;#39; =&amp;gt; ['my_app_name']];&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Updates to&amp;nbsp;Forecast Commitment&lt;/h3&gt;
&lt;p&gt;Prior to this release, the Commitment value in the Commitment tab be calculated based on the Opportunities in the forecast before an initial manual commitment. When the user changes the value and clicks &amp;ldquo;Commit&amp;rdquo; the Commitment value is no longer calculated and only changes when the user manually changes.&amp;nbsp;This has caused some confusion amongst Forecast module users because they expect the system to continue to update the Commitment value after their manual changes. To avoid confusion, in this release, Sugar will initiate that value at 0 (zero) so users know they haven&amp;rsquo;t committed anything and the value will only change when they manually change it.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Default Value was removed from Calls and Meetings in the Studio UI&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are removing Default&lt;span&gt;&amp;nbsp;Value from Calls and Meetings in the Studio UI.&amp;nbsp;This option has been removed as it creates a false impression that admins can set reminders. Currently, Sugar uses what is in&amp;nbsp;the User Profile Settings.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On Upgrade, instances will no longer see that and it will not be avilable for new installs.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW113039343 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW113039343 BCX0" data-ccp-parastyle="heading 2"&gt;Additional List View Filters&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="TextRun SCXW80679206 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW80679206 BCX0" data-ccp-parastyle="heading 2"&gt;The addition of three new list view filters in version 14.0 significantly enhances the user experience by making it easier for users to filter and find information quickly. With the &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; operator now available for Textarea fields and the &amp;quot;&lt;code&gt;After today&lt;/code&gt;&amp;quot; and &amp;quot;&lt;code&gt;Before today&lt;/code&gt;&amp;quot; options for Date and Datetime fields, users can easily filter records without having to enter exact dates or build complex operators. &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; also works for custom fields now.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW165847498 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW165847498 BCX0" data-ccp-parastyle="heading 2"&gt;Improved CRM/Self-Service Center integration&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW165847498 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;Currently Self-Service Center(SSC) users are mapped as &amp;ldquo;External Users&amp;rdquo; in CRM. When a case or any other object is created by SSC user, it is linked to the &amp;ldquo;External Users&amp;rdquo; in the CRM. A SSC user can be a Prospect or a Lead or a Contact and currently can be linked to a Contact. The current problem is that the CRM users ( e.g. Sales or Service agents) have to look at two separate screens e.g. 1) External Users and 2) Contact records to see all the related activities for a Contact (depending on which system was used to create the interaction/activity).&lt;/p&gt;
&lt;p&gt;&lt;span class="TextRun SCXW110851170 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;In this release, we are bringing this&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;ne&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;w&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;enhancement&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;to&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ensure that all&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the related&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;activities whether initiated from the SSC by an External User or within the CRM by&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;s&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;are&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;shown&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in a single, c&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;onsolidated&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;view for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;Contact in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;CRM.&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;I.e. All related records of External Users are now also shown as related to the Contact when an External User is related to that C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW110851170 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Display SugarIdentity warning when user is trying to edit IDM fields&lt;/h3&gt;
&lt;p&gt;In this release, we are introducing a warning message when user is trying to edit a field that&amp;rsquo;s owned by Sugar IDM in the&amp;nbsp;User&amp;rsquo;s List View, User&amp;rsquo;s Preview, Dashboards and dashlets.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Enable Sales Stage and Expected close date editable for Sales Console&lt;/h3&gt;
&lt;p&gt;In this release,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Sales Stage&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Expected Close Date&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;were added as&amp;nbsp;editable in console multiline list views and they&amp;nbsp;will behave the same as list views.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Add Users List View to Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In our previous release, we moved Users from BWC to Sidecar but we missed this functionality, now in this release we have fixed it, so you can take advantage of adding Users List Views to your Dashboards&lt;/span&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Update Metric font size&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are&amp;nbsp;updating the font size for the metric total as follows:&lt;/p&gt;
&lt;ul class="ak-ul" data-indent-level="1"&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="171"&gt;Update preferred currency from&lt;strong data-renderer-mark="true"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;text-4xl&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&amp;rarr;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl (&lt;/strong&gt;&lt;code class="code css-1o5d2cw" data-renderer-mark="true"&gt;font-size: 1.875rem; /* 30px */ line-height: 2.25rem; /* 36px */&lt;/code&gt;&lt;strong data-renderer-mark="true"&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="292"&gt;Fix When preferred currency &amp;amp; system currency are turned on, use&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;for preferred currency as well. (today when preferred currency is on or off, they appear at different sizes)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Support for Amazon OpenSearch&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are concluding our efforts to support Amazon OpenSearch which could potentially be used by any admin on their instances.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;User Interface&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins have a new option to configure Full-text search options and use OpenSearch as their FTS engine&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;They can set&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;password&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Elastic search is still the engine and there&amp;#39;s no need to update to OpenSearch, it will be handled by Sugar when there&amp;#39;s handshake with the server&lt;/li&gt;
&lt;li&gt;&lt;span&gt;UI is not available for SugarCloud instances&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Configuration&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins can override config.php to add those configs (see Sugar&amp;nbsp;Config Settings)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Admins can use Environment Variables as a security protection for&amp;nbsp;&lt;span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;/span&gt;&amp;nbsp;&lt;span&gt;&lt;code&gt;password&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Note, the environment variables must be set before Apache server restarted.&lt;/li&gt;
&lt;li&gt;These are the env variables&lt;/li&gt;
&lt;li&gt;&amp;#39;es_username&amp;#39; ==&amp;gt; &amp;#39;username&amp;#39;&lt;/li&gt;
&lt;li&gt;&amp;lsquo;es_password&amp;#39; ==&amp;gt; &amp;#39;password&amp;rsquo;&lt;/li&gt;
&lt;li&gt;&amp;#39;es_transport&amp;#39; ==&amp;gt; &amp;#39;transport&amp;#39;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Note:&amp;nbsp;&lt;/strong&gt;It&amp;rsquo;s important to note that using Amazon OpenSearch requires careful evaluation, especially for on-premise setups (can we say &amp;quot;on-site Sugar instances&amp;quot;?). This is due to the need of opening connections to Amazon&amp;rsquo;s cloud services, which may pose connectivity challenges or latency issues for some customers. We recommend that you evaluate Amazon OpenSearch on a case-by-case basis, taking into account these considerations.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Cookie Consent -&amp;nbsp;Remove &amp;quot;Accept Cookies&amp;quot; step from new user wizard&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are removing our cookie acceptance policy to ensure that we are only requiring users to accept required cookies and nothing else. At present, our cookie accept screen is a required field &amp;ndash; without accepting cookies, the application will not work. As this is not a meaningful choice for the user, Sugar is removing&amp;nbsp;the option and any required checks for this setting. Those fields are being hidden in Studio. Sugar&amp;nbsp;&lt;/span&gt;Portal is&amp;nbsp;also removing the cookie consent same as Sugar app.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable unlink option for records created by External Users&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are disabling the unlink option for records that are created by External Users but shown in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After creating a record as an external user, the unlink option is not available in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Sugar Core Security Updates&lt;/h3&gt;
&lt;p&gt;As part of our ongoing efforts to keep Sugar clean, fast, reliable, and most importantly secure, we have updated&amp;nbsp;Sugar Core code in different areas of the application such as Package Scanner, Module Installer, UI rendering, Handlebar templates, File Uploads and Imports.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Sugar Core PHP 8.2 compatibility&lt;/h3&gt;
&lt;p&gt;We are constantly monitoring issues in the code for PHP 8.2 compatibility and have hardened multiple core code In this release,&amp;nbsp;Most of those fixes are defensive coding following the steps described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/w/dev-tutorials/896/php-7-4-warnings-to-php8-2-errors"&gt;this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Sugar Q2 2024, Sugar 14&lt;/div&gt;
</description></item><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide/revision/6</link><pubDate>Wed, 03 Apr 2024 16:13:13 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Rafael Fernandes</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Revision 6 posted to Dev Tutorials by Rafael Fernandes on 4/3/2024 4:13:13 PM&lt;br /&gt;
&lt;div class="content"&gt;
&lt;p&gt;The purpose of this document is to provide insight to Sugar Developers for upgrading custom Sugar code, extensions, and integrations to the Sugar 14.0 (Q2 2024) release. This guide focuses on changes in Sugar&amp;nbsp;&lt;span&gt;14.0 (Q&lt;/span&gt;&lt;span&gt;2&lt;/span&gt; 2024) that could cause an immediate impact on Sugar customizations and integrations built for earlier Sugar versions.&lt;/p&gt;
&lt;p&gt;Please check out the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/m/event-recaps/2740"&gt;Q2 2024 Developer Webinar recording&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for more developer highlights.&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;For Admin and End User release notes, please visit the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://support.sugarcrm.com/SmartLinks/Release_Notes/14.0.0_Release_Notes/"&gt;Sugar 14.0.0 Release Notes&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;h2 id="mcetoc_1ff80k9i32"&gt;User Experience Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1h8k0rdqt0"&gt;Predict Dashlets on Focus Drawers and Preview&lt;/h3&gt;
&lt;p&gt;In this release, we&amp;#39;ve added the capability for users to&amp;nbsp;view the Opportunity Close Prediction Dashlet and the Lead Conversion Prediction Dashlet directly from their Focus Dashboards and Dashlet Previews, eliminating the need to navigate to an Opportunity or Leads Record View. This enhancement streamlines the user experience, making it easier for users to access and manage their Leads and Opportunities data. By providing better lead and opportunity insights right in their Focus Dashboards and Dashlet preview, we&amp;rsquo;re enabling users to make more informed decisions and improve their overall productivity.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Comment Log in Quotes and all Preview Layouts&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;we are adding&amp;nbsp;Comment Log to the Quotes Module Record View and Preview allows for more efficient management of Quotes, as users can now easily access and update comments directly from their Record View and/or Preview Layout. Before 14.0, the Comment Log was only available for preview layouts in the Bugs module, in 14.0 we expanded the funcionalty to all preview layouts for modules where the Comment Log is available. We also added a scrollbar to the Comment Log making it easier for users to navigate through the comments without losing visibility of other relevant record information&lt;/span&gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Define Users Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;&lt;span class="TextRun SCXW208591049 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Admins can easily see at a glance the number of group users and drill into the drawer without having to navigate&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;away from the list view&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;This enhancement leverages the powerful functionality of&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Sugar&amp;#39;s&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;existing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;f&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ocus&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;d&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ashboards, providing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;users&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;with valuable information at their fingertips without having to drill into individual records or navigate away from other relevant information. This not only improves the efficiency of admins by reducing the time spent on navigation&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;,&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;but also enhances the overall user experience by providing quick access to important data.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW208591049 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;&lt;span class="TextRun SCXW159085114 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW159085114 BCX0" data-ccp-parastyle="heading 2"&gt;Role-based Report and Dashboard Templates&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release, w&lt;span class="TextRun SCXW30004081 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW30004081 BCX0"&gt;e introduce the role-based report and dashboard templates that will come with brand-new instance and will allow users to start working with data immediately, instead of spending time on setting up the reports and dashboards.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide role-based comprehensive templates, developed by our customer-facing departments (project webb). Users&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;Sales Reps or Sales Executives &amp;ndash; will have their dashboard and report available immediately. The reports and dashboards are read-only, but they can be duplicated and modified if needed.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide 6 role-based dashboard templates that can be accessed from left-hand home menu:&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;BDR Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Customer Success Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Executive Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Marketing Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Manager Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Rep Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;Also, we provide 166 report templates.&amp;nbsp;The templates are marked with the new filter visible in the list view. Stock reports were replaced by templates, the filters were replaced accordingly.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;New customer after his instance is set, access granted &amp;ndash; can start working. Sales Reps introduce the Opportunities and Leads to track &amp;ndash; next day can just open the dashboard where they have everything they need.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl10"&gt;&lt;code&gt;&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1givqvoho2"&gt;&lt;span&gt;&lt;span class="NormalTextRun SCXW249156672 BCX0"&gt;&lt;/span&gt;&lt;/span&gt;Sugar REST API updates&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;This Sugar release introduces REST&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;v11_24&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Admins to trigger a password reset in non-IDM mode&lt;/h3&gt;
&lt;p&gt;Allows an administrator of the Users module to trigger an email to be sent to a User requesting them to reset their password&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/password/adminRequest&lt;/pre&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Retrieve Related Activities API&lt;/h3&gt;
&lt;p&gt;The endpoint is used to load list of activities related to module/modules.&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/&amp;lt;module&amp;gt;/&amp;lt;record_id&amp;gt;/link/related_activities&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="mcetoc_1gj9pc6si0"&gt;Supported Platforms Update&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;In this release, we are updating Sugar&amp;rsquo;s Supported Platforms.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;We are dropping support for PHP 8.0 and adding support to PHP 8.3.&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;PHP&amp;nbsp;8.0 to PHP 8.1 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration81.php"&gt;https://www.php.net/manual/en/migration81.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration81.incompatible.php"&gt;https://www.php.net/manual/en/migration81.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.1&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.2 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration82.php"&gt;https://www.php.net/manual/en/migration82.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration82.incompatible.php"&gt;https://www.php.net/manual/en/migration82.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.2&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.3 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration83.php"&gt;https://www.php.net/manual/en/migration83.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration83.incompatible.php"&gt;https://www.php.net/manual/en/migration83.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There isn&amp;#39;t an upgrade path from 8.0 to 8.3, you must ensure it follows the upgrade path 7.4 -&amp;gt; 8.0 -&amp;gt; 8.1 -&amp;gt; 8.2 -&amp;gt; 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MySQL&amp;nbsp;5.4&amp;nbsp;and adding support for 8.1 and 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MSSQL&amp;nbsp;2017 and adding support for&amp;nbsp;2019 and 2022&lt;/li&gt;
&lt;li&gt;We are adding&amp;nbsp;support&amp;nbsp;for&amp;nbsp;Oracle&amp;nbsp;21c and 23c&lt;/li&gt;
&lt;li&gt;We are&amp;nbsp;dropping support for Windows Server 2019.&lt;/li&gt;
&lt;li&gt;We are adding support for&amp;nbsp;Amazon OpenSearch 5.6&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mcetoc_1ff80k9i33"&gt;Configurability&amp;nbsp;updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1f77psegv7"&gt;Sugar Config Settings&lt;/h3&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Setting Name&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Default&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Override Example&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.transport&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;https&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['transport'] = &amp;#39;https&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the protocol to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;full_text_engine.Elastic.username&lt;br /&gt;&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['username'] = &amp;#39;username&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;username to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.password&lt;br /&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config['full_text_engine']['Elastic']['password'] = &amp;#39;password&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;password to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;api.allowedClients&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;[]&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;span&gt;$sugar_config['api']['allowedClients'] =&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;#39;base&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;#39;chrome&amp;#39;, // allow only chrome browser&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;],&lt;br /&gt;&amp;nbsp; &amp;#39;mobile&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;#39;my_mobile_app_name&amp;#39;, // allow my_mobile_app_name custom app&lt;br /&gt;&amp;nbsp; &amp;nbsp; // ... add other custom apps ],&lt;br /&gt;&amp;nbsp; &amp;#39;portal&amp;#39; =&amp;gt; [], // allow anything&lt;br /&gt;];&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;Rules applied in the following order:&lt;br /&gt;- If the platform is not in the list - any client is allowed for it&lt;br /&gt;- If the platform is defined in the list, but the clients list is empty - any client is allowed&lt;br /&gt;- If the platform has one or more clients in the list - only they are allowed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcetoc_1f77psegvl"&gt;Platform Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable access to SugarCRM mobile application&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we&amp;#39;ve introduced a new configuration setting. This addition will empower you to define precisely which mobile clients are permitted to access your Sugar data/instance. It&amp;#39;s managed via a&amp;nbsp;sugar_config called&amp;nbsp;&lt;code&gt;$sugar_config['api'][&amp;#39;allowedClients&amp;#39;&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When you generate an SDK application you are asked to give that application a name. This new config, provides you the the ability to specify which app names can connect to a Sugar instance. For an existing application, in the app.json configuration file, you can see the name in the &amp;ldquo;appName&amp;rdquo; parameter. As an example, if you generated an app with an appName set to &amp;ldquo;my_app_name&amp;rdquo;, you would need to make a corresponding configuration change in Sugar.&lt;br /&gt;For example, to ensure that only the&amp;nbsp;your app_name client, created through the mobile SDK, is allowed, you&amp;#39;ll need to incorporate the following line into your Sugar Sell configuration:&amp;nbsp;&lt;code&gt;$sugar_config['api']['allowedClients'] = [&amp;#39;mobile&amp;#39; =&amp;gt; ['my_app_name']];&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Updates to&amp;nbsp;Forecast Commitment&lt;/h3&gt;
&lt;p&gt;Prior to this release, the Commitment value in the Commitment tab be calculated based on the Opportunities in the forecast before an initial manual commitment. When the user changes the value and clicks &amp;ldquo;Commit&amp;rdquo; the Commitment value is no longer calculated and only changes when the user manually changes.&amp;nbsp;This has caused some confusion amongst Forecast module users because they expect the system to continue to update the Commitment value after their manual changes. To avoid confusion, in this release, Sugar will initiate that value at 0 (zero) so users know they haven&amp;rsquo;t committed anything and the value will only change when they manually change it.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Default Value was removed from Calls and Meetings in the Studio UI&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are removing Default&lt;span&gt;&amp;nbsp;Value from Calls and Meetings in the Studio UI.&amp;nbsp;This option has been removed as it creates a false impression that admins can set reminders. Currently, Sugar uses what is in&amp;nbsp;the User Profile Settings.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On Upgrade, instances will no longer see that and it will not be avilable for new installs.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW113039343 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW113039343 BCX0" data-ccp-parastyle="heading 2"&gt;Additional List View Filters&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="TextRun SCXW80679206 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW80679206 BCX0" data-ccp-parastyle="heading 2"&gt;The addition of three new list view filters in version 14.0 significantly enhances the user experience by making it easier for users to filter and find information quickly. With the &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; operator now available for Textarea fields and the &amp;quot;&lt;code&gt;After today&lt;/code&gt;&amp;quot; and &amp;quot;&lt;code&gt;Before today&lt;/code&gt;&amp;quot; options for Date and Datetime fields, users can easily filter records without having to enter exact dates or build complex operators. &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; also works for custom fields now.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW165847498 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW165847498 BCX0" data-ccp-parastyle="heading 2"&gt;Improved CRM/Self-Service Center integration&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW165847498 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;Currently Self-Service Center(SSC) users are mapped as &amp;ldquo;External Users&amp;rdquo; in CRM. When a case or any other object is created by SSC user, it is linked to the &amp;ldquo;External Users&amp;rdquo; in the CRM. A SSC user can be a Prospect or a Lead or a Contact and currently can be linked to a Contact. The current problem is that the CRM users ( e.g. Sales or Service agents) have to look at two separate screens e.g. 1) External Users and 2) Contact records to see all the related activities for a Contact (depending on which system was used to create the interaction/activity).&lt;/p&gt;
&lt;p&gt;&lt;span class="TextRun SCXW110851170 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;In this release, we are bringing this&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;ne&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;w&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;enhancement&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;to&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ensure that all&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the related&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;activities whether initiated from the SSC by an External User or within the CRM by&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;s&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;are&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;shown&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in a single, c&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;onsolidated&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;view for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;Contact in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;CRM.&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;I.e. All related records of External Users are now also shown as related to the Contact when an External User is related to that C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW110851170 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Display SugarIdentity warning when user is trying to edit IDM fields&lt;/h3&gt;
&lt;p&gt;In this release, we are introducing a warning message when user is trying to edit a field that&amp;rsquo;s owned by Sugar IDM in the&amp;nbsp;User&amp;rsquo;s List View, User&amp;rsquo;s Preview, Dashboards and dashlets.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Enable Sales Stage and Expected close date editable for Sales Console&lt;/h3&gt;
&lt;p&gt;In this release,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Sales Stage&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Expected Close Date&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;were added as&amp;nbsp;editable in console multiline list views and they&amp;nbsp;will behave the same as list views.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Add Users List View to Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In our previous release, we moved Users from BWC to Sidecar but we missed this functionality, now in this release we have fixed it, so you can take advantage of adding Users List Views to your Dashboards&lt;/span&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Update Metric font size&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are&amp;nbsp;updating the font size for the metric total as follows:&lt;/p&gt;
&lt;ul class="ak-ul" data-indent-level="1"&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="171"&gt;Update preferred currency from&lt;strong data-renderer-mark="true"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;text-4xl&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&amp;rarr;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl (&lt;/strong&gt;&lt;code class="code css-1o5d2cw" data-renderer-mark="true"&gt;font-size: 1.875rem; /* 30px */ line-height: 2.25rem; /* 36px */&lt;/code&gt;&lt;strong data-renderer-mark="true"&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="292"&gt;Fix When preferred currency &amp;amp; system currency are turned on, use&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;for preferred currency as well. (today when preferred currency is on or off, they appear at different sizes)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Support for Amazon OpenSearch&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are concluding our efforts to support Amazon OpenSearch which could potentially be used by any admin on their instances.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;User Interface&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins have a new option to configure Full-text search options and use OpenSearch as their FTS engine&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;They can set&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;password&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Elastic search is still the engine and there&amp;#39;s no need to update to OpenSearch, it will be handled by Sugar when there&amp;#39;s handshake with the server&lt;/li&gt;
&lt;li&gt;&lt;span&gt;UI is not available for SugarCloud instances&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Configuration&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins can override config.php to add those configs (see Sugar&amp;nbsp;Config Settings)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Admins can use Environment Variables as a security protection for&amp;nbsp;&lt;span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;/span&gt;&amp;nbsp;&lt;span&gt;&lt;code&gt;password&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Note, the environment variables must be set before Apache server restarted.&lt;/li&gt;
&lt;li&gt;These are the env variables&lt;/li&gt;
&lt;li&gt;&amp;#39;es_username&amp;#39; ==&amp;gt; &amp;#39;username&amp;#39;&lt;/li&gt;
&lt;li&gt;&amp;lsquo;es_password&amp;#39; ==&amp;gt; &amp;#39;password&amp;rsquo;&lt;/li&gt;
&lt;li&gt;&amp;#39;es_transport&amp;#39; ==&amp;gt; &amp;#39;transport&amp;#39;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Note:&amp;nbsp;&lt;/strong&gt;It&amp;rsquo;s important to note that using Amazon OpenSearch requires careful evaluation, especially for on-premise setups (can we say &amp;quot;on-site Sugar instances&amp;quot;?). This is due to the need of opening connections to Amazon&amp;rsquo;s cloud services, which may pose connectivity challenges or latency issues for some customers. We recommend that you evaluate Amazon OpenSearch on a case-by-case basis, taking into account these considerations.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Cookie Consent -&amp;nbsp;Remove &amp;quot;Accept Cookies&amp;quot; step from new user wizard&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are removing our cookie acceptance policy to ensure that we are only requiring users to accept required cookies and nothing else. At present, our cookie accept screen is a required field &amp;ndash; without accepting cookies, the application will not work. As this is not a meaningful choice for the user, Sugar is removing&amp;nbsp;the option and any required checks for this setting. Those fields are being hidden in Studio. Sugar&amp;nbsp;&lt;/span&gt;Portal is&amp;nbsp;also removing the cookie consent same as Sugar app.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable unlink option for records created by External Users&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are disabling the unlink option for records that are created by External Users but shown in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After creating a record as an external user, the unlink option is not available in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Sugar Core Security Updates&lt;/h3&gt;
&lt;p&gt;As part of our ongoing efforts to keep Sugar clean, fast, reliable, and most importantly secure, we have updated&amp;nbsp;Sugar Core code in different areas of the application such as Package Scanner, Module Installer, UI rendering, Handlebar templates, File Uploads and Imports.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Sugar Core PHP 8.2 compatibility&lt;/h3&gt;
&lt;p&gt;We are constantly monitoring issues in the code for PHP 8.2 compatibility and have hardened multiple core code In this release,&amp;nbsp;Most of those fixes are defensive coding following the steps described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/w/dev-tutorials/896/php-7-4-warnings-to-php8-2-errors"&gt;this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Sugar Q2 2024, Sugar 14&lt;/div&gt;
</description></item><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide/revision/5</link><pubDate>Tue, 02 Apr 2024 20:42:57 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Rafael Fernandes</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Revision 5 posted to Dev Tutorials by Rafael Fernandes on 4/2/2024 8:42:57 PM&lt;br /&gt;
&lt;div class="content"&gt;
&lt;p&gt;The purpose of this document is to provide insight to Sugar Developers for upgrading custom Sugar code, extensions, and integrations to the Sugar 14.0 (Q2 2024) release. This guide focuses on changes in Sugar&amp;nbsp;&lt;span&gt;14.0 (Q&lt;/span&gt;&lt;span&gt;2&lt;/span&gt; 2024) that could cause an immediate impact on Sugar customizations and integrations built for earlier Sugar versions.&lt;/p&gt;
&lt;p&gt;Please check out the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/m/event-recaps/2740"&gt;Q2 2024 Developer Webinar recording&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for more developer highlights.&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;For Admin and End User release notes, please visit the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://support.sugarcrm.com/SmartLinks/Release_Notes/14.0.0_Release_Notes/"&gt;Sugar 14.0.0 Release Notes&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;h2 id="mcetoc_1ff80k9i32"&gt;User Experience Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1h8k0rdqt0"&gt;Predict Dashlets on Focus Drawers and Preview&lt;/h3&gt;
&lt;p&gt;In this release, we&amp;#39;ve added the capability for users to&amp;nbsp;view the Opportunity Close Prediction Dashlet and the Lead Conversion Prediction Dashlet directly from their Focus Dashboards and Dashlet Previews, eliminating the need to navigate to an Opportunity or Leads Record View. This enhancement streamlines the user experience, making it easier for users to access and manage their Leads and Opportunities data. By providing better lead and opportunity insights right in their Focus Dashboards and Dashlet preview, we&amp;rsquo;re enabling users to make more informed decisions and improve their overall productivity.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Comment Log in Quotes and all Preview Layouts&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;we are adding&amp;nbsp;Comment Log to the Quotes Module Record View and Preview allows for more efficient management of Quotes, as users can now easily access and update comments directly from their Record View and/or Preview Layout. Before 14.0, the Comment Log was only available for preview layouts in the Bugs module, in 14.0 we expanded the funcionalty to all preview layouts for modules where the Comment Log is available. We also added a scrollbar to the Comment Log making it easier for users to navigate through the comments without losing visibility of other relevant record information&lt;/span&gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Define Users Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;&lt;span class="TextRun SCXW208591049 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Admins can easily see at a glance the number of group users and drill into the drawer without having to navigate&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;away from the list view&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;This enhancement leverages the powerful functionality of&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Sugar&amp;#39;s&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;existing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;f&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ocus&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;d&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ashboards, providing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;users&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;with valuable information at their fingertips without having to drill into individual records or navigate away from other relevant information. This not only improves the efficiency of admins by reducing the time spent on navigation&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;,&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;but also enhances the overall user experience by providing quick access to important data.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW208591049 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;&lt;span class="TextRun SCXW159085114 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW159085114 BCX0" data-ccp-parastyle="heading 2"&gt;Role-based Report and Dashboard Templates&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release, w&lt;span class="TextRun SCXW30004081 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW30004081 BCX0"&gt;e introduce the role-based report and dashboard templates that will come with brand-new instance and will allow users to start working with data immediately, instead of spending time on setting up the reports and dashboards.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide role-based comprehensive templates, developed by our customer-facing departments (project webb). Users&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;Sales Reps or Sales Executives &amp;ndash; will have their dashboard and report available immediately. The reports and dashboards are read-only, but they can be duplicated and modified if needed.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide 6 role-based dashboard templates that can be accessed from left-hand home menu:&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;BDR Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Customer Success Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Executive Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Marketing Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Manager Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Rep Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;Also, we provide 166 report templates.&amp;nbsp;The templates are marked with the new filter visible in the list view. Stock reports were replaced by templates, the filters were replaced accordingly.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;New customer after his instance is set, access granted &amp;ndash; can start working. Sales Reps introduce the Opportunities and Leads to track &amp;ndash; next day can just open the dashboard where they have everything they need.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl10"&gt;&lt;code&gt;&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1givqvoho2"&gt;&lt;span&gt;&lt;span class="NormalTextRun SCXW249156672 BCX0"&gt;&lt;/span&gt;&lt;/span&gt;Sugar REST API updates&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;This Sugar release introduces REST&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;v11_24&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Admins to trigger a password reset in non-IDM mode&lt;/h3&gt;
&lt;p&gt;Allows an administrator of the Users module to trigger an email to be sent to a User requesting them to reset their password&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/password/adminRequest&lt;/pre&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Retrieve Related Activities API&lt;/h3&gt;
&lt;p&gt;The endpoint is used to load list of activities related to module/modules.&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/&amp;lt;module&amp;gt;/&amp;lt;record_id&amp;gt;/link/related_activities&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="mcetoc_1gj9pc6si0"&gt;Supported Platforms Update&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;In this release, we are updating Sugar&amp;rsquo;s Supported Platforms.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;We are dropping support for PHP 8.0 and adding support to PHP 8.3.&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;PHP&amp;nbsp;8.0 to PHP 8.1 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration81.php"&gt;https://www.php.net/manual/en/migration81.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration81.incompatible.php"&gt;https://www.php.net/manual/en/migration81.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.1&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.2 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration82.php"&gt;https://www.php.net/manual/en/migration82.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration82.incompatible.php"&gt;https://www.php.net/manual/en/migration82.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.2&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.3 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration83.php"&gt;https://www.php.net/manual/en/migration83.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration83.incompatible.php"&gt;https://www.php.net/manual/en/migration83.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There isn&amp;#39;t an upgrade path from 8.0 to 8.3, you must ensure it follows the upgrade path 7.4 -&amp;gt; 8.0 -&amp;gt; 8.1 -&amp;gt; 8.2 -&amp;gt; 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MySQL&amp;nbsp;5.4&amp;nbsp;and adding support for 8.1 and 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MSSQL&amp;nbsp;2017 and adding support for&amp;nbsp;2019 and 2022&lt;/li&gt;
&lt;li&gt;We are adding&amp;nbsp;support&amp;nbsp;for&amp;nbsp;Oracle&amp;nbsp;21c and 23c&lt;/li&gt;
&lt;li&gt;We are&amp;nbsp;dropping support for Windows Server 2019.&lt;/li&gt;
&lt;li&gt;We are adding support for&amp;nbsp;Amazon OpenSearch 5.6&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mcetoc_1ff80k9i33"&gt;Configurability&amp;nbsp;updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1f77psegv7"&gt;Sugar Config Settings&lt;/h3&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Setting Name&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Default&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Override Example&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.transport&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;https&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['transport'] = &amp;#39;https&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the protocol to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;full_text_engine.Elastic.username&lt;br /&gt;&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['username'] = &amp;#39;username&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;username to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.password&lt;br /&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config['full_text_engine']['Elastic']['password'] = &amp;#39;password&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;password to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;api.allowedClients&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;[]&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;span&gt;$sugar_config['api']['allowedClients'] =&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;#39;base&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;#39;chrome&amp;#39;, // allow only chrome browser&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;],&lt;br /&gt;&amp;nbsp; &amp;#39;mobile&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;#39;my_mobile_app_name&amp;#39;, // allow my_mobile_app_name custom app&lt;br /&gt;&amp;nbsp; &amp;nbsp; // ... add other custom apps ],&lt;br /&gt;&amp;nbsp; &amp;#39;portal&amp;#39; =&amp;gt; [], // allow anything&lt;br /&gt;];&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;Rules applied in the following order:&lt;br /&gt;- If the platform is not in the list - any client is allowed for it&lt;br /&gt;- If the platform is defined in the list, but the clients list is empty - any client is allowed&lt;br /&gt;- If the platform has one or more clients in the list - only they are allowed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcetoc_1f77psegvl"&gt;Platform Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable access to SugarCRM mobile application&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we&amp;#39;ve introduced a new configuration setting. This addition will empower you to define precisely which mobile clients are permitted to access your Sugar data/instance. It&amp;#39;s managed via a&amp;nbsp;sugar_config called&amp;nbsp;&lt;code&gt;$sugar_config['api'][&amp;#39;allowedClients&amp;#39;&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When you generate an SDK application you are asked to give that application a name. This new config, provides you the the ability to specify which app names can connect to a Sugar instance. For an existing application, in the app.json configuration file, you can see the name in the &amp;ldquo;appName&amp;rdquo; parameter. As an example, if you generated an app with an appName set to &amp;ldquo;my_app_name&amp;rdquo;, you would need to make a corresponding configuration change in Sugar.&lt;br /&gt;For example, to ensure that only the&amp;nbsp;your app_name client, created through the mobile SDK, is allowed, you&amp;#39;ll need to incorporate the following line into your Sugar Sell configuration:&amp;nbsp;&lt;code&gt;$sugar_config['api']['allowedClients'] = [&amp;#39;mobile&amp;#39; =&amp;gt; ['my_app_name']];&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Updates to&amp;nbsp;Forecast Commitment&lt;/h3&gt;
&lt;p&gt;Prior to this release, the Commitment value in the Commitment tab be calculated based on the Opportunities in the forecast before an initial manual commitment. When the user changes the value and clicks &amp;ldquo;Commit&amp;rdquo; the Commitment value is no longer calculated and only changes when the user manually changes.&amp;nbsp;This has caused some confusion amongst Forecast module users because they expect the system to continue to update the Commitment value after their manual changes. To avoid confusion, in this release, Sugar will initiate that value at 0 (zero) so users know they haven&amp;rsquo;t committed anything and the value will only change when they manually change it.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Default Value was removed from Calls and Meetings in the Studio UI&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are removing Default&lt;span&gt;&amp;nbsp;Value from Calls and Meetings in the Studio UI.&amp;nbsp;This option has been removed as it creates a false impression that admins can set reminders. Currently, Sugar uses what is in&amp;nbsp;the User Profile Settings.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On Upgrade, instances will no longer see that and it will not be avilable for new installs.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW113039343 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW113039343 BCX0" data-ccp-parastyle="heading 2"&gt;Additional List View Filters&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="TextRun SCXW80679206 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW80679206 BCX0" data-ccp-parastyle="heading 2"&gt;The addition of three new list view filters in version 14.0 significantly enhances the user experience by making it easier for users to filter and find information quickly. With the &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; operator now available for Textarea fields and the &amp;quot;&lt;code&gt;After today&lt;/code&gt;&amp;quot; and &amp;quot;&lt;code&gt;Before today&lt;/code&gt;&amp;quot; options for Date and Datetime fields, users can easily filter records without having to enter exact dates or build complex operators. &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; also works for custom fields now.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW165847498 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW165847498 BCX0" data-ccp-parastyle="heading 2"&gt;Improved CRM/Self-Service Center integration&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW165847498 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;Currently Self-Service Center(SSC) users are mapped as &amp;ldquo;External Users&amp;rdquo; in CRM. When a case or any other object is created by SSC user, it is linked to the &amp;ldquo;External Users&amp;rdquo; in the CRM. A SSC user can be a Prospect or a Lead or a Contact and currently can be linked to a Contact. The current problem is that the CRM users ( e.g. Sales or Service agents) have to look at two separate screens e.g. 1) External Users and 2) Contact records to see all the related activities for a Contact (depending on which system was used to create the interaction/activity).&lt;/p&gt;
&lt;p&gt;&lt;span class="TextRun SCXW110851170 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;In this release, we are bringing this&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;ne&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;w&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;enhancement&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;to&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ensure that all&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the related&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;activities whether initiated from the SSC by an External User or within the CRM by&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;s&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;are&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;shown&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in a single, c&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;onsolidated&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;view for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;Contact in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;CRM.&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;I.e. All related records of External Users are now also shown as related to the Contact when an External User is related to that C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW110851170 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Display SugarIdentity warning when user is trying to edit IDM fields&lt;/h3&gt;
&lt;p&gt;In this release, we are introducing a warning message when user is trying to edit a field that&amp;rsquo;s owned by Sugar IDM in the&amp;nbsp;User&amp;rsquo;s List View, User&amp;rsquo;s Preview, Dashboards and dashlets.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Enable Sales Stage and Expected close date editable for Sales Console&lt;/h3&gt;
&lt;p&gt;In this release,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Sales Stage&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Expected Close Date&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;were added as&amp;nbsp;editable in console multiline list views and they&amp;nbsp;will behave the same as list views.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Add Users List View to Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In our previous release, we moved Users from BWC to Sidecar but we missed this functionality, now in this release we have fixed it, so you can take advantage of adding Users List Views to your Dashboards&lt;/span&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Update Metric font size&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are&amp;nbsp;updating the font size for the metric total as follows:&lt;/p&gt;
&lt;ul class="ak-ul" data-indent-level="1"&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="171"&gt;Update preferred currency from&lt;strong data-renderer-mark="true"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;text-4xl&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&amp;rarr;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl (&lt;/strong&gt;&lt;code class="code css-1o5d2cw" data-renderer-mark="true"&gt;font-size: 1.875rem; /* 30px */ line-height: 2.25rem; /* 36px */&lt;/code&gt;&lt;strong data-renderer-mark="true"&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="292"&gt;Fix When preferred currency &amp;amp; system currency are turned on, use&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;for preferred currency as well. (today when preferred currency is on or off, they appear at different sizes)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Support for Amazon OpenSearch&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are concluding our efforts to support Amazon OpenSearch which could potentially be used by any admin on their instances.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;User Interface&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins have a new option to configure Full-text search options and use OpenSearch as their FTS engine&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;They can set&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;password&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Elastic search is still the engine and there&amp;#39;s no need to update to OpenSearch, it will be handled by Sugar when there&amp;#39;s handshake with the server&lt;/li&gt;
&lt;li&gt;&lt;span&gt;UI is not available for SugarCloud instances&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Configuration&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins can override config.php to add those configs (see Sugar&amp;nbsp;Config Settings)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Admins can use Environment Variables as a security protection for&amp;nbsp;&lt;span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;/span&gt;&amp;nbsp;&lt;span&gt;&lt;code&gt;password&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Note, the environment variables must be set before Apache server restarted.&lt;/li&gt;
&lt;li&gt;These are the env variables&lt;/li&gt;
&lt;li&gt;&amp;#39;es_username&amp;#39; ==&amp;gt; &amp;#39;username&amp;#39;&lt;/li&gt;
&lt;li&gt;&amp;lsquo;es_password&amp;#39; ==&amp;gt; &amp;#39;password&amp;rsquo;&lt;/li&gt;
&lt;li&gt;&amp;#39;es_transport&amp;#39; ==&amp;gt; &amp;#39;transport&amp;#39;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; It&amp;#39;s important to note that using Amazon OpenSearch requires careful evaluation, especially for on-premise setups. This is due to the need of opening connections to Amazon&amp;#39;s cloud services, which may pose connectivity challenges or if latency becomes an issue for some customers. We recommend you to evaluate Amazon OpenSearch on a case-by-case basis, taking into account these considerations&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Cookie Consent -&amp;nbsp;Remove &amp;quot;Accept Cookies&amp;quot; step from new user wizard&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are removing our cookie acceptance policy to ensure that we are only requiring users to accept required cookies and nothing else. At present, our cookie accept screen is a required field &amp;ndash; without accepting cookies, the application will not work. As this is not a meaningful choice for the user, Sugar is removing&amp;nbsp;the option and any required checks for this setting. Those fields are being hidden in Studio. Sugar&amp;nbsp;&lt;/span&gt;Portal is&amp;nbsp;also removing the cookie consent same as Sugar app.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable unlink option for records created by External Users&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are disabling the unlink option for records that are created by External Users but shown in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After creating a record as an external user, the unlink option is not available in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Sugar Core Security Updates&lt;/h3&gt;
&lt;p&gt;As part of our ongoing efforts to keep Sugar clean, fast, reliable, and most importantly secure, we have updated&amp;nbsp;Sugar Core code in different areas of the application such as Package Scanner, Module Installer, UI rendering, Handlebar templates, File Uploads and Imports.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Sugar Core PHP 8.2 compatibility&lt;/h3&gt;
&lt;p&gt;We are constantly monitoring issues in the code for PHP 8.2 compatibility and have hardened multiple core code In this release,&amp;nbsp;Most of those fixes are defensive coding following the steps described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/w/dev-tutorials/896/php-7-4-warnings-to-php8-2-errors"&gt;this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Sugar Q2 2024, Sugar 14&lt;/div&gt;
</description></item><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide/revision/4</link><pubDate>Tue, 26 Mar 2024 13:45:01 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Rafael Fernandes</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Revision 4 posted to Dev Tutorials by Rafael Fernandes on 3/26/2024 1:45:01 PM&lt;br /&gt;
&lt;div class="content"&gt;
&lt;p&gt;The purpose of this document is to provide insight to Sugar Developers for upgrading custom Sugar code, extensions, and integrations to the Sugar 14.0 (Q2 2024) release. This guide focuses on changes in Sugar&amp;nbsp;&lt;span&gt;14.0 (Q&lt;/span&gt;&lt;span&gt;2&lt;/span&gt; 2024) that could cause an immediate impact on Sugar customizations and integrations built for earlier Sugar versions.&lt;/p&gt;
&lt;p&gt;Please check out the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/m/event-recaps/2740"&gt;Q2 2024 Developer Webinar recording&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for more developer highlights.&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;For Admin and End User release notes, please visit the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://support.sugarcrm.com/SmartLinks/Release_Notes/14.0.0_Release_Notes/"&gt;Sugar 14.0.0 Release Notes&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;h2 id="mcetoc_1ff80k9i32"&gt;User Experience Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1h8k0rdqt0"&gt;Predict Dashlets on Focus Drawers and Preview&lt;/h3&gt;
&lt;p&gt;In this release, we&amp;#39;ve added the capability for users to&amp;nbsp;view the Opportunity Close Prediction Dashlet and the Lead Conversion Prediction Dashlet directly from their Focus Dashboards and Dashlet Previews, eliminating the need to navigate to an Opportunity or Leads Record View. This enhancement streamlines the user experience, making it easier for users to access and manage their Leads and Opportunities data. By providing better lead and opportunity insights right in their Focus Dashboards and Dashlet preview, we&amp;rsquo;re enabling users to make more informed decisions and improve their overall productivity.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Comment Log in Quotes and all Preview Layouts&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;we are adding&amp;nbsp;Comment Log to the Quotes Module Record View and Preview allows for more efficient management of Quotes, as users can now easily access and update comments directly from their Record View and/or Preview Layout. Before 14.0, the Comment Log was only available for preview layouts in the Bugs module, in 14.0 we expanded the funcionalty to all preview layouts for modules where the Comment Log is available. We also added a scrollbar to the Comment Log making it easier for users to navigate through the comments without losing visibility of other relevant record information&lt;/span&gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Define Users Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;&lt;span class="TextRun SCXW208591049 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Admins can easily see at a glance the number of group users and drill into the drawer without having to navigate&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;away from the list view&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;This enhancement leverages the powerful functionality of&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Sugar&amp;#39;s&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;existing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;f&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ocus&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;d&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ashboards, providing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;users&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;with valuable information at their fingertips without having to drill into individual records or navigate away from other relevant information. This not only improves the efficiency of admins by reducing the time spent on navigation&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;,&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;but also enhances the overall user experience by providing quick access to important data.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW208591049 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;&lt;span class="TextRun SCXW159085114 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW159085114 BCX0" data-ccp-parastyle="heading 2"&gt;Role-based Report and Dashboard Templates&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release, w&lt;span class="TextRun SCXW30004081 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW30004081 BCX0"&gt;e introduce the role-based report and dashboard templates that will come with brand-new instance and will allow users to start working with data immediately, instead of spending time on setting up the reports and dashboards.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide role-based comprehensive templates, developed by our customer-facing departments (project webb). Users&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;Sales Reps or Sales Executives &amp;ndash; will have their dashboard and report available immediately. The reports and dashboards are read-only, but they can be duplicated and modified if needed.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide 6 role-based dashboard templates that can be accessed from left-hand home menu:&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;BDR Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Customer Success Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Executive Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Marketing Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Manager Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Rep Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;Also, we provide 166 report templates.&amp;nbsp;The templates are marked with the new filter visible in the list view. Stock reports were replaced by templates, the filters were replaced accordingly.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;New customer after his instance is set, access granted &amp;ndash; can start working. Sales Reps introduce the Opportunities and Leads to track &amp;ndash; next day can just open the dashboard where they have everything they need.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl10"&gt;&lt;code&gt;&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1givqvoho2"&gt;&lt;span&gt;&lt;span class="NormalTextRun SCXW249156672 BCX0"&gt;&lt;/span&gt;&lt;/span&gt;Sugar REST API updates&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;This Sugar release introduces REST&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;v11_24&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Admins to trigger a password reset in non-IDM mode&lt;/h3&gt;
&lt;p&gt;Allows an administrator of the Users module to trigger an email to be sent to a User requesting them to reset their password&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/password/adminRequest&lt;/pre&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Retrieve Related Activities API&lt;/h3&gt;
&lt;p&gt;The endpoint is used to load list of activities related to module/modules.&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/&amp;lt;module&amp;gt;/&amp;lt;record_id&amp;gt;/link/related_activities&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="mcetoc_1gj9pc6si0"&gt;Supported Platforms Update&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;In this release, we are updating Sugar&amp;rsquo;s Supported Platforms.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;We are dropping support for PHP 8.0 and adding support to PHP 8.3.&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;PHP&amp;nbsp;8.0 to PHP 8.1 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration81.php"&gt;https://www.php.net/manual/en/migration81.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration81.incompatible.php"&gt;https://www.php.net/manual/en/migration81.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.1&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.2 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration82.php"&gt;https://www.php.net/manual/en/migration82.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration82.incompatible.php"&gt;https://www.php.net/manual/en/migration82.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.2&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.3 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration83.php"&gt;https://www.php.net/manual/en/migration83.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration83.incompatible.php"&gt;https://www.php.net/manual/en/migration83.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There isn&amp;#39;t an upgrade path from 8.0 to 8.3, you must ensure it follows the upgrade path 7.4 -&amp;gt; 8.0 -&amp;gt; 8.1 -&amp;gt; 8.2 -&amp;gt; 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MySQL&amp;nbsp;5.4&amp;nbsp;and adding support for 8.1 and 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MSSQL&amp;nbsp;2017 and adding support for&amp;nbsp;2019 and 2022&lt;/li&gt;
&lt;li&gt;We are adding&amp;nbsp;support&amp;nbsp;for&amp;nbsp;Oracle&amp;nbsp;21c and 23c&lt;/li&gt;
&lt;li&gt;We are&amp;nbsp;dropping support for Windows Server 2019.&lt;/li&gt;
&lt;li&gt;We are adding support for&amp;nbsp;Amazon OpenSearch 5.6&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mcetoc_1ff80k9i33"&gt;Configurability&amp;nbsp;updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1f77psegv7"&gt;Sugar Config Settings&lt;/h3&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Setting Name&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Default&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Override Example&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.transport&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;https&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['transport'] = &amp;#39;https&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the protocol to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;full_text_engine.Elastic.username&lt;br /&gt;&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['username'] = &amp;#39;username&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;username to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.password&lt;br /&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config['full_text_engine']['Elastic']['password'] = &amp;#39;password&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;password to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;api.allowedClients&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;[]&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;span&gt;$sugar_config['api']['allowedClients'] =&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;#39;base&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;#39;chrome&amp;#39;, // allow only chrome browser&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;],&lt;br /&gt;&amp;nbsp; &amp;#39;mobile&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;#39;my_mobile_app_name&amp;#39;, // allow my_mobile_app_name custom app&lt;br /&gt;&amp;nbsp; &amp;nbsp; // ... add other custom apps ],&lt;br /&gt;&amp;nbsp; &amp;#39;portal&amp;#39; =&amp;gt; [], // allow anything&lt;br /&gt;];&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;Rules applied in the following order:&lt;br /&gt;- If the platform is not in the list - any client is allowed for it&lt;br /&gt;- If the platform is defined in the list, but the clients list is empty - any client is allowed&lt;br /&gt;- If the platform has one or more clients in the list - only they are allowed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcetoc_1f77psegvl"&gt;Platform Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable access to SugarCRM mobile application&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we&amp;#39;ve introduced a new configuration setting. This addition will empower you to define precisely which mobile clients are permitted to access your Sugar data/instance. It&amp;#39;s managed via a&amp;nbsp;sugar_config called&amp;nbsp;&lt;code&gt;$sugar_config['api'][&amp;#39;allowedClients&amp;#39;&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When you generate an SDK application you are asked to give that application a name. This new config, provides you the the ability to specify which app names can connect to a Sugar instance. For an existing application, in the app.json configuration file, you can see the name in the &amp;ldquo;appName&amp;rdquo; parameter. As an example, if you generated an app with an appName set to &amp;ldquo;my_app_name&amp;rdquo;, you would need to make a corresponding configuration change in Sugar.&lt;br /&gt;For example, to ensure that only the&amp;nbsp;your app_name client, created through the mobile SDK, is allowed, you&amp;#39;ll need to incorporate the following line into your Sugar Sell configuration:&amp;nbsp;&lt;code&gt;$sugar_config['api']['allowedClients'] = [&amp;#39;mobile&amp;#39; =&amp;gt; ['my_app_name']];&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Updates to&amp;nbsp;Forecast Commitment&lt;/h3&gt;
&lt;p&gt;Prior to this release, the Commitment value in the Commitment tab be calculated based on the Opportunities in the forecast before an initial manual commitment. When the user changes the value and clicks &amp;ldquo;Commit&amp;rdquo; the Commitment value is no longer calculated and only changes when the user manually changes.&amp;nbsp;This has caused some confusion amongst Forecast module users because they expect the system to continue to update the Commitment value after their manual changes. To avoid confusion, in this release, Sugar will initiate that value at 0 (zero) so users know they haven&amp;rsquo;t committed anything and the value will only change when they manually change it.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Default Value was removed from Calls and Meetings in the Studio UI&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are removing Default&lt;span&gt;&amp;nbsp;Value from Calls and Meetings in the Studio UI.&amp;nbsp;This option has been removed as it creates a false impression that admins can set reminders. Currently, Sugar uses what is in&amp;nbsp;the User Profile Settings.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On Upgrade, instances will no longer see that and it will not be avilable for new installs.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW113039343 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW113039343 BCX0" data-ccp-parastyle="heading 2"&gt;Additional List View Filters&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="TextRun SCXW80679206 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW80679206 BCX0" data-ccp-parastyle="heading 2"&gt;The addition of three new list view filters in version 14.0 significantly enhances the user experience by making it easier for users to filter and find information quickly. With the &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; operator now available for Textarea fields and the &amp;quot;&lt;code&gt;After today&lt;/code&gt;&amp;quot; and &amp;quot;&lt;code&gt;Before today&lt;/code&gt;&amp;quot; options for Date and Datetime fields, users can easily filter records without having to enter exact dates or build complex operators. &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; also works for custom fields now.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW165847498 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW165847498 BCX0" data-ccp-parastyle="heading 2"&gt;Improved CRM/Self-Service Center integration&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW165847498 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;Currently Self-Service Center(SSC) users are mapped as &amp;ldquo;External Users&amp;rdquo; in CRM. When a case or any other object is created by SSC user, it is linked to the &amp;ldquo;External Users&amp;rdquo; in the CRM. A SSC user can be a Prospect or a Lead or a Contact and currently can be linked to a Contact. The current problem is that the CRM users ( e.g. Sales or Service agents) have to look at two separate screens e.g. 1) External Users and 2) Contact records to see all the related activities for a Contact (depending on which system was used to create the interaction/activity).&lt;/p&gt;
&lt;p&gt;&lt;span class="TextRun SCXW110851170 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;In this release, we are bringing this&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;ne&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;w&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;enhancement&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;to&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ensure that all&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the related&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;activities whether initiated from the SSC by an External User or within the CRM by&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;s&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;are&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;shown&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in a single, c&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;onsolidated&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;view for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;Contact in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;CRM.&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;I.e. All related records of External Users are now also shown as related to the Contact when an External User is related to that C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW110851170 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Display SugarIdentity warning when user is trying to edit IDM fields&lt;/h3&gt;
&lt;p&gt;In this release, we are introducing a warning message when user is trying to edit a field that&amp;rsquo;s owned by Sugar IDM in the&amp;nbsp;User&amp;rsquo;s List View, User&amp;rsquo;s Preview, Dashboards and dashlets.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Enable Sales Stage and Expected close date editable for Sales Console&lt;/h3&gt;
&lt;p&gt;In this release,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Sales Stage&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Expected Close Date&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;were added as&amp;nbsp;editable in console multiline list views and they&amp;nbsp;will behave the same as list views.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Add Users List View to Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In our previous release, we moved Users from BWC to Sidecar but we missed this functionality, now in this release we have fixed it, so you can take advantage of adding Users List Views to your Dashboards&lt;/span&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Update Metric font size&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are&amp;nbsp;updating the font size for the metric total as follows:&lt;/p&gt;
&lt;ul class="ak-ul" data-indent-level="1"&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="171"&gt;Update preferred currency from&lt;strong data-renderer-mark="true"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;text-4xl&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&amp;rarr;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl (&lt;/strong&gt;&lt;code class="code css-1o5d2cw" data-renderer-mark="true"&gt;font-size: 1.875rem; /* 30px */ line-height: 2.25rem; /* 36px */&lt;/code&gt;&lt;strong data-renderer-mark="true"&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="292"&gt;Fix When preferred currency &amp;amp; system currency are turned on, use&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;for preferred currency as well. (today when preferred currency is on or off, they appear at different sizes)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Support for Amazon OpenSearch&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are concluding our efforts to support Amazon OpenSearch which could potentially be used by any admin on their instances.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;User Interface&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins have a new option to configure Full-text search options and use OpenSearch as their FTS engine&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;They can set&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;password&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Elastic search is still the engine and there&amp;#39;s no need to update to OpenSearch, it will be handled by Sugar when there&amp;#39;s handshake with the server&lt;/li&gt;
&lt;li&gt;&lt;span&gt;UI is not available for SugarCloud instances&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Configuration&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins can override config.php to add those configs (see Sugar&amp;nbsp;Config Settings)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Admins can use Environment Variables as a security protection for&amp;nbsp;&lt;span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;/span&gt;&amp;nbsp;&lt;span&gt;&lt;code&gt;password&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Note, the environment variables must be set before Apache server restarted.&lt;/li&gt;
&lt;li&gt;These are the env variables&lt;/li&gt;
&lt;li&gt;&amp;#39;es_username&amp;#39; ==&amp;gt; &amp;#39;username&amp;#39;&lt;/li&gt;
&lt;li&gt;&amp;lsquo;es_password&amp;#39; ==&amp;gt; &amp;#39;password&amp;rsquo;&lt;/li&gt;
&lt;li&gt;&amp;#39;es_transport&amp;#39; ==&amp;gt; &amp;#39;transport&amp;#39;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Cookie Consent -&amp;nbsp;Remove &amp;quot;Accept Cookies&amp;quot; step from new user wizard&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are removing our cookie acceptance policy to ensure that we are only requiring users to accept required cookies and nothing else. At present, our cookie accept screen is a required field &amp;ndash; without accepting cookies, the application will not work. As this is not a meaningful choice for the user, Sugar is removing&amp;nbsp;the option and any required checks for this setting. Those fields are being hidden in Studio. Sugar&amp;nbsp;&lt;/span&gt;Portal is&amp;nbsp;also removing the cookie consent same as Sugar app.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable unlink option for records created by External Users&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are disabling the unlink option for records that are created by External Users but shown in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After creating a record as an external user, the unlink option is not available in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Sugar Core Security Updates&lt;/h3&gt;
&lt;p&gt;As part of our ongoing efforts to keep Sugar clean, fast, reliable, and most importantly secure, we have updated&amp;nbsp;Sugar Core code in different areas of the application such as Package Scanner, Module Installer, UI rendering, Handlebar templates, File Uploads and Imports.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Sugar Core PHP 8.2 compatibility&lt;/h3&gt;
&lt;p&gt;We are constantly monitoring issues in the code for PHP 8.2 compatibility and have hardened multiple core code In this release,&amp;nbsp;Most of those fixes are defensive coding following the steps described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/w/dev-tutorials/896/php-7-4-warnings-to-php8-2-errors"&gt;this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Sugar Q2 2024, Sugar 14&lt;/div&gt;
</description></item><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide/revision/3</link><pubDate>Tue, 26 Mar 2024 13:44:47 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Rafael Fernandes</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Revision 3 posted to Dev Tutorials by Rafael Fernandes on 3/26/2024 1:44:47 PM&lt;br /&gt;
&lt;div class="content"&gt;
&lt;p&gt;The purpose of this document is to provide insight to Sugar Developers for upgrading custom Sugar code, extensions, and integrations to the Sugar 14.0 (Q2 2024) release. This guide focuses on changes in Sugar&lt;span&gt;14.0 (Q&lt;/span&gt;&lt;span&gt;2&lt;/span&gt; 2024) that could cause an immediate impact on Sugar customizations and integrations built for earlier Sugar versions.&lt;/p&gt;
&lt;p&gt;Please check out the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/m/event-recaps/2740"&gt;Q2 2024 Developer Webinar recording&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for more developer highlights.&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;For Admin and End User release notes, please visit the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://support.sugarcrm.com/SmartLinks/Release_Notes/14.0.0_Release_Notes/"&gt;Sugar 14.0.0 Release Notes&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;h2 id="mcetoc_1ff80k9i32"&gt;User Experience Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1h8k0rdqt0"&gt;Predict Dashlets on Focus Drawers and Preview&lt;/h3&gt;
&lt;p&gt;In this release, we&amp;#39;ve added the capability for users to&amp;nbsp;view the Opportunity Close Prediction Dashlet and the Lead Conversion Prediction Dashlet directly from their Focus Dashboards and Dashlet Previews, eliminating the need to navigate to an Opportunity or Leads Record View. This enhancement streamlines the user experience, making it easier for users to access and manage their Leads and Opportunities data. By providing better lead and opportunity insights right in their Focus Dashboards and Dashlet preview, we&amp;rsquo;re enabling users to make more informed decisions and improve their overall productivity.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Comment Log in Quotes and all Preview Layouts&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;we are adding&amp;nbsp;Comment Log to the Quotes Module Record View and Preview allows for more efficient management of Quotes, as users can now easily access and update comments directly from their Record View and/or Preview Layout. Before 14.0, the Comment Log was only available for preview layouts in the Bugs module, in 14.0 we expanded the funcionalty to all preview layouts for modules where the Comment Log is available. We also added a scrollbar to the Comment Log making it easier for users to navigate through the comments without losing visibility of other relevant record information&lt;/span&gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Define Users Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;&lt;span class="TextRun SCXW208591049 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Admins can easily see at a glance the number of group users and drill into the drawer without having to navigate&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;away from the list view&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;This enhancement leverages the powerful functionality of&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Sugar&amp;#39;s&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;existing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;f&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ocus&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;d&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ashboards, providing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;users&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;with valuable information at their fingertips without having to drill into individual records or navigate away from other relevant information. This not only improves the efficiency of admins by reducing the time spent on navigation&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;,&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;but also enhances the overall user experience by providing quick access to important data.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW208591049 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;&lt;span class="TextRun SCXW159085114 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW159085114 BCX0" data-ccp-parastyle="heading 2"&gt;Role-based Report and Dashboard Templates&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release, w&lt;span class="TextRun SCXW30004081 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW30004081 BCX0"&gt;e introduce the role-based report and dashboard templates that will come with brand-new instance and will allow users to start working with data immediately, instead of spending time on setting up the reports and dashboards.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide role-based comprehensive templates, developed by our customer-facing departments (project webb). Users&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;Sales Reps or Sales Executives &amp;ndash; will have their dashboard and report available immediately. The reports and dashboards are read-only, but they can be duplicated and modified if needed.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide 6 role-based dashboard templates that can be accessed from left-hand home menu:&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;BDR Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Customer Success Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Executive Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Marketing Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Manager Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Rep Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;Also, we provide 166 report templates.&amp;nbsp;The templates are marked with the new filter visible in the list view. Stock reports were replaced by templates, the filters were replaced accordingly.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;New customer after his instance is set, access granted &amp;ndash; can start working. Sales Reps introduce the Opportunities and Leads to track &amp;ndash; next day can just open the dashboard where they have everything they need.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl10"&gt;&lt;code&gt;&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1givqvoho2"&gt;&lt;span&gt;&lt;span class="NormalTextRun SCXW249156672 BCX0"&gt;&lt;/span&gt;&lt;/span&gt;Sugar REST API updates&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;This Sugar release introduces REST&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;v11_24&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Admins to trigger a password reset in non-IDM mode&lt;/h3&gt;
&lt;p&gt;Allows an administrator of the Users module to trigger an email to be sent to a User requesting them to reset their password&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/password/adminRequest&lt;/pre&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Retrieve Related Activities API&lt;/h3&gt;
&lt;p&gt;The endpoint is used to load list of activities related to module/modules.&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/&amp;lt;module&amp;gt;/&amp;lt;record_id&amp;gt;/link/related_activities&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="mcetoc_1gj9pc6si0"&gt;Supported Platforms Update&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;In this release, we are updating Sugar&amp;rsquo;s Supported Platforms.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;We are dropping support for PHP 8.0 and adding support to PHP 8.3.&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;PHP&amp;nbsp;8.0 to PHP 8.1 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration81.php"&gt;https://www.php.net/manual/en/migration81.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration81.incompatible.php"&gt;https://www.php.net/manual/en/migration81.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.1&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.2 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration82.php"&gt;https://www.php.net/manual/en/migration82.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration82.incompatible.php"&gt;https://www.php.net/manual/en/migration82.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.2&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.3 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration83.php"&gt;https://www.php.net/manual/en/migration83.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration83.incompatible.php"&gt;https://www.php.net/manual/en/migration83.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There isn&amp;#39;t an upgrade path from 8.0 to 8.3, you must ensure it follows the upgrade path 7.4 -&amp;gt; 8.0 -&amp;gt; 8.1 -&amp;gt; 8.2 -&amp;gt; 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MySQL&amp;nbsp;5.4&amp;nbsp;and adding support for 8.1 and 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MSSQL&amp;nbsp;2017 and adding support for&amp;nbsp;2019 and 2022&lt;/li&gt;
&lt;li&gt;We are adding&amp;nbsp;support&amp;nbsp;for&amp;nbsp;Oracle&amp;nbsp;21c and 23c&lt;/li&gt;
&lt;li&gt;We are&amp;nbsp;dropping support for Windows Server 2019.&lt;/li&gt;
&lt;li&gt;We are adding support for&amp;nbsp;Amazon OpenSearch 5.6&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mcetoc_1ff80k9i33"&gt;Configurability&amp;nbsp;updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1f77psegv7"&gt;Sugar Config Settings&lt;/h3&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Setting Name&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Default&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Override Example&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.transport&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;https&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['transport'] = &amp;#39;https&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the protocol to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;full_text_engine.Elastic.username&lt;br /&gt;&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['username'] = &amp;#39;username&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;username to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.password&lt;br /&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config['full_text_engine']['Elastic']['password'] = &amp;#39;password&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;password to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;api.allowedClients&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;[]&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;span&gt;$sugar_config['api']['allowedClients'] =&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;#39;base&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;#39;chrome&amp;#39;, // allow only chrome browser&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;],&lt;br /&gt;&amp;nbsp; &amp;#39;mobile&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;#39;my_mobile_app_name&amp;#39;, // allow my_mobile_app_name custom app&lt;br /&gt;&amp;nbsp; &amp;nbsp; // ... add other custom apps ],&lt;br /&gt;&amp;nbsp; &amp;#39;portal&amp;#39; =&amp;gt; [], // allow anything&lt;br /&gt;];&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;Rules applied in the following order:&lt;br /&gt;- If the platform is not in the list - any client is allowed for it&lt;br /&gt;- If the platform is defined in the list, but the clients list is empty - any client is allowed&lt;br /&gt;- If the platform has one or more clients in the list - only they are allowed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcetoc_1f77psegvl"&gt;Platform Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable access to SugarCRM mobile application&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we&amp;#39;ve introduced a new configuration setting. This addition will empower you to define precisely which mobile clients are permitted to access your Sugar data/instance. It&amp;#39;s managed via a&amp;nbsp;sugar_config called&amp;nbsp;&lt;code&gt;$sugar_config['api'][&amp;#39;allowedClients&amp;#39;&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When you generate an SDK application you are asked to give that application a name. This new config, provides you the the ability to specify which app names can connect to a Sugar instance. For an existing application, in the app.json configuration file, you can see the name in the &amp;ldquo;appName&amp;rdquo; parameter. As an example, if you generated an app with an appName set to &amp;ldquo;my_app_name&amp;rdquo;, you would need to make a corresponding configuration change in Sugar.&lt;br /&gt;For example, to ensure that only the&amp;nbsp;your app_name client, created through the mobile SDK, is allowed, you&amp;#39;ll need to incorporate the following line into your Sugar Sell configuration:&amp;nbsp;&lt;code&gt;$sugar_config['api']['allowedClients'] = [&amp;#39;mobile&amp;#39; =&amp;gt; ['my_app_name']];&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Updates to&amp;nbsp;Forecast Commitment&lt;/h3&gt;
&lt;p&gt;Prior to this release, the Commitment value in the Commitment tab be calculated based on the Opportunities in the forecast before an initial manual commitment. When the user changes the value and clicks &amp;ldquo;Commit&amp;rdquo; the Commitment value is no longer calculated and only changes when the user manually changes.&amp;nbsp;This has caused some confusion amongst Forecast module users because they expect the system to continue to update the Commitment value after their manual changes. To avoid confusion, in this release, Sugar will initiate that value at 0 (zero) so users know they haven&amp;rsquo;t committed anything and the value will only change when they manually change it.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Default Value was removed from Calls and Meetings in the Studio UI&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are removing Default&lt;span&gt;&amp;nbsp;Value from Calls and Meetings in the Studio UI.&amp;nbsp;This option has been removed as it creates a false impression that admins can set reminders. Currently, Sugar uses what is in&amp;nbsp;the User Profile Settings.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On Upgrade, instances will no longer see that and it will not be avilable for new installs.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW113039343 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW113039343 BCX0" data-ccp-parastyle="heading 2"&gt;Additional List View Filters&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="TextRun SCXW80679206 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW80679206 BCX0" data-ccp-parastyle="heading 2"&gt;The addition of three new list view filters in version 14.0 significantly enhances the user experience by making it easier for users to filter and find information quickly. With the &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; operator now available for Textarea fields and the &amp;quot;&lt;code&gt;After today&lt;/code&gt;&amp;quot; and &amp;quot;&lt;code&gt;Before today&lt;/code&gt;&amp;quot; options for Date and Datetime fields, users can easily filter records without having to enter exact dates or build complex operators. &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; also works for custom fields now.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW165847498 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW165847498 BCX0" data-ccp-parastyle="heading 2"&gt;Improved CRM/Self-Service Center integration&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW165847498 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;Currently Self-Service Center(SSC) users are mapped as &amp;ldquo;External Users&amp;rdquo; in CRM. When a case or any other object is created by SSC user, it is linked to the &amp;ldquo;External Users&amp;rdquo; in the CRM. A SSC user can be a Prospect or a Lead or a Contact and currently can be linked to a Contact. The current problem is that the CRM users ( e.g. Sales or Service agents) have to look at two separate screens e.g. 1) External Users and 2) Contact records to see all the related activities for a Contact (depending on which system was used to create the interaction/activity).&lt;/p&gt;
&lt;p&gt;&lt;span class="TextRun SCXW110851170 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;In this release, we are bringing this&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;ne&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;w&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;enhancement&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;to&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ensure that all&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the related&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;activities whether initiated from the SSC by an External User or within the CRM by&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;s&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;are&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;shown&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in a single, c&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;onsolidated&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;view for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;Contact in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;CRM.&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;I.e. All related records of External Users are now also shown as related to the Contact when an External User is related to that C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW110851170 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Display SugarIdentity warning when user is trying to edit IDM fields&lt;/h3&gt;
&lt;p&gt;In this release, we are introducing a warning message when user is trying to edit a field that&amp;rsquo;s owned by Sugar IDM in the&amp;nbsp;User&amp;rsquo;s List View, User&amp;rsquo;s Preview, Dashboards and dashlets.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Enable Sales Stage and Expected close date editable for Sales Console&lt;/h3&gt;
&lt;p&gt;In this release,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Sales Stage&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Expected Close Date&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;were added as&amp;nbsp;editable in console multiline list views and they&amp;nbsp;will behave the same as list views.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Add Users List View to Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In our previous release, we moved Users from BWC to Sidecar but we missed this functionality, now in this release we have fixed it, so you can take advantage of adding Users List Views to your Dashboards&lt;/span&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Update Metric font size&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are&amp;nbsp;updating the font size for the metric total as follows:&lt;/p&gt;
&lt;ul class="ak-ul" data-indent-level="1"&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="171"&gt;Update preferred currency from&lt;strong data-renderer-mark="true"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;text-4xl&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&amp;rarr;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl (&lt;/strong&gt;&lt;code class="code css-1o5d2cw" data-renderer-mark="true"&gt;font-size: 1.875rem; /* 30px */ line-height: 2.25rem; /* 36px */&lt;/code&gt;&lt;strong data-renderer-mark="true"&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="292"&gt;Fix When preferred currency &amp;amp; system currency are turned on, use&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;for preferred currency as well. (today when preferred currency is on or off, they appear at different sizes)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Support for Amazon OpenSearch&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are concluding our efforts to support Amazon OpenSearch which could potentially be used by any admin on their instances.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;User Interface&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins have a new option to configure Full-text search options and use OpenSearch as their FTS engine&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;They can set&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;password&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Elastic search is still the engine and there&amp;#39;s no need to update to OpenSearch, it will be handled by Sugar when there&amp;#39;s handshake with the server&lt;/li&gt;
&lt;li&gt;&lt;span&gt;UI is not available for SugarCloud instances&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Configuration&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins can override config.php to add those configs (see Sugar&amp;nbsp;Config Settings)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Admins can use Environment Variables as a security protection for&amp;nbsp;&lt;span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;/span&gt;&amp;nbsp;&lt;span&gt;&lt;code&gt;password&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Note, the environment variables must be set before Apache server restarted.&lt;/li&gt;
&lt;li&gt;These are the env variables&lt;/li&gt;
&lt;li&gt;&amp;#39;es_username&amp;#39; ==&amp;gt; &amp;#39;username&amp;#39;&lt;/li&gt;
&lt;li&gt;&amp;lsquo;es_password&amp;#39; ==&amp;gt; &amp;#39;password&amp;rsquo;&lt;/li&gt;
&lt;li&gt;&amp;#39;es_transport&amp;#39; ==&amp;gt; &amp;#39;transport&amp;#39;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Cookie Consent -&amp;nbsp;Remove &amp;quot;Accept Cookies&amp;quot; step from new user wizard&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are removing our cookie acceptance policy to ensure that we are only requiring users to accept required cookies and nothing else. At present, our cookie accept screen is a required field &amp;ndash; without accepting cookies, the application will not work. As this is not a meaningful choice for the user, Sugar is removing&amp;nbsp;the option and any required checks for this setting. Those fields are being hidden in Studio. Sugar&amp;nbsp;&lt;/span&gt;Portal is&amp;nbsp;also removing the cookie consent same as Sugar app.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable unlink option for records created by External Users&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are disabling the unlink option for records that are created by External Users but shown in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After creating a record as an external user, the unlink option is not available in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Sugar Core Security Updates&lt;/h3&gt;
&lt;p&gt;As part of our ongoing efforts to keep Sugar clean, fast, reliable, and most importantly secure, we have updated&amp;nbsp;Sugar Core code in different areas of the application such as Package Scanner, Module Installer, UI rendering, Handlebar templates, File Uploads and Imports.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Sugar Core PHP 8.2 compatibility&lt;/h3&gt;
&lt;p&gt;We are constantly monitoring issues in the code for PHP 8.2 compatibility and have hardened multiple core code In this release,&amp;nbsp;Most of those fixes are defensive coding following the steps described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/w/dev-tutorials/896/php-7-4-warnings-to-php8-2-errors"&gt;this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Sugar Q2 2024, Sugar 14&lt;/div&gt;
</description></item><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide/revision/2</link><pubDate>Tue, 26 Mar 2024 13:44:12 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Rafael Fernandes</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Revision 2 posted to Dev Tutorials by Rafael Fernandes on 3/26/2024 1:44:12 PM&lt;br /&gt;
&lt;h1 class="name"&gt;Sugar 14.0 (Q2 2024) Customization Guide&lt;/h1&gt;
&lt;div class="content"&gt;
&lt;p&gt;The purpose of this document is to provide insight to Sugar Developers for upgrading custom Sugar code, extensions, and integrations to the Sugar 14.0 (Q2 2024) release. This guide focuses on changes in Sugar&lt;span&gt;14.0 (Q&lt;/span&gt;&lt;span&gt;2&lt;/span&gt; 2024) that could cause an immediate impact on Sugar customizations and integrations built for earlier Sugar versions.&lt;/p&gt;
&lt;p&gt;Please check out the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/m/event-recaps/2740"&gt;Q2 2024 Developer Webinar recording&lt;/a&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;for more developer highlights.&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;For Admin and End User release notes, please visit the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://support.sugarcrm.com/SmartLinks/Release_Notes/14.0.0_Release_Notes/"&gt;Sugar 14.0.0 Release Notes&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
&lt;div class="content"&gt;
&lt;h2 id="mcetoc_1ff80k9i32"&gt;User Experience Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1h8k0rdqt0"&gt;Predict Dashlets on Focus Drawers and Preview&lt;/h3&gt;
&lt;p&gt;In this release, we&amp;#39;ve added the capability for users to&amp;nbsp;view the Opportunity Close Prediction Dashlet and the Lead Conversion Prediction Dashlet directly from their Focus Dashboards and Dashlet Previews, eliminating the need to navigate to an Opportunity or Leads Record View. This enhancement streamlines the user experience, making it easier for users to access and manage their Leads and Opportunities data. By providing better lead and opportunity insights right in their Focus Dashboards and Dashlet preview, we&amp;rsquo;re enabling users to make more informed decisions and improve their overall productivity.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Comment Log in Quotes and all Preview Layouts&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;we are adding&amp;nbsp;Comment Log to the Quotes Module Record View and Preview allows for more efficient management of Quotes, as users can now easily access and update comments directly from their Record View and/or Preview Layout. Before 14.0, the Comment Log was only available for preview layouts in the Bugs module, in 14.0 we expanded the funcionalty to all preview layouts for modules where the Comment Log is available. We also added a scrollbar to the Comment Log making it easier for users to navigate through the comments without losing visibility of other relevant record information&lt;/span&gt;&lt;/span&gt;&lt;span&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;Define Users Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release,&amp;nbsp;&lt;span class="TextRun SCXW208591049 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Admins can easily see at a glance the number of group users and drill into the drawer without having to navigate&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;away from the list view&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;This enhancement leverages the powerful functionality of&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;Sugar&amp;#39;s&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;existing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;f&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ocus&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;d&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;ashboards, providing&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;users&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;with valuable information at their fingertips without having to drill into individual records or navigate away from other relevant information. This not only improves the efficiency of admins by reducing the time spent on navigation&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;,&lt;/span&gt;&lt;span class="NormalTextRun SCXW208591049 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;but also enhances the overall user experience by providing quick access to important data.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW208591049 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls0"&gt;&lt;span class="TextRun SCXW159085114 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW159085114 BCX0" data-ccp-parastyle="heading 2"&gt;Role-based Report and Dashboard Templates&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;span class="TextRun SCXW111707714 BCX0" lang="EN" data-contrast="auto"&gt;In this release, w&lt;span class="TextRun SCXW30004081 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW30004081 BCX0"&gt;e introduce the role-based report and dashboard templates that will come with brand-new instance and will allow users to start working with data immediately, instead of spending time on setting up the reports and dashboards.&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide role-based comprehensive templates, developed by our customer-facing departments (project webb). Users&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;Sales Reps or Sales Executives &amp;ndash; will have their dashboard and report available immediately. The reports and dashboards are read-only, but they can be duplicated and modified if needed.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;We provide 6 role-based dashboard templates that can be accessed from left-hand home menu:&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;BDR Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Customer Success Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Executive Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Marketing Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Manager Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span data-contrast="auto"&gt;Sales Rep Dashboard&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;Also, we provide 166 report templates.&amp;nbsp;The templates are marked with the new filter visible in the list view. Stock reports were replaced by templates, the filters were replaced accordingly.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span data-contrast="none"&gt;&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span data-contrast="none"&gt;New customer after his instance is set, access granted &amp;ndash; can start working. Sales Reps introduce the Opportunities and Leads to track &amp;ndash; next day can just open the dashboard where they have everything they need.&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl10"&gt;&lt;code&gt;&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id="mcetoc_1givqvoho2"&gt;&lt;span&gt;&lt;span class="NormalTextRun SCXW249156672 BCX0"&gt;&lt;/span&gt;&lt;/span&gt;Sugar REST API updates&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;This Sugar release introduces REST&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;v11_24&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Admins to trigger a password reset in non-IDM mode&lt;/h3&gt;
&lt;p&gt;Allows an administrator of the Users module to trigger an email to be sent to a User requesting them to reset their password&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/password/adminRequest&lt;/pre&gt;
&lt;h3 id="mcetoc_1gjpkca900"&gt;Retrieve Related Activities API&lt;/h3&gt;
&lt;p&gt;The endpoint is used to load list of activities related to module/modules.&lt;/p&gt;
&lt;div class="content-scrollable-wrapper"&gt;
&lt;pre&gt;POST &amp;lt;sugar instance&amp;gt;/rest/v11_24/&amp;lt;module&amp;gt;/&amp;lt;record_id&amp;gt;/link/related_activities&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="mcetoc_1gj9pc6si0"&gt;Supported Platforms Update&lt;/h2&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;In this release, we are updating Sugar&amp;rsquo;s Supported Platforms.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;We are dropping support for PHP 8.0 and adding support to PHP 8.3.&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;PHP&amp;nbsp;8.0 to PHP 8.1 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration81.php"&gt;https://www.php.net/manual/en/migration81.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration81.incompatible.php"&gt;https://www.php.net/manual/en/migration81.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.1&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.2 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration82.php"&gt;https://www.php.net/manual/en/migration82.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration82.incompatible.php"&gt;https://www.php.net/manual/en/migration82.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;PHP&amp;nbsp;8.2&lt;span&gt;&amp;nbsp;&lt;/span&gt;to PHP 8.3 have breaking changes and incompatibilities
&lt;ul&gt;
&lt;li&gt;Here is PHP&amp;rsquo;s official migration guide (&lt;a href="https://www.php.net/manual/en/migration83.php"&gt;https://www.php.net/manual/en/migration83.php&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Backwards incompatibilities guide (&lt;a href="https://www.php.net/manual/en/migration83.incompatible.php"&gt;https://www.php.net/manual/en/migration83.incompatible.php&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;There isn&amp;#39;t an upgrade path from 8.0 to 8.3, you must ensure it follows the upgrade path 7.4 -&amp;gt; 8.0 -&amp;gt; 8.1 -&amp;gt; 8.2 -&amp;gt; 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MySQL&amp;nbsp;5.4&amp;nbsp;and adding support for 8.1 and 8.3&lt;/li&gt;
&lt;li&gt;We are dropping&amp;nbsp;support&amp;nbsp;for&amp;nbsp;MSSQL&amp;nbsp;2017 and adding support for&amp;nbsp;2019 and 2022&lt;/li&gt;
&lt;li&gt;We are adding&amp;nbsp;support&amp;nbsp;for&amp;nbsp;Oracle&amp;nbsp;21c and 23c&lt;/li&gt;
&lt;li&gt;We are&amp;nbsp;dropping support for Windows Server 2019.&lt;/li&gt;
&lt;li&gt;We are adding support for&amp;nbsp;Amazon OpenSearch 5.6&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mcetoc_1ff80k9i33"&gt;Configurability&amp;nbsp;updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1f77psegv7"&gt;Sugar Config Settings&lt;/h3&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Setting Name&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Default&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Override Example&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.transport&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;https&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['transport'] = &amp;#39;https&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the protocol to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;full_text_engine.Elastic.username&lt;br /&gt;&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config[&amp;#39;&lt;/span&gt;&lt;span&gt;full_text_engine&amp;#39;][&amp;#39;&lt;/span&gt;&lt;span&gt;Elastic&amp;#39;]['username'] = &amp;#39;username&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;username to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;full_text_engine.Elastic.password&lt;br /&gt;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;span&gt;$sugar_config['full_text_engine']['Elastic']['password'] = &amp;#39;password&amp;#39;&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;Specify the&amp;nbsp;password to communicate with Full-Text Engine&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;span&gt;api.allowedClients&lt;/span&gt;&lt;/td&gt;
&lt;td&gt;[]&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;&lt;span&gt;$sugar_config['api']['allowedClients'] =&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;[&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;#39;base&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;#39;chrome&amp;#39;, // allow only chrome browser&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;],&lt;br /&gt;&amp;nbsp; &amp;#39;mobile&amp;#39; =&amp;gt; [&lt;br /&gt;&amp;nbsp; &amp;nbsp; &amp;#39;my_mobile_app_name&amp;#39;, // allow my_mobile_app_name custom app&lt;br /&gt;&amp;nbsp; &amp;nbsp; // ... add other custom apps ],&lt;br /&gt;&amp;nbsp; &amp;#39;portal&amp;#39; =&amp;gt; [], // allow anything&lt;br /&gt;];&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;Rules applied in the following order:&lt;br /&gt;- If the platform is not in the list - any client is allowed for it&lt;br /&gt;- If the platform is defined in the list, but the clients list is empty - any client is allowed&lt;br /&gt;- If the platform has one or more clients in the list - only they are allowed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="mcetoc_1f77psegvl"&gt;Platform Updates&lt;/h2&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable access to SugarCRM mobile application&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we&amp;#39;ve introduced a new configuration setting. This addition will empower you to define precisely which mobile clients are permitted to access your Sugar data/instance. It&amp;#39;s managed via a&amp;nbsp;sugar_config called&amp;nbsp;&lt;code&gt;$sugar_config['api'][&amp;#39;allowedClients&amp;#39;&lt;/code&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When you generate an SDK application you are asked to give that application a name. This new config, provides you the the ability to specify which app names can connect to a Sugar instance. For an existing application, in the app.json configuration file, you can see the name in the &amp;ldquo;appName&amp;rdquo; parameter. As an example, if you generated an app with an appName set to &amp;ldquo;my_app_name&amp;rdquo;, you would need to make a corresponding configuration change in Sugar.&lt;br /&gt;For example, to ensure that only the&amp;nbsp;your app_name client, created through the mobile SDK, is allowed, you&amp;#39;ll need to incorporate the following line into your Sugar Sell configuration:&amp;nbsp;&lt;code&gt;$sugar_config['api']['allowedClients'] = [&amp;#39;mobile&amp;#39; =&amp;gt; ['my_app_name']];&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Updates to&amp;nbsp;Forecast Commitment&lt;/h3&gt;
&lt;p&gt;Prior to this release, the Commitment value in the Commitment tab be calculated based on the Opportunities in the forecast before an initial manual commitment. When the user changes the value and clicks &amp;ldquo;Commit&amp;rdquo; the Commitment value is no longer calculated and only changes when the user manually changes.&amp;nbsp;This has caused some confusion amongst Forecast module users because they expect the system to continue to update the Commitment value after their manual changes. To avoid confusion, in this release, Sugar will initiate that value at 0 (zero) so users know they haven&amp;rsquo;t committed anything and the value will only change when they manually change it.&amp;nbsp;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Default Value was removed from Calls and Meetings in the Studio UI&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are removing Default&lt;span&gt;&amp;nbsp;Value from Calls and Meetings in the Studio UI.&amp;nbsp;This option has been removed as it creates a false impression that admins can set reminders. Currently, Sugar uses what is in&amp;nbsp;the User Profile Settings.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;On Upgrade, instances will no longer see that and it will not be avilable for new installs.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW113039343 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW113039343 BCX0" data-ccp-parastyle="heading 2"&gt;Additional List View Filters&lt;/span&gt;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;&lt;span class="TextRun SCXW80679206 BCX0" lang="EN" data-contrast="auto"&gt;&lt;span class="NormalTextRun SCXW80679206 BCX0" data-ccp-parastyle="heading 2"&gt;The addition of three new list view filters in version 14.0 significantly enhances the user experience by making it easier for users to filter and find information quickly. With the &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; operator now available for Textarea fields and the &amp;quot;&lt;code&gt;After today&lt;/code&gt;&amp;quot; and &amp;quot;&lt;code&gt;Before today&lt;/code&gt;&amp;quot; options for Date and Datetime fields, users can easily filter records without having to enter exact dates or build complex operators. &amp;quot;&lt;code&gt;Contains&lt;/code&gt;&amp;quot; also works for custom fields now.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls5"&gt;&lt;span class="TextRun SCXW165847498 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW165847498 BCX0" data-ccp-parastyle="heading 2"&gt;Improved CRM/Self-Service Center integration&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW165847498 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/h3&gt;
&lt;p&gt;Currently Self-Service Center(SSC) users are mapped as &amp;ldquo;External Users&amp;rdquo; in CRM. When a case or any other object is created by SSC user, it is linked to the &amp;ldquo;External Users&amp;rdquo; in the CRM. A SSC user can be a Prospect or a Lead or a Contact and currently can be linked to a Contact. The current problem is that the CRM users ( e.g. Sales or Service agents) have to look at two separate screens e.g. 1) External Users and 2) Contact records to see all the related activities for a Contact (depending on which system was used to create the interaction/activity).&lt;/p&gt;
&lt;p&gt;&lt;span class="TextRun SCXW110851170 BCX0" lang="EN" data-contrast="none"&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;In this release, we are bringing this&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;ne&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;w&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;enhancement&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&amp;nbsp;to&amp;nbsp;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ensure that all&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the related&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;activities whether initiated from the SSC by an External User or within the CRM by&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;s&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;are&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;shown&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in a single, c&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;onsolidated&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;view for&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;Contact in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;the&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;CRM.&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;I.e. All related records of External Users are now also shown as related to the Contact when an External User is related to that C&lt;/span&gt;&lt;span class="NormalTextRun SCXW110851170 BCX0" data-ccp-parastyle="Normal0"&gt;ontact.&lt;/span&gt;&lt;/span&gt;&lt;span class="EOP SCXW110851170 BCX0"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Display SugarIdentity warning when user is trying to edit IDM fields&lt;/h3&gt;
&lt;p&gt;In this release, we are introducing a warning message when user is trying to edit a field that&amp;rsquo;s owned by Sugar IDM in the&amp;nbsp;User&amp;rsquo;s List View, User&amp;rsquo;s Preview, Dashboards and dashlets.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Enable Sales Stage and Expected close date editable for Sales Console&lt;/h3&gt;
&lt;p&gt;In this release,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Sales Stage&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;Expected Close Date&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;were added as&amp;nbsp;editable in console multiline list views and they&amp;nbsp;will behave the same as list views.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Add Users List View to Dashboards&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In our previous release, we moved Users from BWC to Sidecar but we missed this functionality, now in this release we have fixed it, so you can take advantage of adding Users List Views to your Dashboards&lt;/span&gt;.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Update Metric font size&lt;/h3&gt;
&lt;p&gt;In this release,&amp;nbsp;we are&amp;nbsp;updating the font size for the metric total as follows:&lt;/p&gt;
&lt;ul class="ak-ul" data-indent-level="1"&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="171"&gt;Update preferred currency from&lt;strong data-renderer-mark="true"&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;text-4xl&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&amp;rarr;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl (&lt;/strong&gt;&lt;code class="code css-1o5d2cw" data-renderer-mark="true"&gt;font-size: 1.875rem; /* 30px */ line-height: 2.25rem; /* 36px */&lt;/code&gt;&lt;strong data-renderer-mark="true"&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-renderer-start-pos="292"&gt;Fix When preferred currency &amp;amp; system currency are turned on, use&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong data-renderer-mark="true"&gt;text-3xl&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;for preferred currency as well. (today when preferred currency is on or off, they appear at different sizes)&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Support for Amazon OpenSearch&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are concluding our efforts to support Amazon OpenSearch which could potentially be used by any admin on their instances.&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;User Interface&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins have a new option to configure Full-text search options and use OpenSearch as their FTS engine&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;They can set&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;password&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Elastic search is still the engine and there&amp;#39;s no need to update to OpenSearch, it will be handled by Sugar when there&amp;#39;s handshake with the server&lt;/li&gt;
&lt;li&gt;&lt;span&gt;UI is not available for SugarCloud instances&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Configuration&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;Admins can override config.php to add those configs (see Sugar&amp;nbsp;Config Settings)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Admins can use Environment Variables as a security protection for&amp;nbsp;&lt;span&gt;&lt;code&gt;username&lt;/code&gt;,&lt;/span&gt;&amp;nbsp;&lt;span&gt;&lt;code&gt;password&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;transport protocol&lt;/code&gt;&lt;/span&gt;
&lt;ul&gt;
&lt;li&gt;Note, the environment variables must be set before Apache server restarted.&lt;/li&gt;
&lt;li&gt;These are the env variables&lt;/li&gt;
&lt;li&gt;&amp;#39;es_username&amp;#39; ==&amp;gt; &amp;#39;username&amp;#39;&lt;/li&gt;
&lt;li&gt;&amp;lsquo;es_password&amp;#39; ==&amp;gt; &amp;#39;password&amp;rsquo;&lt;/li&gt;
&lt;li&gt;&amp;#39;es_transport&amp;#39; ==&amp;gt; &amp;#39;transport&amp;#39;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Cookie Consent -&amp;nbsp;Remove &amp;quot;Accept Cookies&amp;quot; step from new user wizard&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are removing our cookie acceptance policy to ensure that we are only requiring users to accept required cookies and nothing else. At present, our cookie accept screen is a required field &amp;ndash; without accepting cookies, the application will not work. As this is not a meaningful choice for the user, Sugar is removing&amp;nbsp;the option and any required checks for this setting. Those fields are being hidden in Studio. Sugar&amp;nbsp;&lt;/span&gt;Portal is&amp;nbsp;also removing the cookie consent same as Sugar app.&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Disable unlink option for records created by External Users&lt;/h3&gt;
&lt;p&gt;&lt;span&gt;In this release, we are disabling the unlink option for records that are created by External Users but shown in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After creating a record as an external user, the unlink option is not available in the Contact record.&lt;/span&gt;&lt;/p&gt;
&lt;h3 id="mcetoc_1gb30ctl1e"&gt;Sugar Core Security Updates&lt;/h3&gt;
&lt;p&gt;As part of our ongoing efforts to keep Sugar clean, fast, reliable, and most importantly secure, we have updated&amp;nbsp;Sugar Core code in different areas of the application such as Package Scanner, Module Installer, UI rendering, Handlebar templates, File Uploads and Imports.&lt;/p&gt;
&lt;h3 id="mcetoc_1hgt5tqls9"&gt;Sugar Core PHP 8.2 compatibility&lt;/h3&gt;
&lt;p&gt;We are constantly monitoring issues in the code for PHP 8.2 compatibility and have hardened multiple core code In this release,&amp;nbsp;Most of those fixes are defensive coding following the steps described in&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="/dev-club/w/dev-tutorials/896/php-7-4-warnings-to-php8-2-errors"&gt;this article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Sugar Q2 2024, Sugar 14&lt;/div&gt;
</description></item><item><title>Sugar 14.0 (Q2 2024) Customization Guide</title><link>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide/revision/1</link><pubDate>Mon, 25 Mar 2024 20:21:14 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:e3cd7037-ebd0-48a7-917e-8d2a817a1b68</guid><dc:creator>Rafael Fernandes</dc:creator><comments>https://sugarclub.sugarai.com/dev-club/w/dev-tutorials/939/sugar-14-0-q2-2024-customization-guide#comments</comments><description>Revision 1 posted to Dev Tutorials by Rafael Fernandes on 3/25/2024 8:21:14 PM&lt;br /&gt;
&lt;p&gt;Sugar 14.0 (Q2 2024) Customization Guide&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item></channel></rss>