Litify Org Audit – Findings and Recommendations

Past few months we conducted several audits of Litify instances, used by our clients. Our audits and findings focused on organizations that have been using Litify for more than one year and have done some customizations.?

Here are some high-level findings they share and the recommendations ECHO Technology Solutions made:?

Issue #1:??

Every organization is maxing out on data storage.?

Recommendation: Implement a data archiving solution and the regular removal of obsolete data to optimize storage usage while preserving essential information.?

Issue #2:

The custom code developed post-implementation does not adhere to Salesforce's recommended coding standards. While the code functions correctly, it is not optimized for performance. Over time, this could lead to increased complexity in system administration and future custom development efforts.

Recommendations: Although the detailed recommendations are extensive and could warrant a separate post, here's a condensed overview of essential steps:

1. Implement the Separation of Concerns principle.
2. Enforce Salesforce's Basic Development best practices.
3. Employ meaningful naming conventions for classes, methods, and variables.
4. Eliminate System debug statements.
5. Move DML and SOQL operations out of loops.
6. Break down lengthy methods into smaller ones following SOLID principles.
7. Organize the entire codebase for better structure.
8. Utilize the Testing framework to enhance code coverage.
9. Consider integrating the Apex fflib mocking framework.
10. Address and rectify any issues with basic unit tests.

Issue #3:??

Components using outdated API version. The issue with components using outdated API versions will not break the existing functionality - but could lead to compatibility issues, security vulnerabilities, and reduced functionality in the future as ongoing support and updates for these APIs may become uncertain.?

Recommendations:??

Resolve this issue by updating components with outdated API version to the latest version of the API. It will ensure compatibility, security, and access to the latest features.?

Issue #4:??

The large number of low-impact fields. Low-impact fields are fields that are not being used by users or for automation. These fields are unnecessary clutter.??

Recommendations:??

Consider removing low-impact fields since they are neither used in automation nor are populated. This can improve system performance and will enable easier support and documentation.?

Issue #4:

Multiple flows with similar entry conditions on a single Salesforce object are confusing, and hard to keep track of and understand the logic behind them. Having too many individual processes flows will slow down the system.

Recommendations:

To simplify and possibly speed up the system, combine the flows into one with decision elements. This way, they’ll have a clearer view, making it easier to manage and troubleshoot as needed.

Issue #5:

Process builder and Workflow rules. Salesforce is phasing them out according to the following schedule:

Stage 1 - You cannot create any new Workflow Rules according to Salesforce Winter ’23 Oct 2022.

Stage 2 - You cannot create any new Process Builders according to Salesforce Spring ’23 Feb 2023

Stage 3 - The end of support for both Workflow Rules & Process Builder is estimated at 2025.

Stage 4 - In the Future Salesforce will completely stop both Workflow Rules & Process Builder automation.

Recommendations:

We advise initiating the transition to flows as soon as possible. This will increase the system's performance and enable easier maintenance and upgrades in the future.

Issue #6:

Salesforce files were first introduced in the Winter 16′ Release. A year later, Salesforce decided that Notes and Attachments would become obsolete. Files will be the sharing tool of the future.

Recommendations:

Salesforce Files allows users to “share and collaborate on files, store files privately, manage version updates, and follow files that are important.” Files are optimized for Lightning, and users can Preview Files directly from the Record.

Use the Magic Mover tool to move all Notes & Attachments to Files.

There is nothing critical in our findings. There is no need to hit the “panic button.” All recommendations we made are easy to implement in the course of regular system maintenance and should be performed regularly in the future. This will ensure higher levels of security, reliability, system performance, and usability, and will significantly lower the cost of system maintenance and support.