It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,880
×10,916

question asked: Jan 20 '15, 8:29 a.m.
question was seen: 3,114 times
last updated: Jan 20 '15, 8:50 a.m.

Related questions

Role Based attribute lock down

0
David Beange (111●3●64●101) | asked Jan 20 '15, 8:29 a.m.
We have a desire to be able to restrict the ability to update at attribute within an RTC Work item to make it only available for update by a specific role.
There are various similar posts for older versions of RTC but we are on 4.0.6  and about to upgrade to 5.0.1 or 5.0.2 and wondered if things have moved on in these newer versions.
Therefore field A to be restricted to Role A updating. But all others to be available. Due to the nature of how the instances are hosted there are no options for server side updates.

Thanks

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Jan 20 '15, 8:50 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The permissions are supposed to be used to give roles permissions to change values for attributes. Have you looked into these permissions on role level?

Also see: https://jazz.net/library/article/1093 as I think we discuss role based permissions there.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.