Reports, archives, extracts, and notifications
The Archival PDF is not generated properly when a site user is deleted
Sponsor users: In the Archival PDF, the Subject Archives PDF is now generated appropriately even though the site user who entered data for a subject is deleted from a study. Previously, when the site user who collected data for a subject was deleted from a study, the Subject Archives PDF did not generate as expected. (Issue 34412995)
The Subject Events report takes longer to generate than expected
Site and sponsor users: Now, when you run the Subject Events report you will no longer notice that it takes longer than expected to generate the report (in any mode or format). Previously, running the Subject Events report either took longer than usual or you could not generate the report at all. This was a database issue that has now been fixed by implementing a clearing mechanism to ensure that the performance of reports is optimal going forward. (Issue 34399461)
The Archival PDF takes a long time to generate
Sponsor users: Now, when you run the Archival PDF in a study that contains a larger volume of data, you will notice that the archive is generated in the expected amount of time. Previously, the system may have been slow and your Archival PDF took too long to generate.
This issue was due to the queryDetails API endpoint. The API did not properly retrieve the study version associated with the Archival PDF and this affected the system's performance. (Issue 34161625)
Kit Dispensation report displays data from all sites
Site and sponsor users: When you run the Kit Dispensation report, and select a specific site for the Location setting, you may notice that the report displays data from all sites in a study. Instead, the report should only display data for the specific site you previously selected. (Issue 34294108)
The Subject Query report must not display data on candidate or deleted queries
Site users: Now, as a site user, when you're running the Subject Query report you will notice that you can no longer see data on candidate queries or deleted queries. That is the expected behavior, since only sponsor users should be able to view data on candidate or deleted queries. (Issue 34091418)
The Subject Events report displays data discrepancies (former known issue)
Sponsor and site users: Now, when you generate the Subject Events report, you will notice that data related to event instance numbers is properly displayed, even if you run this report at the same time with other reports in the system. Previously, you may have noticed certain data discrepancies in this report. This issue was caused by the use of multiple data columns (in the application's backend) for multiple reports at the same time.
Retracted workaround: You no longer have to actively avoid running multiple reports at the same time. For example, you can now run the Subject Data report and the Subject Events report at the same time. (Issue 34060530)
Values in the Subject Query report are not properly displayed in Japanese
Sponsor and site users: In the Japanese version of the Subject Query report, all values in the Query State column are now displayed in Japanese, as expected. Previously, values in the Query State column were displayed in English. (Issue 33130514)
Subject Data Extract in a CSV format is empty
Data managers and statisticians: You will no longer run the risk of generating a Subject Data Extract (in a CSV format) that is completely empty. This issue was caused by a database limitation, where data records that exceeded a certain character limit were not displayed in the extract at all. (Issue 34135585)
Deleted columns displayed with an incorrect status in extracts (former known issue)
Data managers and statisticians: Now, in a Subject Data Extract, modified data records are no longer displayed as deleted. Instead, when a data record is modified by a site user, its status is properly reflected in the extract. Previously, you may have noticed that certain data records were displayed as deleted, even though they were still present in the application. This issue could be observed when a site user opened the application in multiple browser sessions and updated the same data record in different ways (for example, they removed the data record in one session and then modified the same data record in another session).
Retracted workaround: None. (Issue 33743917)
The CPORT format is now clearly displayed for SAS extracts
Data managers and statisticians: Now, when you extract subject data in a CPORT format, the extract displays the .CPT extension that is needed to differentiate between extract formats. Previously, this extension was not displayed. (Issue 34227314)
Tool tips for reports are not displayed in the preferred language
Sponsor and site users: Now, when you change your application's preferred language after having generated reports in your study, you may notice that the report-related tool tips appear in the preferred language, as expected. Previously, if you switched between preferred languages during the generation of a report, you may have noticed that the tool tip texts were displayed using a mix of English and Japanese. (Issue 33103591)
Japanese characters are not displayed in a SAS dataset (former known issue)
Data managers and statisticians: Now, Japanese characters are displayed correctly in a Subject Data Extract generated in a sas7bdat format. Previously, Japanese characters were not properly displayed in this type of data extract. This issue was encountered when you opened the SAS dataset with SAS Universal Viewer, version 1.5.
Retracted workaround: None. (Issue 33279322)
Column name in the Subject Queries report might be confusing (former known issue)
Sponsor users: Now, both the Subject Queries report and the Subject Data report display a column called Repeating Section Number, as expected. Previously, the column was called Repeating Form Number without taking into account the number of repeating form instances in a two-section form.
Retracted workaround: None. (Issue 33508078)
The User Assignment and User Assignment by Site reports do not display correct data for removed users (former known issue)
User administrators: Now, after a user is removed from a study, the Status column is updated with a new status of "Removed" for that specific user, as expected. Moreover, when you add a new user to a study, its status is displayed as "New" in the report. After the newly added user signin in the application for the first time, their status is displayed as "Active" in the report. Previously, a user that was removed from the study was still displayed with a status of "New/Active" in the User Assignment reports. This issue occurred when you included historical data in your reports.
Retracted workaround: None. (Issue: 34018392)
Candidate or deleted queries should not be displayed in the Subject Queries report for site users
Site users: Now, when you run the Subject Queries report, you can only see the queries that you are also allowed to see on the user interface (typically queries with a status of Opened, Answered, or Closed - depending on your permissions). Previously, as a site user, you could also see queries with a status of Candidate or Deleted, even though you did not have the permission to view or manage those types of queries on the user interface. (Issue 34091418)
Parent topic: Fixed issues