semasoftware Release Notes logo
Back to Homepage Subscribe to Updates

Release Notes

See the latest features, improvements, and product updates

Labels

  • All Posts
  • Fix
  • Announcement
  • Improvement

Jump to Month

  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026
  • April 2026
  • March 2026
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
Powered by

Create yours, for free!

2 years ago

AI Code Monitor Beta V3.11: Date range affects GenAI stats, View Attestation progress, Organization-wide rules, Inactive user message


Here's the latest video release notes: https://youtu.be/TbpAiftFl_M

In the current release, we have implemented a few customer-centric features, which are explained below:

1) The date range affects the GenAI stats: When I am on the Repository Group page, and I change the date range, not only the charts but also the GenAI usage stats change based on the date range. This allows you to monitor, track & compare the GenAI stats for different time periods.

2) The Repository detail page and PR page now have a feature to view the Attestation progress. As a user, you have the option to view the attestation progress bar that tells you the progress of how many chunks you have attested and how many are left. Apart from that, you also have the option to do bulk attestation. As a user, if you Agree with the labels on the chunks, then you have an option click on “Agree to all” button. 

3) On the SignUp page, we wanted to understand better what are the User needs of signing up for the AICM tool, so that we could serve them better.  We have provided a multichoice selection of "Why is it important for you to measure GenAI in your code?" which will help us capture the user need.


4) To provide clarity of Organization-wide rules set at Repository group level, we are displaying this information explicitly on the Settings page. This is to make it clear that even if there are no Repository-level rules set, even then the Traffic lights might appear on the Repo groups because of Organization-wide rules.

5) Display message to Inactive users on the Login page to help them navigate to next steps

6) As always, under the hood we made improvements in accuracy, including more varied human data in training set

Avatar of authorMatt Van Itallie