Navigation Menu

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

.

Skip to end of metadata
Go to start of metadata

Disclaimer: in order to ensure we make the right decisions for the future of the application, we may change or remove the information that appears here at any time

Coming soon to ExamDeveloper 

Removal of 'Ignore Item Level Shuffle Response' setting

Available from2003 (approximately March 2020)
Rollout pace Full rollout - users will have immediate visibility as a result of upgrade
Last updated 

For QTI templates and packages, the Ignore Item Level Shuffle Response configuration highlighted in the screenshot below will be removed:

The Shuffle Response property in both the item Advanced Properties menu and the QTI PearsonSectionControl node will not be affected.

In the past, Ignore Item Level Shuffle Response has enabled users to ignore/omit the Shuffle Response property set in the Item Advanced Properties menu, when set to Yes or No. However, the new best practice is to have a value of Not Set when the user wishes to rely on the section attribute instead of the item attribute, per the screenshot below.

Note that this property can be set as the default for new items and/or batch edited for existing items.

Enhanced Matching items Scoring - option to use Add or Set

Available from2003 (approximately March 2020)
Rollout pace Full rollout - users will have immediate visibility as a result of upgrade
Last updated 

The current Advanced Scoring for Enhanced Matching only allows for the correct responses to Add correct combinations and does not have the option to Set. Also, the maxvalue adds up all the values of the possible outcomes and does not have an option to select the value with the highest score.

This change will allow users to decide to use Add or Set in Advanced Scoring for Enhanced Matching items. And, if Add is selected the maxvalue will be a sum of all the correct combinations. If Set is selected then the maxvalue will be the highest value.

JSON export: new property 'modifiedByFullName' added to Question.json

Available from2004 (approximately April 2020)
Rollout paceFull rollout - users will have immediate visibility as a result of upgrade
Last updated 

In the JSON export, the Question.json file will be enhanced to include a new property 'modifiedByFullName'.

In addition, for the first revision, the 'modifiedBy' property will be populated with the userID who created that revision. Currently it is null for the first revision.

For consecutive revisions beyond the first revision, the 'modifiedBy' property will continue to be the userID of the user who modified that revision.

Item Cloning enhanced to choose whether or not to copy Comments

Available from2004 or 2005 (approximately April 2020 or May 2020)
Rollout paceFull rollout - users will have immediate visibility as a result of upgrade
Last updated 

Currently, when cloning items, all of the items' Comments are copied over to the newly created cloned item. With this enhancement, users will now have an option to choose if Comments should be copied. Also, the External ID will not be copied over to the newly cloned item regardless of whether the comments are copied over to the newly cloned item.

References: Edition field for Book references

Available from2004 - 2006 (approximately April 2020 to June 2020)
Rollout paceGradual rollout - users may gain visibility over several releases
Last updated 

For Book references, there is no dedicated field for Edition. With this change, a new Edition field will be added for book references. This field will be configurable in Project settings like other reference fields.

The initial roll out will allow Adding, Batch Editing, and Configuring the Edition field.

Subsequent roll outs will:

  • Display additional data for reference searches
  • Include the Edition field in reports, imports, and exports
  • Improve the user interface to promote Searching before Adding
  • Merge Duplicates
  • Improve Batch Edit references

Changes to project sharing rules for items and cases

Available fromTo be determined
Rollout paceFull rollout - users will have immediate visibility as a result of upgrade
Last updated 


When an item or case is removed from a project, it is automatically added to the default 'itembank' project, which is not desirable behavior for many managers. We will be changing the rules around item and case sharing so that:

  • Users will not be able to remove an item or case from the current project if it is editable. They will see an error if this is attempted.

  • A user will still be able to make the item or case editable in a new project; doing so will also continue to make the item viewable in the old project.

  • Users will still be able to remove an item or cases from the current project if it is viewable. Furthermore, it will now be possible to remove the item from the default ‘itembank’ project.
  • Making items and cases editable, viewable or removing them from projects will no longer also share them automatically into the default ‘itembank’ project (this will now need to be a manual action.)

Note: this change will have no impact on sharing exams, sections, or collections, etc.

Legacy custom report retirement 

Available fromTo be determined
Rollout paceFull rollout - users will have immediate visibility as a result of upgrade
Last updated 

By introducing the most recent custom report available to Project Managers on the Manage → Reports page, we are left with three older custom reports that have now been surpassed and are due for retirement. We will be removing the following three custom reports from ExamDeveloper:

  • Question Data
  • Question and Statistics Data
  • All data

Project Managers who are still working with these reports should switch to the custom report available at Manage → Reports (in the Custom Reports tab).

 

 

  • No labels