We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
Release Notes 11.112.2 - 1.112.2
Control
Release Date |
|
HO Version | 11.112.2 |
POS Version | 1.112.2 |
Web Database Compatibility Version | 1.5 |
Features & Enhancements | 07 |
Bug Fixes | 00 |
Navigation |
Features & Enhancements
Serial | Dev ID | Idea Tracker | Description |
---|---|---|---|
1 | 18621 | GIN-I-841 | Snapshot isolation mode can now be enabled in users' POS and Web databaseModule: POS Enhancement Summary: Snapshot isolation is a technique used in the database to ensure data integrity and superior performance of the database. A transaction executing under snapshot isolation appears to operate on a personal snapshot of the database, taken at the start of the transaction. GINESYS POS is recommended to run on snapshot isolation mode. In case the user doesn’t have the mode turned on in his system; the software will guide the user to put it on. Important information Note:
Please follow the given link to know more about snapshot isolation – How to enable snapshot isolation for POS database Scenario: N.A. |
2 | 18491 | GIN-I-837 | Data sync parity file will now be validated to ensure that sync does not get disrupted and POS remains functionalModule: POS – Administration – Data Exchange Enhancement Summary: Earlier the data sync parity file used to be created after update of the sync information in database of the POS. So if there was any issue like a machine shutdown or database crash after the update of the sync information in database – then the parity file would have a back version of the sync information in database which would not match that of the Send/Receive file versions. This would make it seem like a restoration of an old version of the back-up and POS would not open. Now, the data sync parity file will be created before update of the sync information in the web. In case of any mismatch of the sync information, the latest information as available in the local database is updated in the parity file. The feature will ensure data mismatch and compromise of data integrity can be prevented and POS always remains functional. IMPORTANT Note: In case of restoration of outdated backup, POS is still not allowed to open. Scenario: N.A. |
3 | 18627 | N.A. | POS performance tracing can now be enabledModule: POS Enhancement Summary: If performance is suffering in POS and there are issues of POS systems being slow or inefficient; then it can be traced by following the KB link provided: How to enable performance tracing in POS Scenario: N.A. |
4 | 19503 | N.A. | Now users are allowed to change primary backup location via configuration file for POSModule: POS – Administration – Database Enhancement Summary: It has been observed that in case of installations where the data size has grown substantially it takes a lot of time to take full backup and during backup the general working of the POS software becomes slow. The same happens during SYNC also, causing temporary slowness during SYNC operations. One of the reasons for this slowness could be a heavy Disk IO (input-output) operation during backup since multiple operations involving heavy disk operation is taking place in the sequence mentioned below. In most locations, there is no option to increase disk through-put by technologies like SAN or SSD so Disk IO bottlenecks are causing performance problems. After changing the full backup location to the different alternative location, it is mandatory to take a full backup. Otherwise the user will not be able to proceed with further activities in POS (Back-office) and Data Sync. Scenario: N.A. |
5 | 18619 | N.A. | Data will not be removed automatically from Send and Receive files of Sync and new features added to the data exchange dashboardModule: GINESYS Launchpad – Data Sync Enhancement Summary: Now data will not be deleted from Send and Receive tables of Sync permanently, so a user will always have access to historical data unless it is removed by him. It will be preserved in the archives. A date based filter has been added in the data exchange dashboard to allow simplified operations for synced data – both send and receive. 1. A date-filter which can be used for loading and viewing data for a particular period. Important information Note: Default period would be last 7 days starting on the current date. 2. Remove link with a user defined time period. Important information Note:
Scenario: N.A. |
6 | 18622 | N.A. | Differential backup file will now be taken in an intermediate state of data exchange processModule: POS – Administration – Data Exchange Enhancement Summary: Earlier the data exchange process was completed before the creation of the differential backup. This left the database vulnerable to data loss if the send-receive of data was completed before the backup file could be created and then the database crashed due to some reason. Now the backup file will be created in an intermediate state after receiving of data and before sending it. So at any point of time, the data integrity will always be maintained. Scenario: N.A. |
7 | 18493 | OFFPOS-I-20 | All promotions will now be resolved on items returned on adhoc basis at POSModule: POS – Normal POS POS – POS as Collection Centre Enhancement Summary: Earlier promotion resolution on adhoc returned items was restricted to Quantity based Simple Benefit and for a single quantity of the promotional item. GINESYS now allows resolution of promotion on all items irrespective of type of promotion or quantity of item involved. Important information Note:
Scenario: N.A. |