Navigation Menu

Click the "+" to see inside a chapter or use the search to the right.


Child pages
  • Known Issues in Releases

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Title (Internal #)DescriptionWork Around (if known)Fixed in Release
Custom Reports exporting without Metadata (D-35383)

Custom Reports were exporting without data in the Metadata columns.

 The All Data report from Manage - Project Bank - Generate Report search will pull the required metadata information. This report is NOT available from the Manage - Reports tab.PENDING




Title (Internal #)DescriptionWork Around (if known)Fixed in Release
Batch Adding/Removing Exhibits Erases User Tracking (D-35095)

When Batch Editing Exhibits (Adding/Removing) on items with exhibits - standalone/case - it was discovered that the User Tracking data would be erased for the current review state.

 No workaround identifiedPENDING
1906 (Patch)


7.1904 Release

Title (Internal #)DescriptionWork Around (if known)Fixed in Release
Failure to Change Item State from Completed (D-34697)

1) When Items were batch edited from the "Completed" state, they would not move to the intended review state. The error log from the batch edit report would indicate a 500 error for all attempted items.

2) Modifying Item State manually as a Project Manager away from the "Completed" state would also not complete the intended move. This is accomplished via the Question State dropdown at the bottom of the Examine Question page.

 Move items to the Validate state, and then to the intended review state. Users will need to configure the Project Settings to allow for 1+ users to validate questions in order to get this state to appear.7.1905
Adding Collections to Projects adds all Item Bank Collections (D-34920)As an Item Bank Manager, when collections were added to projects, the "All" selection would return all Collections within a given itembank instead of the given search criteria. This resulted in many more collections being added to the project than specified.The collections can be selected individually and added without issue. The issue seems tied to the "All" dropdown when the search has been expanded to the larger item bank. Note that the search criteria works appropriately, but the "All" dropdown retrieves more than specified.PENDING7.1906


7.1903 Release

Title (Internal #)DescriptionWork Around (if known)Fixed in Release
Changing an item type duplicates Comments (D-34409)

When a preexisting question that contains comments has its Question Type modified all comments contained on that Question will be duplicated

Cannot Center Align Images (D-34478)When center-aligning or right-aligning an image within a stem, the image would revert back to its default left-alignment once submitted. This occurred when users clicked the image directly and then selected the alignment.If users move their cursor either before OR after the given image and set the alignment, the alignment will stay set after the item is submitted.7.1905


Title (Internal #)DescriptionWork Around (if known)Fixed in Release
History tab not working upon second view (D-33023)

It was discovered that the history tab was not responding after the initial view. The tab would not open after being viewed the first time. This was happening in a few locations:

1- Question Summary - accessed from clicking on the Stem under "Create Exam Form". Also via "View Item Bank" and clicking on item stems after returning a search.

2- Review Questions - Any Reviewer with a question assignment will see this behavior.

3- Observe Questions - Anyone with an Observer role.

Navigate away from the selected item, and then back to the item. The History tab will be viewable again. This is applicable when examining in lists. Users can also refresh their browser page to reload the item.7.1902
User Batch Activate Not Working (D-33338)The option to Batch Activate users from the Manage Users page is unresponsive.Users can activate users individually.7.1904
Reporting Group Validation Warning (D-33291)Users have reported a validation warning when viewing generated reporting groups on the QTI builder page that states "This Reporting Group's blueprint does not come from the underlying project's blueprint document. Please regenerate this reporting group"We've discovered that this warning has no bearing on exam build and has impact on the reporting group data that is extracted in the QTI. No workaround required, users can proceed with the export without issues.7.1903
Preventing Advance/Return of items after mandatory metadata is set (D-33078)When an item has a mandatory metadata field set on it and a reviewer is looking at the item, it will be seen that the Advance/Return buttons are disabled (as expected) due to the metadata field not being set. If the Reviewer goes in and assigns the value and then uses the Save/Finish Later button to close the item the system will not allow the Reviewer to choose the Advance/Return buttons to move the item and the message will still show that the mandatory metadata fields needs to be added.There are a couple of ways to avoid this issue. The first is that the Reviewer can choose the Advance/Return button on the Modify screen when they add the needed metadata value instead of the Save/Finish Later buttons. The other option is to hit the previous button or navigate away from the page and then go back to choose the Advance/Return button on the Examine page.7.1902
Users allowed to Approve items with Incomplete Assets (D-33088)When an item contains an asset that is not in a Completed state, a Reviewer is able to Choose to Advance the item to complete. The system should prevent the item from going to complete and show a warning that the asset is not in completed state. 7.1902 
System showing incorrect message when required Blueprint is not set (D-33091)When a project setting is turned on to require a Reviewer to classify items to a particular level, a reviewer should not be able to choose Advance/Return on the item until that blueprint level is set. In this case, the Reviewer will see the message that the required blueprint is not assigned and can go in an modify the item to add it. From there, if the Reviewer chooses the Save/Finish Later button to move away from the item, they will still see the warning message and not be able to click on the Advance/Return buttons on the examine page.There are a couple of ways to avoid this issue. The first is that the Reviewer can choose the Advance/Return button on the Modify screen when they add the needed blueprint level instead of the Save/Finish Later buttons. The other option is to hit the previous button or navigate away from the page and then go back to choose the Advance/Return button on the Examine page.7.1902 
Synchronization Error within Review Assignment (D-32064)

Users have reported an issue with the following error within review assignments:

“The Question can not be modified because the server expects to see another question in its place. This could be the result of a synchronization problem. Please use the top menu to navigate back to the page from where you came and try again.”

This occurs when simultaneous users are modifying items. It may be seen by certain users within the same given review assignment.

When this error appears, the modifications to the given item will still be saved. No workaround is necessary; users can move to the next item.7.1903
Batch Removal for multiple Pop up exhibits not working (D-34138)When items have multiple popup exhibits attached to them and a user tries to batch remove one of the exhibits from the item, it doesn't remove correctly and leaves a blank properties setting on the item. This will also make it so QTI will not export for the items and the popup will not be seen in Preview.Edit the item and remove the popup exhibit from the Modify Item screen.7.1904
Case Exhibit Showing up Twice in Collection DOCX format (D-33638)When Cases are included as part of a Collection Word Export, there were reported instances where the case exhibit item was duplicated within the report.This issue applies to the collection export only. The current export recommended for Case items is the Section or Exam DOCX export, which will not have this issue. Issue ONLY applies to the Collection DOCX export when associated with Case items.PENDING7.1906

7.1812 Release 

Title (Internal #)DescriptionWork Around (if known)Fixed in Release
Reference Requirement Ignored on Case Questions (D-33065)If a project config requires references AND allows for the creation of new cases it has been found that users are able to submit case questions without entering a reference.No workaround identified.PENDING
"Margin" string prevents item save/submission (D-32689)

If an item contains the string "margin" followed by any numeric values (doesn't have to be consecutively) wrapped within a Span tag (present in the HTML source when you specify font size, style or color), AND there is additional text after this declaration also wrapped in a Span tag, the system will not allow users to save or submit items.

If font styles need to be declared add an additional declaration before the numeric values as in the example below:


7.1812 Patch
Check Spelling Link not checking spelling (D-32909)The "Check Spelling" functionality only works within the currently selected box - Item Stem or Response option. When clicked, it only runs a check for the selected box, and disregards the other boxes. For example, if stem is selected, the spell check on all response options is not run.Users can Click the "Check Spelling" button for each text box within an item. Also - the "Check Spelling" function under the editor can be run on each text box individually.7.1901
Decimal Margins within Tables from Word (D-33407)Users have reported issues with table margin-bottoms designated as .0001pt. These margins will not allow the item to submit properly. These margins are byproducts of a Microsoft Word export. Tables pasted from Word may have this issue.Workaround requires users to replace ".0001pt" values with "0pt". Other option is to recreate table in the ExamDeveloper table editor.7.1901
Duplicate Sections not assigning Placeholders Correctly (D-33175)

When duplicating parent sections that contain placeholder sections, it was discovered that the Placeholder sections would assign additional placeholder sections when applied to an ExamForm. This can be seen on the "Build QTI Package" screen when exporting a QTI package. In particular, it appeared that ALL remaining placeholder sections would be applied to the duplicate section instead of those designated in the template.

Users creating templates can create sections manually instead of using the "Duplicate Sections" feature. This will create the appropriate number of placeholder sections without adding additional placeholders.PENDING