Global Custom Elements

Local Custom Elements

Use Global Custom Elements

• To manage and maintain Element data in a single source, for centralizing control and optimizing content reuse
• To enable authors to select from existing "records" or instances of data for an Element

Use Local Custom Elements

• To track changes to Elements (as for standard Elements and other version-controlled CommonSpot components)
• To capture specific structured data (field-value pairs) and render them out using your own Element Display Templates, without concern for multiple instances of the data

Authors either add a new data record or select from an existing data record to display Global Element on a page. Global Custom Elements:

• Are not logically bound to the pages containing them and are edited independently.
• Data is not version- or approval-controlled
• Data is entered using the Simple Form interface.
• Are not automatically included in full-text indexes. You must explicitly enable indexing for Global Elements in the Viewing PageSearch Properties dialog, and assign them to a search collection. CommonSpot indexes Global Custom Elements independently of pages.

Local Custom Elements behave much like standard CommonSpot Elements:

• Bound to the page, Local Custom Elements inherit security and approval rules defined for that page.
• Changes are versioned.
• Can only be edited from the page of origin. Content can be reused on other pages.
• Are automatically indexed as part of the page in which they are published.