It's all about the answers!

Ask a question

RTC 502 operational behavior not working as expected


Tojan John (1171357) | asked Aug 04 '15, 9:38 a.m.
 We are using RTC5.0.2 with iFix005 on Linux server. We have master project area from where all other project areas are sharing process configuration. For one of the project area which is sharing the common process, has many team areas. If we modify the operational behavior to set pre-condition (save work item) of team area, it is not working as expected. Once it is modified, the mandatory fields are not highlighted with red asterisk. What could be the issue?

One answer



permanent link
Ralph Schoon (61.0k33643) | answered Aug 04 '15, 9:58 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Are you aware how the operational works e.g are you familiar, that it only works for the first operation configuration that is fond? See: Process behavior lookup in Rational Team Concert 2.0.

In almost all of the cases if this happens, it is a configuration issue.

If the red asterisks don't show up, does the safe fail at least? If not, it is most certainly a configuration issue.

Comments
Tojan John commented Aug 05 '15, 4:53 a.m.

 Hi Ralph,

I am not sure where I am missing the configuration to make mandatory fields highlighted with RED asterisks once the team area operational behavior pre-condition is enabled.

And it is allowing to save the WI. Even though the fields are mandated by the master common project area.


Ralph Schoon commented Aug 05 '15, 5:06 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Read the link provided above carefully and realize that the operational behavior is only executed for an operation the first role found. If you configure behavior for the operation for another role - even just check the box and configure nothing, it will not work with the config for Everyone.

If you have configured the operational behavior for work item save for mandatory attributes in the sharing project area, but it does not show the asterisks and allows saving in 99% of the cases the configuration is not correct. I have seen this over and over again.

  • Check the operational behavior for work item save is only configured for the everyone role in the project are initially
  • Check there is no configuration of operational behavior for any role in any of the iterations in the timeline

If you have configured operational behavior only for the project area level and nowhere else and only for the one role "Everyone" you should see the desired behavior.

So if you still don't see the expected behavior, check the server log files and or get in contact with support.

Your answer


Register or to post your answer.