Replicants as readonly

Is there a way to disable add, delete buttons that appear when you create a replicant?

Find more posts tagged with

Comments

I don't understand what you are going for. The whole point of a replicant is to, well.. replicate. You could limit the maximum number of replicants. so if the max is set to 5, when the 5th is entered, the user wouldn't be able to add any more. You could restrict what users (or roles) have access to editing the items. Although I am not sure if that will disable the delete and add. For example the format in a text area is:

<allowed>
<not>
<cred role="author"/>
</not>
</allowed>

Could you explain a little more what your ending goal is?

Matt

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

conmgmt

This is what we are trying to achieve....

We are going to create a dcr under a category in a generic branch. The DCT used to create this dcr will have replicant. The user creating this dcr will have ability to add/delete replicants...

The dcr created from above is generic and will be copied to a category under several regional branches. The DCT in these regional branches will be similar to the DCT in generic branch, except all the item names will be readonly. The author in the regional branch will have an option to chose which replicant to include in the tpl specific to that region.

The issue is; when the author in the regional branch edits the dcr in the regional branch (note that the dcr is copied from generic branch), he should not be able to add/delete replicants.

Hence I was looking for a way to disable that.

Migrateduser

Did you find a way to disable the add delete and move buttons from the replicant on the DCT, as I have the same problem?

MattP

Hmm-

Sorry, not sure how to solve this without a lot of trial and error. Although, I think you have identified a very good feature request. There should be an allowed tag in the replicant item. You should post that in the request section. Someone with a lot of experience may know how to do this now.

As far as a solution, I would look into a method for allowing the branch user to select which sections they want included, without showing the actual replicants (maybe a dynamic drop down box or check boxes). Then, use either perl or server side logic (asp, jsp) to build the page appropriately. You scenario is pretty interesting. Good luck.

Matt

Matthew Petitjean
BOC Group
Murray Hill, NJ 07974 USA

conmgmt

Sorry, I haven't found a way yet.....