v23.1 - Proactive Disclosure Updates

What's Changed

• Observation fixes -Proactives & print statements removed by @aparna-aot in #6085
• Show Divisional tracking for PD by @aparna-aot in #6087

Full Changelog: v23.0...v23.1

v23.0 - Proactive Disclosure

Merge pull request #6082 from bcgov/release/FOIMOD-release23.0-to-main

Merge pull request #6081 from bcgov/dev-AS-FOIMOD-4303

v22.4 Linked Requests

This release added the ability to manually link requests in FOI Mod. Please note, we are continuing to open requests in AXIS for the time being. This includes linking requests in AXIS, and syncing over the linked request.

Request Management App
Added a new section in the Request tab called 'Linked Requests'. This will replace the old 'Linked Requests' hyperlink.
OLD

NEW

Added the ability to manually link requests in FOI Mod. This includes the ability to remove linked requests. We also added a hyperlink which will take you directly to the linked request in FOI Mod, in addition to displaying the request state the linked request is in. Ministry users will have 'view-only' access to the linked requests section, whereas FOI Operations users will have edit abilities.

22.3 - Request ID Generation and Unopened Requests

Request Management App

• Added the ability for Request IDs to be generated in FOI Mod when a request moves to ‘Intake in Progress’. This will only occur when no information has been entered in the ‘AXIS ID Number’ field. We do not anticipate using this feature until we stop opening requests in AXIS.
• Added the ability for ‘Unopened’ requests to appear in the Intake Team’s ‘Unassigned Requests’ queue. ‘Unopened’ requests are requests that are received through the online FOI request submission form. This should help save time by automatically populating many of the fields when creating a request. We do not plan to enable this until we stop opening requests in AXIS.
• Fixed a UI issue for Ministry users, where fields in the ‘Request’ tab, when they had a high character count, were not displaying properly
• Fixed an issue where character counts were not being enforced in the ‘Request’ tab, and if fields exceeded the character count, the request could go into error. All fields in the ‘Request’ tab now have a character limit enforced.
  When creating a request, temporarily added an ‘Enable Sync’ button in the ‘Request’ tab, which needs to be selected before entering an AXIS ID Number and syncing the request with AXIS.

v22.2 Fee Invoice Generation

Merge pull request #6041 from bcgov/release/FOIMOD-release22.2-to-main

Release 22.2 DEV <> MAIN

v22.1.1 Document Set Hotfix

Request Management App:

• Fixed an issue where CFD Ministry users would upload records and the records log would occasionally go into error and all files uploaded would disappear.

• Disabled the ability for CFD Requests to have tags edited while records are under processing and do not have the green check mark.

v22.1 OpenInfo Queue Fix

Request Management App:

• Fixed an issue where, when a request went from Intake in Progress ->Closed, and the request was re-opened, the request disappeared from FOI Mod.

• Fixed an issue where the ‘Received Date’ field was blank for requests in the Open Information queue(s). This should be fixed going forward and will not be retroactive.

• Fixed an issue where Open Information team users could not search for all requests in Advanced Search. Open Information team users should now be able to search for all requests in Advanced Search.

• Fixed an issue where ‘Consultation’ requests appeared in the Open Information team queue for publishing. Requests with the ‘Consultation’ flag will now correctly be marked as ‘Do Not Publish’ upon closing and will not show up in the Open Information team queue.

• Enabled Open Information team users to unilaterally create and approve an exemption request – this was done by making the ‘Analyst Rationale’ field not mandatory.

• Fixed an issue where, when a request is closed and the close reason is not ‘Full Disclosure’ or ‘Partial Disclosure’, the request state was not being updated to ‘Do Not Publish’. Now, when a request is closed with any close reason that is not ‘Full Disclosure’ or ‘Partial Disclosure’, the request state will correctly update to ‘Do Not Publish’.

v22.0 - Document Set

Records Log – Document Set:

A new feature has been added to the records log, enabling FOI Ops users to be able to assign files to a document set.

When files are assigned to a document set, you will notice a change when you click on the “Redact Records” button – it will now include a dropdown menu where you can select the set of records to load.

Only files assigned to a set will load in the redaction application. To go to the next set, you will need to load it through the records log with the Redact Records button.

FOI Ops staff will also be able to move files across document sets.

Files that are moved into, or across document sets will have all of their annotations and redactions retained (you will NOT lose your work when you move a file into or between sets)

Once records are in a document set, you will only be able to load records assigned to a set. All files with a green checkmark will need to be loaded into a document set to ensure you are not missing records in your packages.