|
Ticket |
Component |
Release Notes |
|---|---|---|
|
BPF-74118 |
Accounts Payable |
APOHUTUL: Implemented an additional validation and retry mechanism to improve the reliability of job status after job completion. The system now re-validates the table data and retries the status update automatically if the expected status change is not detected. |
|
BPF-100050 |
Accounts Payable |
Client-specific for Saint Louis Public School District AP: Update signature for AP checks. |
|
BPF-100443
|
Accounts Payable |
Client-specific for Vermilion Parish SD AP: Updated AP check signature. |
|
BPF-99933 |
Accounts Payable, Payroll |
Client-specific for Lancaster Lebanon Intermediate Unit 13 AP and PY: Updated signature on AP and PY checks. |
|
BPF-99751 |
Accounts Payable, Payroll |
Client-specific for Kansas City Public School District 500 AP and PY: Updated signature for AP and PY checks. |
|
BPF-100319 |
Accounts Receivable, General Ledger |
ARUTUG: Updated the AR undo process to use the post date (AR-POST-DT) instead of the invoice date (ar_ref) for the SYGL UNDODATE cutoff check. Previously, when performing an ARUTUG Undo from both AR and GL, the system would undo the GL posting but fail to relieve the AR subledger posting if the invoice date was outside the SYGL UNDODATE, even when the post date was within range. The AR undo now uses the same date criteria as the GL undo, ensuring both are processed consistently. |
|
BPF-99109 |
Admin Console |
Admin Console : The system now correctly saves the actual User ID regardless of how the user was searched. Wildcard characters from the search pattern are no longer carried into the SSO User Mapping record when searching for a user in Admin Console, Manage Users using a wildcard (e.g., 00000001T2*) and then saving changes to that user's record. Previously, the system incorrectly created a duplicate SSO mapping entry containing the wildcard search term instead of the actual User ID. This led to SSO login failures for affected users. |
|
BPF-93796 |
Forms Printing |
Client-specific for Heartland Area Education Agency #11 PDF: Adjustments for Forms Printing. |
|
BPF-99577 |
Forms Printing |
Forms Printing, AP Checks: The existing common code MICR/AP when enabled, with Desc 5 set as “Y”, the MICR line is now printed only on the main check page, while continuation pages are generated without it. Previously, when a check included multiple invoices and extended onto additional pages, the MICR line was incorrectly printed on those extra pages as well, even though they weren’t actual checks. Online help documentation has been updated for the same. |
|
BPF-97162 |
General Ledger |
GLUTRIIJ, GLBUBAFI: Fixed an issue in the GLBUBAFI and GLUTRIIJ upload utilities where undefined account keys were incorrectly triggering automatic key creation and overwriting the description field. Previously, uploading a file with an account not defined in the system caused the upload utility to attempt creating a new key via GLFG/NEWKEY and placed the undefined key into the description field, leading to confusion. With this fix:
|
|
BPF-99720 |
General Ledger |
GLJEUB: An issue was occurring where editing a record in the grid details section caused the screen to revert to the first record after saving. Users had to manually navigate back to continue editing subsequent records. This has been resolved. The screen now remains on the current record after saving. |
|
BPF-100152 |
General Ledger |
GLRESR03JB, GLRESR15JB: The screen removal script has been corrected to prevent unintended removal of dependent menu entries. The missing GLRESR03JB and GLRESR15JB menu masks have been restored via RootRoll, and the reports are now accessible and searchable from the menu tree as expected. |
|
BPF-98086 |
Installer |
Running No client-side changes are needed; the new ScreenCompile.exe applies this behavior automatically. |
|
BPF-94009 |
Payroll |
Forced Payroll selection criteria to free memory after use. This selection criteria are currently mostly used in Washington State regulatory reporting would be used if standard payroll process is converted to c#. |
|
BPF-100987 |
P-Card |
APPCRC, PO Extract: The Pay Amount field is now editable and able to extract. Previously, the field was unresponsive to keyboard input, preventing users from adjusting transaction amounts during reconciliation. |
|
BPF-99146 |
Position Budgeting |
PBMDCP: Fixed an issue in PBMDCP where menu prompt values entered in uppercase were being saved in lowercase. Previously, when running PBMDCP jobs, model names typed in all caps would occasionally save to the database in lowercase letters, causing incorrect values to appear on the tail-sheet. This has been resolved, and prompt values now consistently retain the case entered by the user. |
|
BPF-100323 |
Punch Out |
POUPPR: When the common code POXP|OPTIONS is configured to not allow updates, the Quantity and Unit Price fields on the Punch Out Purchase Requisition screen now remain non-editable after entering and saving the Ship To name. Additionally, attempting to update any fields on the master record will display an error stating "PunchOut Purchase Orders may not be updated," preventing modifications to any non-grayed-out fields. Previously, the Quantity and Unit Price fields became editable after the Ship To field was saved, allowing unintended modifications. |
|
BPF-100396 |
Punch Out |
POUPPR: Previously, when updating the Vendor ID on a purchase order in POUPPR, the Vendor Address Code would display the correct value (e.g., P1) but revert to the prior vendor's address code (e.g., R2) after saving. This caused printed purchase orders to appear without a vendor address. Users had to manually re-enter the address code as a workaround. This has been resolved. The Vendor Address Code now correctly persists on the first save when a vendor is changed, and printed POs display the expected vendor address. |
|
BPF-98060 |
Recruitment Management |
RMUPPI: Previously, pressing the Enter key would inadvertently add a new line item, which could not be deleted until all mandatory fields were completed. This has been fixed — new line items can now only be added using the add icon (➕) and removed using the delete icon. Pressing Enter no longer creates an unwanted row. |
|
BPF-99218 |
Stores Inventory |
SIUTUG: The process now correctly updates only the sim_item_dtl records matching the job number selected during processing, leaving records from other jobs unaffected. Previously, when running SIUTUG on a job containing a Stores Order with a line item processed across multiple jobs, the system incorrectly updated all sim_item_dtl records for that line item — regardless of whether the job number on the record matched the selected job. |
|
BPF-100201 |
State |
State Specific Idaho PERSI - Fix issue with Employees that have pay but no hours or hours with no pay. |
|
BPF-100311 |
State |
Wisconsin - WISE/EdFi process - Add BPlus Key & Object to error info for missing locations to assist in updating the data. |
|
BPF-98046 |
Sub-Tracker |
STUTMA: Fixed an issue where the STUTMA sub-tracker process was incorrectly displaying hours in the Absentee tab even when no Absentee ID was provided. The system now correctly clears the hours and percentage when the Absentee or Substitute ID is blank. |
|
BPF-100441 |
System |
BusinessPlus Screens: The x-powered-by HTTP response header is now suppressed across all BusinessPlus web pages to enhance security. Previously, the header was included in HTTP responses, which could expose server technology information during security audits. The header is now disabled by default, reducing the server's fingerprint and aligning with production security best practices. |
|
BPF-99494 BPF-99495 BPF-99496 BPF-100037 BPF-100183 BPF-100181 BPF-100182 BPF-100172 |
VBScript, CDD |
CDD, Accounts Payable: Accounts Payable Standard Reports converted to Python - AP1001 AP1002 AP1100 AP1300 AP3001 AP3002 AP3003 AP3101 |
|
BPF-100409 BPF-100458 BPF-100540 BPF-100582 BPF-100583 BPF-100584 BPF-100585 BPF-100586 BPF-100587 BPF-100595 BPF-100590 BPF-100592 BPF-100593 BPF-100594
|
VBScript, CDD |
CDD, Human Resources: Human Resources Standard Reports converted to Python - HR0000 HR0002 HR0007 HR0009 HR0010 HR0011 HR0012 HR0013 HR0014 HR0015 HR0016 HR0018 HR0020 HR0021 |
|
BPF-99648 |
VBScript, CDD |
CDD: In the Macro tab, the system now correctly auto-generates local routines for newly added regions in Python report designs. Previously, selecting a newly added region from the Local Routine dropdown failed to create the corresponding routine, resulting in missing or blank entries. |
|
BPF-100883 |
VBScript, CDD |
VBScript, CDD: The system now auto-generates the macro with the correct scripting version when a new SQL Report is initiated, ensuring the macro type aligns with the report's assigned category. Previously, when initiating a CDD SQL Report, users encountered a "Macro type mismatch between the report and its assigned category" error. |
|
BPF-93761 |
VPAT |
VPAT: The border, fill, icon, and text colors of toast messages (Information, Warning, Success, and Error) have been updated to meet WCAG AA contrast requirements (minimum 4.5:1 ratio) across the following areas:
These changes improve readability for users with low vision or color blindness by ensuring all toast message elements meet accessibility standards. |
|
BPF-96492 |
VPAT |
VPAT, System: Fixed low color contrast issues across Job Screens, Framework Screens, Custom Screens, and Dashboard to meet WCAG non-text contrast accessibility standards. |
|
BPF-97175 |
VPAT |
VPAT: Required fields marked with an asterisk (*) are now properly announced as "required" by screen readers (NVDA and VoiceOver). Previously, screen readers did not convey the required status of these fields, which could cause users relying on assistive technology to miss mandatory inputs. |
|
BPF-97177 |
VPAT |
VPAT, System: Toast notification messages (Information, Warning, and Success) are now properly announced by screen readers such as NVDA and VoiceOver. Previously, these toaster messages were not read aloud, impacting accessibility for users relying on assistive technology. |
|
BPF-97229 |
VPAT |
VPAT, Login: Resolved keyboard navigation (tabbing) issues on the BusinessPlus login-related pages
|
|
BPF-97397 |
VPAT |
VPAT, System: Pressing the Tab key now correctly moves keyboard focus to the date picker, allowing users to open it, navigate, and select a date entirely via keyboard. Previously, when using the keyboard to navigate through the form, the focus skipped the date picker control, preventing keyboard-only and assistive technology users from interacting with it. |
|
BPF-97626 |
VPAT |
VPAT, PYUPPR: Screen readers (NVDA and VoiceOver) now correctly read label names, such as "Created By," "Created When," "Updated By," "Updated When," and "Unique Key" along with their associated field values in the Record Info section. Previously, only the field values were announced without their corresponding labels, making it difficult for assistive technology users to identify which data they were navigating. |
|
BPF-99582 |
VPAT |
VPAT, UI screens:
|
|
BPF-97486 |
VPAT |
VPACT, Grid: Interactive elements in Grid Mode - including the Select, Edit, Sort, Add, and Delete buttons - now properly receive keyboard focus when navigating with the Tab key. Users can activate these elements using Enter or Space. Previously, keyboard-only users could not reach or interact with several key buttons on the page, creating an accessibility barrier. |
|
BPF-99988 |
CDD |
VBScript, CDD : VBScript macro are now converted to python macros. CDD Reports loads selection criteria as expected when accessed via the Thick Client. Previously, users were unable to run classic macro based CDD reports. |
|
BPF-100161
|
Webform |
Webform: Fixed a defect where vendor names containing special XML characters caused the vendor ID lookup to silently fail on the legacy webform. Previously, after entering a vendor ID, the name field would not populate. |
|
BPF-88731 |
Workflow |
The Workflow engine now correctly calculates activity expiration dates when the "Ignore Business Hours" option is unchecked, properly skipping weekends. Previously, an uninitialized variable in the WF engine caused inconsistent expiration calculations - activities configured with the same expiration period could expire on different dates, and weekend exclusion rules were not reliably honored. |
|
BPF-98734 |
Workflow |
Fixed an issue in the Default Timecard Approval workflow (TO.NET_APPROVAL) where the EntryClerkEmail variable was not being assigned correctly in the A22 (Load Email Address) activity. A logic error in the C# code caused the email to be set only when the value was null or empty, instead of when a valid email existed in US_USNO_MSTR. The condition has been corrected so that EntryClerkEmail is now properly populated when the workflow instance creator has a valid email address. |