Component level metadata can be added by placing additional attributes in your content type's opening cfcomponent element. Adding metadata can alter the default behaviour of the framework and help you leverage hidden services.
Flags content type as a system only component. That is the component represents soemthing that is not content. For example, a log, order record and so on.
Activates the "Friendly URL" service for this content type.
Specifies the default friendly url stem. For example, "news" for dmNews. If nothing is specified, the component uses displayname or component filename. Note tree based content (for example, HTML pages) does not use this alias by default.
Activates the Object Broker for this content type.
Determines the maximum number of objects to broker in Object Broker.
Enables the content type to be used within the FarCry site overview tree. For example, HTML (dmHTML) and Link (dmLink).
Activates audit logging for creation, update and deletes on this content type.
Nominates component as an abstract class. This will prohibit the type being deployed to the data persistence layer, and being invoked directly by the framework. For example, types and versions.
Instructs the framework to create lookup references in the refObjects table. Setting the value to false means that all references to the content type must include the specific typename.
Do not use this metadata. This is provided for backward compatibility only and will be removed in later revisions of the code base.
Specifies which webskin templates will be cached and for how long in Object Broker. You should be using View Decorators to define view caching.
Originally designed to differentiate between custom and core content types. Modern versions of FarCry dynamically make this distinction on application initialisation.
Indicates whether or not publishing rules that scan for eligible content types for publishing should consider the components data for scheduling. For example, FarCry CMS plugins "Hand Picked Rule".