3. Enhancement

Enhanced Interface Screen

• Remove “Streaming, CDC, and Planform Events Setting”
• Visible Fields-based Event Type Selection in Event Configuration Section

Enhanced Bulk Processing to Support Per-Integration and Per-Interface Group Scheduler

Apply the Threshold for Raw Basket and Bulk Basket

In the previous version, the Raw Basket and Bulk Basket did not have a Threshold feature to alert users when the basket limit was reached. This feature has now been enhanced to provide Threshold support for both the Raw Basket and Bulk Basket.

Enhance All Manual Process Functions

In the previous version, users could perform the Manual Process function even when the interface was linked with an inactive adapter. In the current version, the Manual Process function is now only available for interfaces with a status of "Deployed", the interface must be linked to an active adapter, and the interface type must be the main interface.

Enhanced Batch Control Board Screen

• The interface filter should provide the selected interface instead of requiring the user to input the interface name into the History Basket.

• The Processing Type filter should be enhanced to allow the selection of the processing type of the baskets for the filter on the History Basket Tab.
• An Interface Group Column was added to the History Basket display records.
• We have added an ORDER BY on the filter for the Working Basket of the batch control board in order to monitor which batch baskets are older or newer records. The default setting for this field is Descending.

Added Refresh Button on All Reports & Dashboards Page

Currently, the Reports & Dashboards feature lacks a Refresh button to update and retrieve the latest records. However, in this version, we have implemented a Refresh button across all Reports & Dashboards.

Separate Adapter Status and Inbound Consumer File of New Agent

In the previous version, the Agent Inbound Consumer file would trigger and become active, and its active status would be stored in the Adapter Status field, indicating that a Consumer File was being utilized. However, in the current version, we have created a new Adapter property called Consumer Status. This Consumer Status field allows the status to be explicitly recorded as either 'stop' or 'start', providing more granular visibility and control over the Consumer File's state.

New 'Retrieve Data' Operation Type: Outbound Processing in 'AUTO Mode', Handles invokeCallout Without Records, Supports Manual & Scheduled Processing

We've introduced a new 'Retrieve Data' operation type to handle outbound queries, even when records lack the required data. Previously, missing records caused issues, but this new type avoids errors during 'AUTO' mode processing, even without any records. We've added this operation mode, which is used only when there are no available records from the filter query. In such cases, the system calls invokeCalloutV3 in 'AUTO' mode. It supports both manual and scheduled processing.

Added Pagination to Generic Basket Histories

We have added pagination functionality to the Generic Basket Histories feature to facilitate easier monitoring of historical basket data. Previously, users were faced with scrolling through long lists of basket records, making it challenging to quickly locate and review specific entries.

Enhanced on Alert When Not Run Function

• We have an icon state to indicate that this scheduler will not run.
• We have updated the comment regarding the number of schedulers that will not run for several hours, minutes, etc.
• Enhanced the Alert Value dependency screen based on the “Unite of time for the alert” field selection.
• Changed the display type to show the scheduler type instead of the scheduler name.

Enhanced Import Database Metadata to Generate Hierarchical Message Type

Previously, users faced challenges importing hierarchical message types, as this required manual configuration - a cumbersome and time-consuming process. To address this, we've enhanced the Import Database Meta Function to automatically generate the hierarchical message type structure, eliminating the need for manual intervention.

Removal of Extraneous Whitespace in some Filter Fields on Message

We have improved the search message function to remove unwanted whitespace from the following fields:

• Message Name
• Business External ID
• System External ID
• Transfer ID
• Transaction ID
• Basket Name

Enhanced IChain Initialization Operation: 'Delete child not present in the payload'

We have enhanced the IChain Initialization Operation “Delete child not present in the payload” This operation deletes a collection of child records. In the previous version, the remaining records child could not be deleted if one record failed to be deleted. However, this operation has been enhanced. Now, if a record fails, some records in the collection can still be deleted successfully.

Enhancement Screen Display  to Remove Some Pagination on Different Sections and Pages

We have enhanced the Screen Display to remove some pagination from the Different Sections and Pages.

• Remove the pagination from a data table of related Interface Page in sections IStructure, IMapping, IWorkflow, etc.
• The change has an effect on another screen like:
• Agent Control Board(Old) > data table in adapter tab
• Meta, Repo, Message Type related list > view all?
• Message Type related list > Select a field from the repository, use the existing message type

Added A few Buttons and Filters Sections on the License Page

We have added Remove Key and Remove Key for All Users.

• The Remove Key button means you need to select the user who wants to remove Skyvva Lience Skey.
• The Remove Key for All Users will remove all the Skyvva License Keys in the list of users

• Full Name
• UserName
• FirstName
• LastName
• Active
• Type Of Users
• Users with no license key
• Users with active license key
• Inactive Users
• Users with invalid License key
• Users with expired license key
• Expiration Date

Enhanced Message Status Handling for Empty Responses

We have enhanced our response handling to set the status when there is an empty response. The available statuses are as follows:

• When empty response -> Status Completed (green)
• When empty response -> Status Failed (red)
• When empty response -> Status Pending (yellow)
• When empty response -> Status Cancelled (grey)

You can set the message status in the Response Handling field of the inbound interface using these four picklist values while managing empty responses.