10.1 Retention Schedule Overview

Important:

If your retention schedule contains 10,000 or more series, categories, and folders, then your database administrator should build database indexes on the tables to enhance performance. For record folders, add indexes on the columns of the Folders table. For retention categories, add indexes on the columns of the Categories and Dispositions tables. For series, add indexes on the columns of the Series table. For further information about defining an index on a table column, see your database documentation.

A retention schedule is an organized hierarchy of series, categories, and record folders that can cluster content into similar groups, each with its own retention and disposition characteristics. Many retention schedules can be created for the requirements mandated by an organization.

If a record folder does not have its own security settings, the folder inherits security settings from its parent retention category. Each record folder can have its own security settings that further limit access to the items in that folder. Record folders can be further secured by using supplemental markings and custom security fields.

Record folders also inherit disposition rules from their retention category. By default, all record folders within a retention category inherit disposition instructions from the category. A disposition rule defined within a category can be applied to a specific record folder if the folder has a unique disposition instruction.

Record folders for temporary content are destroyed with temporary content as part of final disposition processing. Records administrators create new record folders as necessary to accommodate processing temporary items. Record folders for content subject to review and permanent content are not destroyed, and do not have to be re-created due to final disposition.

Note that if the RoleEntityACL component is enabled on the Content Server system, that component does not affect any retention objects such as categories or folders. Therefore, the ability to use ACLs on a URM role is not enabled on category creation pages or folder creation pages even if the RoleEntityACL component is enabled. The use of role ACLs is enabled on the checkin page if the component is enabled.

Important:

The retention schedule is not a contribution mechanism, but rather a disposition mechanism. It defines how and when content should be processed during its life cycle. It is not intended to check content into the repository.

10.1.1 Retention Schedules and MoReq2 File Plans

In previous versions of Oracle WebCenter Content: Records the term file plan was used to denote disposition schedules. It is now synonymous with retention schedule to designate functionality used to track and maintain retention objects.

With this release, the product can now be used to track items in conjunction with the MoReq2 specification. The MoReq2 file plan is accessible from the Browse Content tray. To enable MoReq2 file plans, set the RmaEnableFilePlan configuration variable to TRUE and restart Content Server.

A file plan has a strict folder hierarchy consisting of four node types: Class, File, Sub-File and Volume, with only Classes allowed at the top level of the hierarchy. Classes provide a framework for classification and files are used to store like records.

Files and Classes cannot be mixed at a single node in the hierarchy. For example, if a Sub-File is placed in a File folder, that File folder cannot contain any other type of item, including content. The exception is if a folder type contains content items, it can also contain volumes. Classes can contain other Classes, Files, or content. Sub-files can contain content items. Volumes can only contain content. The Records software has been configured to allow Create access only to those items that are allowed at the specific point in the hierarchy.

For more details about file plan nodes and the hierarchy, see the Model Requirements for the Management of Electronic Records.

Functionality for using the file plan is similar to that for the retention schedule. One major difference is that disposition actions are applied to Classes by linking the class to a category that has a disposition schedule.

As you review the information in this chapter, consider how the information can apply to your file plan as well as any retention schedule in place at your site.

10.1.2 Retention Schedules and Folders Retention Functionality

Folders Retention functionality is not available if DoD Baseline or DoD Classified is enabled.

The Folders Retention functionality is enabled when the FrameworkFolders component is enabled. Folders Retention allows you to group content items in a retention query folder then apply a retention action to the content in the folder. It does not apply the retention action to the folder itself.

If a content item has dispositions defined in both Content Server and in Oracle WebCenter Content: Records, only the disposition and schedule defined by the Records system is used.

Important:

Because the life cycle information is not viewable when using Retention Folders, it is recommended that you use this functionality for less important items that do not need to be retained or tracked, such as drafts of documents or temporary items. More important documents that need to be tracked and retained should be handled using the Records retention schedules.

Retention actions include the following:

