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; } } }

Editing a DCR in TS 6.5 SP2

System

Hey Everyone,

I am using TS 6.5 SP2, and running into a little obstacle. I was using TS 6.5 without SP2 till very recently, and was able create an environment where only masters can create a DCR of a certain type, but every other role (author, editor, admin) was able to edit it. I did this by setting the credrole="master" in templating.cfg.

After installing SP2, we ran into a situation where no one but a master was able to create or edit that DCR. So, we had to get rid of the credrole="master" in tempating.cfg.

I was wondering if there is any way to retrieve the functionality of having only masters being able to create DCR's, but every other role having the ability to edit it with SP2 installed?

Thanks,

Ido

Find more posts tagged with

Comments

kaalraa

On first thought check for the iw_role of the user while opening the DCR for editing. Through FormAPI can warn the user and close the form if it is not of the master group.

Can read on more about iw_role with FormAPI Developer Guide Smiley Happy

Hey Everyone,

I am using TS 6.5 SP2, and running into a little obstacle. I was using TS 6.5 without SP2 till very recently, and was able create an environment where only masters can create a DCR of a certain type, but every other role (author, editor, admin) was able to edit it. I did this by setting the credrole="master" in templating.cfg.

After installing SP2, we ran into a situation where no one but a master was able to create or edit that DCR. So, we had to get rid of the credrole="master" in tempating.cfg.

I was wondering if there is any way to retrieve the functionality of having only masters being able to create DCR's, but every other role having the ability to edit it with SP2 installed?

Thanks,

Ido

Migrateduser

I would regard the previous behaviour as a bug.

I don't think there's going to be an easy way to do exactly what you want. Perhaps with some UI customization you could replace the New Form Entry command with a custom command that would wrap it and apply the role check you want.

An easier possibility would be to check the role in your FormAPI on the template itself and pop up a warning and disable all fields if a non master has opened the DCT and the DCR doesn't yet have a name. I don't like that much from a usability standpoint, though.

Could you accomplish what you need with file system permissions - give some users (your non-masters) write on files in the directory but not the directory itself and give the masters full access?

gzevin

After installing SP2, we ran into a situation where no one but a master was able to create or edit that DCR.

have you checked with IWOV support what is that - a bug or a new 'feature'?