CQ conditional field hooks in RTC
I am working on mapping a ClearQuest schema to RTC and they have extensive hook code which causes certain fields to become enabled based on other fields values. Is it possible to replicate this functionality in RTC to avoid many synchronization errrors?
For example: In RTC, if a field "Priority" is set to "High", require a new field "Reason" to appear with a list of possible reasons (enumerations). Otherwise, not only is not required but should not show at all in RTC. If this is not possible, what are my alternatives? Do I have to display all possible fields all the time? What if certain enumerations change based on different field values? Is their a guide I am missing to help us understand how to create this conditional field logic in RTC? |
One answer
Ralph Schoon (63.3k●3●36●46)
| answered Dec 17 '08, 12:20 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hello benjamin.chodroff,
Hi Benjamin, to my knowledge this is not easily possible in RTC today. When I was looking into this, my conclusion was that without potentially creating server extensions it is not possible to implement this in RTC at this point in time. Maybe someone else can come up with an easy solution. Until then, my conclusion ist that connecting RTC and CQ requires a CQ schema that is simple enough and has a simplified workflow. Ralph I am working on mapping a ClearQuest schema to RTC and they have |
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.