Service2CM Release Notes 1.2.x
OVERVIEW
This release of the Service2CM connector includes all fixes and enhancements that were shipped in the previous releases of the product. For details on the previous release, please refer to the relevant release notes.
The addition of the capturing of custom requests is considered a breaking change. If upgrading from a previous version of Service2CM, all settings will need to be reconfigured.
RELEASE 1.2.18
NEW FEATURES
SUPPORT FOR CUSTOM OBJECT TYPES
Service2CM can now capture custom request/object types from ServiceNow.
ADMIN SECTION
Significant updates have been completed for the admin section of Service2CM. A host of new features have been added to bring it in line with other FYB products.
LICENSE EXPIRY NOTIFICATIONS
License expiry notifications will now be emailed to the nominated email address(es) when the Service2CM license is about to expire.
OVER THE TOP INSTALL
The Service2CM MSI can now be installed on top of a previously installed version. This retains all settings/configurations from the previous version.
DOWNLOAD LOGS
Log files can now be downloaded via the admin console.
IMPORT/EXPORT
Settings can now be imported and exported via the admin console.
ENHANCED FEATURES
URI SEARCHING
All inputs that required a URI have now been changed to searchable inputs for ease of use. For example, searching for a container can now be done via title or record number.

BUG FIXES
SCHEDULER INITIALIZATION
Fixed an issue with the initialization of the scheduler service that caused users to receive an Application data path could not be located error message.
HOTFIXES
POLLING SERVICE IMPROVEMENTS
Improvements have been made to the polling service and database connection to accommodate environments where the ServiceNow API returns data slower than expected.
PACKAGE UPDATES
The following packages have been updated:
- log4net removed from the application
- Newtonsoft.Json updated to v13.0.1
- RestSharp updated to v106.11.8
OBSOLETE FEATURES
CONTAINER ADDITIONAL FIELD VALUE
We have removed the container additional field value from the configuration interface. As the container and attachment search string fields now allow for ServiceNow placeholders (example: {NUMBER}) to be added. This made the container additional field redundant.
LIMITATIONS
There are no known limitations.
