5 Outstanding Ways To Use Element.cloud To Take Your Documentation To The Next Level

The Documentation Saga - Part II: Take Your Documentation To THE Next Level Using Elements.cloud

But first - here are the top 5 confessions submitted to elements.cloud about what was discovered in some Salesforce Orgs - most of which could have been avoided by better change management, business process mapping and documentation -

1. We’ve maxed out our 500 field limit on a Task. Let that sink in for a minute.
2. 5372 Apex Classes and 55 Managed Packages, but I am not sure which we can delete.
3. 15,000 reports. No comment.
4. Consolidating 2 small Orgs after an acquisition took 8 people 4 months.
5. We found people who are doing Trailhead modules inside our Production Org

Anonymously, of course.

So you went that extra mile - and now you have your business processes ready, your documentation connected and your Salesforce org changes linked. How do you use this?

1. What has changed recently?  If you’re like many companies with multiple System Admins when you want to know what’s changed recently you just need to look to your Catalyst Dashboard to see how many new meta data artifacts have been created or updated recently

2. You are hitting custom field limits. To delete or not to delete, that is the question! Check the usage analysis and the %filled for your fields. Read through impact analysis for your fields and you will have your answer! Salesforce org analytics gives you a high level overview of your org and directs you towards pain points in the system.

3. A new requirement has come in - You don’t know what were the previous customizations and how they impact the new requirements - Do you build or modify? Find every customization related to your process in one spot. Reduce your investigation time to figure out next steps.

4. Too many user licenses are being used up? Run a users related report to figure out who is using your system and how often. Maybe 10 users never logged in - gasp! Elements.cloud also provides a bunch of other insightful reports - for example, Managed package impact analysis, Reports/ Templates last used and even Salesforce Org model comparison.

5. Use too many tools to track requirements, releases and to version all of it? We recommend- nay, urge you to track your requirements and user stories and all the to and fro chatter that happens while you agree upon changes - within Elements.cloud itself. The process diagrams can be versioned and associated with your Salesforce releases as well! It allows you a chance to link with JIRA requirements. It offers capturing pain points, key performance metrics, risks, opportunities for improvement, process controls, waste, bottlenecks, external integrations and more.

The best part is ANYONE can use this tool, Salesforce savvy or not.

Here’s an example of a process in action:

Lead to Sale

Here's how links to Documentation look like

To summarize, we have nailed our elements.cloud implementations to document our customer Orgs.

If you are thinking, “Let’s see, I have 700 fields and 280 are formula fields on one object”, write to us today!