Retention By Revision: used to specify how many revisions of an item to keep. For example, if a content item in the query folder has 8 revisions, when the retention rule is run, the first 3 revisions are deleted and the latest 5 revisions are retained. Note that if the Records system is installed, an item will not be deleted if it is frozen.

Retention By Age: used to specify how long an item exists before it is deleted. If the Records system is installed, the options for periods are the periods specified in the Records configuration. If the Records system is not installed, all default periods except for fiscal periods are included.

Retention By Category (only available if the Records system is installed and enabled): used to specify a category disposition to apply to a query folder. This is similar to specifying a category ID on a content item.

When specifying this option, you can also specify if the action requires approval. Approval is performed in the same manner as approvals in the Records system.

The following list summarizes the actions available with Retention Folders:

If Oracle WebCenter Content: Records is not installed and enabled:

Retention By Category is not available for use

Retention By Revision AND Retention By Age can be combined

If Oracle WebCenter Content: Records is installed and enabled:

Retention By Category is available for use

Note that delete dispositions in Folders Retention are treated differently than deletions in the Records system. The shortest delete interval is used in Folders Retention instead of the longest interval as is used in Oracle WebCenter Content: Records.

Folders Retention differs from using a Records retention schedule in that the life cycle of content that is managed by Folders Retention is not visible to the user. When content is managed via the Records system, the life cycle of the disposition schedule is displayed by browsing for the folder then clicking Information then Life Cycle from the folder's Actions menu.

This feature uses scheduled jobs to run the retention rules. The following intervals can be specified:

Weeks/Days: the job runs daily between the specified start and end time. It runs any Retention by Age rules that specify an age in days or weeks or any category dispositions that are defined as days or weeks.

Calendar Months: the job runs monthly on the specified start day, and the specified start and end time. It runs any Retention By Age rules with an age specified in months (Calendar Months, Calendar Quarters, and so on). It also runs any category dispositions that are defined as months.

Calendar Years: the job runs yearly on the specified month and day, and the specified start and end time. It runs any Retention By Age rules that specify an age in years and runs any category dispositions that are defined as years.

Fiscal Months: the job is only created if Oracle WebCenter Content: Records is installed. This functions similarly as Calendar Months.

Fiscal Years: the job is only created if Oracle WebCenter Content: Records is installed. It functions similarly as Calendar Years.

Retention Revisions: the job is run periodically, determined by the interval specified. The default is one month. Specify the intervals of days, weeks, months, and years. This job runs all Retention By Revisions rules.

Folders Retention functionality can only be set up and managed by users with Content Server administrative privileges. A user with Records Administrator privileges cannot set up Folders Retention functionality unless that user also has Content Server administrative privileges.

For details about accessing and setting up the Folders Retention functionality, see the Oracle WebCenter Content Application Administrator's Guide for Content Server.

10.1.3 Planning a Retention Schedule

Do not base a category on a dynamic feature such as organization hierarchy because organizations are reorganized on a frequent basis. Use static divisions for category departments, and be more generic with categories. Record folders can be more specific.

10.1.3.1Retention Schedule Hierarchy

A typical hierarchy of a retention schedule consists of series, categories, and/or record folders. Series are optional top-level nodes that can be nested. A retention category cannot be nested, due to the nature of its disposition schedules. Record folders can be nested. The following figure shows the basic hierarchy of retention schedule objects.

Content is filed directly into a retention category, and optionally can be filed into a record folder under a retention category. The retention schedule is the top-most series root node. The top node is created automatically.

The remaining retention schedule objects (series, folder, or retention category) are created by the Records Administrator. Users or administrators create content for filing within the application. A series is an optional container created by the Records Administrator. A retention category is required, and it contains disposition instructions for processing content. A record folder is optional, and it also organizes content according to some commonality.

The figure below shows the main characteristics of each retention schedule object at a glance. Series do not have security set directly on the series object, whereas retention categories, record folders, and content all have a variety of security options, including Access Control Lists (ACLs), supplemental markings, custom security fields, and (custom) classifications.

