About Content Profiles Using Profiles to Customize Content Screens

Managing Metadata 3-13 ■ Selecting a Profile Trigger Field on page 3-36 ■ Disabling a Profile Trigger Field on page 3-37 ■ Creating and Defining a New Profile on page 3-37 ■ Editing an Existing Profile on page 3-37 ■ Deleting an Existing Profile on page 3-38 ■ Managing the Rules in a Profile on page 3-38 ■ Previewing a Profile on page 3-38 ■ Troubleshooting a Previewed Profile on page 3-39 ■ Department-Based Content Profile on page 3-41 ■ Black-Hole Check In Profile for Resumes on page 3-45 ■ Global Rule to Restrict Content Check-In Based on User Role on page 3-52 ■ Global Rule to Restrict Content Type Metadata Changes on page 3-54

3.2.1 About Content Profiles

Administrators can use Content Profiles to configure Check In, Update, Content Information, and Search pages, so end users see only directly relevant metadata fields, thereby rendering basic pages simpler to use. Content profiles do not create or modify any content server tables. They are simply used as a type of filter for what information will be displayed. All information for the Content Profile is stored on the file system in the IntradocDirdataprofilesdocument directory. This section covers the following topics: ■ Content Profile Elements on page 3-13 ■ Profile Links on page 3-14

3.2.1.1 Content Profile Elements

A profile is composed of rules and a trigger value, which are set up on the Profiles and Rules tabs of the Configuration Manager screen. Administrators can create multiple content profiles and all are available to the end user. For each profile, the end user has a distinct Check In page and Search page available. Although all profiles are visible to all users, each user can configure their user interface to hide or display links to specified profiles. See Profile Links on page 3-14. Content profiles consist of: ■ Rules ■ Triggers

3.2.1.1.1 Rules A rule consists of a set of metadata fields that determine whether fields

are editable, required, hidden, excluded, or read-only based on their criteria when specific conditions are met. You can change a rule’s behavior based on an input, or activation condition. A rule can be evaluated for every profile global, or it can be Note: Documents cannot be associated with more than one profile in the system. 3-14 Application Administrators Guide for Content Server evaluated for specific profiles. For ease of use, you can use rules to group metadata fields under an optional header. For example, a profile’s rules can determine the user type and, depending on the document type being checked in, ensure that only specific metadata fields are displayed. All other fields can be hidden.

3.2.1.1.2 Triggers A trigger field is a metadata field that is defined on the

Configuration Manager: Profiles Tab . If a document matches a trigger value for a profile, then that profile is evaluated for the document. There can be an unlimited number of profiles, but only one trigger value per profile.

3.2.1.2 Profile Links

When a profile is enabled on the Edit Content Profile Links page, the profile is available from the Search and New Check In menus on the toolbar. If no profiles are enabled for display, the Search and New Check In menus become direct links to the Advanced Search page and standard Content Check In Form, respectively. After a profile has been created, it appears in the Search and New Check In menus on the toolbar when you refresh your browser session. By default, all profiles are listed as options under both menus. However, not every user will be authorized to use all of the listed profiles. On the Edit Content Profile Links page, users can decide which profiles to display by selecting or clearing applicable check boxes. For example, a marketing employee may not have the necessary privileges to use an accounting profile. In this case, the user can clear the check boxes for the accounting profile and it does not display under Search and New Check In menus. For more information about the user interface in general and the content profile links in particular, see the Oracle Fusion Middleware Users Guide for Content Server.

3.2.2 Content Profile Rules