Author: Simon

1.0.4

Added

• notifications framework implemented

Fixed

• error when trying to complete a multi page form via nomination on dashboard
• regsitering supervisors links correctly when user tries to manually enter known email address

1.0.3

Added

• added message about SSO and activation link to profile page
• cetegorised New Assessment Menu

Changed

• removed training history from exams section

1.0.2

Added

• prompt trainees for GMC number when not present
• supervisor/deanery admin can manually refresh trainees exams screen

1.0.1

Fixed

• bug preventing career history displaying

1.0.0

Added

• show evidence in modal dialogue when inspecting coverages
• automatically filter for completed assessments on supervisor's view
• removed the underline from the 'required' asterisk and coloured asterisk red to highlight
• career history screen now shows additional fields specialty, FT equivalance and labels OOP posts where appropriate

Fixed

• correctly show control labels on checkboxes elements
• use the title of the learning objective as the main heading on PDP
• bug preventing competency mapping
• bug TPD review was defaulting to induction meeting form
• removed 'unverified' label from members who have not linked SSO
• bug boolean questions showing Yes/No incorrectly in show form view

Portfolio Online is under constant development, and many of the changes and fixes that are made may not be obvious.

In order to increase the visibility of the development process we are now maintaining a changelog which we will publicise as updates are pushed onto the production server.

Updates are record in the changelog during the ongoing maintenance process, along with bug fixes and the implementation of new features.

Periodically these are bundled and deployed and at that time we will publish a new article here that summarises everything that went into the current release.

We will start this process by tagging the next release as version 1.0.0.

Maintenance releases (point releases), will contain bug fixes and minor enhancements. These will increment the rightmost digit. e.g. 1.0.0 -> 1.0.1

Minor releases represent a noticable change in functionality, these will increment the middle digit, and reset the point release. e.g. 1.0.x -> 1.1.0

Major releases occur when there are significant changes to the system, such as to the underlying framework/platform. This would increment the main version number e.g 1.x.x -> 2.0.0

If you have any feedback on how the changelog can be improved then please use the suggestion_forum on our support pages.