While it is possible to file content into multiple locations in the retention schedule, this is not recommended due to the complexity of processing multiple disposition schedules. For best performance results, content should be filed into a single folder or category. When multiple disposition schedules are attached to an item, the item is processed by the disposition with the longest retention period.

10.1.3.2Attribute Inheritance

Some of the attributes of retention schedule objects are inherited from parent objects. In certain cases, the attributes can be overridden at a lower level.

10.1.3.3Review Status Attributes

Review status, which includes the review period and reviewer, can be set at the retention category level, folder level and the item level. The lowest level (the item level) takes precedence if all information is of equal duration and is set at the category, folder, and item levels.

In the case of review periods with differing lengths between a parent and child objects, the shortest review period takes precedence for a child folder and is indicated in the relevant content information pages. The longer review period is ignored. If the shorter review period is removed or changed, the longer review period is used again in cycling reviews for content.

Important:

Within a parent and child object hierarchy, the review period with the shortest review period takes precedence for a child folder over a longer review period set on the child folder.

For example, a subject-to-review category has a review period of two calendar quarters. A child folder within the subject-to-review category has a review period set as four calendar quarters. Because the category higher in the hierarchy (the parent) has a shorter review period, the child folder ignores its own longer review period setting. In essence, the folder has a review period override in effect.

If the review status is not set at the record folder level for a record folder in a subject-to-review category, the folder always inherits review status from the category. At the content level, a content can inherit review information from the category, and the content can inherit information from the folder if it does not have its own review settings.

If a content item is filed directly into a subject-to-review retention category, it inherits settings from the category. If a subject-to-review item is filed into a subject-to-review record folder, it inherits settings from the immediate parent folder. Because record folders can be nested, the immediate folder parent determines review attributes for the item.

If a retention category is subject to review, and none of the folders or content items have their own review settings, then the folders and the items all inherit review attributes from the category.

You can create a non-review retention category containing record folders, content, and items subject to review. The reverse is not possible. You cannot create a retention category that is subject to review containing non-subject-to-review record folders and items due to inheritance of the subject to review attributes.

10.1.3.4Permanent Status Attributes

Permanent items cannot be destroyed by a disposition instruction. Permanent items typically are a small percentage of an organization's information base. Permanent status is determined by the National Archives and Records Administration (NARA) as having sufficient historical value to warrant continued preservation beyond the normal time needed for administrative, legal, or fiscal purposes. Permanent items are sometimes referred to as archival items.

10.1.3.5Disposition Instructions

Disposition instructions are defined at the retention category level, with some rules being applied uniquely to a child record folder. A record folder inherits disposition rules from the retention category. Content items inherit dispositions from their retention category, and if applicable, a folder with its own uniquely applied disposition rule. For more information, see Chapter 14, "Defining Disposition Instructions".

10.1.3.6Frozen Folder and Content Status

Freezing a record folder inhibits disposition processing for the folder and its child folders and content.

Record folders and content items inherit the freeze status if it is present on an ancestor. In addition to inheriting the freeze status, freezes can be performed at lower levels within a hierarchy where inheritance is not present. A child record folder or an item within a record folder can be frozen.

Freezing a content item outside of a folder also inhibits disposition processing and prevents the metadata was being updated.

10.1.4Creating and Navigating Object Levels

To use any retention objects, choose Browse Content from the Main menu. Depending on a user's rights and role, the user can browse all Retention Schedules or just the ones created by that user.

A user must be at a certain context, or level, within the retention schedule to work with retention schedule objects. Depending on the location within the hierarchy, different menu options appear in the main Actions menu when browsing the retention schedule.

The table below shows what retention schedule objects can be created at each level.

At this level:

You can create:

Series or root node

Series

Retention category

Retention category

Record folder

Content item

Record folder

Record folder

Content item

10.1.4.1 Retention Schedule Menus

The main root node is considered the retention schedule series node. At the series level, a series or retention category can be created.

