Release 5.1 Notes

From Wiki

Jump to: navigation, search

CLMS Release 5.1 will comprise the following changes:


New features

Context Map editing on the website (FR #797)

Code Map editing on the website (FR #517b)

Context Business Rules (as per spec)

Context Map Business Rules (FR #797)

What's changed XML difference reports (FR #555)

My Account page (as per spec)

  • Tab for Code Lists replaces CV Sets
  • New tab for Contexts
  • New tab for Context Maps


  • ContextMapDownload web service (FR #770b)


  • Malware checks: Validation against javascript in string fields (SEC3)


  • JoinedUpSystems wiki tool selected and installed
  • Website user help pages
  • Workbench user help pages

Updated features


  • EDT page rewritten for better performance and to work on CORP network
  • Slow pages rewritten with new data architecture


  • Colour scheme has been updated to use NPIA website colours
  • Context Download schema now includes an <Environment> element (FR #846)

Withdrawn features

  • CV Map download (replaced by Context Map download)
  • CV Map upload (to be replaced by Context Map upload in next Workbench release)
  • CV Set difference reports (replaced by Code List differencing)

Bug fixes for 'live' bugs


  • TypeLength checking on Publish Context (Bug #139)
  • Context and EDT name validation (Bug #160/713)
  • Timeout error message (Bug #362)
  • Missing Id in URL throws unhandled exception (Bug #479)
  • Sorting of Context favourites (Bug #766)
  • EDT Difference report errors (Bug #546/548)
  • Difference report names Old and New incorrectly (Bug #669)
  • Context history incorrect (Bug #705)
  • Clone CV Set times out (Bug #750)
  • Cannot edit draft CV Set with history tab active (Bug #758)
  • Context Favourites not sorted (Bug #766)
  • Poor handling of failed Context download (Bug #778)
  • EDT name check required on insert (Bug #801/893)
  • EDT name error message is unclear (Bug #802)
  • Inconsistent naming of Parent Code Filter field (Bug #807)
  • EDT difference report fails (Bug #816)
  • New User Account approval requests being wrongly routed (Bug #832)
  • Email alerts not working (Bug #835)
  • Distinction between Data Model and Data Standard Contexts unnecessary (Bug #837)
  • Registration process field errors (Bug #859)
  • My Account page should show drafts and latest Code Lists owned or stewarded(Bug #889)
  • Only Registrars should be able to link Organizations to Communities (Bug #891)
  • User's choice of team is lost during Registration process (Bug #903)
  • Expected Live Date field not handled properly (Bug #905/906)
  • CV Set BR209 rule failure (Bug #912)
  • Javascript injection vulnerability (Bug #961)

Known issues with this release

  • Code Maps cannot be uploaded with Workbench as it has not yet been revised to support Context Maps
  • Bug #902 Locked-out User email is sent to users without User Editor Rioles
  • Bug #968 Context Map Validation errors not displayed correctly when BR366 is included
  • Bug #970 If a user has Registrar role but NOT Context Map Editor role the Edit button for the Context Map Admin Details tab is displayed but the page throws an error when the button is pressed.
  • Bug #975 The Context Map Validate button present when the Context Map is in edit mode
  • Bugs #976-979 Four of the Context Map Business Rules that check the cardinalities of Code Maps (e.g. is a code mapped more than once?) do not work as intended. A Context Map could be published that has unreported Business Rule validation errors. If any Context Maps are published before the bugs are fixed the development team will revalidate them and inform the respective Steward Team if any unreported validation errors are detected.
  • Bug #980 A further Context Map Business Rule that checks that the Planned Live Date on a Context Map is no earlier than the Live Date on its Source or Target Context fails under certain conditions. This is unlikely to be an issue in the short term as we are not aware of anyone that uses this date yet for application synchronization.
  • Bugs #984/985 If the Element Value Policy for an EDT is set to either 'Use Code without Parent Code' or 'Use Full Meaning' (which are both unusual options) AND the Type Length is left blank an erroneous Business Rule validation error is generated. A value must be entered for Type Length to stop this happening.
  • Bug #986 Unable to delete draft Code List incorrect error message
  • Bug #987 Code List Legacy Code Map navigation incorrect
  • Bug #988 Code List 'Who Uses it' tab should include Code Maps (converted to Feature Request)
  • Bug #989 Code List Search error - The Search function for ' example Codes or Meanings' gives error:
Please choose "Code Lists" when searching for example CV Elements even when Code Lists are selected
  • Bug #990 New Context error message when no Version number entered is unfriendly
  • Bug #991 Duplicate EDT name error message incorrect
  • Bug #992 Organization Browse shows Superseded Contexts
  • Bug #994 Team membership delete error
  • Bug #999 Context Map Validation Timeout error message - no success/failure message is displayed
  • Bug #1000 Context Map Validation times out under some circumstances

Performance caveat

  • Please note that this software release is intended to run on a dedicated production server. Procurement of an appropriate production server is underway and transition is anticipated during February 2009. Until then we continue to run all JoinedUpSystems environments on one very limited server (less powerful than most laptops) and performance will continue to be an issue.
  • UPDATE: The live service was moved to a dedicated production server on 6 Mar 2009.
Personal tools