Welcome to SnowMirror 2.5. The new version supports the ServiceNow Fuji release and a number of new important features. One of them is the support for full loads configuration together with incremental data loads. Another one is the support for incremental view replication. And as always, many other improvements and bug fixes.
ServiceNow Fuji Support
Since SnowMirror 2.5 we fully support the new ServiceNow Fuji version released a couple of days ago. The most important change for SnowMirror is the new application scope and other changes in the security area. All the tables have to allow the access to the direct web services (enabled by default). Read more about Application Access Settings.
Full Load Scheduler
SnowMirror now allows to configure a Clean&Sync action independently on the main incremental scheduler. E.g. the incremental load might load the data every hour and the full load happens every Sunday at night. The benefit is more confidence in having the data complete. There are ways in ServiceNow how to avoid the system timestamps to update or how to insert the data with modified timestamps. And it really happens from time to time. This new feature solves most of the issue.
Improved View Synchronization
Views can be replicated using the incremental loads as well. Which was not possible until now. However there are still some limitations. It works only for those types of views where you can identify a master table and only changes in the master table will trigger the update. Master table records cannot be in the view twice. So basically only views with joined 1:N tables fit. E.g. incident with joined referenced fields. And then only changes in the incident table trigger the incremental load.
However in combination with the previous feature this might be a great time and bandwidth saver for some of our users.
See the full change log in our admin guide.
