22 WebCenter Sites User Defined Properties
User defined properties are properties added by WebCenter Sites users (usually administrators or developers) to the WebCenter Sites wcs_properties.json
file.
The following topics provide information about user defined properties:
22.1 About WebCenter Sites User Defined Properties
WebCenter Sites user defined properties are properties that can be manually added to the WebCenter Sites wcs_properties.json
file to enable optional WebCenter Sites features.
Certain WebCenter Sites features require properties that are not available in the WebCenter Sites wcs_properties.json
file by default. In these cases, an administrator or developer must create the property in the wcs_properties.json
file, using the Property Management Tool in the WebCenter Sites Admin interface. For example, when you implement resultset caching, you can create up to three properties for any WebCenter Sites database table for which you want to set caching values.
For information about adding properties to the WebCenter Sites wcs_properties.json
file, see Adding Properties.
22.2 User Defined Properties for WebCenter Sites
The table below provides a description for each user defined property you can add to the WebCenter Sites wcs_properties.json
file.
Table 22-1 WebCenter Sites User Defined Properties
Property | Description |
---|---|
Used to specify whether approval locking is
If you wish to switch back from approval locking per target to default behavior (that is, global lock), remove the |
|
This property applies to the inCache framework. It is used to define the size of the For example, if the property is set to If you wish to use this property, add it to the WebCenter Sites Default value: |
|
Specifies the maximum number of child folders that WebCenter Sites can generate in parent folders under subdirectories of For example, if this property is set to If you wish to use this property, you must add it to WebCenter Sites If you also need to specify the maximum number of parent folders that WebCenter Sites can generate, use the Default value: |
|
Specifies the maximum number of parent folders that WebCenter Sites can generate in subdirectories of If you wish to use this property, you must add it to the WebCenter Sites Within the parent folders, WebCenter Sites generates child folders. If you wish to specify the maximum number of child folders that can be generated, use the Default value: |
|
Used to specify the number of days that data is stored in the Legal value: Integer > 0 Default value: Note: By default, this property is not present in the WebCenter Sites |
|
To add a key for a new table in the WebCenter Sites database, add this property to the WebCenter Sites wcs_properties.json file, where tablename is the name of the new table.
|
|
Default value: |
|
If the Oracle Real-Time Decisions (RTD) engine is integrated with WebCenter Sites, add this property to the WebCenter Sites Default Value:
where |
|
If the Oracle Real-Time Decisions (RTD) engine is integrated with WebCenter Sites, add this tag to the WebCenter Sites |
|
If the Oracle Real-Time Decisions (RTD) engine is integrated with WebCenter Sites, add this tag to the WebCenter Sites |
|
This property determines whether Engage visitors will be tracked through the database- or memory-centric method, which improves the performance of heavily trafficked sites featuring Engage assets. In memory-centric tracking, WebCenter Sites stores visitor scalar attribute values to the add-on repository, and visitor history attribute values to its own database. All computations to determine a visitor's segments are performed in memory; results are cached. By default, this property is not automatically included in the WebCenter Sites This property must be set on the delivery system in one of the following ways:
On content management systems, this property must be either set to false or omitted, given that visitor attributes are created and managed only on CM systems that are enabled for database-centric tracking. Management of visitor attributes is not supported on delivery systems; the attributes must be published to the delivery systems. |
|
This property is supported only on delivery systems. This property controls whether a WebCenter Sites delivery system queries the If you do not use Dimension assets (that is, for multilingual support), do the following to prevent your delivery system from unnecessarily querying the |