Live

What's New - December 16, 2024

Client Job Invoice and Estimate audit trails, API access control, plus other improvements and fixes

🎉 NEW FEATURES

Client Job Invoice and Estimate Audit Trails

Effective Date: November 23, 2024

We've introduced comprehensive audit trail functionality for Client Job Invoices and Estimates, providing complete visibility into all changes made to these transactions. This release is part of our broader initiative to deliver detailed transaction-level history across the platform.

Client Job Invoice Audit Trail

Access Path: Accounting > Receivables > Client Job Invoices > Audit Trail link

The audit trail captures all modifications to invoice records, including:

  • Basic invoice details (invoice numbers, dates, client and job information)
  • Financial data (rates, amounts, markups, service fees, and totals)
  • Status changes (draft, posted, cancelled)
  • Line item modifications
  • Client order numbers and job task information

For complete details about this feature, see our Client Job Invoice Audit Trail Guide.

Estimate Audit Trail

Access Path: Jobs > Estimates > Audit Trail link

The audit trail tracks all changes to estimates, including:

  • Basic estimate details (estimate numbers, dates, client and job information)
  • Financial data (rates, amounts, markups)
  • Status changes (draft, submitted, approved)
  • Line item details and modifications
  • Service descriptions and scope changes

For complete details about this feature, see our Estimate Audit Trail Guide.

Reading Audit Trail Reports

Both reports use the same format for consistency:

  • Each row represents an action (insert, update, or delete)
  • Modified fields are highlighted in grey
  • Action Date and User columns show when changes occurred and who made them
  • Filter by ID to see a complete history for a specific invoice or estimate

Enhanced API Security

Enforcement Date: January 1, 2025

Overview

We've implemented transaction-level security across all API endpoints. Each endpoint now requires specific system access permissions for GET, POST, and UPDATE operations.

Key Changes

  • Added Permission section to API documentation for each endpoint
  • Permissions align with system transaction types
  • Access levels include Full Access and Read Only, varying by endpoint

Example Permission Structure

 
API Endpoint User Access Group Permission
Transaction Type Access Level 
Retrieve Entries of Supplier Invoices Supplier Invoices

Full Access

Read Only

Create Entries of Supplier Invoices Supplier Invoices Full Access

 

Implementation Requirements

  1. Review current API user access levels. For complete endpoint permissions and implementation details, visit our API documentation.
  2. Update API user permissions based on required access.
  3. Test API integrations and report any issues or questions by submitting a ticket. 

 

⚡IMPROVEMENTS

Enhanced Master File Audit Trail Reports

We've updated the format of all master file audit trail reports to align with our new transaction audit trails. This improvement makes it easier to track changes across all system records.

Changes

  • Modified fields are now highlighted in grey
  • Consistent format across all audit reports
  • Improved readability for change tracking

Optimized Supplier Transaction Processing

We've implemented pagination improvements to handle large transaction volumes more efficiently.

Supplier Invoice Form

  • Added pagination showing 50 lines per page
  • Optimized for invoices with hundreds of lines (tested up to 600 lines)
  • Improved performance when scrolling through large invoices

Supplier Payments Page

  • Reduced records per page from 100 to 50
  • Enhanced performance for payment processing
  • Faster page load times

🔧 FIXED ISSUES

Password Reset Process

Issue: Users received misleading "Current Password is incorrect" error message when attempting to set or reset passwords. Resolution: Error message logic corrected to properly handle password reset scenarios. Impact: Users can now complete password resets without encountering incorrect error messages.