Members Of A Repository with Custom Permissions Unable to Add Assets Using The "Add To Assets" Button
(Doc ID 2896694.1)
Last updated on OCTOBER 04, 2022
Applies to:
Oracle Content Management - Version 22.9.1 and laterContent and Experience Cloud Classic - Version 19.3.2 and later
Content and Experience Cloud Service - Version 20.1.2 and later
Information in this document applies to any platform.
Symptoms
Members of a repository that have custom permissions are unable to see the mentioned repository on the drop-down list that appears after clicking the "Add to Assets" button on the Documents page.
Steps to reproduce:
1. Go to the repositories page, select an existing Repository that accepts digital assets, click on Members
2. Add a new member or edit an existing one by unchecking the delete permission, as an example, on the Assets section, just to change the permission from Contributor to Custom.
3. Go to the Documents page, select a document and click on the Add to Assets button
4. Note that the pull-down does not contain the desired Repository.
Changes
N/A
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |