It's all about the answers!

Ask a question

How do you access RTC Custom Enumeration List literal values in the Rational Insight warehouse?


Steve Mulligan (1761321) | asked Sep 30 '13, 1:27 p.m.

We created a Custom Enumeration List in RTC called "Flags".
It is updated into the Rational Insight warehouse in the table REQUEST_STRING_M_EXT.
An example is:
 REQUEST_STRING_M_EXT.NAME - flag
 REQUEST_STRING_M_EXT.VAL - |flag.literal.l26|flag.literal.l24|flag.literal.l18|flag.literal.l29|

Normally the literal values and associated names are present in the warehouse REQUEST_ENUMERATION table, but they are not there for the Flags enumeration list.

Are they stored someplace else?  Does something need to be set in RTC to get them to be updated into the warehouse?


Comments
Steve Mulligan commented Oct 10 '13, 4:54 p.m. | edited Oct 10 '13, 4:55 p.m.

As a workaround, an additional field called Test_Flags was added to the process template.  For it rather than using the Flag Enumeration List, it used the Flag Enumeration (i.e. single select).  The field was then hidden, as we do not want it displayed in the UI.  The Rational Insight ETL then brought the enumerated values into the REQUEST_ENUMERATION tabe.


Cathy Xu commented Feb 12 '18, 10:03 p.m.

Hi Steve,

Could you please share a bit more details of how you define the additional field "Test_Flags" to be hidden in RTC? Thank you very much in advance!

One answer



permanent link
Kunal Bajaj (26810) | answered Apr 10 '14, 12:14 p.m.
Steve,

We seem to have the same problem. We do not have a link between the Enumeration and the WorkItem (Request). The RIODS.REQUEST table does not have the REQUEST_ENUMERATION_ID as a foreign key as the Enumeration is for custom attributes. Is the workitem linked through another table or does this need to be 

Kunal

Comments
Steve Mulligan commented Apr 10 '14, 12:54 p.m.

A Request can have multiple custom attributes, each with an Enumeration, so the REQUEST_ENUMERATION_ID cannot be in the RIODS.REQUEST table.
There are different types of custom attributes, each with its own table for defining a one-to-many relationship between REQUEST and Custom Attribute.  For string attributes there are three tables (RICALM.REQUEST_STRING_EXT, RICALM.REQUEST_STRING_L_EXT, RICALM.REQUEST_STRING_M_EXT).  There are integer and long integer attribute tables (RICALM.REQUEST_INT_EXT, RICALM.REQUEST_LONG_EXT) and a boolean attribute table (RICALM.REQUEST_BOOL_EXT).  In each of the attribute tables, the NAME field contains the attribute name, while the VAL field contains the attribute value.  The VAL field can contain the actual value you want or it can contain a literal that you need to look up in the RICALM.REQUEST_ENUMERATION table.  The REQUEST_ENUMERATION.EXTERNAL_ID field links to the attribute table VAL field.

You need to look at a few example to understand the relationships.


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.