+ Start a Discussion

Organization Assessment - Tools/Apps

We are planning to do an org assessment.

Background: We have a huge org (especially Case objects - Lot of workflows, lot of triggers - optimizing code in triggers) we almost reached limits. (Millions of records in Case object; slowness & performance issues in retrieval/creation of cases)

Is there any tool/app exchange app which can audit the org and provide the results on fields, workflows, triggers, etc, where ever the org limit are reached or close to hiting the limits and also any design flaws/ recommend any performance improvement areas.

Can anyone please suggest:
1. Tools/ app exchange apps which can be useful for auditing the org
2. Tools which can suggest/recommend the improvement areas
Hi Hemanth, 

See the articles below, 



Also see an App Exchange package, 


Admin best practices guide, 


See a Partner's solution as well, 


Reply back if you looking for anything specific. 


Thanks for your reply Ashish...

I should have rephrased by question better.

In our org we are facing performace issues due to volume of triggers, workflows etc..so we are planning to do a Health check on the org and trying to optimize the trigger code.

We do already have installed the Field trip and it provides valuable information on the field usage.

1. Can you please suggest a tool to review the trigger code automatically
2. Also if we need to review the trigger code manually, what are the performace factors that we need to focus on.
e.g: Multiple triggers on the same object,recursive triggers, etc...
3. Is there any best practices document to write triggers.
Hi  , 

I personally have not used / reviewed any tool for this purpose, hence I cannot comment on that part. 

As Salesforce is Hosted on Cloud there is not much that we can do from the Client end to improve the Bandwidth or Performance. \

However we can track our usage and use some best practices to optimize the performance. 

Found some relevant  information - sharing below, 


Salesforce Labs Free App: 


Other Apps:






Related thread, 



Salesforce Articles:


Best Practice #5: Streamlining Multiple Triggers on the Same Object

It is important to avoid redundancies and inefficiencies when deploying multiple triggers on the same object. If developed independently, it is possible to have redundant queries that query the same dataset or possibly have redundant for statements.

Note that it is very important to detail exactly how governor limits are applied when multiple triggers are deployed on the same object. For starters, you do not have any explicit control over which trigger gets initiated first. Secondly, each trigger that is invoked does not get its own governor limits. Instead, all code that is processed, including the additional triggers, share those available resources.

So instead of only the one trigger getting a maximum of 100 queries, all triggers on that same object will share those 100 queries. That is why it is critical to ensure that the multiple triggers are efficient and no redundancies exist.





There should only be one trigger for each object.
Avoid complex logic in triggers. To simplify testing and resuse, triggers should delegate to Apex classes which contain the actual execution logic. See Mike Leach’s excellent trigger template for more info.
Bulkify any “helper” classes and/or methods.
Trigers should be “bulkified” and be able to process up to 200 records for each call.
Execute DML statements using collections instead of individual records per DML statement.
Use Collections in SOQL “WHERE” clauses to retrieve all records back in single query
Use a consistent naming convention including the object name (e.g., AccountTrigger)


Within an Apex Trigger context, the Force.com governor limits are currently too low to directly invoke many of the FinancialForce APIs successfully, especially when considering bulk record operations on custom objects. To avoid hitting governor limits, consider starting a background Batch Apex job from the trigger instead. However, be warned, as per the Apex Developer’s Guide, the platform limits the number of concurrent Batch Apex jobs queued per org to five. Once this is reached, the Database.executeBatch method will throw an exception and the records associated with the given trigger invocation will not be inserted. The advice from Salesforce is that the developer needs to take great care to consider this constraint if using Batch Apex from a trigger. The advice from FinancialForce.com is to avoid this approach, and instead consider using the new Spring '10 Scheduler or a button to invoke a Batch Apex job. Only consider using Batch Apex from a trigger if you are 100% confident you understand the implications. Specifically, that you have put in place adequate error handling and recovery, have volume tested, and ideally have control of the means by which your users manage records for the custom object associated with the trigger.