Tegsoft Release Notes (202312291624)

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 is following 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,

• Alpha Release: This release includes all the updates developed and tested by the developer. The "alpha release" is the most frequent release of the major three. Once related development is done and tested by the developer Alpha 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.

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

• Stable Release (SR): This is the published release of Tegsoft products and it includes only the "Done" stage tasks. Even though, this release is published after several tests and is safe to apply directly, a UAT or Pre-production environment is always recommended for a better upgrade experience. Just because of several testing and quality assurance steps usually SR is behind Beta Release and is rare in publishing frequency. All the SR details are published in this article link. SRs are usually published once or twice a year.

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

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.

Pinned Notes 📌

1. What's New? ⚡️

1. DataProcessing tool implemented to support both HighAvailable Systems and Data Management for all Tegsoft Architechtures (DEVELOPMENT-2281)

   Data processing started to be handled as a separate line in the Tegsoft Development Cycle. Please see the article for capabilities, and the high availability cluster article for large-scale data management.

2. Filtering by Phone Number Implemented in CDR Report (DEVELOPMENT-2991 / 126747)

   The feature to filter by phone number in the CDR Report has been developed.

3. Annual Migration of Project Data (DEVELOPMENT-3354)

   Data management tools implemented. Please check the article for details: https://docs.tegsoft.com/docs/project-based-data-processing.

4. Campaign management interfaces (Voice, E-Mail, SMS) have been updated for V3 (DEVELOPMENT-3166 /127222) (DEVELOPMENT-3436)

5. DAHDI requirement has been removed (DEVELOPMENT-3423)

   The MeetMe and DAHDI requirements have been eliminated by replacing them with ConfBridge.

6. New Teggy Flow Components Implemented (DEVELOPMENT-3385)

7. Added Ability to Automatically Send SMS to Caller (DEVELOPMENT-3386)

   Campaign chain functionality has been added for answered calls. An action has been created for answered calls in IVR and agent campaigns. In campaigns where this feature is activated when the dialed number answers the call, the defined SMS content in the interface will be sent to the called person's phone. The functionality is also planned to be operational in case of answered campaign calls, similar to campaign result actions.

8. CentOS Strem 9 compatibility updates (DEVELOPMENT-3357)

   CentOS Stream 9 ISO has been prepared. Please contact support for early access and documentation.

9. Dashboard, not ready stages display improved (DEVELOPMENT-3320)

10. Logout agent statistics implemented for the dashboard (DEVELOPMENT-3266)

11. Skill reports, excel export now includes calls answered within the first 40 seconds (DEVELOPMENT-3382 / 127766)

12. Automatic update automation has been implemented (DEVELOPMENT-2818)

    Automatic Tegsoft update feature and tools have been published. For further details please check https://docs.tegsoft.com/docs/upgrading-to-recommended-version

13. Voiscope, Call Exper, and Analytix multi-language support has been implemented (DEVELOPMENT-3426)

14. Dynamic EXCEL Report custom execution time feature implemented (DEVELOPMENT-3163)

15. New Acapella TTS Cloud version integration has been implemented (DEVELOPMENT-3257)

16. Pre-dial check capabilities now support inter-campaign controls to avoid calling a contact if already called in another campaign (DEVELOPMENT-3338)

17. Abandon call campaign settings have been improved (DEVELOPMENT-3471)

    The wait time settings in the missed call campaign have been modified. The existing wait time has been changed to the minimum wait time, and a new maximum wait time field has been added.

2. What's Improved? ⚡

1. Customer Representative Screen > Reports > Making the Queue Missed Data Parameterized in CDR Report (DEVELOPMENT-3322 /127626)

A new parameter has been defined to hide abandoned calls from Agent CDR reports in Agent Desktop.

If ContqactCenterParameters.getParameter(agent.disableAbandonCallReport) is true, abandon call reporting is disabled.

2. Quality Analysis Image Enhancement (DEVELOPMENT-3019)

