The appConfig.xml file (installed by default at C:\Program Files\FileNet\Collaboration\WEB-INF\config) contains configuration parameters for behavior and presentation by software components. These parameters could be reused in a different web application with a different user interface paradigm.
See also Example of the appConfig.xml file.
The following are controlled within the appConfig.xml file:
Element | Description |
caching | Controls whether or not the file itself is cached. Changes to the default settings may impact performance. |
default-page | Identifies the jsp page to use for each of these instances. FileNet recommends that you do not change these settings. |
error page | |
signin page | |
start page | |
popup page | |
teamspace folder id or path | Specifies the folder used for teamspaces. FileNet recommends that you do not change this setting. |
teamspace folder class | FileNet recommends that you do not change this setting. |
label maximum length | Defines the length used for truncation if the caller of the truncation method does not pass in a length. Default is 50 characters. |
label truncation format | Defines how strings are truncated for display. By default, truncation replaces characters near the end of the string with an ellipsis, and retains the last few characters. The exact number of characters retained is specified separately for each column definition. For example, the format {0} ... {1} results in an 80/20 display (where the 80% of the displayable characters appear first, followed by an ellipsis, then followed by 20% of the displayed characters). Another possible format is {0}... which truncates the string at the end, displaying the beginning followed by the ellipsis. |
error handler | Specifies the classes that are used as popup warnings (as opposed to being shown on the error page) |
object types | Defines the containers and objects available in the application. |
access roles | Defines the labels used for each of the security roles available. The <symname> defined in the XML file for each role maps to the label defined here. The label is displayed to the user in the TCM application UI. If you add a custom role you must map the <symname> for the role to a label in this file. See Security and roles for more information. |
images | Defines the icons used in the UI for the application. |
column definitions | Defines the data displayed in the UI, the headings for each column in the UI, and how that data is sorted. See Column definitions for more information. |
magazine definitions | Provides a template used for magazine-type display of the different collaboration objects. Use this area to customize the way discussion postings and other objects display. See Magazine definitions for more information. |
module | Defines and controls the sub-modules (helper pages or pop-ups) available for the main modules in the TCM application. Refer to the Collaboration Developer's Guide for information on customizing modules. |
response set definitions | Defines the set of pre-configured poll responses. You can add new sets of responses to this list, remove a set, or modify one of the existing sets. See Response set definitions for more information. |
actionset definitions | Defines the actions that are available for the various objects under the possible conditions. See Action set definitions for more information. |
The TCM application uses columns to display data on many of the dialog screens. You can change the way the data appears by editing the column definitions.
The TCM application uses a "magazine" format to display some types of collaboration objects, such as comments and discussion objects.
When a user specifies the responses available for a poll, they can select a set of commonly used responses. The response set definitions control which sets are available. For an example of adding a new set of poll responses, see Example: Changing default poll responses.
In the TCM application, the actions available to the user at any given time depend on the type of object selected as well as the state of that particular object. For example, when a user selects a document, the actions available depend on whether the document is checked out or not. The action set defines the different states that an object can be in so that the appropriate actions can be made available based on the state of the object.
NOTE Be aware that some actions may have unexpected results when allowed for some objects. Consider carefully all of the possible scenarios when adding an action to an object type.
For more information on how the available actions are controlled within the TCM application, see the Collaboration Developer's Guide.