Difference between revisions of "Patch: 14th August 2018"

From UnionCloud Support
Jump to: navigation, search
(UC Architecture - Assets)
(Global Committee Expiry Dates)
Line 4: Line 4:
 
Introduced global expiry date configuration to expire the group committee members.<br/>
 
Introduced global expiry date configuration to expire the group committee members.<br/>
 
Removed Start date and end date concept for committee post and added active, inactive status for group committee posts.     
 
Removed Start date and end date concept for committee post and added active, inactive status for group committee posts.     
*This issue has been resolved.
+
*This was an enhancement
  
 
== UC-975 ==
 
== UC-975 ==

Revision as of 10:31, 16 August 2018

This page details the content that has been released in the patch 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.

UC-436, UC-976

Global Committee Expiry Dates

Introduced global expiry date configuration to expire the group committee members.
Removed Start date and end date concept for committee post and added active, inactive status for group committee posts.

  • This was an enhancement

UC-975

Automated Data Anonymisation Amendment

Previously, the logic for Alumni Anonymisation considered any students that had not logged in within, and were not students since, the period you configure from the Admin >> Setup >> Alumni screen, however this presented an issue that if a user hadn't logged in, but still had an active Group Membership, or an Event Ticket in the future, they could still be deleted. We have amended the logic to not consider users for deletion in either of these cases.

  • This issue has been resolved.

UC-520

UC Architecture - Assets

Speed Up Asset Precompile process.

  • This was an ehancement

UC-1102

Updated Global JS Handling

Incorrect Global JS Handling

when a user submits an updated Global JS file, UnionCloud says 'Global javascript updated successfully' which isn't true. The file has saved, but is then processed in the background before being applied to UnionCloud, if whilst the file is being processed there are any issues, incorrect syntax, missing bracket etc. The file won't update on UnionCloud, but we have still given the end user a message saying updated successfully.

We have now amended this process to prompt the user to update Global JS before the file will save successfully.

  • This issue has been resolved.

Uncat

Minor uncategorised fix

Title
Details