Menus are relative to the location in the hierarchy. For example, at the Folder level you can create a folder or content. You cannot create a category.

The following list describes the possible menu options that may appear depending on the location in the hierarchy. These options may appear on an individual item's Actions menu or on the Page menu.

Information in parenthesis indicates the area of the hierarchy where the information appears.

Undo Obsolete (Table menu only): Marks items and the folder as not obsolete. Note that to undo the obsolete status for content items, you must search for the items, select the checkboxes for those items to be marked, then select Clear Dates then Obsolete from the Set Dates menu.

Add to Favorites: Used to add the marked object to the Favorites list.

10.2Using a Series

A series is an optional feature for organizing content. If an organization has a multitude of retention categories, setting up series can assist with managing the view of the retention schedule hierarchies. Series should be a static and non-specific method of organization: for example, Buildings not 7500 Building. This allows the hierarchy to remain static over time. Series can be nested within each other.

Series are also useful for creating work-in-progress retention schedules because series can be hidden from users, which prevents people from filing any data into the hidden series.

10.2.1 Managing a Series

Permissions:

The appropriate rights are required to work with series. There are separate rights for reading (viewing), creating, deleting, moving, editing, and hiding/unhiding series. The predefined Records User and Records Officer roles can only read (view) series. The predefined Records Administrator role can perform any of the other series-related tasks.

10.2.1.3Hiding and Unhiding a Series

A hidden series and its children are not visible to anyone without the Series.Hide/Unhide right. This feature provides a staging area for setting up and testing retention schedules. After a retention schedule is ready for production, unhide the series.

Permissions:

The Series.Hide/Unhide right is required to perform these actions. This right is assigned by default to the Records Administrator role.

Access the retention schedule. Choose Edit then Hide Series from the Actions menu for the series to hide.

You are prompted to enter a reason for the action. Enter a reason and click OK to confirm or leave the text box empty. Click Cancel to abort the entire action.

If confirmed, the series icon is now semi-transparent to indicate it is hidden.

Follow the same procedure to unhide the series. Access the retention schedule then choose Unhide Series in the item's Actions menu. If the action is confirmed, the series icon is no longer semi-transparent to indicate it is not hidden.

10.2.1.4Moving a Series

All child series, categories, record folders and content items move with the parent series.

Permissions:

The Series.Move right is required to perform this action. This right is assigned by default to the Records Administrator role.

Access the retention schedule. Choose Edit then Move Series from the Actions menu for the item to move. To move multiple items, select the checkbox for the series and choose Move from the Table menu.

Click to expand the tree, and click the series that will contain the item. The location field populates with the new location.

Click OK. The Exploring Series Page shows the series in its new location.

10.2.1.5Deleting a Series

Permissions:

The Series.Delete right is required to perform this action. This right is assigned by default to the Records Administrator role.

If a series is populated a message appears when an attempt is made to delete the series, prompting the user to delete the contents as well as the series. Be sure to move any content, record folders, categories, and any nested series from the series to be deleted if any of those objects should be retained.

Tip:

To delete multiple items, select the checkbox for the items and choose Delete from the Table menu.

Access the retention schedule. Choose Delete then Delete Series from the Actions menu for the item to delete.

You are prompted to confirm the deletion. Click OK to delete the series, or Cancel to cancel the delete action. To delete any child objects, select the checkbox for Include child content items on the prompt that appears. Click Yes when done.

You are prompted to enter a reason for the action. Enter a reason and click OK to confirm or leave the text box empty and click OK. Click Cancel to abort the entire action.

If confirmed, the series is deleted from the retention schedule.

10.3Retention Categories

A retention category is a retention schedule object with associated security settings and disposition instructions defined. Retention categories cannot be nested within other retention categories because they are disposition instructions, not an organization container. They are a method of grouping content with the same disposition requirements.

The appropriate management rights are required to work with retention categories. There are separate rights for reading (viewing), creating, deleting, moving, and editing categories. The predefined Records User and Records Officer roles can only read (view) categories. The predefined Records Administrator role can perform any of the other category-related tasks.

