Skip to content

Release v251127

Summary

This release includes the following changes:

  • The latest configuration has been pushed into DEV and TEST
  • PowerBI has been configured and is now live in DEV and TEST (excluding the 'Submission Type report - the E2 team is working on a fix for this)
  • This release includes partially completed configuration for DH Cabinet record subtypes. As testing of the DFFH Cabinet record subtypes begins, please focus only on the following types: CABAR, CABCC, CABMC and CABSUB.

What should be tested

  • All specified workflows for Parliamentary record types, accurate to the up-to-date workflow diagrams at https://miro.com/app/board/uXjVJCUmfbA=/ This includes Transition names ('I want to' values), Task names and popups, workflow pathing such as 'send on' and 'send back' actions and which roles they travel to
  • Metadata fields and dropdown values for all record types, including Record general metadata (metadata consistent across all Parliament records) and Record specific metadata (metadata specific to subtypes)
  • Available Roles and Role details
  • Reporting (excluding 'Submission Type)

What we should avoid testing

  • Any other record types. Other record types will be visible, but these are under construction so they will not be functioning correctly.
  • Permissions: Role assignments and new permissions sets have not been finalised. This means that any new permissions changes requested by DFFH will not be in effect. The same permissions will apply that were present in Stage 1 (i.e., Information security classification field + standard permissions for users in roles). You will not be able to accurately test
    • Business or Division administrators
    • New permissions sets
    • Who can see / not see records in the dashboard
    • Who has access / does not have access to records
    • Who can take action / not take action on records
  • Key Date fields and Key Date automation: Changes to these requirements have occurred recently, so this has not been reflected in configuration.
  • 'Submission type' Report

At present, users have permissions to create both DFFH and DH related subtypes. Once permissions configuration is finalised, the ability to create records for the other organisation will be removed for most users, and access will be limited to their assigned organisation only.

New requirements that will not be reflected in the configuration at this stage

  • Content in the DFFH 'Suggested task names' documents that are not reflected in the configuration documents
  • Updated Key Date metadata field names and additional Key Date metadata fields
  • Updated Key Date automation requirements
  • Items from the 'Customisations' workshops that will be delivered when ready at a later date

Smoke Tests

  • Confirm 'Due to Parliament', 'House' and 'Parliament Reference Number' fields are no longer present in PPQ records during creation
  • Confirm that the 'Created By User' column contains entries in the Dashboard. If the column is missing: Navigate to Dashboard -> Edit Columns -> Select 'Created By User' -> Save. You should now see the column on the far-right side of the Dashboard containing users who created the records