Skip to content

Release v251114

Summary

This release includes both a product version upgrade for Brief Connect and draft configuration for Parliamentary record types, including ADJ, CQ, PET, PPQ, QON, QWN. These record types have been configured to the current specifications of the Parliamentary requirements documentation. It is important to note that this documentation is being updated regularly and that some configuration details may be out of date.

ID Title
660452 Parliament configuration - PET
660451 Parliament configuration - QWN
660450 Parliament configuration - QON
660449 Parliament configuration - PPQ
660448 Parliament configuration - CQ
660447 Parliament configuration - ADJ

Additional changes included in the new product version upgrade are detailed in our v2.3.0 Brief Connect release notes. (password is WeLove2ReadTheBCDocs!!)

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

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 in the last 24 hours, so this has not been reflected in configuration.
  • Reports: these won't work correctly until we have synchronised configurations after the release. This will be done early in the week commencing 17.11.

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

Package version: 2.3.0-rc.8

Manual pre-deployment steps

Review release pipeline variables

It's important to apply any changes to pipeline variables before a release created, because every release creates a snapshot of pipeline variables on the moment of creation, and the only way to re-deploy the application with updated variables - creating a new release

  1. Go to Azure DevOps, open Brief Connect project
  2. In left panel navigation go to Pipelines - Library - Variable groups
  3. Review variables for all environments included in this release and update the values where required.
  4. Save the changes

Create release for 'Deploy Brief Connect Application' release pipeline

  1. Go to Azure DevOps, open Brief Connect project, go to Pipelines - Releases page
  2. Find Deploy Brief Connect Application release pipeline, click on it to open
  3. If there is no release with a version specified in Package version section above, then execute the instruction below to create a new release. Release name should have the next pattern: v[Package Version] (n), where (n) just a counter, in case multiple releases created for the same package version.

Create new Brief Connect Application release (click to expand)

  1. Go to Azure DevOps, open Brief Connect project, go to Pipelines - Releases page
  2. Find Deploy Brief Connect Application release pipeline, click on it to open
  3. Click on Create Release button on the right
  4. Specify the Package Version variable with value from Package version section above. For example 2.0.0.
  5. Add a description (it's optional).
  6. Click on Create button
  7. Release with version v[Package Version] (0) will be created and will be available in the list of releases, after you refresh the page.

image.png

Pipeline deployment steps (in order)

  1. Deploy release v[Package Version] (n) (where (n) is latest number available, and Package version from the section above) for Deploy Brief Connect Application release pipeline in Azure DevOps to the target environment.
  2. Deploy release Release 16 for Deploy BC - Office Resources release pipeline in Azure DevOps to the target environment.

Manual post-deployment steps

Import Latest Configuration File

Config file to import: DFFH Configuration v251113-config.zip

  1. Log into the target Brief Connect environment as Brief Connect Admin user. Open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel)

    If there is no configuration set, you have to set up Administrator user Id in the Environment variable AdminEntraId in the Azure Function App. The value should be the Object Id of the user in Entra ID (Azure AD). 2. Select "Import from Zip" and apply new config via AdminPanel. 3. Ensure latest config is selected from the dropdown and click Apply. 4. In AdminPanel in your target environment, select Update SharePoint Content Types button from the menu bar. Ensure that uploaded configuration is selected from dropdown first.

Clear the Server cache

Role required: Brief Connect Administrator

  1. Log into the target Brief Connect environment as Brief Connect Admin user. Open the Admin Panel (https://[WEB_APP_URL]/#/adminPanel)
  2. Open browsers Developer Tools, open Console tab and run the command window.clearCache() there. After successful execution, you should see Cache cleared. Server Result: true message in the console.

Templates

Parliament templates have been added to the Document Templates library in SharePoint. The mappings will need to be updated once the release has gone live. To update mapping:

  • Navigate to the templates document library: https://dhhsvicgovau.sharepoint.com/sites/BriefConnect-NonProd/Document%20Templates/Forms/AllItems.aspx
  • There are 3 new templates for Parliament, shown below image.png
  • To update the 'Record type' column with the correct record type, select the item and then select details
  • Update the 'Record type' field with the corresponding record type
  • The PPQ template should be allocated to PPQ
  • The other two templates should be allocated to all other Parliamentary record types - ADJ, CQ, PET, QON, QWN

Smoke Tests

Confirm that record initiation is successful for each of the following Parliamentary record types:

  • ADJ
  • PET
  • CQ
  • QON
  • QWN
  • PPQ