The new features released in v10.4.1 require them to be "turned on" through the Admin Console. Go to the Repository Options\Settings node and right-click Properties. The Settings dialog box comes up - go to the Records Management tab. Click on any of the 5 options you want to enable. That's it!
Discussion
Discussion
TIP - How to turn on 10.4.1 new Records Management features
"Only allow records management for documents and folders under the record series" actually turns off new functionality and returns you to the pre-10.4 behavior.
Miruna, can you please explain the logic on having that function in the same list as the NEW functions? How does it interact with the other 4 options?? Thanks.
This is not a new tab. The first 2 Records Management options were there before 10.4.
Miruna, my question doesn't relate to the Records Management tab itself, but how the option "Only allow records management for documents and folders under the record series" interacts with the other 4 options. Can you explain the design rationale so I/we can understand this dialog box options? Thanks.
It does not interact with the others.
Laserfiche 10.4 introduced the so-called "flexible" records management where you can attach retention to any entry in the repository. This was a feature requested by a large number of our users who do not have a dedicated records manager and do need the full power of records management. That serves the needs of most organizations, but it does relax the rules for records management. Since some organizations need to comply with DoD standards, we've added an option to turn off the new functionality and revert to the "classic" records management setup. Checking the box for "Only allow records management for documents and folders under the record series" toggles flexible RM off.
The first 2 are records management options, they're independent of flexible vs classic settings. They work the same way in both cases.
The last one is a refinement on RM functionality, also independent of classic/flexible RM. It was introduced because some customers wanted to be able to change metadata that was considered irrelevant for RM purposes in their setup (like tags)