R27 Patch: 09th September 2017 - Revision history

Ash: /* Uncat */

2017-10-20T14:42:18Z

‎Uncat

2017-10-20T14:42:08Z

‎ZD8520

2017-10-20T14:40:31Z

‎ZD8410

2017-10-20T13:04:44Z

‎ZD8484

2017-10-20T13:02:38Z

‎US2901

2017-10-20T12:59:53Z

‎Last Updated Date - APIs

2017-10-20T11:48:50Z

‎US2896

2017-10-20T11:47:36Z

‎US2896

2017-10-16T15:01:55Z

‎US2891

2017-10-16T14:42:46Z

‎Related Articles / Resources

@@ Line 85: / Line 85: @@
 === Minor uncategorised fix ===
-[[File:relevant_image.png|thumb|description]]
-Title<br/>
+N/A

@@ Line 78: / Line 78: @@
 == ZD8520 ==
 ===Issue Accessing Mobile Shop / Freshers App===
+Caching issue on permissions was affecting the visibility of the 'Freshers Fair App' button, and when assigning the Freshers App permission to users, the button to download the APK file was not becoming visible.
 *This issue has been resolved.

@@ Line 72: / Line 72: @@
 == ZD8410 ==
 ===Linking to Resources instead of S3 Bucket===
+Corrected an issue, that when previously adding links to Resources from the WYSIWYG CK Editor, when embedding, it would add a link directly to the file S3 bucket location.<br>
-Details
+This isn't an issue for the end user, as they are still getting the file they requested, however it was creating a minor issue in that because they weren't visiting the Resources Index and choosing the download link, we weren't able to track a number of views / downloads a resource had, this has been updated.
 *This issue has been resolved.

@@ Line 66: / Line 66: @@
 == ZD8484 ==
 ===Program SOAP Upload Fix===
-Details
+Owing to some previous UnionCloud code refactoring, we had injected an error to the way the SOAP Service can upload and update Programme Files, this was causing an error with some new unions trying to write their first SOAP Integration. It took some time to be brought to our attention because of how few unions utilise SOAP as their method for Data Integration, with most now primarily using REST Webservice.
 *This issue has been resolved.

@@ Line 59: / Line 59: @@
 == US2901 ==
 ===Queue-it  Integration Changes===
-Details
+Due to the previous placement of Queue-it at the point a user tries to purchase a ticket, there were still numerous database requests from users who were trying to access the Events Module overall, which didn't actually relieve much load on the platform.<br/>
 *This issue has been resolved.

← Older revision		Revision as of 11:48, 20 October 2017
Line 33:		Line 33:
	\|}		\|}

−	An example response	+	An example response;
−	~~<codeblock>~~	+
−	{	+	{
−	"meta": {	+	"meta": {
−	"Summary": {	+	"Summary": {
−	"Total": 1,	+	"Total": 1,
−	"Failure": 0,	+	"Failure": 0,
−	"Success": 1	+	"Success": 1
−	}	+	}
−	},	+	},
−	"data": [	+	"data": [
−	{	+	{
−	"id": "ASD2",	+	"id": "ASD2",
−	"uid": 1517693,	+	"uid": 1517693,
−	"forename": "Cyrus",	+	"forename": "Cyrus",
−	"surname": "Bailey",	+	"surname": "Bailey",
−	"email": "c.bailey@lancaster.ac.uk",	+	"email": "c.bailey@lancaster.ac.uk",
−	"updated_at": "23-08-2017 12:06:47"	+	"updated_at": "23-08-2017 12:06:47"
−	}	+	}
−	]	+	]
−	}	+	}
−	~~</codeblock>~~	+

@@ Line 21: / Line 21: @@
 == US2896 ==
 ===Last Updated Date - APIs===
 Details

@@ Line 13: / Line 13: @@
 == US2891 ==
-[[File:relevant_image.png|thumb|description]]
+[[File:US2891.PNG|thumb|Details in Remote Shop]]
 ===Details in Remote Sales===
-Details
+A number of users had reported to us that they had difficulty establishing the details of the user when looking them up in the Remote Shop. This wasn't so much of a problem with a union was scanning a student card, but if a Union was required to type in the email address of a user who turned up at a counter, to look up their student account, sometimes when they would dictate an email address, phonetically similar letters could cause confusion. For example if a user email address was <code>mno123@institution.ac.uk</code> It is easy for a user to hear the incorrect letter given how phonetically simiar they are. The problem was compounded by the fact that when an administrator pressed search it returned the user email address.<br/>
 *This issue has been resolved.

@@ Line 10: / Line 10: @@
 ===Related Articles / Resources===
 This is something that has always been a part of our plan, and we've finally had some time to implement it. As you can see from the screenshot opposite, so long as you give all of your Articles and Resources tags, when a user reaches the end of the article and selects a tag, it will take them to the Articles or Resources index and show all other articles or resources matching that same tag.
-*This was an enhancement
+*This was an enhancement.
 == US2891 ==