Module : Infrastructure / System

Issue	Type	TrialGrid Version	Description
3702	Feature	64	A new 'healthcheck' has been added to alert TrialGrid Ltd if there is an issue with the API used to check spellings for Diagnostic 0020.
3676	Feature	63	The javascript component used to display lists in TrialGrid has been upgraded to the latest version. There is no change in functionality.
3645	Feature	62	On prerelease and other non-production environments the background worker will be scaled down after a period of user inactivity and scaled back up when a user logs in. There is no change in the production environment.
3622	Bug	61	Uploaded files which had a ( or ) in the name were not being scanned for viruses because of a bug in a vendor system. This has been corrected.
3072	System	44	Code that runs diagnostic fixes was improved. This has the side-effect of invalidating all existing diagnostic results with fixes. These fixes will no longer work and will fail with an error. Re-run diagnostics to get valid fixes.
3038	System	43	There is a new monitoring endpoint to check the Redis database connections. This is for TrialGrid Ltd use only.
3039	System	43	There is a new configuration setting for collecting screenshots when generating Test Case PDFs. This is for TrialGrid Ltd use only.
2888	System	40	It is now possible to export all projects, drafts and content for an Organization in one TrialGrid environment and import into another TrialGrid environment. Contact support@trialgrid.com if you would like to do this.
2639	System	34	All failed login attempts are now logged so that TrialGrid personnel can be informed of persistent failed login attempts.
2520	System	33	A background process now monitors performance of Rave URLs.
2400	System	30	Following Disaster Recovery test, updated system scripts for creating new application.
1532	Feature	30	Files uploaded to TrialGrid are now scanned for viruses and malware.
2439	Bug	29	Automated Test runs were failing for some users due to automated web browser crashes. This was corrected.
2408	Feature	28	Changes were made to TrialGrid's validation pipeline. No changes are visible to users.
2407	Feature	28	Python library packages were updated. No changes are visible to users.
1841	Feature	27	When setting a new password, TrialGrid now checks against the HaveIBeenPawned service. This check can be disabled on request.
2341	Feature	27	On request, TrialGrid can configure password complexity and expiry rules for an Organization in TrialGrid.
2340	Bug	26	Progress reporting for long running tasks could sometimes stall. This could effect draft uploads.
2327	Feature	26	Chrome Browser availability is now automatically checked as part of the periodic status checks performed on the system.
2231	System	23	Application program code for Aliases was removed from TrialGrid. No changes are visible to users.
2205	Feature	23	Third party libraries used by TrialGrid were updated to latest versions. There are no changes visible to users.
2062	Feature	21	Before deploying new versions to production, system configuration variables (not visible to users) will be checked for consistency with the beta environment.
2038	Feature	19	A daily background process will check that all objects' standard compliance status is up to date.
2033	System	19	System code was reorganized to make maintenance easier. Users will see no difference to functionality.
1834	Feature	19	The implementation of the permission system was simplified (i.e. who is allowed to see which URLs/Projects etc). Users should see no difference in functionality. All existing security tests were maintained.
1983	Bug	19	A system change was made to reduce the number of task progress messages stored by the system. Users should not notice any change in functionality.
1974	Bug	19	Logging into iMedidata to download Architect Spreadsheets would fail for some users due to browser cookie settings. This was corrected.
1957	Feature	18	On deployment of new TrialGrid versions a database consistency check has been changed. There is no change to functionality.
1941	Feature	17	When viewing Tasks and Alerts a maximum of 1000 rows will be displayed. Tasks older than 365 days will be deleted. Alerts older than 30 days will be deleted.
1924	System	17	System libraries were updated. Users should not see any functional changes.
1920	Feature	17	Emailing support@trialgrid.com will now automatically create an issue in TrialGrid's issue tracking system. An automated reply with the issue tracking number will be received.
1905	Feature	17	The user messaging subsystem was rewritten to reduce usage of the database. This is a system architecture change that should not affect users.
1910	System	17	The 'tokenizer' for extracting words from text for Diagnostic 00020 Spell Checking has been changed.
1885	Feature	17	System IQ/OQ checks now include a check that the email server can be accessed. This is a validation activity and does not affect end-users.
1906	Feature	17	Third-party software packages used by TrialGrid were updated to latest versions. No changes are visible to users.
1903	Bug	17	TrialGrid unit tests were upgraded for compatibility with Rave 2020.2.0. No changes are visible to users.
1887	Feature	17	Test Cases now run in a separate queue from other background tasks.
1880	Feature	17	A new system monitoring endpoint has been added to check that the background queue is not too long.
1881	Feature	17	When deploying a new version of the application the deployment process will automatically turn off maintenance mode if the application has been placed into maintenance mode.
1882	Feature	17	The application name, version number and date/time have been added to the installation log and post installation test log which are available in the Validation documentation for that release.
1874	Bug	16	Long running background tasks, such as Test Case runs, were being duplicated leading to errors. This has been corrected.
1837	Feature	16	A system command was added to generate an Excel listing of Active Diagnostics for a project and their settings. Users see no change but this is a precursor to adding an Excel report Export of Diagnostic settings.
1807	Feature	16	Changes were made to support Disaster Recovery. No changes are visible to users.
1764	Bug	16	Creating PDFs for Test Case runs with large numbers of screenshots used a lot of memory. This was corrected. Users are unaffected by this system change.
1735	Feature	16	A configuration setting was added to the background queue process to help manage memory usage. No change is visible to users.
1731	Feature	16	New settings have been added to the TrialGrid web server to help manage web server memory. No changes are visible to users.
1720	Feature	16	Automated Test Case runs were consuming more server memory than necessary. This has been improved. A previous attempt to correct this issue was made on 2020-02-06.
1502	Feature	16	New contols have been added to TrialGrid to improve the security of web pages. No changes are visible to users.
1721	Feature	16	Python language packages used by TrialGrid were updated to the latest versions. No changes are visible to users.
1708	Feature	16	The system now has a task that periodically sweeps the database of expired user sessions. Users will notice no difference to functionality, this is a system housekeeping change.
1720	Feature	16	Automated Test Case runs were consuming more server memory than necessary. This has been improved.
1686	Feature	16	A new performance monitoring tool has been added to TrialGrid to help identify any potential performance issues.
1648	Feature	16	Some Javascript packages have been updated to the latest versions. No changes are visible to users.
1644	Feature	16	A new step has been added to TrialGrid's internal application testing which will look for Javascript code which might be incompatible with older browsers, such as Internet Explorer 10.
1505	Feature	15	A system admin management command was added to regenerate the validity state for test cases.
1455	Feature	15	If there is a Javascript error in the browser it will now be automatically reported to TrialGrid for investigation. This will help ensure cross-browser support. There is no action required from users and no visible change to the TrialGrid application.
1437	Bug	14	If a formatting mistake is made in the latest release or release notes then the document generation will display with these tables unformatted. The content is present but looks ugly. A test was added to ensure that these tables are formatted correctly.
1182	Bug	13	The process to remove failed tasks did not run on schedule correctly. This was corrected.
1110	Feature	13	Some email-related system settings were moved from system configuration into code because of the risk of changes between beta / pre-production and production versions. End-users will see no difference and are not affected.
134	System	13	Upgrade to the latest hosting environment. No user impact.
1104	System	13	Upgrade to the latest Python version. No user impact.
1105	System	13	Added pre-deployment database version check. No user impact.
941	System	11	Upgraded infrastructure to latest version of web-messaging system.
1025	Feature	11	Infrastructure changes have been made to enable the creation of a prerelease environment, prerelease.trialgrid.io. At least 2 weeks before a new release to the production environment, www.trialgrid.io, the new version will be deployed to prerelease.trialgrid.io and the production database will be copied to prerelease.
993	Bug	10	New diagnostic settings were not being added to existing diagnostics and a post-deployment check to verify that settings were updated was not being run. This has been corrected.
979	Feature	9	As Diagnostics are changed over time, new settings are added to them and instances of Diagnostics that have been added to Projects should reflect those changes. To ensure that this is the case a new deployment check was added that compares the count of settings for each Diagnostic to the count of settings of each Project Instance of that Diagnostic. If the results do not match then Diagnostics have not been updated properly and the deployment fails.
922	System	9	Upgraded infrastructure.
937	Feature	9	Changes to Project roles were not audit trailed. This has been corrected.
422	System	7	Upgraded TrialGrid infrastructure. No changes were made to product features.
721	Feature	6	To further improve performance of TrialGrid web pages, gzip compression has been enabled. No differences should be visible, except for faster page load times.
620	System	4	Some Diagnostics were generating errors in the system log when reporting results of fixing back to the user. This had no impact to users but has been corrected.
572	System	3	In release v2 some packages (3rd party software libraries) were updated. The licenses were unchanged but required review. Build process is now set to fail if there are unapproved licenses in the package list to ensure that software built with 3rd party libraries which have not been license-approved cannot be deployed (to Beta or to Production).
512	Bug	2	A System Administrator page was unavailable due to a missing javascript file.
265	Feature	1	Validation Docs: Licenses for Javascript packages are documented, including approval status. This is enabled by use of the yarn package manager to control usage of third-party Javascript packages.
357	Bug	1	Notification emails include local links to objects instead of absolute links including host. Fixed so that full URL is provided and can be clicked on from email.
324	Bug	1	Update error reporting to provide more meaningful error message pages to users.
324	Bug	1	Initial work to provide more meaningful error message pages to users.
294	Bug	1	Release notes table malformed in release on 18 July 2017. This was fixed.