Qualys upgrade deleted custom fields added to VUL

nancym
ServiceNow Employee
ServiceNow Employee

Hi, any Qualys experts out here who can help explain potentially why the plugin upgrade to version 12.10.1 would cause custom fields to disappear? My understanding was that upgrades will not overwrite custom work like additional fields. (But maybe a key table like the one housing VULs will always be updated?) Here are the fields that were removed from VUL records: 

nancym_0-1705600112194.jpeg

 

Thank you,

Nancy

1 ACCEPTED SOLUTION

Martin Dewit
Kilo Sage

Some things I would look at:

 

Review those missing field's last updated date and updated by to see who, what, and/or when. Either on the VUL table or the Version history on the Form Layout.

 

When you upgraded the Qualys integration did you review the Upgrade History? This is where changes are recorded from previous version to the updated version. For example, it will show you what 12.10.1 changes it skipped over because of any customization you had and you can decide whether to skip, merge, or revert the code. Link to Upgrade History docs

 

Did you also verify that your VR version is compatible with this Qualys version? I could see the possibility of it missing a VR update that coincides. See KB for compatibility matrix (requires login)

View solution in original post

1 REPLY 1

Martin Dewit
Kilo Sage

Some things I would look at:

 

Review those missing field's last updated date and updated by to see who, what, and/or when. Either on the VUL table or the Version history on the Form Layout.

 

When you upgraded the Qualys integration did you review the Upgrade History? This is where changes are recorded from previous version to the updated version. For example, it will show you what 12.10.1 changes it skipped over because of any customization you had and you can decide whether to skip, merge, or revert the code. Link to Upgrade History docs

 

Did you also verify that your VR version is compatible with this Qualys version? I could see the possibility of it missing a VR update that coincides. See KB for compatibility matrix (requires login)