Release Notes

DA (PG) Version PG Release 19

Stories delivered

  • [DTC-559] - Improvements to the start date field (Description)

    Make start date field more accurate and intuitive.

    Simple wireframe provided by UX... http://5fwh38.axshare.com

    Delivery criteria:
    Field should only contain dates from 2000 onwards
    User should be given the option to allocate 'start at any time' as an alternative to a start date
    User should not be able to select 'start at any time' for UKPASS courses

    • Technical Task: [DTC-553] - Move duration next to study type on the course details page
    • Technical Task: [DTC-636] - Update API
    • Technical Task: [DTC-637] - update UI
  • [DTC-489] - Back to dashboard and list view link from courses (Description)

    As a course management user I want a link back to the dashboard and back to course list view so that when I'm looking at my courses I can easily navigate away from the courses area

    • link on course list page back to dashboard page
    • text to read "My dashboard"
    • Link on course details page to go back to course list - text to read 'course list'
    • Previous search query is preserved

    Please check work done on dashboard/provider page for consistency

    • Technical Task: [DTC-552] - Change label on edit button on list view page to read 'View'
    • Technical Task: [DTC-632] - Move duration next to study type on the list view page
    • Technical Task: [DTC-638] - update UI
  • [DTC-532] - View UKPASS fields in UI (Description)
    • As UCAS I want to be able to view the fields that UKPASS requires in the UI so that the new course management system can support the application service

    See attached wireframes (sorry they're not pretty!!)

    Fields (in display order) are:
    UKPASS course? - y/n - course profile level
    Balance indicator - Course profile level, must see buttons that represent each of 5 balance indicator values (below). Field to read 'what is the subject composition of your course?'

    • M (Major/Minor)
    • B (Balanced)
    • T (Triple)
    • C (Combined)
    • S (single)

    JACS information - Course profile level. The number of required JACS codes is determined by the balance indicator, as follows:

    • M (Major/Minor) - JACS codes 1 & 2 required
    • B (Balanced) - JACS codes 1 & 2 required
    • T (Triple) - JACS codes 1, 2 & 3 required
    • C (Combined) - JACS codes 1 & 2 required
    • S (single) - JACS code 1 required

    ATAS flag - The following statement should appear ONLY when an ATAS flag is applied to the course 'An ATAS certificate is required for this course'
    PG ID / Course Code - Field to read 'UKPASS application code'
    Course Short title Field to read 'Short course title' up to 20 characters
    modular - (y/n) Field to read 'Is this a modular course?'
    CPD flag - (y/n) Field to read 'Is this course suitable for maintaining Continued Professional Development (CPD)?'
    International Information not mandatory, text field up to 2000 characters Field to read 'Information specific to International applicants', when no data is available display 'no specific international information available'

    Delivery criteria:

    • Only courses that are identified as a UKPASS course will see the UKPASS specific fields
    • Balance indicator (subject composition) should show the correct corresponding number of JACS codes
    • ATAS certificate statement should appear ONLY when an ATAS JACS code is present
    • Technical Task: [DTC-633] - Update UI
  • [DTTOGO-459] - Provider contact - edit (Description)

    As a HEP I want to be able to change contact information so that I can keep my information up to date

    • User must have ability to edit existing contact by activating an edit function (e.g. button)
    • User must be able to make changes and save edits
    • When clicking on Edit, all existing contacts become editable
    • When Edit button is activated, Save and Discard changes buttons become available
    • When Save or Discard is clicked, Edit button is then available again
    • Store user ID, timestamp for changes (check for Department edit as well)

    Query: Impact of user id on seeding?

    • Technical Task: [DTTOGO-756] - Design discussion
    • Technical Task: [DTTOGO-757] - Refactoring (align with Cuba)
    • Technical Task: [DTTOGO-758] - Implement edit contacts client side
    • Technical Task: [DTTOGO-759] - Write bbt
  • [DTTOGO-690] - Seed new fields (Description)

    As a provider I want to have all new fields populated so that my provider details are stored correctly

    Seed new fields where data exists in XAP:

    • Update extract to bring in new fields, lookup using in memory lookup for id and store id in Event store
    • Seed new fields where data exists in XAP
    • If country not found, default to not known
    • If region not found, default to none specified
    • Inst code - from XAP
    • Sort name - from XAP

    Leave provider code empty

    • Technical Task: [DTTOGO-655] - Update Provider Upsert message
    • Technical Task: [DTTOGO-719] - Map data into Eventstore
    • Technical Task: [DTTOGO-769] - Design discussion
    • Technical Task: [DTTOGO-770] - Get Upsert message to insert into MySql
  • [ESP-487] - As UCAS I want to be able to return a pCode to Collect based on a GUID request so that Collect can consume pCodes where necessary

Tasks

  • [CIT-622] - Look at Function New-SWRandomPassword duplication in scripts
  • [CIT-686] - Imperva DNS Verification
  • [CIT-690] - CloudFormation Template Change - Applications Certificate Update
  • [DTJAPAN-211] - Set up Collect on individual/team environments

Incomplete tasks

There are no incomplete tasks

Unfinished stories that are partially released

There are no unfinished stories

Resolved Bugs

  • [TD-1541] - Certain BBT steps creating numerous users and not destroying

Spikes

Spikes are investigative stories that enable the development team to work out how to solve problems in future stories

There are no completed spikes

Unresolved Issues

There are no unresolved issues

Improvements

Improvements are items of work that the development teams have identified to improve the product / improve the ways of delivering the product and remove technical debt

There are no Improvements items identified for this release