Dynamic API Bot Configuration via LCNC Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In robotic process automation (RPA), configuring software bots to use APIs is resource-intensive and iterative due to frequent changes in API parameters and software upgrades, requiring repeated reprogramming to ensure correct API usage.
Innovation Solution
A computer system provides a predefined template for users to enter API information, metadata, and object data, coupled with a low-code no-code development platform, allowing users to configure software bots to generate requests in formats required by APIs without rewriting code, enabling dynamic API bot functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional programming methods are used to configure bots for API calls, then the bot can execute API requests, but reprogramming is required frequently when API parameters or software upgrades occur, increasing resource consumption and maintenance complexity
Solution Approach 1:
The patent implements a dynamic configuration approach where bot parameters are not hard-coded but can be modified through a visual interface. Configuration parameters such as API endpoints, authentication credentials, and data mappings can be adjusted without reprogramming the bot itself, allowing the system to adapt to API changes while maintaining the same bot executable.
Solution Approach 2:
The patent introduces a configuration file as an intermediary layer between the bot executable and the API parameters. This configuration file serves as a mediator that can be updated independently of the bot code, allowing changes to API specifications without requiring modifications to the bot's core programming logic.
2Measurement precision
If users manually configure each API parameter through traditional methods, then precise control over API calls is achieved, but the process becomes resource-intensive and time-consuming
Solution Approach 1:
The patent implements self-service capabilities where the system automatically generates, validates, and updates configuration parameters based on user selections in the visual interface. The system performs automatic syntax validation, parameter type checking, and configuration generation without requiring manual coding, thereby maintaining precision while significantly improving configuration speed.
Solution Approach 2:
The patent provides pre-configured templates and default parameter settings that are prepared in advance. When users need to configure a bot for API calls, they can select from pre-defined templates that already contain common parameter structures, reducing the time and effort required while maintaining configuration precision through the visual interface.
3Reliability
If frequent reprogramming is performed to maintain correct API usage, then the bot remains functional with updated APIs, but resource consumption and maintenance costs increase significantly
Solution Approach 1:
The patent implements dynamic configuration files that can be updated independently of the bot executable. When APIs change, users can modify the configuration parameters (such as endpoint URLs, authentication methods, or data field mappings) without reprogramming the bot, thereby maintaining reliability while avoiding the resource-intensive process of reprogramming.
Solution Approach 2:
The patent uses configuration files as copyable templates that can be duplicated and modified for different API scenarios. Instead of reprogramming the entire bot for each API change, users can copy existing configuration files, make necessary parameter adjustments, and deploy them, significantly reducing maintenance resources while ensuring reliable API integration.
Data Source
AI summary
Techniques for implementing a dynamic API bot for robotic process automation are disclosed. In some embodiments, a computer system performs operations comprising: providing a data file having a predefined template comprising dedicated fields for an identification of an API, a type of call method, metadata identifying one or more objects, and data of the object(s); providing a low-code no-code (LCNC) development platform configured to enable a user to develop a bot by dragging and dropping application components of the bot; receiving, via the LCNC development platform, a configuration of the bot comprising a configuration of the application components of the bot and an identification of the data file; and running the bot, the bot being configured to generate a request using the data file, converting the data of the object(s) into a payload in a format required by the API based on the data file.