How can I debug a Service Catalog variable?

[Community Alums]

I need to familiarize myself with a Service Catalog item that was originally configured by someone else. The way this was all set up is a little insane, so bear with me. Part of the reason I'm asking for help is so I can start to untangle all this.

We have four variables, all dependent on each other. Three of them have reference qualifiers pointing to script includes, that query a table based on what was entered in the variable before it to give the validate choices. The fourth table is a simple reference qualifier pointing to the sys_user table.

What is happening is that after filling in the first three variables, the fourth variable auto-populates with whoever is mapped to the combination (1st, 2nd, 3rd variable) in a separate routing table. I cannot for the life of me figure out what script is populating the fourth variable.

Does anyone know of an easy way to debug the variable? I'd like to avoid going through and toggling each client script/ui policy manually (together there are over 100 of them). I tried to field debugger, but it doesn't look like it works for Service Catalog items.

[Bradford Shelle]

I'd start with the Catalog Client Scripts. Copy the name of the variable in question, then do a search on the client scripts where the script field contains the name of your variable and see what shows up. That should at least begin filtering down on the list. Hopefully the previous person didn't go too far off their rocker and hard code the name of the variable in a script include that's being called via Ajax or anything.

[Community Alums]

I actually took a high level approach a little while after posting this and just disabled all Catalog UI Policies and Client Scripts running on this item. The field is still being populated, so yea. Kind of at a loss at this point.

[Community Alums · Accepted solution]

I actually managed to figure this out, in case anyone is ever running into the same issue. It turned out to be configured using a data lookup policy, with a source table mapping what the outcome of all the combinations will be.