All Co-Existent County SPOCs and Technical Contacts:
As requested, here is the list of patches that IBM tested and applied to the Dedicated County Windows 10 Workstations for October 2024:
MS Windows 10 22H2 Patches
MS24-OCT: Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 - KB5044020 (x64) Important
MS24-OCT: Cumulative Update for Windows 10 - KB5044273 (x64) Critical
MS Windows 10 21H2 Patches
MS24-OCT: Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 - KB5044020 (x64) Important
MS24-OCT: Cumulative Update for Windows 10 - KB5044273 (x64) Critical
MS Windows 1607 (LTSB) Patches
MS24-OCT: Cumulative Update for .NET Framework 4.8 for Windows 10 Version 1607 - KB5044021 (x64) Important
MS24-OCT: Cumulative Update for Windows 10 Version 1607 - KB5044293 (x64) Important
MS Office 2016 Patches
MS24-OCT: Security Update for Microsoft Excel 2016 - KB5002643 Important
MS24-OCT: Security Update for Microsoft Office 2016 - KB5002635 Important
Office 365 Patches
Office 365 Version 16.0.18025.20104 Available - Current Channel - Office 365 (English (United States)) Important - Unspecified
Mozilla Firefox Patches
TS - Mozilla Firefox (x64) 128.3.1 ESR Available 10/1/2024 – High mfsa2024-47
Action Required
No action is required. Informational only.
CWS/CMS
CWS/CMS: Business Objects Issue and Workaround
All SPOCs, Technical Contacts, and CAD Contacts:
An issue has been discovered with the current version of Business Objects used with the CWS/CMS application.
Issue Description:
Whenever a numeric field, such as government entity code, is used as a condition in a data provider (query), the query will run correctly the first time. Whenever the data provider is edited, the system will return a type mismatch error and require the user to remove and re-add the condition. The query will then run, as long as it is not edited again.
This only appears to be an issue with numeric fields; character fields, such as Client Name, do not experience this issue. Once the query is run, it operates normally as long as the user does not go back and edit the data provider. The user can refresh the data and save, as well as edit the report formatting, without issue.
Issue Resolution:
A patch level update will be required to resolve the issue. The CWDS Office and IBM are evaluating the next Business Objects patch to determine if it will resolve the issue, without generating any new issues. There is currently no estimated time of when the patch will be implemented. Additional updates will be sent out as new information is received.
Workaround:
When Business Objects informs the user of a type mismatch error after a numeric field is used as a condition in a data provider, and the data provider is edited, then the user must remove and re-enter the condition. The query will run, without issue, as long as the data provider is not edited again.
Action Required
Until the issue is corrected with the appropriate patch update, users will need to perform the workaround listed above, by removing and re-entering the condition when they receive a type mismatch error message.
An issue has been discovered with the current version of Business Objects used with the CWS/CMS application.
Issue Description:
Whenever a numeric field, such as government entity code, is used as a condition in a data provider (query), the query will run correctly the first time. Whenever the data provider is edited, the system will return a type mismatch error and require the user to remove and re-add the condition. The query will then run, as long as it is not edited again.
This only appears to be an issue with numeric fields; character fields, such as Client Name, do not experience this issue. Once the query is run, it operates normally as long as the user does not go back and edit the data provider. The user can refresh the data and save, as well as edit the report formatting, without issue.
Issue Resolution:
A patch level update will be required to resolve the issue. The CWDS Office and IBM are evaluating the next Business Objects patch to determine if it will resolve the issue, without generating any new issues. There is currently no estimated time of when the patch will be implemented. Additional updates will be sent out as new information is received.
Workaround:
When Business Objects informs the user of a type mismatch error after a numeric field is used as a condition in a data provider, and the data provider is edited, then the user must remove and re-enter the condition. The query will run, without issue, as long as the data provider is not edited again.
Action Required
Until the issue is corrected with the appropriate patch update, users will need to perform the workaround listed above, by removing and re-entering the condition when they receive a type mismatch error message.
If unable to find a specific Bulletin, please contact Communications.