Version : 1
Released : 2017-10-03
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
2 |
Feature |
Projects now have a Files area which allows files to be uploaded and downloaded from the system. |
|
3701 |
Feature |
It is now possible to search and filter diagnostics in the diagnostic management page. |
|
170 |
Feature |
The layout of the Diagnostics help page was improved to make Diagnostic titles clearer. |
|
240 |
Feature |
Derived Fields are excluded from the Diagnostic which checks if QueryNonConformance has been set on numeric Fields |
|
241 |
Feature |
Derived Fields are excluded from the Diagnostic which checks if QueryFutureDate has been set on date Fields. |
|
256 |
Bug |
Rave gxml such as '<core:link folderoid="AE" formoid="SAE" text="SAE form"></core:link>' was incorrectly flagged as invalid by the Place Sticky HTML Diagnostic, and caused Diagnostic pdf generation to fail. The Invalid HTML strings Diagnostic will correctly flag gxml as being not allowed, and will now autofix invalid strings. It will also flag forbidden HTML tags and attributes such as '<body>' and 'onclick'. |
|
259 |
Feature |
The Invalid HTML strings Diagnostic now checks Folder Names in addition to Field strings. |
|
266 |
Feature |
Matrices have been added to the Empty Objects Diagnostic and will be raised as findings if there are no Folders/Forms in a Matrix |
|
278 |
Feature |
A diagnostic that checks that date fields are compared against at least one other date field is required. Diagnostic 0068 was added with this function. |
|
279 |
Feature |
Diagnostics should have a visible unique identifier to make referring to them easier. A unique identifier was added to the display of diagnostics in the Diagnostic results and Diagnostic Management pages. The identifier was included in the PDF output of Diagnostic results. |
|
280 |
Bug |
Diagnostics management form does not filter by properties after a reload of the page. This bug was fixed. |
|
281 |
Bug |
When a new setting is added to a diagnostic, the Project instance of that Diagnostic is not updated with the new setting. Code was added to achieve this and a database migration was also added to update any existing Diagnostics with new settings (e.g. new Field/Form exclusion settings from last release) |
|
230 |
Feature |
A new setting has been added to the following Diagnostics to allow objects (Fields, Data Dictionaries, Edit Checks, etc) to be excluded if the object identifier is excluded or matches an exclusion pattern: 00022 FormOIDs should not start with numbers 00023 Date Fields should have a consistent naming suffix or prefix 00024 Time Fields should have a consistent naming suffix 00025 Date/Time Fields should have a consistent naming suffix 00026 Active Checks should not reference inactive Forms or Fields 00027 Valid Record Positions for Standard and Log Fields in Edit Checks and Derivations 00028 Data Dictionary CodedData should not contain commas or semicolons. 00030 Custom Function length 00031 Edit Check SYS_ prefix 00032 QueryFutureDate should be set for Date and DateTime Fields 00033 Numeric fields should have query non-conformance set 00034 Fields which require translation should not also be marked as required 00035 Data entry Fields should have a SAS Label 00036 Fields with default values should not have SDV set 000037 Fields with default values should not be set as Required 00038 Checkbox, Data Dictionary and Time Fields should not be set to Query for Non-Conformance 00039 All question Fields should have a pre-text label 00040 Field OIDs should be unique 00041 Data Dictionaries should not have a coded value of 0 (Zero) 00042 Consider setting QueryNonConformance for Fields related to Data Dictionaries with a Specify option 00043 Data Dictionaries should be unique 00044 List of keywords to be substituted in Data Dictionary 00045 List of words to be substituted in Draft Field Default Value 00046 Place Sticky Check Action should not contain HTML tags 00047 Data Dictionaries should not have duplicate Coded Values or User Values 00048 Derived Fields should have a standard prefix 00049 Data format must be valid for Field control type 00050 Data format must be valid for associated Data Dictionary 00051 Fields should have a SAS Format specified 00052 SAS Format should match Rave Field Data Format 00053 Variables should have consistent properties 00054 Unused objects (Data Dictionaries, Unit Dictionaries, Custom Functions) 00055 Empty objects (Forms, Data Dictionaries, Unit Dictionaries, Custom Functions, Matrices) 00056 Fields associated with Coder Dictionaries should have an OID of less than 20 characters length 00057 Fields associated with Coder Dictionaries should have string formats 00058 Check Actions should have a matching Check Step 00059 Custom Functions used in RaveX should not use blacklisted methods 00060 IsPresent Check Action 00061 Valid HTML tags 00062 Default Values should be in associated Data Dictionary 00064 Edit Check Coded Value steps should be compared against valid Data Dictionary Entries 00065 Fields which are not Date or Time Fields should not have date related properties set 00066 Checkbox Fields should not have an IsEmpty or IsNotEmpty step in Edit Checks 00067 Forms should have unique names |
|
330 |
Bug |
Diagnostic 00020 (Spell check) would fail to fix the reported spelling mistake if the correction contained unicode characters. This has been fixed. |
|
353 |
Bug |
Diagnostic result endpoint used to request fixing diagnostic findings can return a 500 Server Error Response for Diagnostic 61. The diagnostic was fixed. NOTE: Diagnostic results created prior to this fix may still exhibit this error when you try to "fix" because the code to fix the issue is stored in the database and is now out-of-date. Re-run diagnostic and fix will work. |
|
361 |
Bug |
HTML Content Diagnostic (61) should provide a link to the folder when correcting Folder Name. Folder link was added. |
|
406 |
Bug |
Diagnostic 00042 says it excludes by Data Dictionary Name but actually excludes by Field OID. Fix was to update the diagnostic help text and to add a new parameter that excludes by Data Dictionary Name. Users may need to remove (inactivate) and re-activate this diagnostic to see this change. Note, de-activating a diagnostic will remove any settings already entered so manage this change with care. |
|
237 |
Feature |
User requested that release notes be provided to track changes made in new releases of the product. We have added a link from the top of every page that shows the version number and this links to the latest release page in help which then links to the full release history. |
|
274 |
Bug |
After clicking on the release number in the header there's a grey box where the release number was displayed. Fix for this is to remove focus from the link after it is clicked. |
|
346 |
Feature |
The 'Feedback' button is now labelled 'Support'. |
|
294 |
Bug |
Release notes table malformed in release on 18 July 2017. This was fixed. |
|
324 |
Bug |
Initial work to provide more meaningful error message pages to users. |
|
324 |
Bug |
Update error reporting to provide more meaningful error message pages to users. |
|
357 |
Bug |
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. |
|
265 |
Feature |
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. |
|
331 |
Bug |
Performance of copying Forms has been improved. |
|
360 |
Bug |
Changing EDC Roles causes timeouts. Added waits so that the system cannot have multiple queued requests to change EDC roles at any one time. e.g. If you change one Role you have to wait for that to save before you can change another. |
|
362 |
Bug |
When changing EDC Roles and Review Groups, Saves can be very slow. Performance was improved. |
|
2447 |
Feature |
A count of project team members now appears on the Project page. |
|
2448 |
Feature |
A listing of project team members can now be accessed from the Project page. |
|
2449 |
Feature |
Project Team members can now be removed from the Project Team list. |
|
249 |
Feature |
View list of users per Project at the URL level without having to look into every Project to find users. |
|
303 |
Feature |
There should be a permission to control whether a user can create a new Draft in a Project |
|
366 |
Feature |
If a user has Standards Approval Permission in any URL, they should see a count of Approval Requests on their home page. |
|
424 |
Bug |
If a user has not accepted a project invite (i.e. set up their account) then subsequent invites ask them to log in instead of creating the account - this was fixed so that the user receives a new request to set up their account' |
|
257 |
Bug |
Retired |
If a Custom Function Template was changed from a Method to a Function type then it was not appearing in the autocomplete list in the Edit Check Editor. |
225 |
Feature |
Retired |
Custom Function Template names can now be up to 44 characters in length. 6 characters are reserved for a suffix to be appended when generating a unique Custom Function name from a Template. The suffix will be a colon and a random 5 digit integer value, eg 'TEMPLATE_NAME:12345'. The random suffix is added to ensure uniqueness for each set of parameters with which the template is invoked. |
314 |
Feature |
Retired |
Custom function templates should be at the URL level. |
148 |
Bug |
Retired |
When creating a new Edit Check the Edit Check must be saved before Unit Tests can be created. |
375 |
Feature |
Retired |
Warn if a user tries to leave an Alias which has not been saved. |
3 |
Feature |
A user with team management permission for a Project is able to invite new or existing users to participate in the Project with a particular Role via an email invitation. |
|
168 |
Bug |
Leaving the password field blank on login caused a server error. This was corrected. |
|
354 |
Bug |
Password reset view was case sensitive on email address. This was corrected. |
|
355 |
Feature |
Allow users to log in with (username OR email address) AND password. Note that email address is not case sensitive. |
|
2819 |
Feature |
Username for login is no longer case-sensitive. |
|
327 |
Feature |
Password requirements should appear on screen and in help. |
|
356 |
Feature |
Documented password requirements (Added as Issue for validation documentation tracking reasons) |
|
359 |
Feature |
Prevent users from changing their email address to duplicate another user email |
|
416 |
Feature |
Keep records of when users login and logout. System now keeps a record of login, logout, last activity date/times and IP address on login. |
|
425 |
Feature |
If there have been invalid login attempts prior to a successful login, the user should be warned on successful login. |
|
2820 |
Feature |
If a user enters an invalid username or password the error message shown does not indicate whether the username is valid for security reasons. |
|
2821 |
Feature |
Users can be inactivated in the system by TrialGrid personnel. Users inactivated in this way will not be able to log in and will see a message informing them that they account is inactive/blocked. |
|
417 |
Feature |
Disable user account after a number of invalid password attempts. This is system configurable but currently set to 4 attempts. |
|
426 |
Feature |
After the user has made two unsuccessful login attempts, a warning should appear which shows how many attempts remain before the account becomes locked out and requires a password reset (using Forgot Password functionality) to unlock the account. |
|
436 |
Bug |
If a user had 2 failed login attempts they could no longer log in at all. This was fixed. |
|
2791 |
Feature |
Standards compliance information is shown in all object listings when a Draft is linked to a Standard Library. The listings can be filtered by Compliance status (e.g. matched / modified from library / not found). |
|
2792 |
Feature |
Deviations from the standard (i.e. modified from standard or not found in standard library) can now be explained by users that have appropriate permissions and these explanations can be approved or denied by users assigned to the project with a role that has Manage Standards Approval permission. |
|
2921 |
Feature |
Standards compliance is now calculated for objects in the system. |
|
2922 |
Feature |
It is now possible to perform visual comparisons between a draft object and its library counterpart. |
|
186 |
Feature |
When an object with a standards deviation explanation was deleted, the standards explanations list would not load with an error. This was was corrected. |
|
234 |
Feature |
Exclude CopySource, Needs Restesting and Retesting Reason from fingerprints. "Fingerprints" are a way of taking the properties of an object (Form, Folder etc) and creating a unique identifier (a "hash") from it. When you want to compare two objects and see if they are the same you can compare the fingerprints instead of looking at every property. This change removed CopySource, NeedsRetesting and RetestingReason properties from Objects so that a change in those values is not reflected in the fingerprints since it is not important for "changes" as far as a user is concerned. |
|
197 |
Feature |
Add 'required' entry to library properties for dictionaries and fields. In this release the work was done for Data Dictionaries with Unit Dictionaries and Fields to follow in a later release. |
|
197 |
Feature |
Allow Fields to be Required / Not Required for standards compliance (work for Data Dictionaries already done) |
|
227 |
Feature |
If an Edit Check has been copied from a Standard Library which is not the main Standard Library for the CRF Draft, then the Edit Check will be compared against its source Standard Library. If and Edit Check has been copied from another CRF Draft then the Edit Check will be compared against the main Standard Library associated with its CRF Draft for Standards Compliance. |
|
306 |
Bug |
The 'fingerprint' of Check Steps (used during Standards Compliance) were not being updated correctly when an Edit Check was saved. This has been fixed. |
|
307 |
Bug |
The 'Explain' button in the Form editor was not working. This has been fixed. |
|
308 |
Bug |
The 'Explain' button in the Custom Functions list was not working. This has been fixed. |
|
311 |
Bug |
Standards Compliance filters were not working in the Custom Functions list. This has been fixed. |
|
242 |
Feature |
Users will receive alerts when Standards Compliance actions are taken, for example a user with Manage Approvals permissions will receive an alert when a request for approval is made. Users with Request Approval permission will receive an alert when a request is approved or denied. The number of new alerts will be displayed in the top menu bar. Users may also receive emails when Standards Compliance actions are taken. Users can choose whether or not to receive email notifications in their user profile. |
|
337 |
Bug |
When viewing a Data Dictionary which is linked to a Data Dictionary in a Standards Library, the 'Standard Required' column will display 'Not in Standard' if the Coded Data or User Data String do not match the Library version. |
|
343 |
Feature |
The Standard Library associated with a Form can now be changed to any Standard Library to which the user has access. This will override the Standard Library associated with the Draft. |
|
367 |
Feature |
Users with standards approval permission should be able to view listings of current requests and past requests |
|
420 |
Feature |
At the Project Level provide listings of Standards Approval Requests, Approvals |
|
3974 |
Feature |
Drafts now have a Check Explorer which visualizes the relationships between forms via Edit Checks. |
|
2572 |
Feature |
Matrices can now be created and managed in the system. |
|
2527 |
Feature |
Edit Checks can now be created in the system. |
|
2534 |
Feature |
A listing of all Edit Checks is now provided. |
|
2528 |
Feature |
Existing Edit Checks can now be edited. |
|
2529 |
Feature |
The Edit Check listing now shows CheckActions for that Check and counts of CheckActions if a CheckAction appears more than once for a Check. |
|
2530 |
Feature |
Edit Checks can now be deleted from the Check listing. |
|
2531 |
Feature |
The Edit Checks listing can now be filtered to just valid or invalid Checks. |
|
2532 |
Feature |
The Edit Checks listing can now be filtered to just active or inactive Checks. |
|
2533 |
Feature |
The Edit Checks listing can now be filtered by search text to show only those Checks containing that text in the Check name. |
|
140 |
Feature |
A Form Editor now exists to allow the edit for Forms and Fields. |
|
193 |
Feature |
On opening the Form Editor the page would scroll to the bottom of the Field List which would hide the heading of the page. This was corrected. |
|
2595 |
Feature |
When a Form is created, it is assigned the next available Form Ordinal. |
|
3208 |
Feature |
Data Dictionaries in Libraries may now have a "Master Dictionary" set from the other Dictionaries in that Library draft. Dictionaries in study drafts which make use of this library dictionary can add entries from this master dictionary as an "allowed change". The idea is to support the concept of controlled terminologies. |
|
3412 |
Feature |
The Custom Function editor now has options for indent and dedent of source code. |
|
3413 |
Feature |
The Custom Function editor now has buttons for undo and redo of changes to source code. |
|
3414 |
Feature |
The Custom Function editor now has buttons for search and replace in the source code. |
|
3415 |
Feature |
The Custom Function editor now provides syntax highlighting for SQL and C-Sharp source code. |
|
2576 |
Feature |
A count of Custom Functions now appears on the Draft home page. |
|
2920 |
Feature |
The Form Editor now has a "Standards Control" tab for Forms and Fields that appear in a standard library. |
|
233 |
Bug |
Derivation 'Applies To' is missing after import. 'Applies To' is the datapoint to which the derivation result will be written. This was added to the Derivation on import. |
|
238 |
Bug |
The CQL help page has some formatting issues and needs a link / reference to the Custom Function Templates Page. The formatting was adjusted and a link added. |
|
236 |
Bug |
This issue is related to the Infix Editor and "Intellisense". If a FieldOID was not unique in the study (i.e. existed on more than one Form) then the system would not provide the list of possible coded values for that field. The fix was to detect if the duplicate fields share the same dictionary, if they do then the coded values are shown. If not, the system shows a warning that the Field is not unique. In this case, specifying the Form as well as the Field will allow the system to determine which Field is being referenced and therefore which set of Coded Values to display. |
|
257 |
Bug |
If a Custom Function Template was changed from a Method to a Function type then it was not appearing in the autocomplete list in the Edit Check Editor. |
|
255 |
Bug |
Forms in the SUBJECT folder were not being displayed in the Matrix editor grid. |
|
2575 |
Feature |
A count of Matrices appears on the Draft home page. |
|
225 |
Feature |
Custom Function Template names can now be up to 44 characters in length. 6 characters are reserved for a suffix to be appended when generating a unique Custom Function name from a Template. The suffix will be a colon and a random 5 digit integer value, eg 'TEMPLATE_NAME:12345'. The random suffix is added to ensure uniqueness for each set of parameters with which the template is invoked. |
|
285 |
Feature |
Allow user to create a new Draft. |
|
2479 |
Feature |
The system now has a list of Drafts and a count of Drafts on the Project home page. |
|
232 |
Bug |
Field with format HH nn has no control displayed in Form editor. This issue was fixed. |
|
287 |
Feature |
When changing between fields in the Form editor the Property sheet should remain on the currently selected property type. This has been implemented. Reduces the amount of clicking required to edit fields. |
|
289 |
Bug |
Form Active/Inactive is not updated to database as expected. This was fixed. |
|
198 |
Feature |
There is no ability to add a new Form. This capability has been added. |
|
288 |
Bug |
Delete button in Form list does not work. This has been fixed. |
|
192 |
Bug |
Rave does not permit duplicate Form names or names which contain characters other than _, 0-9 and A-z. Form editor was changed so as not to permit duplicates. |
|
297 |
Bug |
When opening a date field no query for future date appears even if it is reported into the ALS. This issue was fixed. |
|
292 |
Feature |
When trying to upload a file not in Excel 2004 xml format an internal error message was displayed. Now a message 'CRFDraft sheet could not be found' will be displayed. |
|
293 |
Feature |
When uploading an Architect Loader Spreadsheet containing warning and error messages, the warnings were briefly displayed and then hidden when an error occurred. Warnings and errors in the ALS content are now displayed and can be viewed in the Draft upload view. Invalid cross-references (for example a Field referencing a Form OID which does not exist in the Forms tab) will now cause the import to fail with errors. |
|
301 |
Feature |
Expand Draft Editor for Primary Matrix, Primary Form and other elements. |
|
295 |
Feature |
Reorder forms in the form list view. |
|
302 |
Feature |
When deleting a Form or Folder, reorder the remaining ordinals so they're consecutive. |
|
298 |
Feature |
There should be a folder editor to edit and create new Folders. |
|
314 |
Feature |
Custom function templates should be at the URL level. |
|
148 |
Bug |
When creating a new Edit Check the Edit Check must be saved before Unit Tests can be created. |
|
153 |
Feature |
When copying Edit Checks from a Standard Library or another Project Draft, Unit Tests will be copied with the Edit Check |
|
191 |
Feature |
Edit Checks can be copied from a Standard Library or another Project Draft. Copying an Edit Check will copy any Custom Functions referenced by the Edit Check which do not already exist in the CRF Draft. |
|
277 |
Feature |
The 'Copy to clipboard' feature in the Edit Check Editor now copies the entire Edit Check, including Check Actions to the clipboard in Rave quickedit format. |
|
312 |
Feature |
Edit Check Autocomplete now includes autocomplete for Checkbox fields and will display a list of the two possible values for checkbox fields ('0' and '1') when a Checkbox field is being compared against a static value. |
|
320 |
Bug |
Some Check Actions (SetDataPointVisible for example) with checkbox options were always displaying with a checked value. This has been fixed. |
|
323 |
Bug |
An Architect Loader spreadsheet containing EDC Roles with unicode characters failed on import. This has been fixed, for EDC Roles, Marking Groups and Review Groups. Diagnostics 00018, 00019 and 00021 have also been fixed to accept unicode characters in Review Groups, Marking Groups and EDC Roles. |
|
325 |
Feature |
Forms can be copied from a Standard Library or another Project Draft. All Fields in the Form will be copied and any Data Dictionaries or Unit Dictionaries references by Fields in the Form which do not already exist in the target Draft will be copied. |
|
328 |
Bug |
The Form editor now validates that Form and Field Help text can be a maximum of 4000 characters. |
|
331 |
Bug |
Performance of copying Forms has been improved. |
|
333 |
Bug |
Activity records were not being created after updating an Edit Check. This has been fixed. |
|
336 |
Bug |
Saving a Data Dictionary would fail if a Coded Data or User Data String value was longer than 2000 characters. This has been fixed. |
|
339 |
Bug |
When copying an Edit Check any Custom Functions referenced in Check Actions were not being copied. This has been fixed. |
|
344 |
Feature |
Data Dictionaries can now have multiple 'Specify' entries, as in Rave. |
|
345 |
Feature |
Data and Unit Dictionary Coded Data/Units are not case-sensitive, ie. 'mU' is not the same as 'MU', as in Rave. |
|
348 |
Feature |
In the Data Dictionary editor the User String is now displayed before the Coded Data, as in Rave. |
|
349 |
Bug |
Form editor does not warn when a DataFormat is invalid. This was fixed. |
|
329 |
Feature |
Field errors in Form editor not easily visible - errors now reported at the top of the Form page along with any Form property related errors. |
|
313 |
Bug |
Field properties can't be edited without scrolling to end of form. Previously the property sheet automatically positioned at the top of the view area, now it is fixed in place and scrolls with the list of fields. |
|
363 |
Feature |
Warn if a user tries to leave a Form which has not been saved. |
|
364 |
Bug |
Data Dictionary Fields in Form editor overflow the Field Preview Area. This was fixed by limiting the width to 260 pixels maximum. |
|
370 |
Bug |
When a form is copied into a draft the data and unit dictionaries referenced by fields on that form should not be copied if they already exist in the target draft. If a form contained multiple references to the same data or unit dictionary (ie. more than one field referenced the same dictionary) and the dictionary did not already exist in the target then multiple dictionaries were created. This has been fixed. |
|
372 |
Feature |
When editing Data or Unit Dictionaries, the Tab key can now be used to move to the next line. |
|
373 |
Feature |
Warn if a user tries to leave a Data Dictionary which has not been saved. |
|
374 |
Feature |
Warn if a user tries to leave a Unit Dictionary which has not been saved. |
|
375 |
Feature |
Warn if a user tries to leave an Alias which has not been saved. |
|
376 |
Feature |
Warn if a user tries to leave a Derivation which has not been saved. |
|
377 |
Feature |
Warn if a user tries to leave an Edit Check which has not been saved. |
|
378 |
Feature |
Warn if a user tries to leave a Custom Function which has not been saved. |
|
379 |
Feature |
Warn if a user tries to leave a Folder which has not been saved. |
|
4003 |
Feature |
Warn if a user tries to leave a Matrix where Folder/Form combinations have been changed but not saved. |
|
382 |
Bug |
When adding a Data Dictionary from the quick-add in the form Editor the DataFormat for the field is incorrectly set. Fixed. Set to numeric or text ($) format depending on coded data content |
|
383 |
Feature |
When clicking on a pretext label in the form preview/editor focus should move to the property sheet for that field and the pretext field should be selected |
|
388 |
Feature |
View Restrictions / Entry Restrictions and Review Groups should have helpers to make it easier to enter these names |
|
389 |
Feature |
View Restrictions / Entry Restrictions / Review groups tags should be color coded. Blue means present in the core configuration. Orange means not present or not active in the core configuration |
|
390 |
Feature |
A user should be able to copy and paste tags between View / Entry restrictions and Review Groups boxes. Ctrl-C, Ctrl-V recognition and a copy button were provided. |
|
391 |
Feature |
A user should be able to enter a comma-separated list of names for View Restrictions / Entry Restrictions / Review groups |
|
398 |
Feature |
Query Non-Conformant and Field Required are auto-set when creating a field. Rave defaults these to un-set for a new field. Changed to be un-set by default. |
|
401 |
Feature |
On saving a Form, display error if a variable already exists on another form. |
|
405 |
Feature |
Typing @ in the Form Entry / View restrictions or Field Entry / View Restrictions or Review Groups should show a list of possible entries from core configuration |
|
415 |
Feature |
In the Field property sheet it would be clearer to have "Log / Standard" label next to the Log / Standard switch. This was added. Note: This feature was added in a prior release but a test was added to the regression suite in this version to ensure the change was documented and tested. |
|
2818 |
Feature |
On login users should be taken to their home page unless they tried to deep link into a page in which case on login they should be redirected to that page. |
|
3653 |
Feature |
It should be possible to have background tasks (such as uploading drafts) and see the progress of these tasks in the user interface and in historical listings of background tasks and their outcomes. |
|
258 |
Feature |
Added latest Rave releases (up to 2017.1.0) to the selection list available when creating a URL in TrialGrid. |
|
247 |
Bug |
When creating a new EDC Role with Site Role Active an error message appeared "Request to save EDC Role failed!" Issue was fixed so that user cannot switch Site Role / Active switches until the Role Name has been saved (which it does as soon as you exit the field) |
|
286 |
Bug |
When inviting a user to a team, an invalid email address would cause an error message. This was fixed. |
|
283 |
Feature |
It would be useful if the Draft List for a Project had a "last activity" date so you could more easily find the drafts people have been working on |
|
3652 |
Feature |
The system has an alerting feature to notify users of activities they may be interested in such as completed tasks they initiated. |
|
326 |
Bug |
The time displayed against alerts in the alert notification would change to 'a few seconds ago' after 30 seconds. This has been fixed. |
|
335 |
Bug |
Data Dictionaries with long User Data Strings were expanding to overlap the Standards Compliance panel. This had been fixed and the Data Dictionary Entries table will resize when the browser window is resized. |
|
341 |
Feature |
Marking and Review Groups in URL Configuration should always have unique names. |
|
360 |
Bug |
Changing EDC Roles causes timeouts. Added waits so that the system cannot have multiple queued requests to change EDC roles at any one time. e.g. If you change one Role you have to wait for that to save before you can change another. |
|
362 |
Bug |
When changing EDC Roles and Review Groups, Saves can be very slow. Performance was improved. |
|
321 |
Bug |
Add new Data Dictionary on Add Form is not wide enough. This was fixed. |
|
371 |
Bug |
On Internet Explorer, navigating away from every page causes a "Do you want to leave this page?" alert. This has been fixed. |
|
405 |
Feature |
Typing @ in the Form Entry / View restrictions or Field Entry / View Restrictions or Review Groups should show a list of possible entries from core configuration |
|
340 |
Bug |
Requirements test coverage for Core Configuration settings was expanded. |
|
351 |
Feature |
Validation Docs: Link between Issues / Merge Requests. |
|
352 |
Feature |
Validation Docs: Link between Requirements tests and Issues. Where an Issue is referenced in a Requirement Test the validation docs now generate a hyperlink to a copy of the Issue and its history in the validation package for ease of traceability. |