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

New Behavior of Allowed Tag in Templating.cfg

smwangi

Anyone figured out how to make a a DCR editable but not creatable. Before TS6.5 SP2. We could restrict the creating of new DCR using the allowed tag in templating.cfg. But now we either have to let all roles be able to create a new DCR or otherwise users who could edit (but not create) are now getting an error message when they try and edit.

Find more posts tagged with

Comments

Adam Stoller

You could probably do something with FormAPI and/or one of the various callout mechanisms.

You should probably also open a case with IWOV Support if this is indeed a change in behavior (though it sounds like the current behavior is more "correct" to me)

smwangi

Interwoven describe this is a bug fix

Johnny

Anyone figured out how to make a a DCR editable but not creatable. Before TS6.5 SP2. We could restrict the creating of new DCR using the allowed tag in templating.cfg. But now we either have to let all roles be able to create a new DCR or otherwise users who could edit (but not create) are now getting an error message when they try and edit.

Is this specific to SP2?.. We currently do this via the allowed tag (restricting it to master) - we're using 6.5 with no SP installed.

smwangi

Is this specific to SP2?.. We currently do this via the allowed tag (restricting it to master) - we're using 6.5 with no SP installed.

This is specific to SP2 but only after the latest patch 1634.

example_report.rptdesign

saumil

So any patch needs to be installed for resolving this bug?