Navigation Menu

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

.

Versions Compared

Key

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

...

Coming soon to ExamDeveloper 

Preserve incomplete review / validation data during batch edit  

Available from1908 (approximately August 2019)
Rollout paceFull rollout - users will have immediate visibility as a result of upgrade
Last updated11 July, 2019

In the event that an item has been partially reviewed (but additional users are still required to agree on a decision to trigger a state change), then any modification that results in a new revision will reset the review for the current state, necessitating a ‘re-review’ of the item.

This enhancement will enable a project manager to override this rule during a batch edit, so that a partially complete review can continue where it left off, with the updated data, without requiring a ‘re-review’.

Note: this setting is ignored on review states that:

  • Only require one reviewer to complete. 
  • Have not been started. 
  • Have already been completed. 

Image Removed

Translate Questions permission and Translate Assignments

...

Batch Clear Formatting 

Available from1910 1909 (approximately October September 2019)
Rollout paceFull rollout - users will have immediate visibility as a result of upgrade
Last updated 12-September-2019

ExamDeveloper Batch Edit feature will be enhanced with this work. It will have the ability to remove font-face and/or font-size using Batch Edit. There will also be an option to clear all formatting through Batch Edit.

Ability to upload and use Audio files 

Available fromTo be determined1909 (approximately September 2019)
Rollout paceFull Gradual rollout - users will have immediate visibility as a result of upgrademay gain visibility over several releases
Last updated 12-September-2019

ExamDeveloper will support audio (.mp3, .wav, and .ogg) file types after this work. Users will be able to add these file types to the asset library, and attach them to item content.

...

  • In Project.json, in the metadata element, key 'editor' will be renamed to 'type' and 'appliesTo' will be renamed to 'displayOn"
  • In question.json, the stateName property (which is always null) inside the stateinfo element will be removed
  • In question.json, in the userTrackingInformation element,
    • the stateLabel property (which is always null) will be removed
    • the reviewAction property will have possible values of 'Advanced' and 'Returned' instead of 'Accepted' and 'Rejected'
    • the outcomeState property will be null (not 0) when there is no outcome
    • the sortOrder property will have a value and not be 0
    In Report.json, the Quetions property typo will be corrected to Questions inside the Context element

...

Custom report updates 

Available fromTo be determined1911 (approximately November 2019)
Rollout paceGradual rollout - users may gain visibility over several releases
Last updated 12-September-2019

The following JSON data will be exported in an improved format to be consistent with the user interface: 

For metadata:

  • editor will be renamed type.
  • type will show the user interface name (e.g., Dropdown List, Block Text, etc.) instead of a number.
  • appliesTo will be renamed displayOn.
  • displayOn will show the user interface name (e.g., Question, Exam, Asset) instead of a number. 

For review workflow:

  • reviewStateName (e.g., Review 1, Review 2, etc.) will now show the name of the review state.
  • stateName is not populated and so will be removed.

For user tracking information:

  • state will be added (e.g., Draft, Review, Completed, etc.)
  • reviewStateName will be added (e.g., Review 1, Review 2, etc.)
  • stateName is not populated and so will be removed.

...

to provide key-value pair mappings, for values in Project.json and Question.json files: 

  • LookUp.json file: will contain the element and its key-value pair details in JSON format
  • Users.json file: will contain - userID, Firstname, Lastname, and Username details of all the users who contributed to the items in the extracted JSON export
  • In existing question.json, userTrackingInformation element data will be exported in an improved format:
    • The stateLabel property (which is always null) will be removed
    • reviewAction will have possible values as Advanced and Returned instead of Accepted and Rejected
    • outcomeState will be be null (not 0) when there is no outcome
    • sortOrder will be a value and not 0

Changes to default scoring for Display, Essay, and Compound items

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

In an Exam publisher, it is most likely that Display, Essay, and Compound items will be unscored. However, when these types are added to an exam, they're marked as 'scored' by default. Therefore, with this change, these item types will be marked as unscored by default when they are added to an exam.

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.)