Follow

Version 2023.1.1

Modules changed in this release are:

Billing

Fixes

Bug Fix Reference
In Billing, there was an issue in the Edit Bill option on the Approvals tab, whereby after clicking the option it was possible to click it again whilst the bill was loading. This has now been fixed. The Edit button is now disabled and not selectable while the bill is loading. Furthermore, while editing the bill, if the user attempts to navigate back to the Approvals tab and click the Edit button again, they will now receive a helpful message stating, "You must save current bill before editing another". 23765
In Billing, there was an issue in the Edit Bill option on the Approvals tab, whereby it was slow to open the bill. This problem was noticeable when the bill contained a significant number of jobs. Enhancements are now included in this release to improve the performance in this area by optimizing the process of retrieving jobs. Instead of fetching each job, all jobs are now retrieved all at once. 23720

An issue was reported in the Billing tab - Client / Job Selection regarding the right-mouse context menu option View Client Fees Ledger, whereby the Fees Ledger displayed was not the one relating to the currently selected row. This happened when using the following keystrokes: -

  • Right click on a client
  • Select view client fees ledger from the context menu
  • Very quickly (i.e., before the Client Details form has opened!) Right click on the client again
  • Select view client fees ledger again
  • Close the Client Details form
  • Right click on a different client
  • Select view client fees ledger

Enhancements have now been included in this release to prevent the second selection of the same client's Fees Ledger with a progress overlay which will help prevent most users encountering the issue. However, where network traffic slows down, the issue could potentially be experienced.

12919

 

Credit Control

Fixes

Bug Fix Reference
In Credit Control, the Aging columns did not retain layout changes when moved to the beginning of the grid. This has now been fixed. 23758

 

Expense Approval

Fixes

Bug Fix Reference
There was an issue where child items for one parent row in the approval grid displayed under another row in the grid which resulted in a mismatch of total amounts when grouped by Staff. This has now been fixed. 23759

 

Job Budgeting

Enhancements

Enhancement Reference
In Budget Template setup a new value "Staff and Values" has now been added to the dropdown to reduce extra clicks and user errors when setting up a new Budget. 23732

 

Job Rollover

Fixes

Bug Fix Reference
There was an issue where the scripts that perform the roll were using a function not supported by Older versions of SQL Server. This has now been fixed. 23795

 

Time and Expenses

Enhancements

Enhancement Reference

Time grids row filter display is now governed by a firm switch TEGridFilter. When the switch is off the row filters will not be displayed.

 

The new switch is in Functional Area = 5 - T&E/ASTEE

 

Setting 1 = Show filters in List View, Grid View and Expenses.

Setting 0 (the default when inserted on upgrade) = No filters show in List View, Grid View and Expenses.

 

By default the switch is off (0), prior to this release the filter row was displayed by default. Firms that require the row filters will need to update the switch settings (1).

23730

Fixes

Bug Fix Reference
When entering a timeline, an issue was reported whereby a job listed in the dropdown for the selected client was not actually a job on the client.A fix has now been made for this preventing the incorrect job from displaying in the dropdown. 12745

 

UDF (Custom Forms)

Fixes

Bug Fix Reference
In Client UDF, the tab "Child Clients" (Child Customers) was displaying a Delete button. Delete was not valid for child rows and the button has now been removed. 5752
When a user double-clicked on the Save and Close button it resulted in a validation error. This has now been fixed. 19820
There was an issue in UDF where the Cascade Client changes form did not ghost the relevant fields. This has now been fixed. The appropriate fields in the form are now correctly ghosted as intended. 12468

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk