|
  
|
||
|
|
||
ExSync 4.0.0.0
| 1. | A Corrections table for Transactions/Lines has been added. This allows adjustment values to be added to the transactions to correct posting run failure values where Exchequer is out of balance. This is a major step forward and makes reporting easy. |
| 2. | An optional service application to run selected synchronisation in conjunction with the Windows scheduler. The service can also be triggered across the network from the command line or batch file from other applications. |
| 3. | The ability to add SQL code execution to Transactions & Jobs synchronisation to modify the data or execute corrections. |
| 4. | The ability to select Customers/Suppliers/Stock from the last used date to speed up updates with options to select all data, from a date or from today. |
| 5. | The ability to select Jobs from a range of job numbers, all jobs, or from a job number forward. This speeds up the update process. |
| 6. | Exchequer leaves null values in the company/daily rate currency values which causes divide by zero errors on multi- currency reporting . We set all null values to 1 so that division works. |
| 7. | At the back end we have made provision for a ‘Developer’ edition which will be a further upgrade option. This gives customers and/or their developers the ability to have post synchronisation custom stored procedures, the triggering of Shell API’s or external events/applications/batch files. Also on the development road map there will be SOAP integration, turning ExSync into an automation framework. The Service and Developer edition allow for complete customisation. Developers can add code to do pretty much anything on the extracted data. The possibilities are endless. It transforms the engine into a management system capable of executing multiple procedures on any system. It is limited only by the constraints of MSSQL, MySQL or your imagination. |
| 8. | In August 2012, the service edition ver. 1.0.0.1 will have the ability to trigger global events, which is something not possible in the standard application. When the service finishes a sync cycle it will be able to trigger a global procedure that can trigger many other procedures or VB script…. Shell…. You name it! The scope is absolutely huge! All running from Windows schedule or on demand. |
ExSync 3.1.1.1
| 1. | Where there are many Customers/Suppliers or where records have not changed very much. A new option exists to Select All records, A specific date or all records from a particular date (using the Exchequer cuLastUpdate field). Once All Customers & Suppliers have been synchronised a daily synchronisation can select just records changed 'Today' |
| 2. | Where there are many Stock or where records have not changed very much. A new option exists to Select All records, A specific date or all records from a particular date (using the Exchequer stLastUpdate field). Once all Stock have been synchronised a daily synchronisation can select just records changed 'Today' |
| 3. | On Transaction Headers & Lines we have added the ability to execute SQL code by loading it from files at runtime. This allows users to format and execute particular SQL statements on the Transactions |
| 4. | We have added two SQL Tables called TransactionLines_Corrections & TransactionLines_Corrections Using a thRunNo & TlRunNo 0f -9999 correction values can be added to the data. This is particularly useful when Exchequer Posting Run errors leaves gaps in the data and allows for adjustments to be made. The SQL option above deletes and then inserts these values after synchronisation. This is a powerful feature to correct Exchequer anomalies. |
| 5. | SQL update code to copy the Transaction Header TransDate value to the lines table. Exchequer post non date values into the Date filed in the Transaction lines table and make it impossible to convert 4 or six digits to dates. These values are the RunNo of the posting corrections. Why they do this is a mystery. As a result we do not synchronise the transaction lines date, instead we copy it over from the header. |
ExSync 3.0.1.1
| 1. | Up to 4GB RAM can be used by ExSync on a 64bit OS. Ideally a multicore box with upwards of 8GB RAM |
| 2. | The Transaction Lines & Job Actuals tables have been modified so that they are not purged each synchronisation, meaning that a true Archive of all transactions is now possible. |
| 3. | If you re-sync a period. Only that period is purged and updated. |
| 4. | For transaction lines we have implemented changes that improves performance from around 127 records a second to 255 a second on my test machine. 1018853 Transaction Lines in 01:06:25. |
ExSync 3.0.0.1
| 1. | On 64 bit systems we can use up to 4 GB for the application on top of the operating system. Typically a Windows 7 or Server 2008 system with 8GB or more of RAM will enable ExSync to work at peak performance (based on 4GB allocation for the operating system. More RAM would be required for other applications/services). This doubles the capacity of ExSync. |
| 2. | TransactionLines & Job actuals tables are no longer purged. Once the year and period has been selected and they are synchronised any future synchronisation will only purge the selected years. This means that you can now archive all TransactionLines and Job Actuals. On closed periods the data is saved and only the current periods are purged on synchronisation. |
| 3. | Revised, processing methods for transaction tables enhancing performance and reducing memory allocation. Effectively an archive solution for Transaction/Lines. |
| 4. | Optional stored procedures are available at the end of the synchronisation cycle. Activated by a simple check box the stored procedure can be triggered. SQL code can be put in the stored procedures on the database server to do whatever processing you need or indeed to trigger other stored procedures. There is no coding required from us to use this feature you simply write your own stored procedure/s. |
| 5. | Fixed issue with Transactions thHold where changing SQL data type to an integer instead if a tiny int. |
| 6. | Fixed issue with Transactions thTotSettleDisc where value was in correct or missing. |
ExSync 2.0.1.9
| 1. | Fixed error saving settings if Pervasive or SQL database’s are closed. |
| 2. | Fixed issue with Stock Locations where some customers have duplicate stock locations. Multiple Stock Locations now permitted. |
| 3. | Timed interval synchronisation added from 1 hour to 72 hours per cycle. |
| 4. | Compatibility with Oracle MySQL 5.12 and upwards fixing issue with ‘Bad Handshake’ |
ExSync 2.0.1.8
Compatibility with Advanced Exchequer 6.3 changes to Pervasive database with the addition of fields to the following tables.
Employees Table
emUTRCode |
VerifyNo |
Tagged |
CISSubType |
emEmailAddress |
emSpare600A |
emSpare600B |
TransactionLines Table
tlReference |
tlReceiptNo |
tlFromPostCode |
tlToPostCode |
Transaction Table
thWeekMonth |
thWorkflowState |
thOverrideLocation |
thSpare7 |
thSpare |
thYourRefLB |
ExSync 2.0.1.7
In response to customer requests we have implemented a period filter to reflect the Exchequer ‘Year’ & ‘Period’ values. This allows 3 filters to be set to synchronise data for 3 years and periods between 1 to 12.
The years do not have to be consecutive and the periods can vary between years, allowing for huge flexibility in synchronising and viewing period data from transactions.
ExSync 2.0.1.6
Modification to Microsoft SQL server data connection to allow SQL authentication from hosts not on the domain.
WIBU licensing implemented to allow floating network licences.
ExSync 2.0.1.5
Change in Stock Location table query from Pervasive. There are anomalies in the query we were using to filter the data. We have now modified the query to reflect the guidelines from Exchequer to filter on the table where StockLocation.SLSubType_D = 'D' instead of StockLocation.slIdxRecSub = ‘CD’.
ExSync 2.0.0.0
MS SQL Data access layer.
ExSync version 1 used standard Microsoft ADO to connect to Microsoft SQL Server. In version 2 we have moved SQL data access to connect to SQL Server directly through OLE DB, which is a native SQL Server interface. This change has enabled us to develop a faster and cleaner SQL Server data connection.
ExSync now connects through OLE DB through a set of COM-based interfaces. This is designed to be lightweight and consists of a minimal layer between the application and SQL Server databases.
In comparison, ADO uses several layers to access SQL Server, and requires additional data access software to be installed on client machines, either through ODBC or UDL connection.
Pervasive Data Access Layer
We are limited to using ODBC to access the Pervasive SQL data store to access Exchequer data to stay within the framework of read only access to Exchequer in order to maintain the business rules and integrity of Exchequer data.
This limitation affects performance and we have tried a number of different ways of accessing ODBC efficiently. ODBC is now implemented using advanced data access algorithms and optimization techniques. This has radically affected performance and enables us to convert data quickly.
Oracle MySQL
Version 2 sees the option for Oracle MySQL connectivity. The key advantages are increased performance and lower cost.
ExSync & ExReport use a direct connection over the network to MySQL. In direct mode we bypass ODBC and all data access libraries to gain a much faster throughput to the database.
In comparison, the client mode uses several layers to access MySQL, and requires additional data access software to be installed on client machines, which affects performance.
With the MySQL version we gain performance.
ExSync Period filtering.
In response to customer requests we have implemented a period filter to reflect the Exchequer ‘Year’ & ‘Period’ values. This allows 3 filters to be set to synchronise data for 3 years and periods between 1 to 12.
The years do not have to be consecutive and the periods can vary between years, allowing for huge flexibility in synchronising and viewing period data from transactions.
New Licensing System
Customer demand for floating licences and increased flexibility and security made us look at a new licence system.
We have chosen a dongle based network aware system from Wibu Systems a world leader in software licencing, security and encryption.
This new technology allows us to simply deploy upgrades to licences and software. We will also be able to release new features in a single application and unlock licences easily.
Feedback
Most of the changes and new features have come from feedback from customers and we are always keen to hear from you to further improve the product and make it the best complimentary tool for Advanced Exchequer.
For more release notes, please see the PDF file on the Installation CD.
