The Force.com Workflow Search Tool makes it easy to find workflows where field names or values have been used in the criteria or the field updates. Currently there is no easy way to search for workflows like this which can make it difficult to carefully make changes to fields or field values. The only way I have been able to get this kind of information before is to include the workflows in my Force.com IDE project and then do a find in files search. The benefit of this tool is that the results are displayed in a hierarchical fashion and the matching pieces are highlighted for you.
- .NET 4.0
- User must belong to a profile with the “API Enabled” and “Modify All Data” permissions.
How It Works
- Logs in using the Partner WSDL
- Downloads all of the workflow rules from the org using the Meta Data API
- Loads the XML for the selected object and checks the different pieces of the workflow for the search text. It returns only the workflows that had a match somewhere.
Posted by Kyle Peterson on September 12, 2011
Update: This tool no longer works with Salesforce’s debug logs since they have switched to the new log format.
The Force.com Debug Log Parser (DLP) makes it easy to understand debug logs generated by the Force.com/Salesforce service. The debug logs contain a lot of useful information like what apex triggers fired, what workflow fired, what field updates were made, and what order everything happened in. Sifting through the logs manually is time consuming and does not make the event hierarchy very evident.
If someone is having an issue with a transaction in their Force.com environment, you can ask them for a debug log of the transaction and you could easily understand their setup better.
- See the different events that fired
- Validation Rules
- Easily understand the order of events and their hierarchy
- Quickly identify workflow rules that evaluated to true and the field updates that resulted from them
ForceDebugLogParser.zip (19.7 KB)
Posted by Kyle Peterson on June 4, 2009