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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 60 Next »

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


Ability to Search on Manage Item Bank - Add Content - Collections


Available from

1808 (approximately August 2018)

Rollout pace

Full roll out - users will have immediate visibility as a result of upgrade


Add/Remove content feature, available through Manage Item Bank screen, does not allow users to filter collections fulfilling certain criteria thus restricting its use. As a result, we intend to bring search functionality for Collections similar to how it exists for Cases & Questions.

  • The change makes it possible to search for Collections on Add/Remove content screen.

  • It will not be possible to save a search with certain criteria.

Removal of the Edit Exam Group page


Available from

1808 (approximately August 2018)

Rollout pace

Full roll out - users will have immediate visibility as a result of upgrade

Last updated



In order to make ExamDeveloper more streamlined, we are retiring Edit Exam Group page which has very low usage.  Most of the functionality (addition / modification and deletion) on this page is redundant and is available elsewhere in the ExamDeveloper.

The Edit Exam Group page will be replaced by the ability to allow users to change the Exam Group name, which can not be edited anywhere else in the application.

Cases: Separating the split screen exhibit from the case


Available from

1809 (approximately September 2018)

Rollout pace

Full roll out - users will have immediate visibility as a result of upgrade

Last updated9-August-2018


Case lead-in text is intimately linked with the case, but this makes it difficult to define whether a case is a question type, a grouping of questions, an exam section or a supporting display exhibit, which make cases near-impossible to enhance and maintain without impacting other areas of the application.

We are taking steps to more robustly define and separate the individual components that make up a case, so that we can deliver additional case enhancements in future. This will result in the following initial changes:

  • New and existing case lead-in text and language will be treated as a display-only question type (referred to now as a case exhibit) with its own history and Question ID.

  • Users will have the ability to search for case exhibits and set metadata, enemies, blueprints, advanced properties, etc. against them, but configuring this data will not initially be available on the add/edit case page.

  • The case exhibit blueprint will be ‘Unassigned’ by default.

  • The case exhibit language and lead-in text will remain attached to the case, editable via the same pages, and deliverable to candidates in the same way.

  • Case exhibits will show up in the split screen exhibits menu when modifying a case question alongside stand-alone exhibits, and it will be possible to sequence the tab display order alongside stand-alone exhibits that don’t belong to the case, for that question.

  • When a case is deleted, it will be possible for the case exhibit to remain attached to the case questions in the project (as a stand-alone exhibit), but the ‘grouping’ of questions will no longer exist.

  • When a question is removed from a case, the case exhibit will be removed from that question automatically.

  • It will be possible for writers to submit the case exhibit for review (it will be reviewable independently like any other display-only question type), and they will not be able to edit the case exhibit while it’s not in a Draft or Rejected state.

  • Clicking ‘Submit All’ on the add/edit case page will also submit the case exhibit for review, alongside any case questions.

  • Case enemies and language will become part of the case exhibit. Consequently, exams and sections will check for exhibit enemies when saving.

  • A new case revision will be created whenever a user:

    • Changes the case name.

    • Adds or removes a question on the case.

    • Reorders questions on the case.

    • Changes the lock response configuration for questions on the case.

  • Changes to case exhibits and questions on the case will not create a new case revision, but they will create a new question revision.

  • A user will always see the latest revision of questions and case exhibits that are attached to the revision of the case they’re viewing.

  • When sharing case questions or case exhibits across projects, then the case (and other questions on the case) will be automatically shared in the same way.

  • When performing a question search by Case Name, if no case name is provided then the search will return questions that are on any case in the current project, instead of all questions in the project (regardless as to whether they are on a case or not.)

  • It will no longer be possible to search for assets by the ‘On Case’ criteria.

  • It will no longer be possible to search for questions by the ‘Order on Case’ criteria.

  • When performing a case search:

    • It will be possible to search by Case ID (which will no longer contain the case exhibit language), Case name, Case exhibit language, and Case exhibit text, and On exam form on the view cases, build section, build exam and case project sharing pages.

    • It will no longer be possible to search for cases using the following criteria: Editable On, Viewable On, Written By, Date Written, Date Modified, On Exam Section, Question ID, Blueprint ID, Type, Stem Text, Option Text, Question Metadata, Comments, External Id, Reviewed by, On Collection (Note that this does not affect searches that return questions instead of cases.)

  • The error that prevents cases from being saved if it contains two questions that are enemies of each other will be removed.

  • When importing an enemy relationship for a question or exhibit that is on a case, other questions on the case will no longer automatically be made enemies (e.g., Item A is made an enemy of Item B, which is on a case with Item C; Item A will no longer automatically be made an enemy of Item C, but it will be possible to set this relationship manually or by using the enemy import spreadsheet).

  • It will be possible to see how many questions are on the case on the view cases page.

  • The case ‘type’ column will be removed from the application.

  • The section and exam imports (in XML and XLS format) will allow users to add case questions using the <question> element instead of the <case> element.

  • On the enemy import spreadsheet, if a user sets a question as an enemy of a question belonging to a case, ExamDeveloper will no longer make other questions on the case enemies automatically. Users will still be able to define enemy relationships with other case questions manually via the spreadsheet.

  • Case lead-in text will be removed from the newest custom report.

  • The question import templates will be updated to create cases in a different way:

    • On the spreadsheet import, the cases tab will be removed and replaced with columns to indicate the case name on the questions tab.

    • On the XML import, <case> will be removed and instead case exhibits will be created using <question> (marked as a display type). It will be necessary to reference the case name from both the case exhibit (using a new <case> element), as well as from any questions that should be attached to the case (using the existing <exhibit> element).

