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.
Comment: 2005 updates

...

Coming soon to ExamDeveloper 

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.

Image Removed

References: Edition field for Book references

...

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

Changes to

...

error notifications for Validators

Available fromTo be determined2005 (approximately May 2020)
Rollout paceFull rollout - users will have immediate visibility as a result of upgrade
Last updated 

When Validators validate 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.

, they do not receive any errors if the item is missing required Metadata or if the Asset attached to the item in in an incomplete state. Moving forward, users will start getting error messages when the item advances to the Validate state if the item is missing required Metadata and/or if the item includes incomplete Assets.

Legacy custom report retirement 

...