HRSD - generic lookup table

[Colleen]

I have a requirement for a custom multi-select field to be added to a table that extends HR case (sn_hr_core_case).  I can use the List data type but would need a table to store the choices.  I took a look at the tables that came with HRSD application and found Generic Lookup (sn_hr_core_generic_look_up) which appears to be suitable but I cannot find any information on how to use it.  The Generic Lookup table contains no data and has no fields except for sys id, created on etc.

Is there any guidance on how to use the Generic Lookup table in HRSD?  For clarity, sn_hr_core_generic_look_up DOES NOT extend dl_matcher.

[Maik Skoddow]

Why don't you create a child table of dl_matcher? Children of that table are exempted and thus are not counted as custom tables!

[Colleen]

Hi Maik

I suspect my reference to dl_matcher may have caused confusion.  My understanding of dl_matcher tables is that they are to generate a target field value based on the values of other fields - e.g. priority calculated from impact and urgency.

I do not need a dl_matcher lookup.  What I need is a table to hold choice labels and values for a List type field.  Another option could be to use the sys_choice table, but there are restrictions on access on sys_choice for non-admin users.

I hope that clarifies my question.

[ChrisBurks · Accepted solution]

Hi @Colleen ,

What you described here is what we've used the Generic Look Up table for. I was fortunate to be on a project led by ServiceNow and what you described about using something for choice labels and values is exactly how it was used.

You probably noticed that the table doesn't come with any fields at all aside from the system fields. Thus when setting it up be sure to include a "Type" field so that in case the table needs to support multiple scenarios it can be filtered for the appropriate choices/values.

[Cristi5]

Hello @ChrisBurks , do you know if there is a similar OOTB table not part of the HRSD module that can be used to store data that doesn't fit into the OOTB tables and needs to be available as field and variable choices? (There are too many values that represent different things and should be available for different custom fields, to just create them in the sys_choice table)