It's all about the answers!

Ask a question

Operation Behavior not overwritten with multiple roles?

Benjamin Chauviere (3723) | asked Mar 11 '16, 3:44 a.m.

in RTC, we have a list of Adopter roles, personally I'm assigned to several roles in RTC (PM, Adopter, Scrum Master), I wanted to put some read only fields only for Adopters, so I modified the Operation behavior only for the Adopter role.

I can see this affects me as well, whereas I thought that my PM role with not this constraint will overwrite it.
Do I have to delete my Adopter role?

Is that behavior correct ?

Accepted answer

permanent link
Ralph Schoon (62.0k33643) | answered Mar 11 '16, 5:35 a.m.
Benjamin, carefully read this article:

The important part is, that it tries to find an operational behavior configuration in the order of the roles. Once it finds a configuration it executes this behavior and does not look for other roles.

So in your case, if the required attributes are for the adopters, you configure the behavior for that role. If you have a more high skill role, put it on top and configure the operational behavior for that role - e.g. to have no operational behavior configured, just check the flag that it is configured and don't configure anything.

Or configure whatever you need there.

Please note, there is no inheritance mechanism that automatically inherits any behavior across roles.
Benjamin Chauviere selected this answer as the correct answer

Benjamin Chauviere commented Mar 11 '16, 7:03 a.m.

Thanks much Raph as usual for your prompt support, I achieved to fulfill what i wanted to do! As well as for your good summary.

Thank you,

Your answer

Register or to post your answer.