Release 27
This page details the content that has been updated in the Union Cloud Release named in the title above, if you were looking for the content from a different Sprint, or Union Cloud Release, please take a look at the Version History page to see all Sprints and Releases.
Release 27: Payments & Polyglots
The next UnionCloud update will be released 22nd April. There are two major parts to this release, the updated payment gateway moving to Braintree, and the inclusion of the ability to embed multiple languages, though in the first instance we will just be adding Welsh.
Contents
Bilingualism
Bilingualism Info Here
- Image.png
Description
- Image.PNG
Description
- Image.png
Description
- Image.png
Description
- Additional Language configuration for NUS and Union admin
- Enable Administrators to enter content in Welsh for;
- CMS - Developers Toolkit & WYSIWYG editor
- Configurable Messages & Emails
- Groups & related entities
- Events & related entities
- Elections
- Referenda
- Student Voice Module
- Campaigns - NUS, Union, Group
- Bilingual Implementation for Student side, encompassing following modules;
- Groups
- Events
- Cart
- Delivery Page
- Order Summary
- My account excluding My Volunteering
- Voting
- Referendum
- Student Voice
Braintree
Braintree Info Here
Typical UnionCloud basket
Checkout: Card Payment Selected
Once Card Number is entered it will detect Card Type and recolour accordingly
Checkout: Paypal Payment Selected
Checkout: Paypal SignIn/Redirect
Checkout Completed
- Integration with Braintree Payment Gateway for payments on UnionCloud
- Auto-reconciliation of unfulfilled orders using Braintree API
Tickets & UserStories
Info from fixed tickets & User Stories here.
User Stories
N/A
ZenDesk Tickets
ZD6662
Shopping Cart for Guest user on Connect
Issue with Cart Configuration on Connect, meant that when a user logged in on the Basket / Payment Gateway screen on NUSConnect their cart was cleared.
- This issue has been resolved.
ZD7544
Event Ticket Type Validation
Updated Validation on Event Dates to reflect the following;
Event in Future:
Event Start Date: Editable and validated. (Start date needs to be greater than current)
Event End Date: Editable and validated. (Start date needs to be greater than current and start date set)
Ticket sale start date: Not validated w.r.t to current date-time when event is in future. (Still has to be less than event end date.)
Ticket sale end date: Not validated w.r.t to current date-time when event is in future (Still has to be less than event end date.)
Event is Ongoing:
Event Start Date: Disabled. (This will be in past as event is ongoing)
Event End date: Can be edited as long as the new date is in the future.
Ticket sale start date: Not validated w.r.t to current date-time when event is in future. (Still has to be less than event end date)
Ticket sale end date: Not validated w.r.t to current date-time when event is in future. (Still has to be less than event end date)
Event is past (End date and start date both in past)
Start Date: Disabled
End Date: Enabled
Ticket sale start date: Disabled
Ticket sale end date: Disabled
- This issue has been resolved.
