cancel
Showing results for 
Search instead for 
Did you mean: 

Preventing alternate containment

Highlighted
Mike Leydon
Regular Collector

Preventing alternate containment

We have containers that have been migrated from a previous RM system. All these containers (and their documents) are in legacy record types. All the containers are closed, and the system option to prevent new documents being added to them is set - all okay so far.

 

However, users are still able to set these folders as alternate containers (of course, they have to set a 'proper' container as well).

 

Is there any way to prevent users setting a closed folder (or folders of a particular record type) as an alternate container? Without blocking them from viewing/searching these folders completely?

 

And yes, I know they are different in that alternate containment is just a relationship and is different to 'real' containment.

 

Cheers,

 

Mike.

2 REPLIES
EWillsey
Honored Contributor

Re: Preventing alternate containment

The only way to prevent a user from building the "alternative container" relationship is to deny them the update meta-data access control.

Mike Leydon
Regular Collector

Re: Preventing alternate containment

Hmmm, I am sure we tried that - I will have to double-check. That was my first thought as well.

 

I should have mentioned that this is on 7.11 Build 1828.

 

Mike.

//Add this to "OnDomLoad" event