mO SharemO Share

Release Notes 11.133.0 -1.133.0


Control

Release Date

13 November 2017

HO Version11.133.0
POS Version1.133.0
Web Database Compatibility Version1.9
Features & Enhancements03
Bug Fixes02
Navigation

Features & Enhancements

Serial

Dev ID

Idea Tracker

Description
133884GIN-I-333

GIN-I-333 Password policy can now be enforced for the entire Organization Group

Module:

Ginesys Web - Admin - Organization - Hierarchy - Organization Group
Ginesys Web - Admin - Security - User - Users
Ginesys Web - Admin - Security - Partner - Users
Ginesys Web - Retail Management - Security - Manage - Users
Ginesys Launchpad - POS Analytics 
Ginesys Launchpad - POS Settlements 
Ginesys Launchpad - POS Report Templates 
Ginesys Launchpad - Ginesys Planning 
Ginesys Launchpad - Data Sync
Ginesys POS (Owned and Outright stores)

Enhancement Summary:


Strong passwords are the first line of defence against unauthorized usage of any software. Now, Ginesys allows its users to enforce effective password policies. Users can set password policies for the entire Organization Group. The number of days after which the password has to mandatorily change and the strength of password can also be enforced by the HO. Once it is set, all sites belonging to the Organization Group will follow the same password policy.

Scenario:

The Password expiry (in days): The Password expiry (in days) is not mandatory and can be kept blank. But once defined, it can only be a whole number between 1 and 999. This basically means that, after the number days that are specified in this field has passed the password will have to be reset.

  • If left blank, it will never expire until its explicitly changed.
  • If the password expiry is set to one (1) day then the password will have to be reset everyday

    If suppose a user changes the password on 13th November, 2017, then he will be allowed to login until 14th November, 2017. When he tries to login, on 15th November, he will be asked to change the password.


  • If this number happens to be two(2), then the password will mandatorily have to be re-set after every two days; including the date when the first password is set. 

Enforce Strong Password: There is also a drop-down to enforce the usage of a strong password. If 'Yes' is selected from the list of values, it will ensure that the following conditions are fulfilled for each password subsequently created. The default for this is set to 'No'

  • Minimum 8 characters required
  • Atleast 1 uppercase alphabet [A-Z] required
  • Atleast 1 lowercase alphabet [a-z] required
  • Atleast 1 digit [0-9] required
  • Atleast 1 Non-alphanumeric [~!@#$%^&*_-+=`|\(){}[]:;"'<>,.?] character required
    Note: Front slash(/) and Space key are not allowed as password characters.


Important information regarding applicability of Password configuration

  1. Both the configuration mentioned above will be applicable to Admin (Head Office) and System (store) as well.
  2. Both the configuration available above will be applicable to all types of users, i.e., Head Office (internal as well as partner users for shipment tracking) and POS users (both centrally and locally managed).

Caution:

If immediately after this patch update, you enforce password expiry (in days) option, then all users will have to change their password before logging into Ginesys HO and POS. The system will capture the last password changed information only once the user changes their password post this patch update.
We recommend you to implement this rule by considering your operations. Like sending an instruction to all the users to change the password with a deadline date, else they will be forced to change the password as soon as you enable password expiry.
233406GIN-I-1422

GIN-I-1422 Import Excel feature is now available for AP & AR Voucher

Module:

Ginesys Web - Admin - Utilities - Data Import

Enhancement Summary:

Import Excel is now available separately for importing records in AP Voucher and AR Voucher.

Scenario:

N.A.

334500GIN-I -1394

GIN-I -1394 GINESYS Desktop user can now preview report of any transaction in Web browser

Module:

Ginesys Desktop - Admin - Utilities - Document Settings - Report Template

Enhancement Summary:

Now GINESYS Desktop user can preview reports in a Web browser. The Web Report configuration has to be provided with Application Server Name and Server Port and then in the Add Web Report window tag the desired Document Report to the Web report. Then it would show in the list of reports with document reports and can be accessed from the respective module to open in the web browser.

Important

Please note users have to upgrade GINESYS Web report with latest available kit before using this feature.

Supported Browsers - Only Chrome and Internet Explorer

Default Report Output -  Only PDF and HTML

User can’t change Report Name, Report Title and Report File Name from Report Template module. But they can be changed from the Edit Web Report Window.

New buttons have been added for Web Report Setup in Report Template module:

  • Web Report Config.
  • Add Web Report
  • Edit Web Report

    To know more about the Ginesys Web Report New Installation Kit, click here.


Bug Fixes

Serial

Dev IDIssue TrackerDescription
133946N.A.

33946 Invalid reference number is getting updated, while using Quick Populate option to update reference number to all rows 

Module:

Purchase - Invoicing - Service Liability Workbench

Reported Version:

11.132.0

Scenario:

1. Enter an invalid reference number in quick populate field. 
2. Alert appears stating that reference provided is invalid. 
3. However, observe that even after the alert, reference number gets populated in all rows. 
235052

35052 Multiple records are getting inserted, when user tagged the supplier site wise in the Procurement web module 

Module:

Ginesys Web - Procurement - Vendors - Vendor
Procurement - Goods Received Challan
Procurement - Order Management - Purchase Order
Procurement - Order Management - Goods Received Challan - Agst Order
Procurement - Invoicing - Purchase Invoice 
Procurement - Invoicing - Purchase Return 

Reported Version:

11.132.1

Scenario:

1. Tag a supplier/vendor site wise in the web Vendor master.
2. Now open any of the modules given above. 
3. Observe that for one record in any of them, multiple instances of it are to be found in the database.