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

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

Questions
Tags
Users
Badges
Steve Mulligan
(176●13●21) 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?

0 votes

Comments
Steve Mulligan
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
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!

1 answer
8,147 views
0 votes

One answer

Permanent link
Kunal Bajaj
(26●8●10) 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

0 votes

Comments
Steve Mulligan
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 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.

Ask a question
Guidelines
FAQ
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
× 12,144

Question asked: Sep 30 '13, 1:27 p.m.

Question was seen: 8,147 times

Last updated: Feb 12 '18, 10:03 p.m.

Confirmation Cancel Confirm