This release contains a rewrite of our email system to address several bugs, payment improvements, API updates, and general UI/UX improvements and bug fixes.
Click here to view the list of minor fixes included in this release.
Several facilities reported that PCS was occasionally sending out multiple order confirmation emails to their customers. This could be viewed in the Activity Log of the order:
The decision was made to rebuild much of how PCS handles emails to address this and several other email related issues.
A facility reported that some of their tax-exempt products were still displaying a sales tax calculation on the customer invoice, although these taxes were correctly not included in the invoice total.
Invoices will no longer calculate a tax for a product for which the tax does not apply.
Users were encountering the following script error when using the Point of Sale Terminal Application to view the Activity Log:
Users were also encountering the following script error when attempting to add a new Contact Log type through the Point of Sale Terminal application:
These have both been resolved and should no longer be encountered when viewing the Activity Log or creating a new Contact Log type in Terminal.
On what seemed like an infrequent and inconsistent basis, we would receive reports of customers stating that a facility using WorldPay Hosted had charged their credit card, but that the charge would not display in PCS.
We have added significant updates to the way WorldPay Hosted transactions are processed in PCS to prevent this from happening and to provide our development team with better error-logging.
A few facilities reported an issue where customers were not receiving their confirmation emails. This was not an issue with their inbox settings and these emails were not going to the spam folder.
This has been addressed by the rewrite of the way PCS handles emails, and should no longer be an issue. If a customer does not receive a confirmation email, it will be the result of their inbox settings.
Once facility reported that following our last release, Embed cards would not process if there was not enough value on the card to pay the entire amount.
This has been fixed. If the total balance on the order is greater than the amount on the Embed card being charged, PCS will now charge the amount on the Embed card and apply it to the order.
The remaining balance on the order will still need to be paid after the partial payment is made.
Facilities using WorldPay Hosted for credit processing have the ability to click on a payment through an order's Payment History and void the payment if it has not yet been batched by WorldPay:
Users were encountering the following error when attempting to void:
This has been fixed, WorldPay Hosted payments can once again be voided before they are batched.
One facility was having difficulty getting their payments to process online through their PayWay account.
We worked directly with PayWay to resolve the issue for the facility. The problem was caused by a setting on PayWay's end that had gone unnoticed do to the relatively low number of facilities processing with PayWay.
Our old API information was found on the Facility Info page in two sections. The first section was located here:
The user would then need to click on the help icon for the rest of the information:
We have added our new API information to the Facility Info page, and have consolidated the old API info into a section labelled Legacy API:
See above, the old API can be found on the Facility Info page.
When not caused by a user's inbox settings, this problem was caused by an issue in the way PCS was built to send send emails.
This is another email-related issue that should no longer occur now that the way PCS handles emails has been rebuilt.
If a cancellation email ends up in spam going forward, it will be caused by a user's inbox settings.
Orders and invoices still referred to Products as items in a few places. Since the last update, Item now refers to a type of Product. This has been fixed on orders. These are now correctly labelled Products, which can refer to any type of product (including an item):
This has also been fixed on print and email order invoices:
Customers using PayWay for credit card processing reported that PCS was not capturing detailed payment information. For example, this order's Payment History displays a PayWay transaction, but it is lacking the customer or card info:
PCS will now capture and display much more payment information for transactions processed through PayWay.
The Admin page was still displaying a link to the old, deprecated version of the Admin page:
This has now been removed, and the old page is no longer supported. All links to the old page should now redirect to the new Admin page, which has been in use for over a year.
If a facility using our waiver system visited the customer page, customers that never signed a waiver would display as if they had signed a waiver and it had since expired:
This is been corrected. Customers that have not signed a waiver will display this way:
There was a bug that caused customer profiles to display as if they had not signed a waiver when the waiver that the customer had signed expired:
This has been addressed, all waivers signed by a customer will now be visible under the Waivers tab from the customer's profile:
Attempting to modify the birth date of a customer who had already signed a waiver was resulting in an internal server error.
This has been resolved and the error no longer occurs.
Several facilities reported that they were not receiving their notification emails when customers booked parties online.
This has been resolved by the rewrite of how PCS handles emails.