Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Why does filedAgainst exclude archived values in allowedValues, while priority and severity include them?

In RTC (EWM),  a difference in how archived lookup values are handled in the allowedValues list returned by the OSLC resource shape API:

  • For rtc_cm:filedAgainst (category field of type rtc_cm:Team ), if a category is archived, it is excluded from the list of allowed values.

  • However, for oslc_cmx:priority and oslc_cmx:severity (both of type rtc_cm:Literal ), the archived values still appear in the allowedValues list.

Can you please explain why there is this difference in behavior?

Why are archived enumeration values (like priority/severity) included, while archived categories (filedAgainst) are filtered out from the API response?

Understanding the rationale behind this inconsistency would help in aligning our integration logic with RTC's intended design.

Thank you

0 votes


Be the first one to answer this question!

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 11,053

Question asked: Jun 23, 2:58 a.m.

Question was seen: 532 times

Last updated: Jun 23, 2:58 a.m.

Confirmation Cancel Confirm