🤯 What do I do now?
Example Use Cases for Customizations
While learning Sugar development it is helpful to have an idea of some use cases to help you move your learning along. The following use cases are some ideas that you can use to learn the framework. These use cases are the tip of the iceberg of what you can do with Sugar it is not a full list of customizations that are possible.
Thanks for reading Sugar Developers Guide! Subscribe for free to receive new posts and support my work.
Use Case 1
Bi-directional integration with another application. This could be an ERP, Inventory Tracking, Marketing, Support, internal application, Signature management, Package Shipping, etc. When data in one application changes, the data should be reflected in the other.
Example: When an Opportunity is Closed Won, we would like to ship via FedEx. We would like to create the shipment, print the shipping label and packing slip without leaving Sugar. Additionally, we would like Sugar to keep track of the tracking information and notify us due to any delays.
Use Case 2
When we are viewing a record (e.g., Account), we would like to view data from another application. We do not want the data to be present in Sugar, we want to view the data in real-time from the other application without having to leave Sugar.
Example: We would like to be able to see information about their Accounts Payable information from our Accounting Software.
User Case 3
When an Account record is saved, if any of the Address fields, or the phone numbers, or the name changes and the changes are not performed by the User with the user_name ‘apiuser’, update another application. Leverage the Web Logic Hooks functionality but narrow the data that is sent to the remote system to only the criteria specified.
Use Case 4
We would like to only allow certain users to be able to create Accounts. We would like the OOTB functionality to function for editing Accounts however we would like to limit who can create an Account.
Use Case 5
The OOTB Phone Fields allow users to enter anything into the field unfortunately, there are no limitations. They can enter numbers, characters, etc. We would like to limit the users to only being able to enter E.164 formatted phone numbers. The field should verify that the phone number is a valid formatted phone number for the region and country that has been entered.
Use Case 6
We would like to add a field year. The field should only display the current value and the next 7 years’ worth of years. This should be dynamic and the available 7 years should change each year.
Use Case 7
When the Assigned User of the Accounts module is changed, update all of the related records to be the same assigned user.
Use Case 8
In addition to the OOTB functionality for assignment notifications, enable the option to send an SMS, Slack, MSFT Teams, or other types of notifications.
Use Case 9
Add the ability to integrate Sugar data with Slack, or Teams maybe add a /sugar command to these platforms
Use Case 10
In order to improve our sales process, we would like to integrate a Power Dialer into the Leads and Contacts module. This would allow a user to filter the records in the List view and then easily dial them with a single click.
A power dialer is a piece of automated telephone technology that dials a phone number right after a call is completed. As soon as the user is finished with a call, the power dialer will call the next contact on the list.
Use Case 11
As a user when entering an address it would help if the address uses a type-ahead feature that will ensure that we enter an address correctly. There are many websites that have this functionality.
Use Case 12
It would be helpful if we could see a map of our customers and be able to generate a route to their location.