4. Enhancement

Added Agent Instances on the Left Side of the Agent Control Board #

We have enhanced our Agent Control Board by adding Agent Instances to the left-hand panel for better viewing, easier switching, and easier searching of Agent Connection Destinations. Now, you have a complete overview of how many agents are connected to your organization and which connections exist. You can navigate through the agent instance ID tree and select one for pinging the connection.

Enhancements and Handling of xxxxxExecution Scheduler #

We enhanced to prevent the xxxxxExecution scheduler from failing to pick up the interface link with the Agent xxxx Adapter for outbound processing. The reason why we are not allowing the user to set the interfaceExecute scheduler is that we have an issue with duplicate outbound processing when a user configures it in two places: once on the agent scheduler and again on InterfaceExecute on the globe scheduler tab.

Additional for handling:

• The InterfaceExecution scheduler is created when the interface is not linked to an Agent Adapter. We generate this schedule while accessing the scheduler on the integration screen, specifically the globe scheduler screen.

• The InterfaceExecution scheduler is not created when the interface is linked to Agent Adapter xxxx. We do not create this schedule while accessing the scheduler on the integration screen, specifically the globe scheduler screen.
• For IntegrationExecution and InterfaceGroupExecution:
  • If all interfaces are within the integration and the InterfaceGroup is linked with the agent xxx adapter, these two schedulers will not be created.
  • If all interfaces are within the integration, and the InterfaceGroup is linked with both the agent xxx adapter and a non-agent xxx adapter, these two schedulers will be created as normal.
  • If all interfaces are within the Integration and the InterfaceGroup is linked only to the non-agent xxx version, IntegrationExecution and InterfaceGroupExecution schedulers will be created as normal.

• We added a warning log to get the information while this scheduler executes. It will skip the interface execution that the link New Agent Adapter uses.

Added ‘Job Trigger By’ Column to the Interface List of Agent Control Board #

We have added a new ‘Job Trigger By’ column to the Interface List on the Agent Control Board to indicate whether the interface was triggered by INTERFACE, GROUP, and INTEGRATION categories, either by a scheduler (value = SCHEDULER) or manually (value = MANUAL)

Enhancements to the Interface Group to Display the Information within the Agent Control Board #

We have made some enhancements within the interface group as follows:  

• We have improved Salesforce to display the Agent job information of the Interface Group.
• Additionally, we have added the display of Agent Connection and adapter status on the interfaces within the Interface Group tab of the Agent Control Board.

Enhancements to Amazon xxx Adapter #

Various Enhancements with the Amazon xxx Adapter:

• Previously, the AmazonAPIGateway adapter only supported GET and POST operations. Now, it has been expanded to support additional methods, such as HEAD, PUT, DELETE, and PATCH. Furthermore, it did not initially support dynamic paths, queries, and headers; however, these features are now supported.
• Enhancements have been made to the Custom Authentication Class functionality for the following adapters:
  • AmazonAPIGateway
  • Amazon SNS
  • Amazon SQS
  • Amazon Event Bridge

Enhanced Message Comment to Better Clarify that the External ID Fields cannot be Filtered in a Query Call #

In the previous version, you could use a textarea or VersionData field as an external ID. An error message would appear with the comment ‘field xxxxx cannot be filtered in a query call.’ This message was not clear. Therefore, we have enhanced the comment to ‘Cannot Use Field xxxxx as an External ID because its data type is TEXTAREA/BASE64, which cannot be used in query filters.

Enhanced Organized Setup of Agent Control Board #

We have organized the Setup screen as follows:

• Added a Security Settings category to the group: 
  • User Management
  • Register OAuth2 Client
  • Configure JWT
  • Configure API Key
• Implemented search functionality across all setup sections

Added Job Status Reset Functionality within the Interface List View of the Agent Control Board #

We encountered an issue where the interface gets stuck in processing with an IN_PROGRESS status. Previously, to reset the job, users had to log in to the PostgreSQL database on the Agent server. To address this, we have implemented a ‘Reset Job Status’ feature accessible by clicking the Job ID link within the Interface List View on the Agent Control Board. It is important to note that this option should only be used when you are certain that processing is not stuck. If the interface is still processing, avoid using this option to prevent unexpected errors.

Fixed Message Type for Database View of Import Database Metadata Function #

We have an unnecessary Message Type Database View for the ‘Import Database Metadata’ function. Therefore, we fixed it by removing the Database Operation, and we made the View have only one message type template as follows: 

• DB_View_(ViewName) => Type: Database View Template
  • Request => Type: Database Request
    • (ViewName) => Type: Database View
      • WHERE-Clause => Type: Database WHERE Clause
      • WHERE-Expression => Type: Database WHERE Expression
  • Response => Type: Database Response
    • Records => Type: Plain structure 
      • (ViewName) Plain structure

Enhanced Mapping Saving to Generate Database Query Statements #

We have improved the mapping saving process with Aget Database. If you are only mapping the Primary Key and Foreign Key fields when the user checks these fields exclusively, without selecting other fields. Upon saving the mapping, the Database Query will save ‘SELECT * FROM TableName’. However, if your mapping includes fields beyond the Primary Key and Foreign Key, a query will be generated for all mapped fields, such as ‘SELECT PKField, FKField, Fieldxx FROM TableName’.

Enhanced Outbound Processing to Create a Pending Message While the Outbound Adapter is in Inactive Status #

In the previous version, when the adapter was inactive and linked to the outbound interface deploy status, you may make a callout such as invokeCallout, invokeCallout2, and invokeCallV3, resulting in no message creation or processing. However, we have enhanced the system to create pending messages with all generic adapters and process messages later as needed. Note: This feature is not supported by the Agent xxxxx adapter.

Added Queue Tab for Agent Control Board #

We have added the Queue Tab to the Agent Control Board for monitoring the processing queues of the Integration, Interface Group, and Interface. Within this tab, you can perform actions such as pausing queue processing and deleting queues. This feature provides greater visibility into the queuing system, allowing for efficient management and control over the processing flow within the system.