You can use the Optimize / Clean-up tab in your Salesforce Org Model to identify and mark metadata that needs to be deleted, optimized, documented or investigated. It is a quick and easy tool to aid you in your clean-up efforts.
Article outline
Prerequisites
How to use the Optimize / Clean-up tab
Optimize workflow
Reporting on optimization actions
Optimize history
Auto-classification
You might be also interested in
Prerequisites
Registered and verified Elements account
Sync'd Salesforce Org with Elements
How to use the Optimize / Clean-up tab
The Optimize / Clean-up tab is present in the right panel for all synced Salesforce metadata in your Org model. It is available under the broom icon.
Users with edit rights on the org model can change the status, choose the assignee, and leave a comment on why they chose a particular action.
TIP Assignees will not receive a notification upon being selected for particular metadata.
Optimize workflow
You can choose any Optimize / Clean-up status at any point. There is no fixed workflow restricting you. However, in order to make sense of the provided statuses, we recommend you follow the approach outlined below:
The Optimize / Clean-up tab is meant to help you manage your org clean-up quickly and effortlessly. However, to plan and document specific actions, we recommend you raise business requirements and user stories to document how the metadata should be optimized.
Reporting on optimization actions
You can spot metadata that was classified as needing some optimization in the org model by looking at the "Optimization" column.
For a more focused search, you should generate an "Optimize" report in the org model.
The report will bring back the list of all metadata in the org model with their optimization status (for most of them it will be "unassessed"), user comment, assignee, metadata type and other information. You can use filters to narrow down the list of results to metadata that are in a particular state.
Optimize history
All optimize actions (status changes, assignee changes, comments) are stored in the history stream, so you can quickly understand the previous actions on the metadata.
Auto-classification
Following metadata are automatically classified as "Optimize potential" after each sync:
Low impact fields
Page layouts without assigned profiles or with profiles without any active users
If you have suggestions on what metadata could be automatically classified as "Optimize potential", let us know!
You might be also interested in
Complete list of supported metadata types - this article will shed more light on what metadata type is supported in Org Model
See how certain field places in dependency - use this feature to visualize your metadata dependencies in a simple, yet powerful easy to view form