How has a U.S. non-profit organization increased their user satisfaction by upgrading Salesforce

Challenges

-Poor performance due to legacy fields and code.
-Slow transition time.

Solution

-Remove no longer used code and data models.
-Refactor the remaining code.
-Create code-free solutions for the objects where bulk processes fail.

Results

-Increased user satisfaction by increasing transaction speed.
-Improved response to change by using no-code logic builders.

Our client is the largest organization of scientists, psychologists, clinicians, educators, consultants, and students in the United States. Their Salesforce Implementation was 12 years old and had gathered a lot of technical debt over the years resulting in performance degradation.

They were seeking a technology partner to help them refactor the implementation and replace the code with the newer no-code options to upgrade their Salesforce performance.

We reviewed and analyzed their current business logic implementation on the Sales cloud and came up with recommendations on refactoring scope.

Key Industry

Healthcare education, Non-Profit member association

Key Pains

Poor performance and transition time due to old Salesforce implementation

Product Mix

Upgradation of Sales Cloud

The Challenges

  • Performance degradation of batch jobs and integration while creating and updating records.
  • Legacy fields and code in the system were no longer in use but affected the transaction time.
  • The implementation was done on old logic, which took time in case of the change request.

Technical Approach

  • Leveraging the client’s existing CI/CD approach divided the plan into small individual changes/stories.
  • The first iteration targeted removing legacy code and data models that were no longer in use.
  • In the second iteration, converted trigger code into record triggered flows.
  • In the third iteration, converted synchronous operations into asynchronous using platform events and listener flows.

The Solutions

  • Documented business processes where performance was low.
  • Identified the processes that were no longer in use and the ones still in use.
  • Followed the approach to remove the code pieces and data model no longer in use to refactor the code still in use.
  • Strategized converting code into no-code solutions.

The Benefits

After upgrading the implementation, the client benefited in several ways:
  • The system started performing better with each release, even on heavy tasks such as bulk tasks and integrations. Moreover, it finally started accepting bulk API requests.
  • All the unused code and data models were removed, which made transactions faster.
  • Converting synchronous transactions to asynchronous made the transactions much faster.
  • Change requests became easier and faster to accommodate in release cycles.

The Results

After implementing the solutions client got the benefits of accepting bulk API requests, and transactions became faster and easier to accommodate in release cycles.
  • Resolved the problem of performance degradation in the Salesforce sales cloud.
  • Achieved user satisfaction by increasing transaction performance.
  • Improved change request delivery using no code logic builders.