Version 2.2

Owned by Nadine Roeper
Aug 31, 2018
4 min read


General changes and corrections

  • The verification range in the queue implementation can be configurated in the server settings. Higher values could relieve the system if applicable.
  • The transformation "Demand data" generates a panel list of the selected columns for the demand.
  • The maintenance of the security memory has been adapted. The first and last record include a blocking indicator in the SIS data base. Therefore, these can better be exluded in the maintenance process. The previous solution had a higher period and could lead to a timeout.
  • The compliance regulation for the missing compliance has been expanded. The record can now be repeated. So, the generation highness can be set up for instance for the synchronisation of several mandates.
  • The process output during the implementation has been expanded so that records can better be allocated.
  • An individual transfer can be released for several records at the same time in the detailed display of a queue entry.
  • SQL connections will not be considered anymore for the license verification.
  • The usage of a security memory can be deactivated by the server configuration.
  • Saving of record copies can be deactivated for records by the server configuration.
  • The tooltips have been expanded in the SIS administrator for processes and data services.


Sage 100 / Office Line

  • The data demands for changes in the CRM have been adjusted by milliseconds. By the exchange integration, milliseconds could be included in "Updateddate" what could lead to a wrong change recognition.
  • Setting of the main contact person in the CRM updates the data images of the company in case these were synchronised to the CRM. This serves the conflict management.
  • Setting of the standard address in the CRM updates the data images of the company in case these were synchronised to the CRM. This serves the conflict management.
  • The incorrect turnover figures (current and previous year) at the last day of a month have been corrected.
  • The kind of tax in the proof transfer has been corrected.
  • The incorrect post code in the if applicable divergent delivery address of the proof transfer has been corrected.
  • The setting rescources include a new process template for the deletion of persons by deleted contact persons. This can also be adapted in order to update the status rather than deleting the person for instance.
  • The process template for the proof meta data has been adapted that the names of the translations groups have not suited to the standard in the CRM.
  • The template "Contact person by CRM person" has been adapted. By transformation, if applicable the changed area in the CRM reamins and the area of the company will be used for the first generation.
  • The usage of a session connection to the CRM has been unified.
  • All demands to the application server has been transformed to a paging process. Therefore, OutOfMemory errors will be avoided in the application server. This change concerns the versions 7.0 and the following ones.
  • New plugins for the synchronisation of address registers with CRM addresses are available. A generation of new address registers will not be supported in Sage 100.
  • If a current account for an already synchronised company / address will be generated, a divergent version number has been saved in the data image. This could lead to a wrong conflict recognition. 
  • The hierarchy verification for persons/contact person now also searches in the complementary direction for available data images.
  • The hierarchy verification for account/current account now also searches in the complementary directions for available data images.
  • The template "Address by CRM company" has been adapted. The area allocation has been removed. If applicable, a desired area allocation needs to be configured independently.
  • The template "Current account by CRM account" has been adapted. The area allocation has been removed.
  • For the proof transfer, a debugging has been introduced whereby the transfer can be repeated.
  • The Sage 100 version 8.0 / 2017 will be supported.
  • The OfficeLineSetup offers the opportunity to select the modules which need to be installed.


Sage New Classic

  • The data demands for changes in the CRM have been adjusted by milliseconds. By the exchange integration, milliseconds could be included in "Updateddate" what could lead to a wrong change recognition.
  • Setting of the main contact person in the CRM updates the data images of the company in case these were synchronised to the CRM. This serves the conflict management.
  • The templates "Customer/Suppliers by CRM company" have been adapted. By transformation, the in the CRM changed area remains if applicable.
  • The templates "Contact person by CRM person" have been adapted. By transformation, the changed area will if applicable remain and the area of the company will be used for the first generation.


Sage CRM

  • Column names which include "sp_", will be ignored by the scheme generation in the SIS.
  • The forwarding in the CRM after transferring a CRM order has been corrected.
  • The list of the data services received an "Update button" in order to correct the display in version 2017.
  • The SIS tracking received an "Update button" in order to correct the display in version 2017.
  • The SIS tracking considers both directions of the synchronisation.
  • The table script for saved data services did not verify during deletion if the table mode will be used what leaded to an SQL error.
  • The connection verification can be deactivated for webservice requests. This is an expert setting and should not be changed without any reason ( e. g. resources requirements).
  • The SQL error through a missing"SET" part when saving data by data base access has been fixed.
  • The error notification has been fixed in the SIS process list.


Generic SQL parcel

  • The SQL parcel supports the deletion in a desired SQL connection. This will be configurated by the compliance regulations.
  • The result of SQL data services can be seen in the SIS administrator.





Impressum