This chapter includes the following sections:
A large number of built-in disposition actions are included, such as Cutoff
, Destroy
, Transfer
, Move
, and Declassify
. Your environment might require disposition actions other than the predefined options. You can design disposition actions to reflect your organization's specific needs.
Note:
If custom dispositions were previously created using an older version of the Records system, those dispositions should be re-examined and updated to use the newest services and actions. The Action Service parameters have changed from previous versions of this software, and any changes to existing custom dispositions are not mapped automatically.
Custom disposition actions are based on Oracle WebCenter Content services, which can be called with specific parameters to define the behavior of the disposition actions. For example, you could create a disposition action to automatically retain the last three revisions of content items using the DELETE_ALL_BUT_LAST_N_REVISIONS_SERVICE
service with the NumberOfRevisions=3
parameter.
Note:
Custom disposition features are available only to users with the Rma.Admin.Customization
right. By default, this right is not assigned to any of the predefined roles. You must assign it to a role before this functionality is exposed.
The following tasks are for managing dispositions:
You can create or edit a custom disposition action for records through Content Server.
Note:
Creating custom disposition actions requires in-depth technical knowledge of Oracle WebCenter Content. Contact Consulting Services to define custom disposition actions.
Note:
The Rma.Admin.Customization
right is required to perform this task. This right is not assigned by default to any of the predefined roles, which means it must be assigned to a role for this functionality to be exposed.
To create a custom disposition action:
Choose Records then Configure from the top menu. Choose Disposition Actions then Custom.
On the Configure Dispositions page, click Add in the Custom Disposition Action section.
On the Create or Edit Disposition Action page, enter a unique ID for the custom disposition action in the Action ID text box.
Enter a name for the custom disposition action in the Action Name text box.
Enter a description for the custom disposition action in the Brief Description text box.
Enter a group name for the custom disposition action in the Group Name text box. The default value for this field is stored in the ww_strings.htm
file in the wwOptGroupLabelCustomDispositionActionsList
. It is set to Custom Actions
by default.
To use a different group name than Custom Actions, modify the string value in the resource file and restart Oracle WebCenter Content Server. Do not change the suggested default value in the Group Name field.
Choose the service to be used for the custom disposition action from the Action Service list.
(Optional) Specify one or more parameters for the selected action service.
(Optional) Select any of the checkboxes as required. The selections include Must Be First, Must Be Last, and Require Approval. These actions determine when the custom disposition action will be used.
Click Create.
A message is displayed saying the disposition action was created successfully, with the action information.
Click OK.
The following Action Service Parameters are required for the specific Action Service.
Disposition/Event | Service Parameters |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To edit a custom disposition action:
To view the information about a custom disposition action:
Note:
The Rma.Admin.Customization
right is required to perform this task. This right is not assigned by default to any of the predefined roles, which means you must assign it to a role before this functionality is exposed.
Note:
The Rma.Admin.Customization
right is required to perform this task. This right is not assigned by default to any of the predefined roles, which means you must assign it to a role before this functionality is exposed.
Custom disposition actions can be deleted only if they are no longer used in the disposition instructions for any category.
To delete a custom disposition action:
To delete multiple dispositions, select the checkbox for the dispositions to delete on the Configure Dispositions page, and choose Delete from the Table menu.
You can disable a custom disposition action through Content Server.
Note:
The Rma.Admin.Customization
right is required to perform this task. This right is not assigned by default to any of the predefined roles, which means you must assign it to a role before this functionality is exposed.
Note:
Some dispositions are required for processing of instructions to occur. Disabling a disposition could interfere with the processing of disposition instructions. Always verify ahead of time that it is acceptable to disable a disposition.
To disable a custom disposition action:
This example creates a custom disposition action that automatically retains the last three revisions of a content item.
Note:
The Rma.Admin.Customization
right is required to perform this task. This right is not assigned by default to any of the predefined roles, which means you must assign it to a role before this functionality is exposed.
Choose Records then Configure from the top menu. Choose Disposition Actions, then Custom.
On the Configure Dispositions page, in the Custom Disposition Action section, click Add.
Complete the metadata fields as follows on the Create or Edit Disposition Action page:
In the Action ID field, type RetainLast3Rev
.
In the Action Name field, type Retain Last 3 Revisions
.
In the Brief Description field, type Only keep the last 3 revisions of a content item
.
In the Group Name field, type Custom
.
From the Action Service list, choose the wwString
name of a disposition action; for example, Notify Author
.
In the Action Service Parameters field, type NumberOfRevisions=3
.
Click Create.
The newly created disposition action can now be selected from the list of available disposition actions when creating disposition rules.
Physical items can be assigned retention schedules, which define their life cycle. When creating a physical item you can assign a retention schedule to it. This links the physical item to a set of retention and disposition rules, which specify how long an item should be stored and when and how it should be disposed.
The same retention schedules and disposition rules may be used for physical items as for electronic items, but disposition rules used only for physical items can also be defined.