Release Note 11.152.0 - 1.152.0
Prerequisites for this version
Ginesys version 11.152.0 onward, below mentioned components will have to be present in the Ginesys application server for functioning of Ginesys. These are components that are important for advancement of the .NET technology stack of Ginesys. They have no functional impact and should be installed by your IT administrator before attempting to update to Ginesys version 11.152.0.
Windows version 2012 R2 (x64) or above
IIS (Internet Information Services) 8.5 or above
ASP.NET Core 3.1 (x64) hosting bundle to run .NET Core based applications
Download from this link https://dotnet.microsoft.com/download/dotnet-core/thank-you/runtime-aspnetcore-3.1.3-windows-hosting-bundle-installer
Know more about .NET Core at https://dotnet.microsoft.com/download/dotnet-core/3.1
To know more, How to install software component prerequisites for Ginesys 11.152.0
Control
| Release Date | 30 May, 2020 |
| HO Version | 11.152.0 |
| POS Version | 1.152.0 |
| Web Database Compatibility Version | 1.16 |
| Features & Enhancements | 11 |
| Bug Fixes | 00 |
| Navigation |
Features & Enhancements
| Serial | Idea Tracker | Description |
|---|---|---|
| 1 | BO-I-148 | Audit Trail has been introduced to track all user entries in GinesysModule: Ginesys Web - Admin - Utilities - Audit Trail Feature Video:
Enhancement Summary:
Scenario: This features is introduced for security purpose, with audit trail you can prove your regulation compliance to your external auditors; you can restore your lost transactions; detect fraud and malpractice. Suppose certain policy changes have been affected in retail stores. If at a later date, the management needs to refer to those changes to know who changed the policies and what the values before modification were, they can just export the audit data in a report. To know more please read - How To: Setup a SQLite database browser to browse Ginesys Audit trail data file Managing the Audit Trail in Ginesys ERP Admin Existing Item History has been disabled Ginesys earlier had an internal Item History tracking which is now disabled this version onwards. In case you have any custom working around this, please ensure you change to the new audit structure. Item audit tracking has been enabled by default which this patch execution. |
| 2 | GIN-I-2827 | Seamless and Integrated E-way Bill SolutionModule: Ginesys Web - Admin - Utilities - E-way Bill Generator Enhancement Summary: Ginesys has made necessary next level development w.r.t. integration of our Software with EaseMyGST, for seamless and hassle-free generation of E-way Bill. Some of the Key features includes:
Important Note: On how this will work for existing clients after updating the Ginesys version, please mail at support@easemygst.com. Once updated, you should follow the steps given in the following article to enable EWB generation from Ginesys: How To: Enable integration of E-Way Bill Plugin (EaseMyGST) in Ginesys HO |
| 3 | GIN-I-1830 | Settlement Validation has been provided to avoid stock mismatch between POS and HOModule: Ginesys Launchpad - POS Settlements Enhancement Summary: A validation has been imposed in daily store wise settlement at HO to avoid the stock mismatch between POS and HO. This validation works on entry-type wise stock movement data - to exemplify, it takes into account the number of items going out from the stock through POS Bills etc. and the stock replenished or coming in from GRCs etc. If any stock mismatch is found, the settlement will be restricted in HO and the troubleshooting can be performed at the same point. If any mismatch occurs the user will be alerted of the mismatch in the HO settlement window. The user will have to log a support ticket and get the data cross-checked by Ginesys technical team in such cases. Scenario: Suppose in a store, 2 GRC (stock-in of 70 units) and 5 POS bills (stock-out of 30 units) have been generated at a particular date. The record of this stock movement of +70 and -30 should be present in HO database at the time of Settlement from POS at day end. However, if a particular POS Bill is missed out in sync cycle before settlement, correct stock data will not be available in HO database. After this update, if the stock movement data does not match, HO settlement will be restricted and user will be asked to raise a ticket with Ginesys to check out the mismatch. |
| 4 | GIN-I-2869 | Extinct Items gets restricted in POS OrderModules: POS - Back Office - Transaction - POS Order Enhancement Summary: Extinct items sometimes get included in orders mistakenly, causing embarrassment for the retailer and awkwardness for customer. Selection of extinct items from Select Item, in POS Order, were already restricted. Now, scanning is also getting restricted. On scanning an extinct item, the user will be restricted with a message - Scanned Barcode <Value> is Extinct. Cannot Populate Item. |
| 5 | GIN-I-2923 | Switch User functionality in POS is now access right drivenModules: Ginesys Web - Retail Management - Security - Roles Enhancement Summary: Managers can control users' access rights towards the Switch User at POS, so that no frauds can be committed by switching the roles. A new app operation called - Allow Switch User - has been introduced. If selected, by ticking the check-box, it allows that user to apply the Switch User feature. Note: By default the feature will get enabled for all existing users, if required, this can be controlled using the role - menu - operation selection. |
| 6 | GIN-I-2902 | E-Invoice related changes has been releasedBefore E-invoice was deferred by the government, Ginesys had already developed E-Invoice related changes, now the changes are being released. However, some changes w.r.t to implementation of E-Invoice in future are expected, till that time please ignore the options related to E-Invoice or IRN (Invoice Reference Number) which ever is visible in the user interface. Some changes related to E-Invoice which might impact your current working New policy introduction for allowing POS bills with GSTIN tagged to the customer - Some clients may have wanted to restrict B2B bills from POS in order to avoid the complexity of generating E-Invoice from POS locations, so we had introduced this policy. The policy name is "Allow POS Bill for a customer with GSTIN details", by default it will be set as Yes, this can be managed from Head office - Policy management. If this is set to No, the cashier will be prompted to proceed with preparation of the bill without tagging the customer's GSTIN. Due to this, we have applied a restriction in POS bill modification & recalculate tax, i.e., a bill which has been prepared as a B2B bill, it cannot be changed to B2C and vice versa. |
| 7 | GIN-I-2470 | Principal Place of Business (PPOB) capturing provision addedModules: Ginesys Web - Admin - Organization - GST Identification Number (GSTIN) Enhancement Summary: While applying for GSTIN, you need to specify the principal place of business in the application. This is basically the primary registered office for the state/GSTIN. In Ginesys, we have provided a provision to tag the PPOB. Important - No impact of data Note:This is just for reference, no functional impact around this capture. Applicability on Sites Note: Only the sites where the selected GSTIN is tagged can be selected here. |
| 8 | GIN-I-2922 | Technical/Integration related: Changes have been made in GDS (Outbound) to include new events in the frameworkModule: Ginesys Data Services (Outbound) Enhancement Summary: GDS (Outbound) has been enhanced to include new events in the framework -
Also, some changes has been made to existing events: SNDORDER Scenario: Data from certain events given above was not being obtained from all integrated software wherever Ginesys had business workflow integration with any other ERP. After this update, users will be able to smoothly access Ginesys data for those particular events. |
| 9 | GIN-I-2909 | Technical/Integration related: Enhancement has been made in Third party MOP integration in Ginesys POSModule: Ginesys POS - Normal POS - Payments Enhancement Summary: Enhancement has been made in Third party MOP integration in Ginesys POS to make it safer and easier. Users can contact their respective account managers to take advantage of the new enhancements. |
| 10 | GIN-I-2493, GIN-I-2803 | Technical/Integration related: GST details now get synced to Third Party loyalty vendorsModules: Ginesys POS - Normal POS Enhancement Summary: GST breakup is now synced to EasemyRetail which in turn can send the details to your loyalty vendors if required. Also, few additional information like cashier details, remarks, etc. are also added. |
| 11 | GIN-I-2021 | Technical/Integration related: Zwing Integration related changes releasedSome of the technical changes required from Ginesys for integrating Zwing POS as an independent POS solution has been done and released in this version. Only one user interface change was done, for this, i.e. - addition of "Installation Type" where Zwing POS or Ginesys POS needs to be selected. |
Bug Fixes
Serial | Dev ID | Issue Tracker | Description |
|---|---|---|---|
| 1 | 0000430 | N.A. | "Unable to connect to the remote server" - error message shown in log and scheduled SMS not being sentModule: Ginesys Launchpad - SMS Notification Reported Version: 11.151.31 75100 Scenario: 1. Go to System Internet Settings > Connections > LAN Settings |
| 2 | 0000442 | N.A. | Sync data of Track Secondary sites not showingModule: Retail Management - Utilities - Explore - Data Sync Reported Version: 11.151.31 73193 Scenario:
|