Note that when retention categories are sorted and listed, they are listed on a per-source basis. For example, if three sources are used (Source1, Source2, Source3), all items from Source1 are sorted as a separate group, items from Source2 are sorted as a separate group, and items from Source3 are sorted as a separate group. Then items from each source are displayed in a round-robin style with the first item of Source1, the first item from Source2, and the first item from Source3, followed by the second item of each source.

10.3.1.1Creating or Editing a Retention Category

A retention category can contain record folders or content. You can create retention categories at the root node level, or within a series.

Permissions:

The Category.Create right is required to perform this action. This right is assigned by default to the Records Administrator role.

(Optional) Accept the default security group or select a group from the Security Group list. The Default Content Server security checkbox must be selected on the Configure Retention Settings Page.

(Optional) If Accounts are enabled, choose the associated account for the category.

(Optional) If your organization uses the default security on categories, select an author of the retention category from the Author list. The author defaults to the user currently logged in and entering the information.

Enter a unique identifier for the category.

Enter a name for the category.

Enter a description with a maximum of 1000 characters.

(Required for U.S. Government Agencies) Enter the code of the authority for the disposition in the Disposition Authority box. Private sector organizations can enter the person or department responsible for the category, or enter none.

To restrict revisions of items in the category, select Restrict Revisions.

To restrict deletions of items in the category, select Restrict Deletes.

To restrict edits of items in the category, select Restrict Edits.

If the retention category is to contain content for review, and all objects should inherit the subject to review status, do the following:

Select Subject to Review.

To specify a reviewer for the retention category rather than allow the reviewer to revert to the notify recipient system default, select a reviewer from the Reviewer list. When selecting a reviewer, make certain that user has the rights required to perform the review. Otherwise an error message is displayed and the user cannot perform the review.

Enter an integer value for the number of review periods.

Select the defined period from the Review Period list.

(Optional) If your organization uses Access Control Lists (ACLs), then assign group permissions to the category:

To assign group permissions, click Select near Group Permissions. The Select Alias page opens.

Select or type the alias, enable the Read, Write, Delete, and Admin permissions as appropriate for the alias, and click Add to List. Repeat this step for each alias for which to set permissions, and click OK. The alias and its permissions show in the Group Permissions text box of the Create Retention Category page.

(Optional) If your organization uses Access Control Lists (ACLs), then assign user permissions to the category:

Select or type the user, enable the Read, Write, Delete, and Admin permissions as appropriate for the user, and click Add to List. Repeat this step for each user for whom to set permissions, and click OK. The user and their permissions show in the User Permissions text box of the Create Retention Category page.

Click to expand the tree, and click the series to which to move the category. The location field populates with the new location.

Click OK. The Exploring Series Page and Browse Content area show the retention category in its new location.

10.3.1.6Deleting a Retention Category

Use this procedure to delete a retention category.

Permissions:

The Category.Delete right is required to perform this action. This right is assigned by default to the Records Administrator role. Delete permission (D) for the RecordsGroup security group is also required.

You are prompted to confirm the delete. Click OK to delete the category, or Cancel to cancel the delete. To delete any child objects, select the checkbox for Include child content items on the prompt that appears. Click Yes when done.

You are prompted to enter a reason for the action. Enter a reason and click OK to confirm or leave the text box empty, and click OK. Click Cancel to abort the entire action.

If confirmed, the retention category is deleted from the retention schedule.

10.3.2 Retention Category Example

This example creates an archive disposition action for the retention category to be reviewed. This example retention category has a three month review period.

10.4 Record Folders

Retained items differ from other documents in the repository because they have different metadata are associated with a disposition life cycle. A record folder organizes similar items within a retention category. A retention category can have multiple record folders, and record folders can be nested within other record folders.

Record folders can inherit disposition rules from their parent record folder or category. Separate disposition instructions for individual folders can be set up as well. This is done when the dispositions are created for the category where the folder is stored. It is not done during the creation of the folder.

