Metadata Only Profile Rule Does Not Work When Adding Content to New Folio; Error: "The content item must have a primary file"

(Doc ID 1388131.1)

Last updated on JUNE 01, 2017

Applies to:

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

Symptoms

When attempting to check in content from a Folio whose content profile has the Metadata Only option enabled, the Folio still requires a primary file.

The following error is displayed to the user:

Content item 'xx' was not successfully checked in.
The content item must have a primary file.



The issue can be reproduced with the following steps:

  1. Create a Rule with an activation condition --> Side Effects of:

    <$AllowPrimaryMetaFile="true"$>
  2. Create a Content Profile and associate the above rule to the profile.

  3. Create a Folio Template and save it under that profile.

  4. Create a New Folio based on the above template.

  5. Right click on the node in Folio --> Insert item for check in.

  6. In the Check In form, there is no Metadata Only checkbox, and the primary file is required.


Note that when you use that profile and go to the New Checkin page for that profile (outside of Folios), the Metadata Only checkbox is displayed on the checkin form, and you are able to check in a file without a primary file.

It is expected that this same rule apply when adding content by checkin to a new Folio using that profile.

Cause

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