Fonts in draft fees narrative tab were showing in px (pixel) rather than pt (point). This was changed to be pt.
It was suggested that a work status be added to Tasks.
The tblStateJurisdiction table is an old table, reference to which was removed from some SP’s, but not all as access to this table for some clients is still needed.
When on the client owner WIP billing portfolio and choosing to view it by Group, the group selection box didn't appear.
Timesheet header in the timesheet admin > manage tab, was not aligning with the work profile set up on a staff member within their timesheet settings.
When accessing the Staff Jobs page, users were faced with a “Violation of Primary Key constraint...” error message.
Changes were made to the Bulk Fee printing page in Billing Admin to speed up the generation, re-generation and printing of fees.
When setting Arial 12 as the font and size, the system wasn’t honouring the default setting in categories.
The SP that returned a list of favourite reports to the staff reports dashlet was working ok, but the UI (user interface) was showing duplications of each report listed.
When the user clicked on the “New Claim” button in expenses, nothing happened.
Email addresses set in tblSystemOptions for invoices and statements CC, BCC and From addresses were not being picked up by the Bulk fee Printing page.
When adding a work profile to a Staff user and clicking apply, when going elsewhere in the staff details to make changes and apply those, the work profile entry got added a second time.
If a user did not have FeePost permissions, they could still see an active confirm button within draft fees and were able to click it to confirm a fee.
It was found that unlinked credit notes weren’t getting an automatic fee number assigned to them.
Checkboxes on Draft as Owner and Creator shouldn’t be available if the bill has no narrative details when bulk printing. The view button will be disabled when users are in a fee if no narrative is on the bill.
The VAT showing on recurring fees was to three decimal places.
If a user navigated to Reports > Task pad > Reports Admin, clicked on the parameters tab on any report, adding the parameter details and clicking done, followed by save, an error message was displayed.
When adding new leave entries, they show amber in colour. It was found that once they were submitted and approved, that they didn’t change to the confirmed leave colour of purple, as stated in the page’s legend.
If a Questionnaire question was set up to require an answer prior to being available for entry within any of the v9 style pages, the required answer setup was not working as expected. The field should be greyed out until the expected text is entered into the previous and prior question, at which point that field is white and activated. (Reported of PB Mares - 30308)
It was decided that when entries get into tblJob_History, where the Jurisdiction Status changes, the statusindex needed to be added to the HistData column for reporting purposes
When the Jurisdictions were updated, they seemed to be going into tblJob_History as HistType = 4 instead of 3, as the pes_Job_Jurisdiction_Update SP defines.
When creating a Zero Bill against a job, it should auto close the job but it was found that the system wasn’t populating the ‘Actual End’ field within the job with today’s date when finalising a zero bill.
In the billing admin screen the "Next Tax/VAT Invoice no” was changed to be “Last Tax Invoice no.”
It was found that the Leave type settings from the Admin > Leave Types page, were not being honoured in the new leave request dialog, and that users were having to select another leave type, then return to the one they wanted in order for the new leave request fields to follow the expected settings and behaviours set up in the leave types page.
When users created a leave type using multiples of 0.05 to the hour, the system was incorrectly calculating multiples when added in the leave request itself.
There was a title missing from the periods grid in the periods page. It was “Description”.
When accessing client details, users were seeing an input string error message.