Voice recording analysis graphic display has been improved.

3. RI-CDR Voice Recording Screen - Voice Graph Enhancements (DEVELOPMENT-2879)

Development has been implemented to always set the Inbound and Outbound graphs as Blue for Agent - Red for Customer.

4. Echo- CDR Quality Data Field Validation (DEVELOPMENT-3421)

The fields related to CDR quality data were reviewed, and QA processes were conducted.

5. Excel Character Corruption and Import Performance Enhancement (DEVELOPMENT-3410)

Campaign data import performance improved.

6. V3 Agent Desktop - POPUP URLs - Refresh Button Improvements (DEVELOPMENT-2786 / 126247)

   

Agent desktop external CTI popup applications window improved by adding a refresh button.

7. Webchat - Creating Media Content Templates from the Tegsoft Interface (DEVELOPMENT-3349 / 127706)

An improvement has been made to create media content templates from the Tegsoft interface for WhatsApp campaigns.

8. Activity Reports - Addition of Call Queue Filter (DEVELOPMENT-3360 / 127721)

   

A new filtering option (Call Queue) has been added to the filtering section of the activity reports.

Although activities and queues can be selected for reporting from CDR and Call Queue reports, development has been made to add the Queue filter to the Activity report.

9. Adding the Activity Report to the Agent Desktop Screen as an Improvement (DEVELOPMENT-3364 / 127711)

An activity report has been added to the MT screen, where they can only see the activities they have created.

10. Contact Card - Unable to Make Calls from PHONE Fields Other Than Phone1 (DEVELOPMENT-3294 / 127555)

Click to dial, click to send SMS, and click to send e-mail buttons are added on V3 CRM screens.

• The bug where clicking the phone icon on the screen did not initiate a call when it should have has been fixed.

• Added a phone icon next to fields with phone numbers on the Details page, allowing direct dialing when clicked.

11. Opening of HA V2 Screens (DEVELOPMENT-3367 / 127735)

Accessing V2 apps on high availability cluster for backward compatibility feature added.

12. Improvement made on the Activity Screen: Date is now CREATEDDATE instead of ACTDATE (DEVELOPMENT-3441 / 127860)

Update on the list screen: Create and ACTDATE are now displayed together.

The date information on the Activity screen now comes from the CREATEDDATE field, matching the date entered when entering activity details, as part of the improvement.

13. CRM Activity tab not displaying end date (DEVELOPMENT-3482 / 127930)

Improvement made to display both begin and end dates for an activity, even if only the begin date was previously visible, with the end date shown below or beside it.

3. What's Fixed? 🔧

The following fixed bugs appear in this release:

1. Voice Recording Page DTMF Filter Query Error Bug Fix (DEVELOPMENT-3362 / 127724)

CDR Summary-Detail DTMF field allows generating keypad reports. However, when attempting to generate a report from the Voice Recording page with same filter, the encountered bug has been fixed.

2. Synchronization Bug Rectified on Agent Desktop Real-Time Monitoring Page (DEVELOPMENT-3380 / 127750)

The bug related to data not being synchronized properly after logging in has been fixed with the latest release.

3. Improved DTMF Logging and API Reporting Access for Campaign Call Data (DEVELOPMENT-3232 / 127390)

The bug causing the inability to listen to some audio recordings through the stream audio API due to Call ID discrepancy has been fixed.

4. IllegalArgumentException Handling (DEVELOPMENT-3409 / 127817)

Resolved IllegalArgumentException in integration parameters.

5. Notification Improvement (DEVELOPMENT-3227)

With this improvement, if the customer does not respond the message written by the customer agent in the chats coming from the customer’s app within X minutes, the notification service will be triggered.

1. If the customer still doesn’t respond, when the second notification period arrives, the service will be triggered again and when the session timeout period is reached, the chat will be disabled.

2. When the webservice is triggered, the 1st NOTIFICATION and 2nd NOTIFICATION service types should be different from each other. This is because the content of the 2nd notification is different. Therefore, for Fiyuu to understand, the service type must be different.

