...
ID | Functional Area | Fixed issue | Impact/Risk | Includes Web- services | ||||
|---|---|---|---|---|---|---|---|---|
1438 | Form Saving | Populate Conditions were not functioning if the field being populated was blinded to the saving user | Low | 1357 | Form Building | When creating child forms, field blinding had to be reset if it was being used on the parent form. Not anymore. | Low | X |
1384 | Data Management/Monitoring Reports | Consent Report was not showing column headers in light mode | Low | |||||
1381 | Form Saving | If a form tab is conditionally hidden, edit checks were still running on that tab | Low | |||||
1386 | Subject ePRO | Subject list of completed forms was not displaying records if more than one form was being collected | Low | X | ||||
1401 | Form Building | Editing query deployment on edit checks was not enabling the save button | Low | |||||
1299 | Form Building | Checkbox field with embedded text label now automatically adjusts width based on text length | Low | |||||
1415 | Form Building | Copy and paste of conditional actions dropped choice field criteria at the destination field | Low | |||||
1419 | Query Management | Query override on edit checks was still displaying queries to the default distribution | Low | |||||
1043 | Query Management | Query email notifications were not being triggered when queries were manually added via the app | Low | X | ||||
1391 | ePRO/eDiary Configurations | Event driven diary types were not enforcing the max forms value that was set based on the diary configuration | Low | X | ||||
616 | Form Building | Visit based expressions within conditional actions would not work if the expression was built on the web and the selected visit existed only in one out of many cohorts | Low |
...