10.4.1About Record Folders

A record folder can inherit security settings from a category, or have its own security settings. Supplemental markings can also be set on a record folder and users to further secure the folder above and beyond all other security mechanisms. In addition to inheriting security settings and disposition rules, folders also inherit content review information from the parent category. If a folder is inheriting review information, it is indicated on the Record Folder Information page.

The review information taking precedence is at the lowest node (the shortest review period prevails), such as in the case of nested folders. Review information can be overridden at the folder level. For example, you can specify a different reviewer or review period cycle but you cannot specify a folder within a subject-to-review retention category as a folder that is not subject to review. If you do not want a record folder to be reviewed, you must create the folder in a non-subject-to-review category.

Permissions:

The appropriate management rights to work with record folders are required. Separate rights are required for reading (viewing), creating, deleting, opening/closing, editing, moving, and freezing/unfreezing folders. The predefined Records User role can only read (view) record folders. The predefined Records Officer role can read, create, edit, and move folders. The predefined Records Administrator role can perform all folder-related tasks.

It may be necessary at times to create a volume for a folder. When a volume is created, the content in that folder is moved to the newly created volume folder. The folder uses a naming convention of prefix+timestamp+suffix. Both prefix and suffix can be defined by setting configuration variables. For details, see the Oracle WebCenter Content Idoc Script Reference Guide. If neither is defined, a prefix of volume_ is used.

After the volume is created and the content placed inside, the folder is closed and cut off. Subsequent content items can be checked in to the parent folder and additional volumes can be created. The Cutoff and Create Volume disposition action do this.

Note that volumes are used in retention schedules as well as file plans (used for MoReq tracking).

(Optional) To change the filer (or author) of the record folder from the default, select the user in the Filer field.

Enter a unique identifier.

Enter a name for the record folder.

(Optional) Enter a description of the folder.

(Optional) If the record folder is going to contain subject-to-review items:

Select Subject to Review.

Select a reviewer for notifications to override the system default set in the Configure Retention Settings Page page. The reviewer selected must have the Folder.EditReview right. Without that right, the reviewer cannot mark a record folder as reviewed.

Enter the number and select type of period in the Review Period fields. If the category of a record folder is defined as subject to review, and a child record folder does not have its own review information defined, then the record folder inherits the review information from its category or its parent record folder. For further details, see Section 10.1.3.2, "Attribute Inheritance."

External information: If the item is external to the Records system, add its location, container, and applicable dates. For example, if an item has to do with a legal contract, the activation date represents the contract start date. The date format depends on user locale and preferences set in system properties. This field can also be used to treat a record folder and its content as a single piece of content from a disposition standpoint.

You can also enter a deactivation date corresponding to a content item but external to the Records system. For example, if an item has to do with a legal contract, the expiration date represents the date the contract expires. This date differs from the expiration date for documents in the repository because the content can still be accessed in the Records system after deactivation. Content expired in Oracle WebCenter Content cannot be accessed after expiration.

Delete Approval Date: A date after which the folder can be deleted.

(Optional) To assign supplemental markings to the folder, select one or more markings from the Supplemental Markings list. Even if a user or group has permission to access a record folder, supplemental markings can still restrict record folder access. For more information, see Section 6.4.1, "Supplemental Markings Details."

Click Lifecycle Preview to view the disposition instructions associated with the category and thus the folder.

Click Create. The record folder is shown in the exploring retention category or record folder page.

10.4.2.2Creating a Volume Folder

Use this procedure to create a volume folder within a retention category, or as a child folder of another record folder.

Note:

You can only create volumes in a category or folder that contains only content. It cannot contain other retention items.

When a volume is created, all content in the folder is moved to a newly created volume folder. After the volume is created and content is moved, the folder is closed and cut off. Subsequent content items can be checked in to the parent folder, and additional volumes created for them.

Permissions:

