Allow non admins to change properties on released objects

We have a few custom metadata values on topic in Knowledge Center, some of these values can't be changed on released objects in publication manager. The user gets a Warning message that certain properties can't be changed on released objects. Where can I find the configuration file for this setting.

Translate

Rate translation

Suggest better translation

Parents

Dave De Meyer over 7 years ago

In general we are missing the exact software version of the server and client tools, as things change over the years. On top the behavior is also different for PublicationOutputs versus ContentObjects (like Maps, Topics, Images, etc)

Perhaps you find some inspiration in Understanding the steps in DocumentObj Update method, especially the part about having a valid status transition available.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Akheil Jain over 7 years ago in reply to Dave De Meyer

Hi Dave, we are currently on Knowledge Center 2016 SP1 or (12.0.1), the properties I mentioned in my initial post are custom metadata we added to topics and maps. Non Admin users get a prompt this value can not be changed on a released object.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Dave De Meyer over 7 years ago in reply to Akheil Jain

Generically, "Released" indicates that users shouldn't change things anymore. And only Admins have the power to overwrite on their own discretion. A non-Admin user needs an active workflow step.
What you can do, is add a workflow transition, let's say from "Released" to probably a new status "Released ReadOnly". You could give only access to this workflow step to a set of power users by UserRole (not necessarily Admins). This should allow them to update the Released object.
If you need to hammer down more, there is always a possibility to implement an IWrite* plugin for your custom scenario.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

Dave De Meyer over 7 years ago in reply to Akheil Jain

Generically, "Released" indicates that users shouldn't change things anymore. And only Admins have the power to overwrite on their own discretion. A non-Admin user needs an active workflow step.
What you can do, is add a workflow transition, let's say from "Released" to probably a new status "Released ReadOnly". You could give only access to this workflow step to a set of power users by UserRole (not necessarily Admins). This should allow them to update the Released object.
If you need to hammer down more, there is always a possibility to implement an IWrite* plugin for your custom scenario.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

No Data

Tridion Docs > 01 - General Discussion Forum

Allow non admins to change properties on released objects