Tegsoft Release Notes (20250217)

A. Introduction

Welcome to the release notes for Tegsoft.

The release notes include key details about Tegsoft releases, including information on new and improved features, and bug fixes. Please review the topics carefully, as they include late-breaking information that may not be available in other Tegsoft documentation.

Tegsoft is a software company that follows CMMI standards, please check support process articles for further details.

There are seven stages in the development process

1. To Do: Any development task starts with this stage.        

2. In Progress: Once the development process starts, the task moves to this stage.        

3. Waiting/Blocked: If any external action is required (like sample data, customer feedback, some sub-results, etc.)

4. Test Waiting: Tasks are moved to this stage after development and developer tests are completed.        

5. Test In Progress: All the development tasks that have an impact on the Tegsoft baseline always go through the test process. The test process is part of the Quality Assurance Policy of Tegsoft Company.

6. Test Failed: After the test stage if any update is required; because of a major malfunction, minor errors, styling/multi-language issues, or any quality issue; the task goes from the "Test In Progress" stage to the "Test Failed" stage.        

7. Done: Once the task goes through all the automated/manual testing processes successfully, the task moves to the "Done" stage.          

Active sprint tasks can be monitored from this link.

There are three types of major releases for Tegsoft products,

• Latest Release: This release includes all the updates developed and tested by the developer. The "latest release" is the most frequent release of the major three. Once related development is done and tested by the developer Latest Release is created automatically. So this release includes all the updates for the tasks in the "Waiting/Blocked", "Test Waiting", "Test In Progress", "Test Failed" and "Done" stages. This release is not recommended for critical production environments but is usually stable enough to apply after user tests. Applying directly without tests may cause unexpected results and loss of time or money. UAT or Pre-production environments are always recommended for a better upgrade experience.

         

• Main Release: The Main Release is produced by sourcing an Latest Release, so it basically includes all the updates of that Latest Release. Some tasks/updates included in the "Main Release" may be fully tested and some may be included just after the developer test. Main releases are more stable than the "Latest Releases", and they are published after Regression Tests. Tegsoft Test Team performs automated and/or manual testing steps before calling out an "Latest Release" as a "Main Release". Once Main Release is published, some test results may be published with it. You can check this article link for further release-specific details frequently. Main Releases are usually published once a week or biweekly.

You can access on-premise upgrading instructions with your partner credentials via this link.

B. Information About Release Notes 🔍

The purpose of the Release Notes communicate the major new features and changes in this release of Tegsoft. It also documents known problems and workarounds.

This Release Note is comprised of four sections:

1. What's New?

New Feature Notes describe and announce the new features of development for Tegsoft products. Every item listed under this section describes the basics of a newly developed feature. Detailed descriptions/instructions will be accessible from the links provided at the end of the new feature description.

2. What's Improved?

Improvement Notes describe changes, in a feature/function that is already active.

The types of changes are listed below:

• Data field updates (removal or addition of fields)

• Changes in reports or applications

• API functionality changes

• Performance improvements

• Layout changes

3. What's Fixed?

Fix Notes are the list of known and fixed customer-reported defects or security fixes. Some instructions or workarounds may be described.

4. Related Documentation

Related Documentation is the list of links for more information related to the release.

C. Pinned Notes 📌

D. What's Fixed? 🔧

1.The issue of email content visibility in the Communication History has been resolved. (DEV-3984)

2.The issue of incorrect grouping when selecting the Monthly Breakdown in the Activity Summary Report has been resolved. (DEV-4125)

3. The filter problem in the Dashboard's Outbound section has been resolved. (DEV-4153)

4. The routing combobox issue on the voice campaign screen has been resolved. (DEV-4174)

5. The number of downloadable records problem on RM-Requests page has been resolved. (DEV-4178)

6. When the loadTestModeActive parameter is active, the issue with call and agent assignment in the clustered environment has been resolved. (DEV-4181 & 4136)

7. The interruption of the IVR incorrect dialing announcement has been resolved. (DEV-4184)