8 Working with WebCenter Content

8.1.1 Global Profile Rules

The IpmRepository component sets up global profile rules to group system fields and ensure their display when an application profile is created. These profiles are created or updated each time Content Server is started.

The IpmRepository component creates the following rules:

Any global rule does not need to be referenced by a specific profile in order to be active.

8.1.2 Application Profile and Profile Rules

When an application is created, a profile and rules are created to handle the display of the application fields. The profile rules determine how the application fields are grouped and provide any default values for those fields. The following table describes the rules:

In the rule names above, <X> is replaced with an internal application identifier. Any rules that are not global rules need to be referenced by a profile to become active.

A profile is created for the application and is given IpmApp_<X> as the profile name, where <X> is an internal application identifier. The label for the rule is the application name.

8.1.3 Working With Folders

Imaging does not automatically assign application documents to a folder. However, by modifying an application profile and profile rules, you can automatically assign documents to a specific folder. To modify application rules to automatically assign documents to a specific folder, do the following:

1. Create a new contribution folder to hold the application content. Make a note of the folder's identifier, for example 932000007.

2. Add a new profile rule and make note of the name. For example, App_<X>_Folder.

3. Select the Folder (xCollectionID) field and set the type to Info Only.

4. Enable Use default value and set the default value to the folder identifier obtained above. This allows people checking content in using the Content Server check in form to see the assigned folder.

5. Enable Is derived field and set the default value to the folder identifier obtained above. This allows the value to be set upon check in from any source, including from Imaging upload.

   Setting the rule in this manner will not allow users to move content from one folder to another, including the trash folder. To allow the ability to delete documents and move files between folders, change the derived value to use custom script and add something similar to:

   <$if not (IDC_SERVICE like "COLLECTION_DELETE_LOT|COLLECTION_RESTORE_ITEM")$>
                                              <$dprDerivedValue="932000007"$>
   <$endif$>
   

6. Edit the application profile for the Imaging application you wish to modify and add the rule defined above to the Rules tab.

8.1.4 Working With Oracle Universal Records Manager

Imaging does not automatically assign documents to a retention category or life cycle. However, by modifying an application's profile and profile rules, you can automatically assign documents to a retention category or life cycle. The following steps are for assigning a retention category value. If you wish to assign a life cycle, substitute xLifeCycleID for xCategoryID.

1. Create a new retention category and make note of the retention category identifier. For example, you could use App <X> Category.

2. Add a new profile rule and make note of the name. For example, you could use App_X_Category_rule.

3. Select the Retention Category field (xCategoryID) and set the type to Info Only.

4. Enable Use default value and set the default value to the retention category identifier obtained above. For example, App X Category. This allows people using the Content Server check in form to see the assigned category.

5. Enable Is derived field and set the default value to the retention category identifier obtained above (App X Category). This allows the value to be set upon check in from any source, including from Imaging upload.

   Note:

   If the category to which you are mapping the documents is a category that is a records-only category, you will also need to add a field for xIsRecord and set its default and derived values to "1".

6. Edit the application profile for the Imaging application you wish to modify and add the rule defined above to the Rules tab.

8.1.5 Working With Information Rights Manager

Imaging does not automatically assign application documents to an IRM classification. However, by modifying an application profile and profile rules, you can automatically assign documents to an IRM classification.

1. Add a new profile rule and make note of the name. For example App_X_IRM).

2. Select the IRMProtection field (xIRMProtection) and set the Type to Info Only.

3. Enable Use default value and set the default value. This value must match an Oracle IRM context. This allows people using the Content Server check in form to see the assigned IRM classification.

4. Enable Is derived field and set the default value. This value must match an Oracle IRM context. This allows the value to be set upon check in from any source, including Imaging upload.

   Note:

   If IRM is not configured correctly, or the value does not match a valid context, you will be unable to check content into Content Server because it will fail IRM validation.

5. Edit the application profile for the Imaging application you wish to modify and add the rule defined above to the Rules tab.

8.1.6 Working With WebCenter Spaces

Imaging documents are not automatically accessible within WebCenter Spaces, but documents can be automatically assigned to Folders visible within WebCenter Spaces. Manual configuration and modification of an application profile and profile rules are required to ensure that Imaging documents will be accessible.

1. Configure Content Server and Imaging to use the same LDAP-based identity store that Oracle WebCenter has been configured to use.

   For information on configuring WebCenter and Content Server to use an LDAP identity store, see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.

2. Configure Content Server as the bridge between Imaging and WebCenter Document Service using an Imaging supported version of Java.

3. WebCenter Spaces' Document Service uses the Folders component, and Imaging must be configured to automatically specify Folders for checked in content. For more information regarding configuring Imaging with Folders, see the section Section 8.1.3, "Working With Folders."

For further information regarding WebCenter Spaces integration with Content Server, see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.

8.2.1 Content Server Document Properties

The following table identifies how Imaging document properties map to Content Server document properties.