This document describes the new features, modifications, and corrections effected in mycloud Release Sprint 1.0.1.0 8

This document is divided into the following sections: 

1. About the Release
2. New Features
3. Modifications / Enhancements
4. Corrections / Bug Fixes
 5. Known Restrictions / Issues 

About the Release 

Release Date: 03 April 2017 

Modifications / Enhancements 

This release includes following new modifications / enhancements: 

1. Payment Gateways => GlobalPay :- 

Please refer "GlobalPay" section under "Interfaces => Payment Gateway" section for how to setup Globalpay payment gateway in mycloud.

Users can perform refund for the transactions done through payment gateway. In mycloud PMS => Cashiering : Cashiering screen provides an option to view all transactions done through GlobalPay interface in both local and payment gateway currency. (see image below)

• From the same screen user will be able to refund a payment against a transaction.
• By default it will be a full refund, and it can not be more than the original posted payment.
• User can do partial refund but amount can be rebated only once
• At the same time system will post a refund charge in the selected account to update the account folio.
• Amount will be visible in local cuurency in PMS but will be refunded in payment gateway currency
• After posting retention , user can make a refund on cancel guests also of the remaining amount .
• After refund user can print folio which will include refund transaction, and transfer refund transaction to another account 

2. PMS => Revenue Management => Confugure/Send Occupancy alerts based on room type occupancy :-

The system provides the function to alert the preconfigured users, if the occupancy of hotel/room type exceeds "N" number of rooms. This occupancy level can be configured for all room types or for a particular room type.
There is new user access/role has been added under PMS => Manager Functions 

* All alerts having single recipients list. All set alerts can be sent to a single recipients list.
* Recipients list can have multiple email ids separated by ";" (semicolon).
* If no email id is configured under the recipients list, system will send the alerts to System Admin email id.
* Multiple alerts can be configured with different combinations on room type and date range.
* There will be no overlapping of alerts for same date range under a single category of alerts (Hotel occupancy / Room type occupancy). There will be no overlapping of dates under hotel occupancy alerts and the same way there will be no overlapping of dates under room type occupancy for a particular room type. 

* System resends the alerts, if occupancy is changed (increased/descreased) by a number of 'X' rooms. If an alert is set for a room type to send an email if occupancy exceeds "N" number of rooms and it is configured to resend the alert if occupancy is changed by 2 number of rooms. Then system will send email if the occupancy of that room type exceeds "N", and the system will send the email again if occupancy exceeds "N + 2", "N + 4", "N + 6" ..... and so on.

* Alert email will be sent only of occupancy exceeds "N" number of rooms.
* Alerts are sent in emails only.
* Following the alert email format. 

3. PMS => Reports => Guest ledger with VAT => Show revenue amounts without VAT (excluding VAT component) :-

"Guest ledger with VAT" report modified to show the revenue as net of VAT, as VAT component is being shown separately on the report. So now this report will show revenues without VAT components. 

4. PMS => Channel Allocation => Upgrade booking to a room type which has no allocation against the booking rate type :-

* Channel room type upgrade path modified to validate the allocations against given room type and channel of the guest for arrival and departure. If no allocation found then system will treat it as room type upgrade.
* Previously system used to validate the linking of room types with the channel, but there was no validation on room and rate type link.
 * In this modification system will validate the room type in channel allocation of the channel, if there is any allocation found for room type, rate type, arrival and departure then system will validate the channel allocation for room type upgrade otherwise system will simply ignore the channel allocation.

5. PMS => Housekeeping => Alert user if tries to make a room Permanent out of order for dates after valid availability dates:-

* Currently system gives "room already block" if user tries to make a room POO for such dates which are out of max reservation days (valid days for which system generates availability on night audit).
* Make POO path modified to alert user with a message "Selected date is out of the valid availability date range. Please modify the date and try again." if user tries to make room POO for such dates.

6. PMS => Cashiering => Show debtor account name on settlement and debtor account checkout screen :-

* Previously system used to show only debtor account id on settlement and debtor account checkout screen.

* Now system will show debtor account name also on these screens. 

7. PMS => Cashiering => Show deposit required amount on cashiering screen :-

"Deposit due" amount information added on cashiering screen which will help the users to know the exact amount to be collected from the same screen itself.

Corrections / Bug Fixes 

This release includes following corrections / bug fixes:

1. PMS => Reports => Trial Balance => Correct deposit ledger opening and closing balance in case of deposit/retention transfers :-

2. PMS => Reservations => While doing recheck-in, arrival and expected arrival could be modified :-

On opening CO guests arrival date, expected arrival date and arrival time and arrival details were enabled and allowed for change resulting while doing recheck-in, system allowed to change the arrival date of checked-out guest and later it did not allow to modify inhouse booking due to invalid arrival date.