New

It is recommended customers with ServiceNow Connector upgrade to the latest release.

Perform if upgrading from a previous version of SovLabs ServiceNow Connector

1) Install SovLabs Plug-in 2019.8.0

  • The SovLabs ServiceNow Connector release 2019.8.0, needs at minimum SovLabs Plug-in 2019.8.0
  • Requires a 2019.x SovLabs License key

2) Determine which version of the SovLabs ServiceNow Connector that is currently installed

  • In ServiceNow instance, type in “Retrieved Update Sets” in the left pane
  • Find the SovLabs Connector Update Set(s) that is/are “Committed”
  • If there is a SovLabs Connector Update Set 2018.1.7, the SovLabsConnector-Upgrade2018.1.7to2018.3.0.1.zip is required
    • Then, SovLabsConnector-2019.8.0-upgradeFrom-2018.3.0.1 is required
  • If there is a SovLabs Connector Update Set committed on or after May 29, 2018, the SovLabsConnector-Upgrade2018.1.6to2018.3.0.1.zip is required
    • Then, SovLabsConnector-2019.8.0-upgradeFrom-2018.3.0.1 is required
  • If a SovLabs Connector Update Set was installed before May 29, 2018, please contact support@sovlabs.com

3) When committing an upgrade Update Set, please Accept Remote Update when running a Preview and then Commit

4) A new prerequisites is required. Set All Application Access for table with name: question_choice (Label: Question Choice):

  • Go to System Definition > Tables > question_choice
  • Go to Application Access
  • For All application scopes, make sure Can read, Can create, Can update, and Can delete are checked

5) What’s New?

  • Add 2019.x SovLabs License Key for ServiceNow Connector
  • Added ability to enable the vRA Business Group to be selected at request time by the end-user in ServiceNow when ordering the Catalog request
  • Import Catalog Item / Modify Catalog Item Mapping Page Enhancements
  • New field for “Override vRA Business Group?”
  • Updated “Constant” label to be “Template” 6) Improvements/Resolved Issues
  • Error logs in ServiceNow and ServiceNow MID Server
  • ServiceNow Request to show a useful error when the request is unable to be generated in vRA
  • Hid unnecessary fields during Import/Modify for a vRA Blueprint that caused confusion on how to affect the number of instances