The Folder.Create right is required to perform this action. This right is assigned by default to the Records Officer and Records Administrator roles.

This procedure also assumes security is configured and rights are assigned to users.

There are three methods to create a volume folder. This procedure describes two of those methods. See Creating a Volume Through Disposition for details about using dispositions to create volumes.

Open the retention category or record folder in which to create a volume folder.

Choose Create then Create Volume or Schedule Volume Creation from the Page menu of a folder or a file plan folder (MoReq) containing only content.

Create Volume creates the volume and inserts content immediately.

Schedule Volume Creation opens a popup window where the volume creation can be scheduled depending on options selected:

The volume will be created when a certain number of items is checked into the folder.

The schedule is checked when batch processes are executed and if matched, a volume is created and the content moved then.

10.4.2.2.1 Creating a Volume Through Disposition

When creating a disposition that has the Create Volume or the Cutoff and Create Volume action, slightly different actions occur.

If the Create Volume action is used, a volume is created. The content from the category or folder where the volume was created is then moved into the volume.

If the Cutoff and Create Volume action is used, the volume is created, and the content is moved and the volume is cut off from further processing.

10.4.2.3Editing a Record Folder

Occasions on which a record folder would be edited include updating:

A specific user access for ACL if alias/group permission is not used.

A reason for freezing a record folder.

Activation or expiration dates for internal content.

Elaborating on or editing a folder description.

he physical locations and containers for the physical counterpart of electronic items as they progress through their life cycle and are transferred to other locations.

Permissions:

To edit a record folder you authored, you must have the Folder.EditIfAuthor right. This right is assigned by default to the Records Officer role. To edit a record folder you did not author, you must have the Folder.Edit right. This right is assigned by default to the Records Administrator role.

Click to expand the tree, and drill down in the hierarchy until reaching the category or folder where the record folder will be moved. The location field populates with the new location.

Click OK. The Exploring Category or Exploring Folder Page and Browse Content area show the record folder in its new location.

10.4.2.6Deleting a Record Folder

If a record folder has its own disposition rule or rules defined for it, deleting the record folder deletes the disposition rule from the category. To prevent the rule from being deleted, remove the association to the specific record folder. This is discussed in more detail in the Oracle WebCenter Content Administrator's Guide for Records.

Permissions:

The Folder.Delete right is required to delete a record folder. This right is assigned by default to the Records Administrator role.

Open the retention category containing the record folder to delete.

Navigate to the record folder to delete.

Choose Delete then Delete Record Folder from the Item Actions menu.

You are prompted to confirm the deletion. Click OK to delete, or Cancel to cancel the deletion. To delete any child objects, select Include child content items on the prompt that appears. Click Yes when done.

You are prompted to enter a reason for the action. Enter a reason and click OK to confirm or leave the text box empty and click OK. Click Cancel to abort the entire action.

If confirmed, the record folder is deleted from the retention schedule.

Select a Reviewer to receive e-mail notifications when it is time to review the record folder.

Enter 3 Months as the Review Period.

Click Create. The record folder opens in the Exploring Retention Category page. Click the Info icon for the new record folder. The Record Folder Information Page displays Subject to Review: Yes and the corresponding Review Period. Any inherited review information from a parent record folder or from the retention category is also given.

10.4.3.2 Creating Record Folders Subject to Recurring Audit Triggers

This example demonstrates creating a record folder subject to the recurring audit trigger. For more information about the built-in recurring audit trigger, see Section 11.1, "Trigger Overview." The Audit Periods must already be defined in the Configuration Manager utility. For further information about configuring audit period lists, see the Oracle WebCenter Content System Administrator's Guide for Content Server.

To create an audited record folder, complete the following steps:

Open the retention category or record folder where the record folder will be created.

Click Create. The record folder displays in the Exploring page. Click the Info icon for the new record folder. The Record Folder Information Page displays Subject to Audit: Yes and the corresponding Audit Period.

Scripting on this page enhances content navigation, but does not change the content in any way.