BasicJSONSelection list-rendering profile metadata keys | HCL Digital Experience

Some item attribute and list property declarations support metadata that can be associated by using corresponding metadata keys.

You can use them in combination with ItemAttribute, AssociatedItemAttribute, ConstructedItemAttribute, ComputedItemAttribute, and Listproperty declarations that are listed under List-rendering profile keys. The following list describes the supported metadata key values:

Use this metadata key to specify a static default value that you want to be returned if the appropriate value cannot be retrieved. Example:
To enforce a specific computation order for the non-lazy computed item attributes and list properties in the current profile, set this metadata on the ComputedItemAttribute and ComputedListProperty. Such a computation order can be required if specific computed attributes must access the value of other computed attributed values. In this case, the attribute that requires the value of another computed attributed must list the other attribute in the Depends metadata key. If the attribute depends on multiple other computed attributes, you can list multiple attribute names as a comma-separated list. Example: You defined computed attributes named link and proxiedLink. You want to make sure that the value for the link attribute is computed before the value for the proxiedLink attribute. In this case, specify as follows:{computed} 
Note: You do not have to flag dependencies on non-computed attributes. Non-computed attributes are always extracted from the JSON before the computed attributes are resolved.
Use this metadata to define the escaping that you want applied when you write the values of this attribute. Specify one of the values xml, json, javascript, or none. The default value is none.
Use this metadata in context of AssociatedItemAttribute declarations to define the cache scope for the associated JSON document. If this document can be shared among multiple users, you can set this metadata to the value true. If the associated document can contain different data for different users, cache it per user. In this case, you can leave this metadata undefined or explicitly set it to false.
Note: Associated documents are cached in the Associated documents that are cached in scope Shared are not automatically invalidated during user login.
Use this metadata on an ItemAttribute, AssociatedItemAttribute, ConstructedItemAttribute, or ComputedItemAttribute to specify one or multiple IDs of attribute value processor plug-ins that you want to run when the attribute value is retrieved. The ID specified must reference the unique ID of attribute value processor plug-ins that are deployed to your system. If you specify multiple IDs, separate them using a comma. Example:
For more information, read Creating and deploying custom attribute value processor plug-ins.