6. Integration of Forgot Password Feature (DEVELOPMENT-3346 / 127699)

The 'Forgot Password' section has been added to the Telescope screen.

7. Error Resolved: Notification Bug for Incoming Chats While Agent on a Different Screen (DEVELOPMENT-3393 / 127767)

The bug where chat notifications were not appearing during an ongoing conversation when the agent was on a different screen in Webchat and WhatsApp has been fixed.

8. Bug Fix: Resolved Issues in V3 Internal Calls (DEVELOPMENT-3406)

The bug causing only the internal number to be displayed in V3 internal calls has been fixed.

9. Bug Fix: Mandatory Additional Parameter Issue in v3 (DEVELOPMENT-3395 / 127787)

A rule has been created in the request-complaint settings by making 2 parameters:

• test1

• test2

mandatory in categories-additional parameters.

In V2 interface, the rule was functioning as intended when creating request. However, in the V3 interface, there was a bug that allowed users to create a request without filling in the relevant sections, despite the rule. This bug been fixed and now and appropriate warning is displayed when attempting to create a request with empty required fields.

10. Fixed: Type and Category Bug on V3 New Request Screen (DEVELOPMENT-3371 /127736)

The bug where the type and category did not automatically appear on the new request screen in v3 has been fixed.

11. Fixed: Empty Last Login Date Bug on V3 User Management Page (DEVELOPMENT-3415 /127832)

The bug where the last login date was coming empty on the v3 User Management Page has been fixed.

12. Resolved: V3 Internal Addition Error in Ring Group (DEVELOPMENT-3411 / 127825)

In V2, Internal additions to the ring group were successful without any errors. However, in the V3 interface, the added internals were not visible. The related bug has been fixed.

13. User Session Access Capabilities has been Improved (DEVELOPMENT-3397 / 127776)

User deletion on the individual card restricted in cases of insufficient permissions.

14. Optimized Event Creation for Faster Performance (DEVELOPMENT-3454 / 127890)

Database operations transitioned to asynchronous, resulting in faster event triggering.

15. UI Bug Fix: Resolved Button Displacement Issue in V3 When Receiving Pending Calls (DEVELOPMENT-2729 /126093)

The bug causing the shift of the Send Message button when an incoming call is received has been fixed.

16. Bug Fix: Addressed Issue of Unupdated Activity Reminder Window in V3 (DEVELOPMENT-3401 / 127795)

The bug where the Activity Reminder window was not updating in V3 has been fixed.

17. Copy Button Added to Campaign Screens in V3 (DEVELOPMENT-3459 / 127906,128)

Campaign copy button from V2 now available in V3 campaign screen.

18. Hold Button Press Disables the Functionality of the Mute Icon (DEVELOPMENT-3457 / 127884)

Development has been made regarding the hiding of the MUTE button during the HOLD stage.

19. Bug Resolved: Fix for DTMF Filter Query Error on Voice Recording Page (DEVELOPMENT-3462)

The DTMF Filter Query Error bug on the Voice Recording Page has been fixed.

20. Prevented Agents from Viewing Pending Calls in Queues They Are Not Registered In (DEVELOPMENT-3486 / 127892)

A bug was fixed where, by default, granting admin privileges to a newly created agent and subsequently revoking those privileges allowed the agent to view pending calls in queues, even if they were not registered.

21. Bug Fix: Addressed Issue of Missing Order Report Results in V3 (DEVELOPMENT-3449 / 127888)

The bug where order reports were displaying smoothly in V2 but not appearing on the screen in V3 has been fixed.

22. Filter Functionality Bug Resolved (DEVELOPMENT-3479)

Fixed error when filling the listener filter.

23. Bug Resolved: Functional IVR DestinationRouter Command Malfunction Fixed (DEVELOPMENT-3390 / 127778)

The bug causing the malfunction of the functional IVR DestinationRouter command has been fixed.