Form section(s) missing from ATF Input variable form
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2019 10:16 AM
We are bringing up ATF as part of our Madrid upgrade, so we have brought all of our PDIs to Madrid but our prod and sub prod instances are still on London. What we encountered was that two of our PDIs have the same problem with configuring test steps, and we don't know if the problem existed prior to Madrid or not, but it does NOT exist in our (London) test instance.
Briefly, when creating a new test step that uses an input variable, the form sections for Reference specification, Choice List Specification, Dependent Field, Calculated Value, and Default Value are missing from the Input Variable form. They exist in the Form layout...
But not on the form
This is true whether creating a new variable, or viewing/editing an existing one.
Our London instance shows the affected sections correctly. Both when examining an existing variable:
And when creating a new one:
The additional form sections are available as soon as the Reference type is selected. The UI Policy that appears to control this action (Show/Hide reference fields section) in my PDI is identical to the one in our Test instance, and at a glance the list of Client scripts and UI Policies do not appear to be different anywhere else. But we can reliably reproduce the same problem on two different Madrid instances -- at least one of which is patched to the latest level since it was only upgraded a few days ago.
Searching HI turned up KB Number: KB0639979 which offers a workaround involving searching for the Advanced view of either table (atf_input_variable or atf_output_variable) and deleting the two records from the list. Since both records are delivered read-only, it seems reasonable to assume that this was not intended to be used once the issue was fixed -- which happened in late Jakarta and Kingston releases. But if it was fixed, it's back and no amount of coercion seems to be able to correct it.
So I'm tapping out and hoping there is some wisdom from the SN Jedi Council to point us toward a solution.
- 2,000 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2020 05:54 AM
Thanks for this! We've actually got a different group administering ServiceNow since I posted this (short version our semi-annual re-orgs frequently move my team into new and uncharted areas which is never dull but brings about situations like this) and it's been just about long enough since we encountered this problem for me to forget most of the details. But we're in the middle of the Orlando upgrade, so if it's going to resurface, this is probably when it will happen.
Only problem we might encounter is that we may not have a "known good instance" to export from. But there's a way around that obstacle too, if it comes to it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2020 08:46 AM
James, have your guys go to https://developer.servicenow.com/dev.do#!/home and get a personal developer instance (free) that matches the version you're using.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2020 08:45 AM
One other item I found useful - The UI Policies for the atf_output_variable form- I believe OOB there are 3 where "Reverse if False" is set to false. I added one more - I set Show/Hide reference fields section as Reverse if false = false. That forces the form into the advanced view every time.