Service calling method and device, computer equipment, storage medium and product
By acquiring initial call data and performing parameter conversion within the low-code platform, the problem of insufficient application of financial components in the financial industry is solved. This enables service call adaptation and unified processing across multiple business scenarios, reducing the complexity of the service call process.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-28
- Publication Date
- 2026-04-07
AI Technical Summary
Existing low-code platforms do not apply financial components in the financial industry deeply enough, resulting in service processing being limited to specific business scenarios and services, thus restricting the ability to adapt service calls to different scenarios.
By acquiring initial call data, performing data transformation based on pre-defined parameter transformation logic to obtain component parameters, and then making service calls based on these component parameters, the system can adapt to multiple business scenarios.
It enables service call adaptation for multiple business scenarios, ensuring that the component parameters obtained after data conversion can be processed uniformly, preventing the difference in initial call data under different business scenarios from affecting the smooth progress of service calls, and reducing the complexity of the service call process.
Smart Images
Figure CN121807408A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of data processing, in particular to a service calling method and device, computer equipment, storage medium and product. BACKGROUND
[0002] Low-code platforms are widely used in the digital transformation of the financial industry as rapid development tools, but the existing low-code platforms in the industry are not deep enough in the application of financial components.
[0003] The existing low-code platform has certain limitations in the process of service processing; it can only process services for specific business scenarios and specific services, which limits the scene adaptation capability of service calling. SUMMARY
[0004] Therefore, it is necessary to provide a service calling method, device, computer equipment, storage medium and product that can adapt to different scenes.
[0005] In a first aspect, the present application provides a service calling method. The method comprises:
[0006] obtaining initial calling data;
[0007] performing data conversion on the initial calling data based on pre-set parameter conversion logic to obtain component parameters;
[0008] performing service calling based on the component parameters to obtain a calling result corresponding to the initial calling data.
[0009] In one embodiment, performing service calling based on the component parameters to obtain a calling result corresponding to the initial calling data comprises:
[0010] determining a scene type to which the initial calling data is directed;
[0011] performing service calling based on the scene type and the component parameters to obtain a calling result corresponding to the initial calling data.
[0012] In one embodiment, performing service calling based on the scene type and the component parameters to obtain a calling result corresponding to the initial calling data comprises:
[0013] determining a component identifier corresponding to the initial calling data;
[0014] performing service calling based on the scene type and the component parameters according to a service component corresponding to the component identifier to obtain a calling result corresponding to the initial calling data.
[0015] In one embodiment, the scenario type includes process scenarios and single-table scenarios.
[0016] In one embodiment, obtaining the initial call data includes:
[0017] In a single-table scenario, retrieve the initial call data entered by the user in the data form;
[0018] When the scenario type is a process scenario, the initial call data is obtained based on the process context data in the process configuration.
[0019] In one embodiment, the method further includes:
[0020] Read the table metadata from the existing database;
[0021] The table metadata is configured with a form based on the mapping relationship between the fields in the stock table and the fields in the low-code form to obtain the data form;
[0022] Determine the core logic of existing business;
[0023] The business process is updated based on the core logic and the data form to obtain the process configuration.
[0024] Secondly, this application also provides a service invocation apparatus. The apparatus includes:
[0025] The acquisition module is used to obtain initial call data;
[0026] The conversion module is used to convert the initial call data based on a pre-set parameter conversion logic to obtain component parameters;
[0027] The calling module is used to make service calls based on the component parameters and obtain the call results corresponding to the initial call data.
[0028] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:
[0029] Get the initial call data;
[0030] Based on a pre-defined parameter conversion logic, the initial call data is converted to obtain component parameters;
[0031] Based on the component parameters, a service call is made to obtain the call result corresponding to the initial call data.
[0032] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:
[0033] Get the initial call data;
[0034] Based on a pre-defined parameter conversion logic, the initial call data is converted to obtain component parameters;
[0035] Based on the component parameters, a service call is made to obtain the call result corresponding to the initial call data.
[0036] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:
[0037] Get the initial call data;
[0038] Based on a pre-defined parameter conversion logic, the initial call data is converted to obtain component parameters;
[0039] Based on the component parameters, a service call is made to obtain the call result corresponding to the initial call data.
[0040] The aforementioned service invocation method, apparatus, computer equipment, storage medium, and product acquire initial invocation data; perform data transformation on the initial invocation data based on pre-defined parameter transformation logic to obtain component parameters; and then, perform service invocation based on the component parameters to obtain the invocation result corresponding to the initial invocation data. As can be seen from the above, this application, during the service invocation process, performs data transformation on the initial invocation data based on pre-defined parameter transformation logic, achieving adaptation of initial invocation data for multiple business scenarios. This ensures that the component parameters obtained after data transformation can be processed uniformly, preventing the smooth progress of service invocation from being affected by differences in initial invocation data under different business scenarios. It achieves service invocation operations for multiple business scenarios without the need for separate design and development for each business scenario, ensuring smooth service invocation and reducing the complexity of the service invocation process. Attached Figure Description
[0041] Figure 1 An application environment diagram of a service invocation method provided in an embodiment of this application;
[0042] Figure 2 A flowchart illustrating the first service invocation method provided in this application embodiment;
[0043] Figure 3A flowchart illustrating the second service invocation method provided in this application embodiment;
[0044] Figure 4 A flowchart illustrating the third service invocation method provided in this application embodiment;
[0045] Figure 5 A structural block diagram of a service invocation device provided in an embodiment of this application;
[0046] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation
[0047] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0048] The service invocation method provided in this application embodiment can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or placed on a cloud or other network server. The process involves obtaining initial call data; implementing data conversion based on pre-set parameter conversion logic to obtain component parameters; and then, making service calls based on the component parameters to obtain the call result corresponding to the initial call data. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. Server 104 can be implemented using a standalone server or a server cluster composed of multiple servers.
[0049] In one embodiment, such as Figure 2 As shown, a service invocation method is provided, which is applied to... Figure 1 Taking server 104 as an example, the following steps are included:
[0050] S201, Get initial call data.
[0051] It should be noted that the process of obtaining the initial call data varies depending on the different business scenarios. These business scenarios can include form scenarios and process scenarios. A single-table scenario refers to a scenario where the component needs to be called in real time to calculate the result after the user inputs basic data. A process scenario refers to a scenario in a business approval process where the component needs to be triggered as an independent node for execution.
[0052] In one embodiment of this application, in a single-table scenario, when it is necessary to obtain initial call data, the data entered by the user in the data form can be obtained, which is the initial call data.
[0053] In another embodiment of this application, in a process scenario, when it is necessary to obtain initial call data, process context data can be extracted through the process engine, and the process context data is the initial call data.
[0054] S202, based on the pre-set parameter conversion logic, performs data conversion on the initial call data to obtain component parameters.
[0055] It should be noted that parameter conversion logic refers to the parameter definition conversion logic for different business scenarios. The parameter conversion logic can record the adaptation and conversion rules between the initial call data and component parameters under different business scenarios, so as to realize the conversion of the initial call data of different business scenarios into component parameters according to the parameter conversion logic.
[0056] S203, make a service call based on the component parameters and obtain the call result corresponding to the initial call data.
[0057] It should be noted that when it is necessary to make a service call based on component parameters and obtain the call result corresponding to the initial call data, the service identifier of the service to be called can be obtained. Then, through the service identifier, the service call can be made based on the component parameters through the service to be called and the call result corresponding to the initial call data can be obtained.
[0058] In one embodiment of this application, in a form scenario, if the initial call data entered by the user in the data form is "Customer ID=123456, Application Amount=100000", then the form field triggers the onChange (focus loss after input) event; based on the pre-set parameter conversion logic, the initial call data is converted to obtain component parameters, which are customerId=123456 and applyAmount=100000; the service identifier of the service to be called is called, and the service is called based on the component parameters to obtain the call result corresponding to the initial call data, which is creditScore=850 and riskLevel=A; according to formScene.resultWriteBack, the result is written back to the corresponding fields of the form (e.g., the "Credit Score" field displays 850, and the "Risk Level" field displays A); the form is updated and displayed, and the user can continue to operate.
[0059] In one embodiment of this application, in a process scenario, if the process execution reaches the "credit check node" (such as the risk control stage of a resource borrowing approval process), the process engine provides initial call data, which may include: context.customer.id=123456, context.loan.amount=100000; based on pre-set parameter conversion logic, the initial call data is converted to obtain component parameters; the service identifier of the service to be called is invoked, and the service is called based on the component parameters to obtain the call result corresponding to the initial call data, which is context.risk.credit_score=850. The process context is updated according to flowScene.resultPass; the process engine reads the updated context and determines the subsequent node (such as risk level A, executing the "automatic approval" node); the process continues to execute, and the component call log is recorded simultaneously.
[0060] The aforementioned service invocation method obtains initial invocation data; performs data transformation on the initial invocation data based on pre-defined parameter transformation logic to obtain component parameters; and then performs a service invocation based on the component parameters to obtain the invocation result corresponding to the initial invocation data. As can be seen from the above, this application transforms the initial invocation data based on pre-defined parameter transformation logic during the service invocation process, achieving adaptation of initial invocation data for multiple business scenarios. This ensures that the component parameters obtained after data transformation can be processed uniformly, preventing the smooth progress of service invocation from being affected by differences in initial invocation data under different business scenarios. This enables service invocation operations for multiple business scenarios without the need for separate design and development for each business scenario, ensuring smooth service invocation and reducing the complexity of the service invocation process.
[0061] In one embodiment, such as Figure 3 As shown, when it is necessary to make a service call based on component parameters and obtain the call result corresponding to the initial call data, the following can be included:
[0062] S301, Determine the scenario type for which the initial data call is intended.
[0063] The scenario types include process scenarios and single-table scenarios.
[0064] S302, based on the scenario type and component parameters, makes a service call and obtains the call result corresponding to the initial call data.
[0065] It should be noted that when it is necessary to make a service call based on the scenario type and component parameters to obtain the call result corresponding to the initial call data, the following may be included: determining the component identifier corresponding to the initial call data; making a service call based on the scenario type and component parameters according to the service component corresponding to the component identifier to obtain the call result corresponding to the initial call data.
[0066] The component identifier is a unique identifier for the component to be invoked that processes the initial call data.
[0067] Specifically, the component identifier corresponding to the initial call data can be obtained in advance, and the component identifier, scenario type and component parameters can be input into the component service call interface to realize service processing of the component to be called through the component identifier, and the feedback result of the component service call interface can be obtained. The feedback result is the call result corresponding to the initial call data.
[0068] The above service invocation method, by determining the scenario type targeted by the initial invocation data, realizes service invocation based on scenario type and component parameters, and obtains the invocation result corresponding to the initial invocation data. This achieves the adaptation operation of initial invocation data corresponding to multiple business scenarios, ensuring that the component parameters obtained after data conversion can be processed uniformly, and preventing the smooth progress of service invocation from being affected by the differences in initial invocation data under different business scenarios.
[0069] In one embodiment, when the scenario type is a single-table scenario, the initial call data needs to be obtained, the following may be included:
[0070] Retrieve the initial call data entered by the user in the data form.
[0071] The data form acquisition process can be as follows: read the table metadata of the existing table database; configure the table metadata according to the mapping relationship between the existing table fields and the low-code form fields to obtain the data form.
[0072] In one embodiment of this application, when it is necessary to read the table metadata of the existing table database, a structured parsing report can be generated by reading the table metadata of the existing table database; then, the table metadata can be determined based on the structured parsing report.
[0073] Specifically, configure the existing database connection (supports MySQL, Oracle, SQL Server, etc.); execute the DatabaseMetaData query to extract table field information (name, type, length, whether it is nullable, comments); the actual source is the database configuration table, such as MySQL's information_schema; identify primary key and foreign key relationships (such as t_loan_application.id related to t_loan_detail.loan_id); the final table structure parsing report can be seen as follows.
[0074]
[0075] Furthermore, the mapping relationship between the fields in the stock table and the fields in the low-code form can be seen as follows:
[0076]
[0077] In one embodiment, when the scenario type is a process scenario, the following may be included when it is necessary to obtain initial call data:
[0078] When the scenario type is a process scenario, the initial call data is obtained based on the process context data in the process configuration.
[0079] It should be noted that when it is necessary to obtain the process configuration, the following may be included: determining the core logic of the existing business; updating the business process based on the core logic and data forms to obtain the process configuration.
[0080] Specifically, when it is necessary to determine the core logic of existing business operations, static code analysis can be used to extract the core logic; the core logic can be as follows:
[0081]
[0082] Furthermore, establish mapping rules for "existing business logic → low-code process nodes" and generate process configurations.
[0083] The above service invocation method ensures the smooth progress of subsequent processes by obtaining initial invocation data in different scenarios, and provides a data foundation for subsequent service invocations.
[0084] In one embodiment, such as Figure 4As shown, when a service call is required, the following can be included:
[0085] S401, in the case of a single-table scenario, retrieve the initial call data entered by the user in the data form.
[0086] S402, when the scenario type is a process scenario, obtain the initial call data based on the process context data in the process configuration.
[0087] S403, based on the pre-defined parameter conversion logic, performs data conversion on the initial call data to obtain component parameters.
[0088] S404, Determine the scenario type for which the initial call data is intended.
[0089] S405, determine the component identifier corresponding to the initial call data.
[0090] S406, based on the service component corresponding to the component identifier, perform service calls based on the scenario type and component parameters to obtain the call result corresponding to the initial call data.
[0091] In one embodiment of this application, a service invocation system can be pre-built to execute service invocation methods. The service invocation system includes a front-end visualization layer, a business service layer, a data storage layer, and a stock adaptation layer. The core modules of the front-end visualization layer include a form designer, a process designer, and a migration monitoring console, providing a drag-and-drop configuration interface that supports dual-scenario configuration of service components, visual monitoring of stock migration progress, and preview of configuration effects. The core modules of the business service layer include a component service, a form service, and a process engine, used to implement core business logic: unified invocation of financial components, form CRUD operations, process execution, and state management. The core modules of the data storage layer include MySQL, MongoDB, and Redis, used to store data: MySQL stores structured configurations (such as component metadata and form fields); MongoDB stores dynamic rules (such as process node configurations); and Redis caches hot data (such as configurations of frequently called components). The core modules of the stock adaptation layer include a reverse parsing service, a data synchronization service, and an interface routing service, used to implement stock migration: parsing the structure and logic of existing tables, synchronizing old and new data, and forwarding traffic from old interfaces to the new platform.
[0092] The aforementioned service invocation method obtains initial invocation data; performs data transformation on the initial invocation data based on pre-defined parameter transformation logic to obtain component parameters; and then performs a service invocation based on the component parameters to obtain the invocation result corresponding to the initial invocation data. As can be seen from the above, this application transforms the initial invocation data based on pre-defined parameter transformation logic during the service invocation process, achieving adaptation of initial invocation data for multiple business scenarios. This ensures that the component parameters obtained after data transformation can be processed uniformly, preventing the smooth progress of service invocation from being affected by differences in initial invocation data under different business scenarios. This enables service invocation operations for multiple business scenarios without the need for separate design and development for each business scenario, ensuring smooth service invocation and reducing the complexity of the service invocation process.
[0093] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.
[0094] Based on the same inventive concept, this application also provides a service invocation apparatus for implementing the service invocation method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more service invocation apparatus embodiments provided below can be found in the limitations of the service invocation method described above, and will not be repeated here.
[0095] In one embodiment, such as Figure 5 As shown, a service invocation device is provided, including: an acquisition module 10, a conversion module 20, and an invocation module 30, wherein:
[0096] Module 10 is used to obtain initial call data.
[0097] The conversion module 20 is used to convert the initial call data based on the pre-set parameter conversion logic to obtain the component parameters.
[0098] Module 30 is used to make service calls based on component parameters and obtain the call results corresponding to the initial call data.
[0099] In one embodiment, the scenario type for which the initial call data is targeted is determined;
[0100] Service calls are made based on scenario type and component parameters to obtain the call results corresponding to the initial call data.
[0101] In one embodiment, the component identifier corresponding to the initial call data is determined;
[0102] Based on the service component corresponding to the component identifier, the service is invoked according to the scenario type and component parameters to obtain the invocation result corresponding to the initial invocation data.
[0103] In one embodiment, the scenario types include process scenarios and single-table scenarios.
[0104] In one embodiment, in the case of a single-table scenario, the initial call data entered by the user in the data form is obtained;
[0105] When the scenario type is a process scenario, the initial call data is obtained based on the process context data in the process configuration.
[0106] In one embodiment, table metadata from the stock table database is read;
[0107] The table metadata is configured with a form based on the mapping relationship between the fields in the stock table and the fields in the low-code form to obtain the data form;
[0108] Determine the core logic of existing business;
[0109] The business process is updated based on the core logic and data forms to obtain the process configuration.
[0110] The aforementioned service invocation device acquires initial invocation data; performs data transformation on the initial invocation data based on pre-set parameter transformation logic to obtain component parameters; and then performs a service invocation based on the component parameters to obtain the invocation result corresponding to the initial invocation data. As can be seen from the above, this application, during the service invocation process, performs data transformation on the initial invocation data based on pre-set parameter transformation logic, achieving adaptation operations for initial invocation data corresponding to multiple business scenarios. This ensures that the component parameters obtained after data transformation can be processed uniformly, preventing the smooth progress of service invocation from being affected by differences in initial invocation data under different business scenarios. It achieves service invocation operations for multiple business scenarios without the need for separate design and development for each business scenario, ensuring smooth service invocation and reducing the cumbersomeness of the service invocation process.
[0111] Each module in the aforementioned service invocation device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can invoke and execute the operations corresponding to each module.
[0112] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 6 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a service call method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.
[0113] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0114] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:
[0115] Get the initial call data;
[0116] Based on the pre-defined parameter conversion logic, the initial call data is converted to obtain the component parameters;
[0117] Service calls are made based on component parameters to obtain the call results corresponding to the initial call data.
[0118] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0119] Determine the scenario type for which the initial data call is intended;
[0120] Service calls are made based on scenario type and component parameters to obtain the call results corresponding to the initial call data.
[0121] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0122] Determine the component identifier corresponding to the initial call data;
[0123] Based on the service component corresponding to the component identifier, the service is invoked according to the scenario type and component parameters to obtain the invocation result corresponding to the initial invocation data.
[0124] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0125] The scenario types include process scenarios and single-table scenarios.
[0126] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0127] In a single-table scenario, retrieve the initial call data entered by the user in the data form;
[0128] When the scenario type is a process scenario, the initial call data is obtained based on the process context data in the process configuration.
[0129] In one embodiment, the processor, when executing a computer program, also performs the following steps:
[0130] Read the table metadata from the existing database;
[0131] The table metadata is configured with a form based on the mapping relationship between the fields in the stock table and the fields in the low-code form to obtain the data form;
[0132] Determine the core logic of existing business;
[0133] The business process is updated based on the core logic and data forms to obtain the process configuration.
[0134] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:
[0135] Get the initial call data;
[0136] Based on the pre-defined parameter conversion logic, the initial call data is converted to obtain the component parameters;
[0137] Service calls are made based on component parameters to obtain the call results corresponding to the initial call data.
[0138] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0139] Determine the scenario type for which the initial data call is intended;
[0140] Service calls are made based on scenario type and component parameters to obtain the call results corresponding to the initial call data.
[0141] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0142] Determine the component identifier corresponding to the initial call data;
[0143] Based on the service component corresponding to the component identifier, the service is invoked according to the scenario type and component parameters to obtain the invocation result corresponding to the initial invocation data.
[0144] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0145] The scenario types include process scenarios and single-table scenarios.
[0146] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0147] In a single-table scenario, retrieve the initial call data entered by the user in the data form;
[0148] When the scenario type is a process scenario, the initial call data is obtained based on the process context data in the process configuration.
[0149] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0150] Read the table metadata from the existing database;
[0151] The table metadata is configured with a form based on the mapping relationship between the fields in the stock table and the fields in the low-code form to obtain the data form;
[0152] Determine the core logic of existing business;
[0153] The business process is updated based on the core logic and data forms to obtain the process configuration.
[0154] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:
[0155] Get the initial call data;
[0156] Based on the pre-defined parameter conversion logic, the initial call data is converted to obtain the component parameters;
[0157] Service calls are made based on component parameters to obtain the call results corresponding to the initial call data.
[0158] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0159] Determine the scenario type for which the initial data call is intended;
[0160] Service calls are made based on scenario type and component parameters to obtain the call results corresponding to the initial call data.
[0161] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0162] Determine the component identifier corresponding to the initial call data;
[0163] Based on the service component corresponding to the component identifier, the service is invoked according to the scenario type and component parameters to obtain the invocation result corresponding to the initial invocation data.
[0164] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0165] The scenario types include process scenarios and single-table scenarios.
[0166] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0167] In a single-table scenario, retrieve the initial call data entered by the user in the data form;
[0168] When the scenario type is a process scenario, the initial call data is obtained based on the process context data in the process configuration.
[0169] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:
[0170] Read the table metadata from the existing database;
[0171] The table metadata is configured with a form based on the mapping relationship between the fields in the stock table and the fields in the low-code form to obtain the data form;
[0172] Determine the core logic of existing business;
[0173] The business process is updated based on the core logic and data forms to obtain the process configuration.
[0174] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.
[0175] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0176] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0177] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.
Claims
1. A service invocation method, characterized in that, The method includes: Get the initial call data; Based on a pre-defined parameter conversion logic, the initial call data is converted to obtain component parameters; Based on the component parameters, a service call is made to obtain the call result corresponding to the initial call data.
2. The method according to claim 1, characterized in that, The process of making a service call based on the component parameters to obtain the call result corresponding to the initial call data includes: Determine the scenario type for which the initial call data is intended; Based on the scenario type and the component parameters, a service call is made to obtain the call result corresponding to the initial call data.
3. The method according to claim 2, characterized in that, The process of making a service call based on the scenario type and the component parameters to obtain the call result corresponding to the initial call data includes: Determine the component identifier corresponding to the initial call data; Based on the service component corresponding to the component identifier, a service call is made according to the scenario type and the component parameters to obtain the call result corresponding to the initial call data.
4. The method according to claim 2, characterized in that, The scenario types include process scenarios and single-table scenarios.
5. The method according to claim 1, characterized in that, The process of obtaining initial call data includes: In a single-table scenario, retrieve the initial call data entered by the user in the data form; When the scenario type is a process scenario, the initial call data is obtained based on the process context data in the process configuration.
6. The method according to claim 5, characterized in that, The method further includes: Read the table metadata from the existing database; The table metadata is configured with a form based on the mapping relationship between the fields in the stock table and the fields in the low-code form to obtain the data form; Determine the core logic of existing business; The business process is updated based on the core logic and the data form to obtain the process configuration.
7. A service invocation device, characterized in that, The device includes: The acquisition module is used to obtain initial call data; The conversion module is used to convert the initial call data based on a pre-set parameter conversion logic to obtain component parameters; The calling module is used to make service calls based on the component parameters and obtain the call results corresponding to the initial call data.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.