CN113590234A - Method, device and equipment for automatically acquiring data and storage medium - Google Patents
Method, device and equipment for automatically acquiring data and storage medium Download PDFInfo
- Publication number
- CN113590234A CN113590234A CN202110785981.5A CN202110785981A CN113590234A CN 113590234 A CN113590234 A CN 113590234A CN 202110785981 A CN202110785981 A CN 202110785981A CN 113590234 A CN113590234 A CN 113590234A
- Authority
- CN
- China
- Prior art keywords
- target
- interface component
- data information
- data
- acquiring
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000004590 computer program Methods 0.000 claims 3
- 238000013461 design Methods 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000012550 audit Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000004801 process automation Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method, a device, equipment and a storage medium for automatically acquiring data, wherein the method for automatically acquiring data is implemented by an RPA (resilient packet access) automation command, and the method comprises the following steps: acquiring a target interface component; and acquiring target data information by using the target interface component. By the method, the design difficulty of the RPA automation command can be reduced, and the RPA program can be maintained easily.
Description
Technical Field
The present application relates to the field of information processing technologies, and in particular, to a method, an apparatus, a device, and a storage medium for automatically acquiring data.
Background
A Robot Process Automation (RPA) is an application that provides a way to convert a user's manual operation into process automation by mimicking the user's manual operation at a computer.
Currently, when an RPA program is designed, page elements need to be relied on for corresponding operations. However, the page elements are not uniform, and the variation of the page elements may make the RPA program unable to execute an error or even unable to execute, so that the RPA program needs to be modified accordingly according to the variation of the page elements, which undoubtedly greatly increases the design difficulty and maintenance difficulty of the RPA program.
Therefore, how to improve the RPA program so that the RPA program can be executed without depending on page elements has a very important meaning for reducing the design difficulty of the RPA program and reducing the maintenance difficulty of the RPA program.
Disclosure of Invention
The application at least provides a method, a device, equipment and a storage medium for automatically acquiring data.
In a first aspect, the present application provides a method for automatically acquiring data, where the method is implemented by an RPA automation command, and the method includes: acquiring a target interface component; and acquiring target data information by using the target interface component.
Therefore, the target data information is directly acquired by using the target interface component, so that the RPA automation command can perform corresponding operation without depending on page elements, the design difficulty of the RPA automation command is reduced, and the RPA program can be easily maintained.
The above-mentioned target data information obtained by using the target interface component includes: obtaining a configuration target interface component by using the determined configuration parameters of the target interface component; and acquiring target data information by utilizing the configuration target interface component.
Therefore, the RPA program can automatically acquire the target data information according to the configuration parameters of the configuration target interface component by using the configuration target interface component.
The above obtaining target data information by using the configuration target interface component includes: sending a data request according to the configuration parameters of the configuration target interface component; receiving a return result of the data request; and obtaining target data information based on the returned result.
Therefore, by sending the data request, the return result of the data request can be received, so that the target data information can be obtained from the return result.
Wherein, the obtaining of the target data information based on the returned result includes: analyzing the returned result to obtain target data information; and/or after acquiring the target data information, the method further comprises: and storing the target data information into a database.
Therefore, by analyzing the returned result, the target data information can be obtained from the returned result. In addition, the target data information is stored in the database, so that the storage of the target data information is realized, and the subsequent management of the target data information is facilitated
Wherein, the configuration parameters at least include one of the following: interface type, interface uniform resource locator, interface data type, and interface data.
Therefore, by determining specific configuration parameters, the determined configuration parameters can be subsequently utilized to obtain corresponding data.
Wherein, the interface type at least includes one of the following types: get, Post, Put, and DELETE; the interface data type includes at least one of: text, JSON, Javascript, XML and HTML.
Therefore, by setting different interface types, different interfaces can be utilized to realize various different operations, and the functions of the RPA program are enriched.
Wherein, the above-mentioned get target interface module includes: and acquiring the interface component selected from the candidate target interface component library, and determining the interface component as the target interface component.
Therefore, by obtaining the interface component selected from the candidate target interface component library and determining it as the target interface component, the specific target interface component can be determined, and the target interface component can be subsequently utilized to automatically obtain data.
A second aspect of the present application provides an apparatus for automatically acquiring data, the apparatus comprising: the system comprises a calling module and an acquisition module, wherein the calling module is used for acquiring a target interface component; and the acquisition module is used for acquiring the target data information by using the target interface component.
A third aspect of the present application provides an electronic device comprising a memory and a processor coupled to each other, the processor being configured to execute program instructions stored in the memory to implement the method for automatically acquiring data described in the first aspect.
A fourth aspect of the present application provides a computer readable storage medium having stored thereon program instructions which, when executed by a processor, implement the method of automatically acquiring data as described in the first aspect above.
According to the scheme, the target data information is directly acquired by using the target interface component, so that the RPA automation command can be correspondingly operated without depending on page elements, the design difficulty of the RPA automation command is reduced, and the RPA program can be easily maintained.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application.
FIG. 1 is a first flowchart of an embodiment of a method for automatically acquiring data according to the present application;
FIG. 2 is a second flowchart of an embodiment of a method for automatically acquiring data according to the present application;
FIG. 3 is a third flowchart of an embodiment of a method for automatically acquiring data according to the present application;
FIG. 4 is a block diagram of an embodiment of an automatic data acquisition device according to the present application;
FIG. 5 is a block diagram of an embodiment of an electronic device of the present application;
FIG. 6 is a block diagram of an embodiment of a computer-readable storage medium of the present application.
Detailed Description
The following describes in detail the embodiments of the present application with reference to the drawings attached hereto.
In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular system structures, interfaces, techniques, etc. in order to provide a thorough understanding of the present application.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship. Further, the term "plurality" herein means two or more than two. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.
The method for automatically acquiring data described in the present application can be implemented by executing an RPA program.
Referring to fig. 1, fig. 1 is a first flowchart of an embodiment of a method for automatically acquiring data according to the present application. Specifically, the RPA program may perform the following steps S11 and S12.
Step S11: a target interface component is obtained.
The interfaces include, for example, a Hypertext Transfer Protocol (HTTP) -based Interface, an Application Programming Interface (API), a Remote Procedure Call Protocol (RPC) Interface, and the like. A component is a package for data and methods, such as a component in C + + Builder, or a component in Delphi, or a control in the VB (visual basic) programming language, and so forth. In this application, a target interface component is a component that can send interface requests, receive interface requests, and receive returned results.
In the present application, the RPA program may obtain the target interface component when executing, i.e. call the target interface component to perform the relevant operation.
In one embodiment, the acquiring of the target interface component may specifically be: and acquiring the interface component selected from the candidate target interface component library, and determining the interface component as the target interface component. The candidate target interface component library may include a plurality of target interface components, and a developer of the RPA program or a person using the RPA program may select one or more target interface components from the target interface component library. At this point, it can be considered that the required interface component has been determined from the library of candidate target interface components. When the RPA program is executed, the interface component selected from the candidate target interface component library can be obtained, then the selected interface component is used as the target interface component, and the target interface component can be utilized to execute the relevant operation. Therefore, by obtaining the interface component selected from the candidate target interface component library and determining it as the target interface component, the specific target interface component can be determined, and the target interface component can be subsequently utilized to automatically obtain data.
Step S12: and acquiring target data information by using the target interface component.
After the target interface component is obtained, the relevant interface in the target interface component can send the interface request or receive the interface request, and then the data returned after the request sent by the target interface component is received. The method for receiving the receipt through the call interface can refer to the common method in the field, and is not described in detail here.
Therefore, the target data information is directly acquired by using the target interface component, so that the RPA automation command can perform corresponding operation without depending on page elements, the design difficulty of the RPA automation command is reduced, and the RPA program can be easily maintained.
Referring to fig. 2, fig. 2 is a second flowchart of an embodiment of a method for automatically acquiring data according to the present application. The present embodiment is a further extension of the aforementioned step of "acquiring target data information using a target interface component", and specifically may include step S121 and step S122.
Step S121: and obtaining the configuration target interface component by using the determined configuration parameters of the target interface component.
The configuration parameters of the target interface component can be set by a developer of the RPA program or a person using the RPA program, or can be automatically acquired by the RPA program in a parameter database. The parameter database is, for example, a parameter file set in advance by a developer of the RPA program.
By using the determined configuration parameters of the target interface component, the target interface component can execute corresponding operations according to the determined configuration parameters.
In one embodiment, the configuration parameters include at least one of: interface type, interface uniform resource locator, interface data type, and interface data.
In one embodiment, the interface types may include Get, Post, Put, and DELETE. Get, Post, Put, and DELETE are, for example, four types in the HTTP interface. For example, the Get interface may send a Get request, i.e., a request to request data to a database, to obtain the data. The Post interface can send a Post request, that is, send data to the server side, and the request can change resources such as the type of the data. The PUT interface may send a PUT request, that is, may send data to the server side, and the request may modify the content of the data, but may not increase the kind of the data. The DELETE interface can send a DELETE request for deleting a resource. In addition, when sending the request, a request in json (JavaScript Object Notation) format may be sent, such as a Post request sent by a Post interface in json format. Therefore, by setting different interface types, different interfaces can be utilized to realize various different operations, and the functions of the RPA program are enriched.
The interface data type may be considered a data format of the data. In one embodiment, the interface data type includes at least one of: text, JSON, Javascript, XML and HTML. It can be understood that Text, JSON, Javascript, XML, and HTML can be general data formats in the internet field, and are not described herein again. Therefore, by setting different interface data types, different types of data can be obtained by the RPA program.
The interface uniform resource locator is, for example, (URL). The interface data may be data that the user specifically wants to obtain, for example, the interface data may be "invoice code", "invoice number", or the like.
Therefore, by determining specific configuration parameters, the determined configuration parameters can be subsequently utilized to obtain corresponding data.
Step S122: and acquiring target data information by utilizing the configuration target interface component.
According to the configuration parameters in the configuration target interface component, the RPA program can utilize the configuration target interface component to execute the relevant operation, so that the configuration target interface component can acquire the target data information.
In a specific embodiment, the target interface component is configured to be a Get interface request component, the interface type is a Get interface, the interface uniform resource locator is "XXXXXX", the interface data type is Jason, and the interface data is "[ { \\" status \ 100033\ ",// employee ID \ departid \": 0003\ ",// department ID \" checkid \ ": 6\",// audit type ID } ] ".
Therefore, the RPA program can automatically acquire the target data information according to the configuration parameters of the configuration target interface component by using the configuration target interface component.
Referring to fig. 3, fig. 3 is a third flow chart of the embodiment of the method for automatically acquiring data according to the present application. In this embodiment, the step of "acquiring target data information by using the configuration target interface component" may specifically include step S1221 to step S1223.
Step S1221: and sending the data request according to the configuration parameters of the configuration target interface component.
In this embodiment, in the configuration parameters of the configuration target interface component, the interface type is an interface capable of sending a data request, for example, a Get interface sends a Get request. Therefore, when the RPA program specifically utilizes the configuration target interface component, the RPA program may send a data request according to the configuration parameters of the configuration target interface component to request to obtain the target data information.
Step S1222: and receiving a return result of the data request.
It is understood that after the RPA program sends a data request, the server side receiving the data request may send corresponding data in response to the data request. At this time, the RPA program may receive a return result of the data request, that is, data that the receiving server side may return in response to the data request, and the data returned by the server may include the target data information.
Step S1223: and obtaining target data information based on the returned result.
Because the return result comprises the target data information, the target data information can be extracted from the return result, so that the target data information can be obtained.
In one embodiment, the target data information is obtained based on the returned result, and specifically, the returned result may be analyzed to obtain the target data information. For some data, due to the interface data type, the returned result needs to be analyzed to obtain the target data information. For example, the returned data is data in json format, and at this time, the data in json format may be analyzed to obtain target data information. Therefore, by analyzing the returned result, the target data information can be obtained from the returned result.
Therefore, by sending the data request, the return result of the data request can be received, so that the target data information can be obtained from the return result.
In one embodiment, the RPA program may also store the target data information in a database after obtaining the target data information, for example, the RPA program may create a database table and store the target data information in the database. Therefore, the target data information can be stored, and the target data information can be conveniently managed subsequently.
The following is an exemplary set of configuration parameters for a target interface component.
Interface types are as follows: and a GET interface.
Interface uniform resource locator:
"http://10.1.3.19:9097/necp/mapp/terminal/service/bill/record/bill/query InoviceByYwid"。
interface data type: JSON.
Interface data:
"[ { \\" staffid \ ": 100033\",/employee ID \ departid \ ": 0003\",/department ID \ checkid \ ": 6\",/audit type ID } ].
Referring to fig. 4, fig. 4 is a schematic diagram of a framework of an embodiment of an automatic data acquisition device according to the present application. The automatic data acquisition device 40 includes: a calling module 41 and an obtaining module 42. The calling module 41 is used for acquiring a target interface component; the acquisition module 42 is used to acquire target data information using the target interface component.
The obtaining module 42 is configured to obtain target data information by using a target interface component, and includes: obtaining a configuration target interface component by using the determined configuration parameters of the target interface component; and acquiring target data information by utilizing the configuration target interface component.
The obtaining module 42 is configured to obtain the target data information by using the configuration target interface component, and includes: sending a data request according to the configuration parameters of the configuration target interface component; receiving a return result of the data request; and obtaining target data information based on the returned result.
The obtaining module 42 is configured to obtain target data information based on a returned result, and includes: analyzing the returned result to obtain target data information; and/or, the automatic data acquisition device 40 further includes a storage module, and after the acquisition module 42 is used for acquiring the target data information, the storage module is used for storing the target data information into the database.
Wherein, the configuration parameters at least include one of the following: interface type, interface uniform resource locator, interface data type, and interface data.
Wherein, the interface type at least includes one of the following types: get, Post, Put, and DELETE; the interface data type includes at least one of: text, JSON, Javascript, XML and HTML.
The calling module 41 is configured to obtain a target interface component, and includes: and acquiring the interface component selected from the candidate target interface component library, and determining the interface component as the target interface component.
Referring to fig. 5, fig. 5 is a schematic diagram of a frame of an embodiment of an electronic device according to the present application. The electronic device 50 comprises a memory 51 and a processor 52 coupled to each other, and the processor 52 is configured to execute RPA program instructions stored in the memory 51 to implement the steps of any of the above-described embodiments of the method for automatically acquiring data. In one particular implementation scenario, electronic device 50 may include, but is not limited to: a microcomputer, a server, and the electronic device 50 may also include a mobile device such as a notebook computer, a tablet computer, and the like, which is not limited herein.
In particular, the processor 52 is configured to control itself and the memory 51 to implement the steps of any of the above-mentioned embodiments of the method for automatically acquiring data, and the processor 52 may also be referred to as a Central Processing Unit (CPU). Processor 52 may be an integrated circuit chip having signal processing capabilities. The Processor 52 may also be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. In addition, the processor 52 may be commonly implemented by an integrated circuit chip.
Referring to fig. 6, fig. 6 is a block diagram illustrating an embodiment of a computer-readable storage medium according to the present application. The computer readable storage medium 60 stores program instructions 61 executable by the processor, the program instructions 61 for implementing the steps of any of the above-described method embodiments for automatically acquiring data.
According to the scheme, the target data information is directly acquired by using the target interface component, so that the RPA automation command can be correspondingly operated without depending on page elements, the design difficulty of the RPA automation command is reduced, and the RPA program can be easily maintained.
In some embodiments, functions of or modules included in the apparatus provided in the embodiments of the present disclosure may be used to execute the method described in the above method embodiments, and specific implementation thereof may refer to the description of the above method embodiments, and for brevity, will not be described again here.
The foregoing description of the various embodiments is intended to highlight various differences between the embodiments, and the same or similar parts may be referred to each other, and for brevity, will not be described again herein.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a module or a unit is merely one type of logical division, and an actual implementation may have another division, for example, a unit or a component may be combined or integrated with another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some interfaces, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Claims (10)
1. A method for automatically acquiring data, the method being implemented by executing an RPA program, comprising:
acquiring a target interface component;
and acquiring target data information by using the target interface component.
2. The method of claim 1, wherein the obtaining target data information using the target interface component comprises:
obtaining a configuration target interface component by using the determined configuration parameters of the target interface component;
and acquiring target data information by utilizing the configuration target interface component.
3. The method of claim 2, wherein said obtaining target data information using said configuration target interface component comprises:
sending a data request according to the configuration parameters of the configuration target interface component;
receiving a return result of the data request;
and obtaining the target data information based on the return result.
4. The method of claim 3, wherein obtaining the target data information based on the returned result comprises: analyzing the returned result to obtain the target data information; and/or the presence of a gas in the gas,
after the obtaining target data information, the method further comprises: and storing the target data information into a database.
5. The method according to any of claims 1-4, wherein the configuration parameters comprise at least one of: interface type, interface uniform resource locator, interface data type, and interface data.
6. The method of claim 5, wherein the interface type comprises at least one of: get, Post, Put, and DELETE; the interface data types include at least one of: text, JSON, Javascript, XML and HTML.
7. The method of any of claims 1-4, wherein obtaining the target interface component comprises:
and acquiring the interface component selected from the candidate target interface component library, and determining the interface component as the target interface component.
8. An automatic data acquisition device, comprising:
the calling module is used for acquiring a target interface component;
and the acquisition module is used for acquiring target data information by using the target interface component.
9. An electronic device comprising a processor and a memory coupled to each other, wherein,
the processor is configured to execute the memory-stored computer program to perform the method of any of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which can be executed by a processor, the computer program being adapted to carry out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110785981.5A CN113590234A (en) | 2021-07-12 | 2021-07-12 | Method, device and equipment for automatically acquiring data and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110785981.5A CN113590234A (en) | 2021-07-12 | 2021-07-12 | Method, device and equipment for automatically acquiring data and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113590234A true CN113590234A (en) | 2021-11-02 |
Family
ID=78247106
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110785981.5A Pending CN113590234A (en) | 2021-07-12 | 2021-07-12 | Method, device and equipment for automatically acquiring data and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113590234A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114070902A (en) * | 2021-11-11 | 2022-02-18 | 中国工商银行股份有限公司 | DELPHI-based message processing method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180197123A1 (en) * | 2017-01-09 | 2018-07-12 | Sutherland Global Services Inc. | Robotics process automation platform |
| WO2018161799A1 (en) * | 2017-03-08 | 2018-09-13 | 中兴通讯股份有限公司 | Cloud application deployment method and system |
| CN109240838A (en) * | 2018-09-20 | 2019-01-18 | 深圳市牛鼎丰科技有限公司 | Interface call method, device, computer equipment and storage medium |
| US20200004798A1 (en) * | 2018-06-27 | 2020-01-02 | Q2 Software, Inc. | Method and system for automating web processes utilizing an abstractable underlying platform layer |
| CN111258563A (en) * | 2020-01-16 | 2020-06-09 | 江苏满运软件科技有限公司 | Interface document generation method and device, storage medium and electronic equipment |
| CN111597059A (en) * | 2020-04-18 | 2020-08-28 | 北京奇保信安科技有限公司 | Interface calling request processing method and device and electronic equipment |
| CN112188014A (en) * | 2020-10-28 | 2021-01-05 | 中国联合网络通信集团有限公司 | Information processing method and device |
-
2021
- 2021-07-12 CN CN202110785981.5A patent/CN113590234A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180197123A1 (en) * | 2017-01-09 | 2018-07-12 | Sutherland Global Services Inc. | Robotics process automation platform |
| WO2018161799A1 (en) * | 2017-03-08 | 2018-09-13 | 中兴通讯股份有限公司 | Cloud application deployment method and system |
| US20200004798A1 (en) * | 2018-06-27 | 2020-01-02 | Q2 Software, Inc. | Method and system for automating web processes utilizing an abstractable underlying platform layer |
| CN109240838A (en) * | 2018-09-20 | 2019-01-18 | 深圳市牛鼎丰科技有限公司 | Interface call method, device, computer equipment and storage medium |
| CN111258563A (en) * | 2020-01-16 | 2020-06-09 | 江苏满运软件科技有限公司 | Interface document generation method and device, storage medium and electronic equipment |
| CN111597059A (en) * | 2020-04-18 | 2020-08-28 | 北京奇保信安科技有限公司 | Interface calling request processing method and device and electronic equipment |
| CN112188014A (en) * | 2020-10-28 | 2021-01-05 | 中国联合网络通信集团有限公司 | Information processing method and device |
Non-Patent Citations (1)
| Title |
|---|
| 程志伦;范玉青;: "钢铁企业基于组件的柔性制造执行系统设计", 计算机集成制造系统, no. 03 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114070902A (en) * | 2021-11-11 | 2022-02-18 | 中国工商银行股份有限公司 | DELPHI-based message processing method and device |
| CN114070902B (en) * | 2021-11-11 | 2024-03-29 | 中国工商银行股份有限公司 | Message processing method and device based on DELPHI |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111782546B (en) | Automatic interface testing method and device based on machine learning | |
| CN112733001B (en) | Method and device for acquiring subscription information and electronic equipment | |
| US9665732B2 (en) | Secure Download from internet marketplace | |
| CN107634947A (en) | Limitation malice logs in or the method and apparatus of registration | |
| CN110909013A (en) | Service list generation method, device, equipment and computer readable storage medium | |
| CN110808868A (en) | Test data acquisition method and device, computer equipment and storage medium | |
| CN113190562A (en) | Report generation method and device and electronic equipment | |
| CN113127335A (en) | System testing method and device | |
| CN109862074B (en) | Data acquisition method and device, readable medium and electronic equipment | |
| CN113590234A (en) | Method, device and equipment for automatically acquiring data and storage medium | |
| CN108829568A (en) | A kind of data monitoring method and device | |
| CN110633432A (en) | Method, device, terminal equipment and medium for acquiring data | |
| CN107347024B (en) | Method, equipment and system for storing operation log | |
| EP3502925A1 (en) | Computer system and method for extracting dynamic content from websites | |
| US8321535B2 (en) | Web services integration systems and methods | |
| EP4145300A1 (en) | Method and apparatus for processing order data | |
| CN115412920A (en) | Internet of things equipment binding system, method and device and electronic equipment | |
| CN112306791B (en) | Performance monitoring method and device | |
| US8200713B2 (en) | Database exploration for building wireless component applications | |
| CN113220558B (en) | Monitoring script generation method and device, and monitoring method and device | |
| CN110909269A (en) | Log reporting method and device | |
| CN113364890B (en) | Data processing method, device, network equipment and medium | |
| CN114338240B (en) | Vulnerability scanning method and device | |
| CN116301869B (en) | Front-end page configuration management and control system, method, equipment and medium | |
| CN113268417B (en) | Task execution method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20211102 |