How to config enumeration values from database in RTC 4.0?
Hi,
i'm trying to use enumerations stored at database in rtc 4.0. However i don't understand how this suppost to works. I was thinking that i will be able to set a data source, table name, id/label columns and thats it, but when i try to insert a new enum i just select my "storage option" and then i create at process configuration screen the enum values. Is that right? if so, how can i change this values at alm database?
Accepted answer
Hi Fausto,
you are not supposed to access the database directly. When selecting database the enumeration is stored in some part of the RTC database and managed for you. You use it like any other enumeration, but management and later changes are easier.
If you archive a literal it is not available any longer for usage. Items that have the value set still will show the value. You can however not select it any longer if you want to change it. Records that have it will show a red cross. You can run a query against items that have it still assigned (use the menu of the condition to be able to select archived values). You can change the items.
If you delete a value the same happens and you can actually ask and see which items still have it. You should change those before deleting.
you are not supposed to access the database directly. When selecting database the enumeration is stored in some part of the RTC database and managed for you. You use it like any other enumeration, but management and later changes are easier.
If you archive a literal it is not available any longer for usage. Items that have the value set still will show the value. You can however not select it any longer if you want to change it. Records that have it will show a red cross. You can run a query against items that have it still assigned (use the menu of the condition to be able to select archived values). You can change the items.
If you delete a value the same happens and you can actually ask and see which items still have it. You should change those before deleting.
Comments
Hi Ralph,
tks for the response. Just one more question: this article https://jazz.net/library/article/1003 says that " Each literal can provide a Name, an Icon, and an optional External Value. External values can be used for accessing attributes via RTC's REST API, such as the OSLC implementation."
Irrespective of what type of storage i choose (process or database), it's right to say that the value stored at work item field its the external value, or still being something like "enum.literal.l1", "enum.literal.l2"?
1 vote
I would assume the value stored at the attribute is going to be the internal value of the name. OSLC would return the name or, if defined the external value. Please be aware, at XML level you could have changed the literal value in the past. Several people have actually done that to make the value queryable when used in conjunction with the old enumeration list representation that was stored as a ; seperated list of enumeration literals.
1 vote
Hi Ralph,
Can i do this RTC502 or 601? I need populite my enumaration in rtc, from other system database. How can i do this?