nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Allow users to edit DCR but not create a new DCR

Trey

I am trying to figure out a way to allow my users to edit a DCR that already exists while not allowing them to create any new dcr's based on this template. I toyed around with the <allowed> option in the templating.cfg and I was able to remove the option from the "File > New Forms Entry" menu. I was also able to view the published page and edit the content of it, but at the same time I was also able to select "New Form" on the surf and edit toolbar and create a new page based on that template.

Any ideas of how I can do what I need?

I am running TS 6.5 (no sp's yet)

Trey Wentz
Ferguson Enterprises, Inc.
e-mail: trey.wentz@ferguson.com

Find more posts tagged with

Comments

JonathonG

We had a similar requirement. We wanted to allow admin users to create new, but no one else. So, we used a FormAPI script that checked the user id against a list of allowed users. If not in the list, we put up an alert to inform the user that they were not allowed to create new ones and closed the template.

Jonathon
Interwoven Developer
Allstate, Inc.

JeremyH

We have done this with FormAPI.

In our case, the DCRs were always created by a process, so there was no need for a person to manually create them.

On form init, you can check the DCR name. If there is no DCR name, you print a message and close the DCR.

As a second level, the Save-As button is disabled. And a Save handler is used to make sure the file has a name. If not, another nasty error can be output. (Though they should never get there.)

Johnny

We did this by restricting the template in templating.cfg to admin/masters.

That way they do not even see the option in pro or std, but can still edit existing pages if they have file permissions.

John Cuiuli

roireport.rptdesign

Adam Stoller

The approach we took at one of my customer's was very similar:
1 - All DCRs are created via a workflow process which prompts for information about type, location, file name, etc.
2 - All DCTs have only the Save option provided (no Save As - also no Preview or Generate as those are taken care of through custom processes)
3- All previewing was performed by generating and deploying files to a staging server

We never ran into the Smart Context Editing / Visual Toolbar (or whatever it's now called) issue - not quite sure why, I guess we just never used the system that way - I think because all the pages were viewed outside of TeamSite so it was never a possibility.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

anisha

You can remove the New Form link on Vpreview tool bar (or SCE tool bar) by editing ui_custom.xml:

<action-list id="iw.ccstd.vpreview.action-list">
<iwov-delete>
<link id="iw.ccstd.vpreview.new_form.link"> </link>
</iwov-delete>
</action-list>

nipper

We did this by restricting the template in templating.cfg to admin/masters.

That way they do not even see the option in pro or std, but can still edit existing pages if they have file permissions.

John Cuiuli

Hey Johnny

Does this still work ? I tried it and it is preventing the user from creating new OR editing DCRs

TIA

Andy

cc96ai

we set it into template.cfg
u can set permission by role or by user

nipper

When I did this, it prevented a new DCR as well as editing a DCR. I am trying to allow authors to edit DCRs but not create new ones.

TS 6.5 SP2 Win2K