You have may have seen a recent video where a menacing figure was growling about Quotes customizations and a “Professor M.”
Who is Professor M? Well me technically. But let me share with you the story.
Here are a couple more UnCon promo videos from SugarCRM’s remarkable technical teams.
First off, we have a video Nick Rose, an experienced solutions architect, and also the Director of Solutions Consulting in the Americas. Come to UnCon and check out Nick’s session on the Understanding the Sugar Platform.
Stay tuned for more videos from the UnCon team!
Register for SugarCon today!
Are you learning about Sugar for the first time? Or maybe, it has been a while, and you want to see how the Sugar platform has evolved since the Community Edition days?
Hey there, Sugar Developers!
I’m SugarCRM’s newest Developer Advocate, and I wanted to take a moment to introduce myself. My name is Lauren Schaefer. Since getting my bachelor’s and master’s degrees in Computer Science at North Carolina State (go pack!), I’ve been slowly migrating north over the years, and I currently live in Pennsylvania.
Here is an important message from David Wheeler, a long time Software Engineer and Architect at SugarCRM, about using e-mail fields correctly.
E-mail handling is core to CRM software. Almost everyone we know uses multiple e-mail addresses every single day for both personal or work purposes. So it goes without saying that managing a person’s multiple e-mail addresses correctly is essential in your Sugar customizations and integrations.
Several years ago, Sugar changed from using email# named text fields (like email1, email2, etc.) to using an e-mail relationship. This was done to better handle multiple e-mails, multiple relationships, and e-mail attributes like opt in or invalid.
However, use of the email1 field remains particularly persistent. We observe many examples of custom code (and some core code) that still use the old email# fields. This is probably because it is convenient to use the email1 field like a regular text field.
But this is out of date, inaccurate, deprecated, and subject to removal in upcoming Sugar releases.
Below we will describe the proper method for using e-mail fields within Sugar customizations and integrations.
An Advanced Workflow process can only be triggered once per PHP process or HTTP request. This is intended to prevent Sugar Administrators from defining infinitely looping processes. (A real catastrophe!) But what does this mean for PHP customizations?
Assume that you have an Advanced Workflow process enabled for the Contacts module that performs an update on this Contact each time it is saved. If you have an Accounts after_save logic hook that performs an update on each related Contact SugarBean then the process will only run against the first related Contact. Any other related Contact that gets saved during your logic hook execution will not have a process run.
This affects not just logic hooks but any other class of PHP customization such as custom API endpoints or jobs.
If you really need to run that process more than once in the same request, here is a workaround:
use Sugarcrm\Sugarcrm\ProcessManager\Registry; ... Registry\Registry::getInstance()->drop('triggered_starts');
Calling this method will clear the internal Advanced Workflow registry that keeps track of the triggered process starts. After calling this method, the same process can then be triggered again inside the same PHP process or HTTP request.
Careful use of this method can make sure that PHP customizations play nicely with processes defined in Advanced Workflow.