Release 5.20

Written By John Greep

We’ve entered a new era in T-Jacs with the introduction of AI. Our first step in utilizing AI is to summarize time sheets for invoicing. This is a big deal for some of you. This will literally save hours of having to manually collate time sheets for customer invoicing. We have more potential with this. Now that we’ve jumped in, we would love to hear your ideas and feedback as to how we can move forward with this. There are more cool things we already know we can do with it.

What’s New

Introduced AI Admin module for external API integration

  • Initial implementation of the AI Admin module.

  • Provides configuration forms, API request handling, and admin functionality for connecting to external AI services.

Added labor summary support with AI generation in the job scope edit Form and invoice edit Form

  • Introduced a Labor Summary field to job scopes and invoices, allowing you to provide or generate summaries using AI.

  • Time sheet descriptions for the current invoice or job scope are submitted to AI to create a summary that can then be applied to your invoices. It’s a bit clumsy still, and you should definitely review the output for sanity and accuracy. You can regenerate the summary to see how the response varies each time.

  • Will be enabled on request. During this beta period, there will be no additional fee and we will consult with you regarding the added value of this feature.

Fixes and Improvements

Added formatting to tab title counters

  • Updated tab title counts to format large counts as 'K' (thousands) or 'M' (millions).

Streamlined Jobs List Page and added more counts to the tabs

  • Unified job lists under a new `Lists` tab for better organization.

  • Expanded the use of counters in the tab titles.

Streamlined Customer List Page

  • Redefined customer lists under a unified `Lists` tab with sub tabs for each list (Current, Inactive, etc.).

  • Fixed a problem opening lists related to customer rates.

Fixed bug preventing user login

  • Under some conditions, the user record couldn't be found and was returning an invalid response.

John Greep
Next

Release 5.19