What is the Expected Behavior when Setting a Framework Folder to "Mark Read-Only"? (Doc ID 2076607.1)

Last updated on JULY 19, 2017

Applies to:

Oracle WebCenter Content - Version 11.1.1.9.0 and later
Information in this document applies to any platform.

Goal

When a user tried to check out/Check out in any items in locked folder (mark read only), the
following error was observed.

Content Server Request Failed
Error Content item 'Content_000402' was not successfully checked in.
Folder 'TESTFOLDER' is read-only.

The following error was observed when trying to check out the same item above.

Content Server Request Failed
Error Unable to check out 'Content_000402'. The content item is
currently checked out by user 'weblogic'.

It seems Weblogic user was allowed to check out the content item, but not allowed to check in a new revision of that same item because the FF folder it was assigned
to is read only.

Users then tried to update the metadata of above item and this was allowed.

So in summary, marking a FF folder read only, does not prevent the item to be
checked out, but it does prevent check ins. It also does not prevent the metadata of
individual items in the folder from being updated.

Is the above behavior an accurate account of what is expected for this "Mark Read-only" feature?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms