...
Sugar 10.3 has increased the scrutiny of files passing through the package scanner. The file custom/include/SugarObjects/templates/person/vardefs.php did not have $module defined as it part of the compliation of the cache/modules/<Module>/<Module>Vardefs.php. We updated the file to pass with Sugar 10.3 package scanner.
Updated the custom phone field to work the changes
Resolved issue where the Messaging Template was incorrectly indicating that a field was locked
When working with a Messaging Template, you can now place the fields where the cursor is located. Previously, the field was always placed at the end of the message box.
Added the ability to have custom template parsing when using Sugar Messaging with modules other than, Contacts, Leads, Targets. Add a file custom/modules/PH_SMSMessages/include/customParser.php to add the functionality
Updated the Carrier Lookup for Ytel to return any errors directly from Ytel
Example Code
Code Block language php <?php class customParser { /** * Update the $bean->description with any additional parsing required * * @param PH_SMSMessages $bean * @throws SugarApiExceptionNotFound */ function parse(PH_SMSMessages &$bean) { if ($bean->parent_type === 'PC1_PC_Phone') { $pc1_pc_phone = BeanFactory::getBean($bean->parent_type, $bean->parent_id); if (!empty($pc1_pc_phone->id)) { if (isset($pc1_pc_phone->leads_pc1_pc_phone_1leads_ida)) { $bean->description = EmailTemplate::parse_template($bean->description, array('Leads' => $pc1_pc_phone->leads_pc1_pc_phone_1leads_ida)); } else { if (isset($pc1_pc_phone->contacts_pc1_pc_phone_1contacts_ida)) { $bean->description = EmailTemplate::parse_template($bean->description, array('Contacts' => $pc1_pc_phone->contacts_pc1_pc_phone_1contacts_ida)); } } } } } }
...