Access roles
Description | Default access roles control access to administrative functions
and to specific workflow-related tools. Default access roles are created
when the application is installed. Custom access roles determine which users can access specific features and commands within Workplace XT. |
---|---|
Deployment Mechanism | FileNet® Deployment Manager: |
Dependencies | The site preferences in which the access roles are configured Tip: FileNet Deployment Manager does
not recognize site preferences as associated objects of access roles
and, therefore, does not automatically include them in the export
files. You must specifically add the site preferences to the export
manifest.
|
Environment-specific data | The principals that are referenced by the Secured Role property Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission. |
Notes® | The access roles for a Workplace XT site
are stored in an Access Roles folder within the source object store
that is specified in the site preferences for the Workplace XT installation. When you import access roles, FileNet Deployment Manager might return a bad reference exception if access roles exist in the destination object store. If this exception occurs, the access roles are still imported. However, FileNet Deployment Manager places them in the Unfiled Documents folder. You must move them to the Access Roles folder. |
Description | Provides a wizard that steps a user through adding a document. An entry template, which is created by using the Entry Template Designer, can provide default values for the destination folder, properties, and security. The entry template might hide some pages in the add wizard, and the template can start a workflow when the new item is added. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies |
Tip: FileNet Deployment Manager does
not recognize the preceding objects as associated objects of document
entry templates and, therefore, does not automatically include them
in the export files. You must specifically add these objects to the
export manifest.
|
Environment-specific data |
Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission. |
Notes | To deploy a document entry template, you must locate the folder in which the template was filed when it was created. |
Description | Provides a wizard that steps a user through adding a folder.
An entry template, which is created by using the Entry Template Designer,
can provide default values for the destination folder, properties,
and security. The entry template might hide some pages in the add
wizard, and the template can start a workflow when the new item is
added. To deploy a folder entry template, you must locate the folder in which the template was filed when it was created. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies |
Tip: FileNet Deployment Manager does
not recognize the preceding objects as associated objects of folder
entry templates and, therefore, does not automatically include them
in the export files. You must specifically add these objects to the
export manifest.
|
Environment-specific data |
Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission. |
Notes | None |
Description | Used to organize objects that are related to each other in some way. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies | Links and, if used, their custom Link subclasses are automatically added to the export manifest as associated objects. There are 2 objects that a Link references (document, folder, or custom object type). The objects that are referenced by a Link do not themselves reference the Link, so you cannot automatically include the Link object when you export an object that the Link references. Therefore, you must explicitly export Link objects. See Common dependencies between objects. |
Environment-specific data | Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission. |
Notes | This feature must be enabled in the site preferences for the Workplace XT Site. If you are deploying this object, you must either deploy the site preferences from your source site to your destination or you must enable links on your destination. |
Description | Represents a file that is created in Search Designer that is run from either the Workplace XT Search or Browse page. Using the search template usually prompts the Workplace XT user to enter or change values and then displays a list of the documents that meet the search criteria. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies |
|
Environment-specific data | Object stores that are referenced by the Searching Object Stores
property Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission. |
Notes |
|
Description | Provides configuration settings that affect Workplace XT appearance, behavior, and connectivity. Administrators set site preferences that use the Site Preferences application. Non-administrative users can set personal preferences, which override some site preferences. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies | If any class or object dependencies exist, they must be manually added to the export manifest; otherwise they are not exported. For information about dependencies, see Common dependencies between objects. |
Environment-specific data | Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission. |
Notes | Site preferences files are saved in the /Preferences folder
of the object store. When you import site preferences, FileNet Deployment Manager might return a bad reference exception if site preferences exist in the destination object store. If this exception occurs, the site preferences are still imported. However, FileNet Deployment Manager places them in the Unfiled Documents folder. You must move them to the Preferences folder. Tip: FileNet Deployment Manager does
not recognize access roles as associated objects of site preferences
and, therefore, does not automatically include them in the export
files. You must specifically add the access roles to the export manifest.
Tip: Import a Preferences folder only if there is an existing
Preferences folder in the destination object store.
A number of Workplace XT sites can be pointed at a FileNet P8 environment. Therefore, after you import the site preferences, you must update the site preferences information in the bootstrap.properties file for the Workplace XT site. |
Description | Represents a file that is created in Search Designer that is run from the Workplace XT Browse page. Using the stored search displays a list of the documents that meet the search criteria. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies |
|
Environment-specific data | Object stores that are referenced by the Searching Object Stores
property Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission. |
Notes | Search templates can be filed anywhere. Be sure to note the location of the templates before you export them. |
Description | Represents the preference settings of an individual user. The user preferences override the equivalent site preferences. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies | The user account for which the user preferences are set. If any class or object dependencies exist, they must be manually added to the export manifest; otherwise they are not exported. For information about dependencies, see Common dependencies between objects. |
Environment-specific data | Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission. |
Notes | User preferences that are specific to Content Platform Engine are saved as files
in the /Preferences folder of the object store and can be exported,
converted, and imported by using the instructions in this table. By
contrast, user preferences from the Tasks section are stored in the
database. For information about how to export and import objects,
see User preferences. Before you use FileNet Deployment Manager to convert exported user preferences, ensure that the users for whom preferences are being exported are included in the security principals data map. For more information, see Create a security principal data map. Do not deploy Workplace XT user preferences objects if you are mapping more than one source security principal to a single destination security principal. User preferences embed the SID of the user to which they apply in their folder containment name. Because the Content Platform Engine server enforces unique containment names within a folder, an error results if more than one of those mapped principals contains a user preference in the deployment data set. Although the user preference objects are imported successfully, the referential containment relationships that file them in the Preferences folder cause an import error. As a result, only a single user preferences object is filed in the Preferences folder on the target environment; the remaining user preferences objects are unfiled. If you imported more than one user preference
that is mapped to the same security principal at the destination and
you want to change the preference document that is filed in the Preferences
folder, use the following procedure:
When you import user preferences, FileNet Deployment Manager might return a bad reference exception if user preferences exist in the destination object store. If this exception occurs, the user preferences are still imported. However, FileNet Deployment Manager places them in the Unfiled Documents folder. You must move them to the Preferences folder. Tip: Import a Preferences folder only if there
is an existing Preferences folder in the destination object store.
|
Description | Provides functionality that is required to support Microsoft Outlook application integration. This feature add-on adds several classes and properties to support Outlook message content, such as the message sender, recipients, and date/time information, in addition to creating and managing link associations between Outlook messages and related objects. |
---|---|
Deployment Mechanism | The classes and properties are created automatically in the object store when the email add-on is installed in the destination environment. |
Dependencies | Workplace XT Common Extensions |
Environment-specific data | Not applicable |
Notes | After you deploy the email add-on, you must configure email integration in the site preferences for the Workplace XT. |
Custom configuration files
Description | If the source installation of Workplace XT has custom modifications
that you would like to retain in the destination installation of Workplace XT, you must copy the updated
configuration files out of the following source directories and manually
add them into the destination:
Important: The term "deployed" Workplace XT directory refers to the
deployment of the Workplace XT application
and not the deployment of the entire FileNet P8 system.
|
---|---|
Deployment Mechanism | FileNet P8 does not have a tool that deploys Workplace XT custom configuration files. Therefore, you must manually add the custom configuration files into the destination environment. |
Dependencies | Workplace XT custom configuration files do not have any dependencies upon any other objects. |
Environment-specific data | Workplace XT custom configuration files do not have any dependencies upon any environment-specific data. |
Notes |
|