BY JIM MARKLE, RIGHTSTAR SYSTEMS
Last time we built a picklist with plenty of room for additional columns of verbose description data or “whatever you want to display” data. It had exactly the data you needed to display and was available as a lookup object from within a Service Request. Like below. But it took some effort to come up with the ability to add all that custom data like “Security Level” and “Description”. But hey, we needed it in there!
This time let’s add a lookup table without having to create a custom object (required for the above) and keep the choices simple. In other words, let’s keep it simple but still see what we need to see! Like this:
In the above example I’ve added a picklist populated with 3 regions. We could have listed more…or fewer columns of data. We can easily display more columns than just the “Instance Name”. But the goal here is to keep it simple and present a picklist of choices where no additional description or other related info is needed. Just the facts ma’am. After clicking on the picklist button in our example, we need a listing of Regional Name choices. We’ll need to select from a list of 3 Regions: Central, East and West. And like before, the selection will transfer to the input text field.
To build this functionality we need the following:
- A new CMDB class.
Much easier than having to do all that “custom object stuff” from before, eh? Ok, let’s get started.
We will first click on the new icon (the little piece of paper with the folded corner…just to the left of the big X) in the CMDB Class creator (Remedyforce Administration/Home/Application Settings/CMDB_Classes) and . . .
create a class called “Region”:
Then we can select the new Region Class and start populating our (3) choices. The result of adding “East” is shown below. More information could be populated and displayed as noted above. But the goal here is to keep it simple and give us a quick process for populating a Service Request picklist:
Here’s how it will look in the CMDB (well, if you filter on the word “Region”):
Now that we have the 3 choices available, let’s add them to a Service Request. Create a Lookup Input field from within the Service Request definition. You know how to create the lookup and point it to an object, right? We’ll use “Base Element” for the lookup (and you were expecting that, right?):
And we’ll build a filter (naturally mine is called “Select Region”) using the newly created Region Class. So now those 3 choices from the CMDB_Class called “Region” will be presented:
The result of all this will be a quick and easily created Service Request lookup table! Cool eh? Ok, here it is again: