-
Type: Bug
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Retention
When the plug is installed "later", after the first, initial deployment, it does not create a RetentionRules document type at root level. This leads to a 404 when trying to access the retention rules from the retention menu.
Looking at the code, it looks like this container is created via a Structure template. So, it is normal behaviour that it does not create the document when installed while the database already was created.
The plugin should be modified so it dynamically creates /RetentionRules if it does not exist.
Workaround: manually create the document. There are 2 steps: create the document, then change its permissions
- Create the document.
For this, I use the REST API, and a POST as Administrator (using API Playground, it's easy). So. Using a POST on a path endpoint, passing / as path (/ is root); Here is the body to pass:
{ "entity-type": "document", "repository": "default", "type": "RetentionRules", "name": "RetentionRules", "properties" : { "dc:title": "RetentionRules" } }
(Notice this could be done via Automation, Java code, etc., of course : REST is not a requirement)
2. Change permissions
Admin > NXQL => SELECT * FROM RetentionRules (because It’s HiddenInNavigation => you don’t see it at root level)
Open and change permissions:
- Block inheritance,
- Add “RecordManager” as “Everything”
(this could also be done via REST, automation, Java, …)