Cases: adding a subset of case questions to a section or exam


Available from

1809 (approximately September 2018)

Rollout pace

Full roll out - users will have immediate visibility as a result of upgrade

Last updated



Today, if a case is added to an exam or section, then all questions on the case must be added. We intend to enhance the application to the point where it is possible to add individual case questions to an exam, without forcing the user to add all other questions on the case. This will result in the following behaviour changes to the add/edit exam and section pages:

  • The ‘Add cases’ tab will be removed.

  • It will be possible to search for case questions on the ‘Add questions’ tabs, and add them individually to the exam (like any standalone question works today.)

  • It will be possible to see which case a question belongs to on the build section / exam pages.

  • If case questions are on a section or exam, and more questions are added to the case, these will not automatically be added to the section/exam.

  • If case questions are on a section or exam, and those questions are removed from the case (or the case is deleted), these will not automatically be removed from the section/exam.

  • The section and exam imports (in XML and XLS format) will allow users to add a subset of case questions.

  • When adding case questions directly to an exam, if the project configuration setting ‘Export cases as sections’ is checked, then a section will automatically be created for each case being added. (If the setting is unchecked, then case questions will continue to be added to the ‘Unsectioned’ section that is automatically created.)

  • When an exam or section is published, the latest revision of standalone exhibits will now be ‘locked in’, just like case exhibits and questions are. (Note that assets will still not be a part of the locked in content.)

  • When saving a section or exam, there will be a check for exhibits that are enemies of each other, or of other questions, on the same section / exam.

  • The ‘Selected’ tab will be removed.

  • It will be possible to reorder questions and sections on a new tab named ‘Contents’, which will replace the existing ‘Questions’ tab.

  • It will no longer be possible to create more than one ‘Unsectioned’ section (e.g. in the instance where a user had a selected tab contains a question followed by a case or section, followed by another question.)

  • When new questions are added to an exam or section, ExamDeveloper will add them to the end of the existing section, starting with standalone questions (in Question ID order), then case questions (first by Case name, then by Case question order.)


Rich Text Editor upgrade


Available from

1809 (approximately September 2018)

Rollout pace

Gradual roll out - users will have visibility over several releases


We are enhancing the Rich Text editor in ExamDeveloper to the latest version. We will also be streamlining the editor to allow only the HTML elements that are supported by the Pearson VUE test drivers. The upgrade will not only result in enhanced user experience with content authoring, it will also lead to UI being more consistent with content rendering in Pearson VUE test drivers.

The editor is used to author Metadata (Block Text), Comments, Item contents (Stem and responses), References and Cases. Upgrade will be gradual, starting in 1809, first feature to roll out with the upgraded editor will be Metadata (Block Text).


For more details on the supported HTML elements and changes see the ?? topic.


Removal of ability to edit statistics on the statistics tab, when viewing a question


Available from

To be determined

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Last updated14-June-2018


From the feedback we have received from statisticians/psychometricians, the current ability to import and export statistics in ExamDeveloper is the preferred process for statistics management, and they’d like to ensure that other users do not have the ability to alter statistics when viewing a question.

As a result of this feedback, whenever a user views a question in ExamDeveloper (such as on the Examine, Observe and Review Question pages, etc.) and they navigate to the statistics tab, they will continue to have the ability to select an analysis group / set to view statistics, however, it will no longer be possible to edit the statistics / default flag on these pages. 

Branching configurations in a review workflow


Available fromTo be determined
Rollout paceGradual roll out - users will have visibility over several releases
Last updated 


In ExamDeveloper it is currently possible to set up a review workflow that forces a reviewer to do one of two things:

  • Accept the question, which moves a question to the next state in the workflow
  • Reject the question, which moves a question to any previous state in the workflow.

We will enhance the configurability around this decision making process, to give managers greater control over where their reviewers can send questions in the workflow:

  • ‘Accept’ and ‘Reject’ will be renamed ‘Advance’ and ‘Return’ respectively, in order to indicate the direction that an item is travelling in through the workflow.
  • For each review state, project managers will be able to configure the ‘outcomes’ that are available to the reviewer when they decide to advance or return an item:
    • An outcome is given a custom name.
    • It will be possible to configure what the next state will be for a given outcome, including Returned (previously ‘Rejected’), other Review states, Validate, Completed and Obsolete.
    • Outcomes will make it possible to:
      • Allow reviewers to skip a state when advancing a question.
      • Restrict the reviewer to a specific state or states when returning a question; or offer no ability to return a question.
      • Require a reviewer to add a comment when advancing a question.
      • Configure whether the reviewer should decide to retain statistics or not (i.e. automatically retain them without offering the choice.)
    • If multiple reviewers are required to advance or return a question, then the last reviewer required to trigger the state change will continue to choose the outcome.
  • A reviewer will be able to modify a question during review and save their changes without that modification automatically counting as advancing the question.
  • Question history  / user tracking will reflect the outcomes and path that a question took through the review workflow at the time, even if the project’s review workflow configuration is modified later.
  • The user tracking tab will continue to reflect the review workflow in the order that it is sequenced, meaning:
    • If an outcome returns a question to a previous state in the workflow, then user tracking is reset back to the new state.
    • If an outcome advances a question through the workflow, and a state is skipped, then the latest question revision will show that skipped state as ‘Not reviewed’.
  • Existing review workflow configurations will continue to behave as they currently do, but can be updated to take advantage of the new functionality.


  • No labels