Skip to main content

Themes

Documentation is organized the way Salesforce is built: by object, process, integration. Your teams often think differently -- by product line, business unit, project or regulation. Themes let you apply your own grouping on top of the documentation.

A theme can gather items of any kind: an external system, a dozen business rules, two objects and a process. The Themes page then shows everything filed under it, across the whole documentation.

Creating and filing​

Themes are created and assigned from the documentation itself.

On a business rule

  1. Open an object page and go to its rules.
  2. Click Classify (Classify this rule) next to the rule.
  3. Pick one or more themes.

Use Manage themes to create, rename, reorder or delete the themes available for rules.

On a page (object, process, integration, Experience site)

  1. Open the page.
  2. Use File this page (File under a theme).
  3. Pick an existing theme, or type a name and click Create theme.

Themes are shared with your whole organization: a theme created by one person is available to everyone.

The Themes page​

Open Themes in the Documentation group of the rail.

  • Browse or search your themes (Search a theme…).
  • Select a theme to see everything filed under it, grouped by kind: processes, objects, business rules, fields, external systems, exposed APIs, Experience sites, components, interfaces, user stories and so on.
  • Open any item to go to its page.

An item marked not in this version was filed under the theme but does not exist in the version you are reading -- for example a rule removed from the org since. The filing is kept, so it reappears if the item comes back.

If you have not filed anything yet, the page is empty and points you to the documentation.

Where themes are used​

  • Rule registers: on an object's rules, Group rules by offers By client theme (your themes) next to By theme (the themes aprity identified in the documentation) and the other groupings.

Good to know​

  • Themes are your organization's own classification. They do not change the documentation content and are not sent to the analysis as corrections. To correct content, use feedback.
  • Filing survives new scans: items keep their theme from one version to the next as long as aprity recognizes them as the same item.