R27 Patch: 21st August 2017 - Revision history

Ash: /* US2858 */

2017-10-16T13:57:14Z

‎US2858

2017-09-20T16:55:00Z

‎ZD8047

2017-09-20T16:54:50Z

‎ZD8047

2017-09-20T16:51:56Z

‎US2895

2017-09-20T16:51:46Z

‎Feedback:Student Details Update API

2017-09-20T16:51:34Z

‎Feedback:Student Details Update API

2017-09-20T16:51:21Z

‎Feedback:Student Details Update API

2017-09-20T16:50:48Z

‎Feedback:Student Details Update API

2017-09-20T16:50:26Z

‎US2895

2017-09-20T16:46:53Z

‎US2858

@@ Line 20: / Line 20: @@
 [[File:Download Results.PNG|thumb|Screen showing where you can download individual results or ALL Election Winners]]
 [[File:Winners.PNG|thumb|Example of how the Download Winners file looks]]
-===Download Election Data===<br/>
+===Download Election Data===
 We've recently implemented a feature we've had demand for, for quite some time.<br/>
 As a UnionAdministrator you now have multiple options for being able to extract data from you SU Elections. This includes the following;

@@ Line 51: / Line 51: @@
 == ZD8047 ==
 ===Show Breadcrumb - Subsites===
 Issue presented whereby users who had access to Administer subsites could apply the 'breadcrumb' option, the breadcrumb option is a global control, so a Union either switches it on or of. If a user switched this on, on a subsite, this was switched on site-wide, and vice versa, as such we have removed the Breadcrumb option from the Subsite CMS controls.

@@ Line 53: / Line 53: @@
 [[File:relevant_image.png|thumb|description]]
 ===Show Breadcrumb - Subsites===
+Issue presented whereby users who had access to Administer subsites could apply the 'breadcrumb' option, the breadcrumb option is a global control, so a Union either switches it on or of. If a user switched this on, on a subsite, this was switched on site-wide, and vice versa, as such we have removed the Breadcrumb option from the Subsite CMS controls.
 *This issue has been resolved.

← Older revision		Revision as of 16:51, 20 September 2017
Line 40:		Line 40:

	== US2895 ==		== US2895 ==
−	~~[[File:relevant_image.png\|thumb\|description]]~~
	===Feedback:Student Details Update API===		===Feedback:Student Details Update API===

@@ Line 48: / Line 48: @@
 ''The reasoning for this is for example if people have preferred names, or for example in the case of a Trans student, if they have changed name, but haven't yet informed the university, then the university could change their name back in UnionCloud via data transfer to their 'Dead Name'.''
 ''As such some of these fields you may want to carefully lock down for example, although you may want to allow them to change their name, you may not want them to change their Course End date, something which in most cases should only be set by the institution''.''"</blockquote>
 This is now also the case for preventing updates submitted via REST/SOAP data transfer.
 *This issue has been resolved.

@@ Line 46: / Line 46: @@
 <br/>
 <blockquote>"''As an administrator, if you allow a student to update their Profile Updates fields, if the university provide an update which doesn't match, the information the student has set manually will override what the university sends.
-The reasoning for this is for example if people have preferred names, or for example in the case of a Trans student, if they have changed name, but haven't yet informed the university, then the university could change their name back in UnionCloud via data transfer to their 'Dead Name'.
+''The reasoning for this is for example if people have preferred names, or for example in the case of a Trans student, if they have changed name, but haven't yet informed the university, then the university could change their name back in UnionCloud via data transfer to their 'Dead Name'.''
 As such some of these fields you may want to carefully lock down for example, although you may want to allow them to change their name, you may not want them to change their Course End date, something which in most cases should only be set by the institution.''"</blockquote>
 <br/>

@@ Line 43: / Line 43: @@
 ===Feedback:Student Details Update API===
-Details
+Similar to US2838 from patch on 8th August;
 *This issue has been resolved.