the definition of a “record” is now much blurrier than in previous versions of the
While the new flexibility is nice, sometimes there is a desire to make sure that an item
really can’t get changed when it gets to a certain point – like when the “Is Record” box
in 10g and earlier was explicitly checked. Without that declaration, an item could still
be edited or otherwise manipulated.
A use case for “locking” such an item usually occurs when a policy or a contract is
being created. The document goes through several iterations of revision, and finally,
the last revision should be declared a “record”.
In 11g, the “Is Record” isn’t exposed on a checkin or update page. However, you can
still get the same functional result with a bit of configuration.
- In config.cfg, enable the following setting (RmaEnableFixedClone=true), and restart the managed server
- Once the system is restarted, go to the retention category where the document resides.
- “Browse”the category and find the item to be declared a record
- Under the “Actions” menu, select “Content Actions --> Create Fixed Clone”.
- The following dialog appears.
- Complete the options in the dialog. You will have to select the correct category where the cloned item will reside. Browse to the correct category, and then select “OK”. You will be returned to the document info page for the original item.
- Go to the retention category where the cloned item was placed. The following entry should appear. Depending on the system configuration, an icon may appear as shown.
- Clicking the info icon, and viewing the document information page shows the item as non-editable, non-deletable, and non-revisable. (If the entire metadata set for the item was displayed, the value for xIsRecord is now set to “1”).
Note that this technique only works with electronic content. Items managed by Physical Content Management are not affected by cloning.