CN113360043A - Service processing method and device - Google Patents
Service processing method and device Download PDFInfo
- Publication number
- CN113360043A CN113360043A CN202110724443.5A CN202110724443A CN113360043A CN 113360043 A CN113360043 A CN 113360043A CN 202110724443 A CN202110724443 A CN 202110724443A CN 113360043 A CN113360043 A CN 113360043A
- Authority
- CN
- China
- Prior art keywords
- transaction
- interface
- configuration information
- target
- identifier
- 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.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 19
- 238000000034 method Methods 0.000 claims abstract description 31
- 230000004044 response Effects 0.000 claims abstract description 28
- 238000012790 confirmation Methods 0.000 claims abstract description 14
- 238000012545 processing Methods 0.000 claims description 80
- 238000012795 verification Methods 0.000 claims description 47
- 230000004048 modification Effects 0.000 claims description 20
- 238000012986 modification Methods 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 9
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 238000013461 design Methods 0.000 description 21
- 230000007246 mechanism Effects 0.000 description 18
- 230000006870 function Effects 0.000 description 9
- 238000013507 mapping Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000008520 organization Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000003032 molecular docking Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000004382 visual function Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04842—Selection of displayed objects or displayed text elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Human Computer Interaction (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention provides a service processing method and equipment, wherein the method comprises the following steps: acquiring a transaction identifier of a transaction selected by a user, and acquiring configuration information; displaying a transaction interface corresponding to the transaction according to the configuration information and the transaction identifier; when a confirmation instruction is received, acquiring business data input by a user on the transaction interface, and determining interface configuration information of a target interface to be accessed corresponding to the transaction according to the configuration information; calling a target interface according to the interface configuration information of the target interface and the service data; and receiving a service response message sent by the target interface, outputting the service response message, and realizing successful calling of an external interface, so that the provided service is richer, service limitation is avoided, and universality is achieved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computer finance, in particular to a business processing method and equipment.
Background
A transaction is a basic unit for performing a business function, and a business function may consist of one to more transactions. At present, when a transaction available for a user is generated, that is, when a transaction code is generated, a corresponding transaction code is generally automatically generated based on a corresponding data table structure, so that a corresponding transaction service available for the user is provided based on the transaction code.
However, when the transaction code is automatically generated based on the data table structure, an external interface cannot be called for service processing, that is, a service provided by an external system cannot be used, so that the service is limited and the user experience is low.
Disclosure of Invention
The embodiment of the invention provides a service processing method and equipment, aiming at solving the technical problem that an external interface cannot be called in the prior art.
In a first aspect, an embodiment of the present invention provides a service processing method, including:
acquiring a transaction identifier of a transaction selected by a user, and acquiring configuration information;
displaying a transaction interface corresponding to the transaction according to the configuration information and the transaction identifier;
when a confirmation instruction is received, acquiring business data input by a user on the transaction interface, and determining interface configuration information of a target interface to be accessed corresponding to the transaction according to the configuration information;
calling a target interface according to the interface configuration information of the target interface and the service data;
and receiving a service response message sent by the target interface and outputting the service response message.
In one possible design, the configuration information includes front-end configuration information;
the displaying of the transaction interface corresponding to the transaction according to the configuration information and the transaction identifier includes:
acquiring element configuration information of the transaction element corresponding to the transaction identifier from the front-end configuration information;
and page loading is carried out according to the element configuration information of the transaction element so as to display a transaction interface corresponding to the transaction.
In one possible design, the method further includes:
and for each transaction element corresponding to the transaction identifier, when the front-end configuration information is determined to have a verification rule corresponding to the transaction element, binding the transaction element with the verification rule.
In one possible design, the interface configuration information includes a message format, an interface calling mode, an input parameter type and an interface identifier;
the calling the target interface according to the interface configuration information of the target interface and the service data comprises:
determining an input parameter value corresponding to the input parameter type corresponding to the target interface according to the service data;
according to the message format of the target interface, packaging the interface identifier of the target interface and the input parameter value to obtain a service processing message;
and sending the service processing message to a target end according to an interface calling mode of a target interface so as to call the target interface.
In one possible design, the configuration information includes front-end and back-end associated configuration information and back-end calling configuration information;
the determining interface configuration information of the target interface to be accessed corresponding to the transaction according to the configuration information includes:
acquiring a key transaction element identifier corresponding to the transaction interface;
determining an interface identifier corresponding to the key transaction element identifier from the front-end and back-end associated configuration information, and determining the interface identifier as a target interface identifier;
and acquiring interface configuration information corresponding to the target interface identifier from the back-end calling configuration information.
In one possible design, the transaction interface includes a plurality of transaction elements;
the calling the target interface according to the interface configuration information of the target interface and the service data comprises:
acquiring a target transaction element corresponding to the business data, and acquiring a verification rule corresponding to the target transaction element, wherein the target transaction element is a transaction element of input business data;
verifying the service data corresponding to the target transaction element according to a verification rule corresponding to the target transaction element to obtain a verification result;
and if the verification result is successful, calling the target interface according to the interface configuration information of the target interface and the service data.
In one possible design, the method further includes:
and acquiring a configuration information modification request, and modifying the configuration information according to the configuration information modification request.
In a second aspect, an embodiment of the present invention provides a service processing device, including:
the processing module is used for acquiring a transaction identifier of a transaction selected by a user and acquiring configuration information;
the processing module is further used for displaying a transaction interface corresponding to the transaction according to the configuration information and the transaction identifier;
the processing module is further configured to, when receiving a confirmation instruction, acquire service data input by a user on the transaction interface, and determine interface configuration information of a target interface to be accessed corresponding to the transaction according to the configuration information;
the receiving and sending module is used for calling the target interface according to the interface configuration information of the target interface and the service data;
the transceiver module is further configured to receive a service response packet sent by the target interface, and output the service response packet.
In one possible design, the configuration information includes front-end configuration information;
the processing module is further configured to:
acquiring element configuration information of the transaction element corresponding to the transaction identifier from the front-end configuration information;
and page loading is carried out according to the element configuration information of the transaction element so as to display a transaction interface corresponding to the transaction.
In one possible design, the processing module is further to:
and for each transaction element corresponding to the transaction identifier, when the front-end configuration information is determined to have a verification rule corresponding to the transaction element, binding the transaction element with the verification rule.
In one possible design, the interface configuration information includes a message format, an interface calling mode, an input parameter type and an interface identifier;
the processing module is further configured to:
determining an input parameter value corresponding to the input parameter type corresponding to the target interface according to the service data;
according to the message format of the target interface, packaging the interface identifier of the target interface and the input parameter value to obtain a service processing message;
and sending the service processing message to a target end according to an interface calling mode of a target interface so as to call the target interface.
In one possible design, the configuration information includes front-end and back-end associated configuration information and back-end calling configuration information;
the processing module is further configured to:
acquiring a key transaction element identifier corresponding to the transaction interface;
determining an interface identifier corresponding to the key transaction element identifier from the front-end and back-end associated configuration information, and determining the interface identifier as a target interface identifier;
and acquiring interface configuration information corresponding to the target interface identifier from the back-end calling configuration information.
In one possible design, the transaction interface includes a plurality of transaction elements;
the processing module is further configured to:
acquiring a target transaction element corresponding to the business data, and acquiring a verification rule corresponding to the target transaction element, wherein the target transaction element is a transaction element of input business data;
verifying the service data corresponding to the target transaction element according to a verification rule corresponding to the target transaction element to obtain a verification result;
and if the verification result is successful, calling the target interface according to the interface configuration information of the target interface and the service data.
In one possible design, the processing module is further to:
and acquiring a configuration information modification request, and modifying the configuration information according to the configuration information modification request.
In a third aspect, an embodiment of the present invention provides an electronic device, including: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the business process method of the transaction program as described above in the first aspect and in various possible designs of the first aspect.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where computer-executable instructions are stored, and when a processor executes the computer-executable instructions, the business processing method according to the first aspect and various possible designs of the first aspect is implemented.
In a fifth aspect, an embodiment of the present invention provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the business processing method according to the first aspect and various possible designs of the first aspect is implemented.
The invention provides a business processing method and equipment, which are characterized in that when a transaction identifier corresponding to a transaction selected by a user is acquired, the transaction identifier indicates that the user needs to use the transaction, namely the business corresponding to the transaction needs to be used, and then configuration information and the transaction identifier are utilized to generate a corresponding transaction page code, namely a transaction interface corresponding to the transaction is displayed for the user to use. When receiving the confirmation instruction, indicating that the service processing is needed, that is, the transaction is needed to be realized, acquiring the service data input by the user on the transaction interface, and determining an external interface which is needed to be accessed when the transaction is realized, that is, interface configuration information of the target interface based on the configuration information, so as to call the target interface by using the interface configuration information, so as to perform the service processing on the service data by using the target interface, that is, the service provided by the external system can be used, and a service response message returned by the target interface when the service processing is successful is output, so as to realize the successful call of the external interface, thereby enabling the provided service to be richer, avoiding the service limitation, and having universality. Meanwhile, when the user needs to update the relevant information of the transaction, the transaction can be updated by updating the configuration information, the operation is simple, the updating efficiency is high, and therefore the user experience can be effectively improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic view of a scenario of a service processing method according to an embodiment of the present invention;
fig. 2 is a first schematic flow chart of a service processing method according to an embodiment of the present invention;
fig. 3 is a schematic diagram of front-end configuration information provided in an embodiment of the present invention;
fig. 4 is a schematic flowchart of configuration information management according to an embodiment of the present invention;
fig. 5 is a second flowchart of a service processing method according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a service processing process provided in an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a service processing device according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms used in the present application are explained below:
trading: the basic unit for completing the business function is irrevocable from the business view, and one business function is composed of one to a plurality of transactions.
Front-end transaction, i.e. transaction interface: and the visual function interface with the input interaction function is visible to the user.
Back-end calling: the service user is invisible, and the user completes the external calling interface of the service function.
Transaction elements: the minimum unit which can be seen or operated by the user is represented as basic operation such as an input box, a button and the like.
Service parameters: the data plays an important role in the operation of the system, and the data has the obvious characteristic of not influencing specific customers but influencing one or all customers, such as loan prices, service switches and the like.
Business rules, i.e. check rules: the business elements themselves or do not need the constraint conditions satisfied by the business elements, such as whether the business elements need to be input, the length, whether the boundary values are satisfied, and the like.
The enterprise-level parameter management, namely the configuration information management is used as an important component of enterprise operation, and efficient and uniform management and control are provided for the operation of each business line. In order to provide a corresponding transaction service to a user, it is often necessary to utilize relevant configuration information to generate a transaction service, i.e. a transaction code corresponding to a transaction, based on the configuration information.
In the prior art, configuration information is generally solidified in a data table structure, when a transaction code is generated, an operation interface understandable by a user is generated by reading information such as comments, field lengths and types of the table structure, and a persistent layer generally executes basic operations of adding, deleting, modifying and checking according to information such as a main key and a field type of the table structure, and finally generates the transaction code for performing basic operations on a single data table. When the business requirement changes, the table structure needs to be modified to modify the configuration information, so that the configuration information is consistent with the business requirement, namely, the transaction interface is consistent with the business requirement. However, since the configuration information is fixed in the table structure, the transaction and configuration information, i.e. the physical table, are tightly coupled, the table structure needs to be modified to modify the corresponding configuration information, and the modification of the table structure is complex and the modification cost is high, so that the difficulty of modifying, i.e. managing, the configuration information is high. Meanwhile, when the transaction code is automatically generated based on the data table structure, an external interface cannot be called to perform service processing, the requirement of docking with the external interface cannot be met, and the universality is not realized.
Therefore, aiming at the problems, the technical idea of the invention stores the relevant configuration information of the transaction foreground and the transaction background in the database in a configuration mode, realizes the dynamic configuration of the transaction, and decouples the configuration information from the transaction, thereby quickly modifying the configuration information and reducing the modification difficulty of the configuration information; meanwhile, data adaptation can be carried out, namely business data submitted by a user are converted into corresponding business processing messages of an external interface to be called, the business processing messages are sent to a system where the external interface is located so as to call the external interface on the system, calling of the external interface is achieved, namely, the external interface is supported to be in butt joint with the external interface, universality and universality are achieved, and user experience is improved.
The following describes the technical solutions of the present disclosure and how to solve the above technical problems in detail by specific examples. Several of these specific examples may be combined with each other below, and some of the same or similar concepts or processes may not be repeated in some examples. Examples of the present disclosure will now be described with reference to the accompanying drawings.
Fig. 1 is a schematic view of a scenario of a service processing method according to an embodiment of the present invention, as shown in fig. 1, when a user needs to use a transaction on an electronic device 101, the electronic device 101 invokes a target interface on a target terminal 102 to implement the transaction, that is, perform corresponding service processing.
The electronic device 101 includes a server, a computer, and the like, which can provide transaction services, i.e., services, and specifically, the electronic device may be a transaction system.
The target 102 is a third-party system, such as a database.
Fig. 2 is a first schematic flow chart of a service processing method according to an embodiment of the present invention, where an execution main body of the embodiment may be the electronic device shown in fig. 1. As shown in fig. 2, the method includes:
s201, acquiring a transaction identifier of a transaction selected by a user, and acquiring configuration information.
In this embodiment, when a user (e.g., business) needs to use a certain transaction, a transaction for which the user needs to be used is selected from the transaction list. And acquiring a transaction identifier corresponding to the transaction selected by the user, and acquiring configuration information so as to load a transaction interface and perform corresponding service processing by using the configuration information.
Optionally, the configuration information includes front-end configuration information (for example, as shown in fig. 3), front-end and back-end association configuration information, and back-end invocation configuration information.
The front-end configuration information represents information related to front-end display content corresponding to a transaction, and includes one or more of a transaction identifier and element configuration information of a corresponding transaction element thereof, a key transaction element identifier, a target transaction element representation, transaction interface layout information (for example, a style sheet), a transaction element position, and a check rule, namely, a business rule.
Optionally, the transaction element is a transaction identifier, that is, a component included in a transaction interface corresponding to the transaction, for example, a text box and a button. Accordingly, the element configuration information of the transaction element characterizes how to display the transaction element on the transaction interface, and includes the identification of the transaction element and the attribute information of the transaction element, such as the background color, shape, font, and other attributes of the text box.
Optionally, the target transaction element represents a transaction element to which the verification rule needs to be bound, that is, a business element, and correspondingly, the target transaction element identifier is an identifier of the target transaction element.
Optionally, the check rule, i.e. the business rule, indicates the constraint condition that needs to be satisfied between the transaction elements themselves or between the transaction elements, such as whether the constraint condition is a must-fail type, a length, whether a boundary value is satisfied, and the like.
Optionally, the key transaction element represents a transaction element that needs to use an external interface, that is, when the transaction interface includes the key transaction element, the external interface corresponding to the key transaction element needs to be called to perform related processing in the process of performing a transaction. For example, when the key transaction element is a mechanism code input box, the user inputs a mechanism code to be queried in the mechanism code input box, and the electronic device queries the mechanism detailed information corresponding to the mechanism code by calling the external interface corresponding to the mechanism code input box. Accordingly, the key transaction element identification is an identification of the key transaction element.
Optionally, the front-end and back-end associated configuration information represents a mapping relationship between the front-end transaction and the back-end, and includes mapping information between the transaction element and the external interface, where the mapping information includes a transaction element identifier and an external interface identifier corresponding to the transaction element identifier, that is, an interface identifier. The front-end and back-end association configuration information also comprises mapping information between the transaction elements and the local data table, and the mapping information comprises transaction element identifications and data table identifications corresponding to the transaction element identifications.
In addition, optionally, the front-end and back-end association configuration information may further include mapping information between the transaction and the external interface, where the mapping information includes a transaction identifier and an external interface identifier corresponding to the transaction identifier.
Optionally, the back-end call configuration information includes interface configuration information. The interface configuration information comprises a message format, an interface calling mode, an input parameter type and an interface identifier.
The message format indicates a format of a message to be sent when the external interface corresponding to the interface identifier is called.
The interface calling mode represents a mode of calling an external interface corresponding to the interface identifier, and is similar to a web interface calling mode, including an http calling mode and the like.
The input parameter type represents the type of the parameter required to be transmitted when the external interface corresponding to the interface identifier is called, namely the parameter type.
The interface identifier includes an interface name (e.g., transaction code, interface address, etc.), an interface number, and the like.
In addition, optionally, the back-end invocation configuration information may further include data table access configuration information, which includes data table identification, script type (add, delete, change, search), and the like.
The data table identifier includes a data table number, a data table name, and the like.
In addition, optionally, the configuration information may be configured by related personnel or automatically according to the business requirement book.
In any embodiment, optionally, the configuration information modification request is acquired, and the configuration information is modified according to the configuration information modification request.
Specifically, after receiving a configuration information modification request input by a user or sent by another terminal, indicating that the configuration information needs to be modified, that is, updating is performed, and extracting the identifier to be modified and the modification information corresponding to the identifier from the configuration information modification request. And obtaining the configuration information corresponding to the identifier to be modified from the configuration information, and determining the configuration information as the configuration information to be modified. And updating the configuration information to be modified based on the modification information corresponding to the identification to be modified, so as to realize the management of the configuration information.
The to-be-modified identifier comprises a to-be-modified transaction identifier, an interface identifier, a transaction element identifier and the like. For example, if the identifier to be modified is the interface identifier 1, and the modification information corresponding to the interface identifier 1 includes a new message format, the message format corresponding to the interface identifier 1 in the configuration information is modified into the new message format.
In this embodiment, as shown in fig. 4, after configuration information configuration is completed, that is, after configuration information of the three parts, i.e., the front-end configuration information, the front-end-related configuration information, and the back-end calling configuration information, is configured according to the service requirement book, the front-end transaction is used as a core, and version management is performed on the transaction, so that version management is performed on configuration information (e.g., front-end configuration information) corresponding to the transaction. And exporting the configuration information according to the transaction and the version number, and importing the configuration information into a transaction system, namely generating an environment to complete production, so that when a user uses the transaction in the transaction system, a corresponding transaction interface can be displayed for the user to interact based on the configuration information corresponding to the transaction, and business processing is performed based on interactive data input by the user, namely business data.
And S202, displaying a transaction interface corresponding to the transaction according to the configuration information and the transaction identifier.
In this embodiment, information (for example, transaction interface layout information) related to generating a transaction interface corresponding to a transaction identifier of a transaction selected by a user is acquired from configuration information, and page loading is performed based on the information to display the transaction interface corresponding to the transaction identifier, that is, to display the transaction interface corresponding to the transaction identifier.
Optionally, the transaction interface includes a plurality of transaction elements. After the transaction interface is displayed, the user can input the business data in the related transaction elements on the transaction interface to perform transaction processing, namely, perform business processing.
S203, when the confirmation instruction is received, acquiring the business data input by the user on the transaction interface, and determining interface configuration information of the target interface to be accessed corresponding to the transaction according to the configuration information.
In this embodiment, when receiving a confirmation instruction input by a user, indicating that service data input by the user needs to be submitted for service processing, the service data input by the user on a currently displayed transaction interface, that is, a transaction interface corresponding to a transaction identifier of a transaction selected by the user, is acquired, so as to perform service processing by using the service data.
In this embodiment, since the external interface may be used during the service processing, that is, the service processing needs to be performed by an external system, it is determined whether the external interface needs to be called according to the configuration information and the transaction identifier. If so, taking the external interface to be called as the target interface to be accessed, and searching the interface configuration information corresponding to the target interface from the configuration information so as to use the interface configuration information to carry out interface calling.
And S204, calling the target interface according to the interface configuration information and the service data of the target interface.
In this embodiment, after the interface configuration information of the target interface is obtained, indicating that the interface call can be performed, the corresponding target interface is called based on the interface configuration information, so that the target interface performs corresponding service processing by using the service data.
S205, receiving the service response message sent by the target interface, and outputting the service response message.
In this embodiment, after the target interface service processing is completed, a service response message is generated and returned to the electronic device. When the electronic device receives the service response message, the electronic device analyzes the service response message, namely, obtains the required information from the service response message and displays the information.
For example, if the service data includes an organization code to be queried, the organization detailed information corresponding to the organization code may be searched for by calling the target interface (for example, organization establishment time), that is, the target interface is called based on the interface configuration information, so that the target interface searches the organization detailed information corresponding to the organization code, and obtains a service response packet returned by the target interface. And acquiring the detailed mechanism information from the service response message, and displaying the detailed mechanism information.
In this embodiment, the configuration information may be subjected to full lifecycle management of configuration information management, version management, data export and commissioning, and the configuration information management according to transaction granularity is supported, thereby implementing transaction-level isolation and management.
As can be seen from the above description, when the transaction identifier corresponding to the transaction selected by the user is obtained, indicating that the user needs to use the transaction, that is, needs to use the service corresponding to the transaction, the configuration information and the transaction identifier are used to generate a corresponding transaction page code, that is, a transaction interface corresponding to the transaction is displayed for the user to use. When receiving the confirmation instruction, indicating that the service processing is needed, that is, the transaction is needed to be realized, acquiring the service data input by the user on the transaction interface, and determining an external interface which is needed to be accessed when the transaction is realized, that is, interface configuration information of the target interface based on the configuration information, so as to call the target interface by using the interface configuration information, so as to perform the service processing on the service data by using the target interface, that is, the service provided by the external system can be used, and a service response message returned by the target interface when the service processing is successful is output, so as to realize the successful call of the external interface, thereby enabling the provided service to be richer, avoiding the service limitation, and having universality. Meanwhile, when the user needs to update the relevant information of the transaction, the transaction can be updated by updating the configuration information, the operation is simple, the updating efficiency is high, and therefore the user experience can be effectively improved.
Fig. 5 is a second schematic flowchart of a service processing method according to an embodiment of the present invention, where on the basis of the embodiment of fig. 2 in this embodiment, when an external interface, that is, a target interface, is called, a relevant message needs to be used for calling, and this process will be described below with reference to a specific embodiment. As shown in fig. 5, the method includes:
s501, acquiring a transaction identifier of a transaction selected by a user, and acquiring configuration information.
And S502, displaying a transaction interface corresponding to the transaction according to the configuration information and the transaction identifier.
In this embodiment, when displaying the transaction interface, the element configuration information of the transaction element corresponding to the transaction identifier is acquired from the front-end configuration information. And page loading is carried out according to the element configuration information of the transaction elements so as to display a transaction interface corresponding to the transaction.
Specifically, the element configuration information of the transaction element corresponding to the transaction identifier is searched from the front-end configuration information, that is, the configuration information of the control included in the interface corresponding to the transaction identifier. And loading element configuration information of the transaction element to convert the transaction element into an operable UI component, and loading transaction interface layout information corresponding to the transaction identifier to combine the UI component into a finished front-end transaction function interface, namely, loading the transaction interface corresponding to the transaction identifier, so that the transaction identifier, namely, the transaction interface corresponding to the transaction identifier can be displayed.
Optionally, when the element configuration information and the transaction interface layout information of the transaction element are loaded, the loading may be performed based on the related script, that is, the related script is called, so as to generate a corresponding page file based on the element configuration information and the transaction interface layout information, and the loading of the transaction interface is realized by loading the page file.
In any embodiment, optionally, for each transaction element corresponding to the transaction identifier, when it is determined that the front-end configuration information has the check rule corresponding to the transaction element, the transaction element is bound with the check rule.
Specifically, for each transaction element on the transaction interface corresponding to the transaction identifier, when the transaction element is a target transaction element, that is, the transaction element is a target transaction element identifier, it indicates that the transaction element needs to be bound with a check rule, the check rule corresponding to the transaction element is obtained from the front-end configuration information, and the transaction element is bound with the check rule, so that the business data input by the user in the transaction element is checked to determine whether the business data input by the user meets the requirements.
When the transaction element is not the target transaction element, the transaction element is indicated to be free from binding the verification rule, and the verification rule is not required to be acquired so as to be bound with the transaction element.
Correspondingly, when receiving the service data input by the user or when the user inputs a confirmation instruction, verifying whether the service data input by the user is legal, namely whether the service data accords with the verification rule, and the specific process comprises the following steps: and acquiring a target transaction element corresponding to the business data, and acquiring a verification rule corresponding to the target transaction element, wherein the target transaction element is a transaction element of the input business data. And verifying the service data corresponding to the target transaction element according to the verification rule corresponding to the target transaction element to obtain a verification result. And if the verification result is successful, calling the target interface according to the interface configuration information and the service data of the target interface.
Specifically, for each target transaction element, the business data corresponding to the target transaction element is acquired from the business data input by the user, and the business data corresponding to the target transaction element is verified based on the verification rule corresponding to the target transaction element. And if the business data corresponding to the target transaction element accords with the verification rule corresponding to the target transaction element, the verification is successful, namely the business data corresponding to the target transaction element is legal, and the verification result corresponding to the target transaction element is determined as a verification result. And if the business data corresponding to the target transaction element does not conform to the verification rule corresponding to the target transaction element, indicating that the verification fails, and determining that the verification result corresponding to the target transaction element is verification failure.
When the transaction identification, that is, the verification results corresponding to all target transaction elements on the transaction interface are successful, indicates that all the service data input by the user are legal, and can perform service processing by using the service data, the target interface is called to perform service processing on the service data by using the target interface.
And when the verification result corresponding to the target transaction element is verification failure, indicating that the business data input by the user has illegal data, outputting corresponding prompt information to prompt the user to modify the business data corresponding to the illegal target transaction element, namely modifying the business data corresponding to the target transaction element with verification failure as the verification result.
In addition, when the business data corresponding to the target transaction element is not found from the business data input by the user, it indicates that the user does not input the business data on the target transaction element, and then the business data corresponding to the target transaction element is determined to be empty.
S503, when the confirmation instruction is received, acquiring the business data input by the user on the transaction interface, and determining interface configuration information of the target interface to be accessed corresponding to the transaction according to the configuration information. The interface configuration information comprises a message format, an interface calling mode, an input parameter type and an interface identifier.
In this embodiment, when the target interface is called, interface configuration information corresponding to the target interface needs to be determined first, and the specific determination process is as follows: and acquiring a key transaction element identifier corresponding to the transaction interface. And determining an interface identifier corresponding to the key transaction element identifier from the front-end and back-end associated configuration information, and determining the interface identifier as a target interface identifier. And acquiring interface configuration information corresponding to the target interface identifier from the back-end calling configuration information.
In this embodiment, the key transaction element identifier corresponding to the transaction identifier of the transaction selected by the user is searched from the front-end configuration information to determine the identifier of the transaction element that needs to use the external interface. After the key transaction element identification is obtained, for each key transaction element identification, namely for each key transaction element, searching an interface identification corresponding to the key transaction element identification from front-end and back-end associated configuration information, and determining the interface identification as a target interface identification corresponding to the key transaction element identification, wherein a target interface corresponding to the target interface identification is an interface corresponding to the key transaction element, and searching interface configuration information corresponding to the target interface identification corresponding to the key transaction element identification from back-end calling configuration information, namely obtaining the acquisition of the interface configuration information corresponding to the target interface identification.
S504, input parameter values corresponding to the input parameter types corresponding to the target interfaces are determined according to the service data.
In this embodiment, for each target interface corresponding to the transaction identifier, that is, for each target interface to be called, an input parameter required for calling the target interface is obtained from the service data input by the user in the transaction interface, that is, the service data corresponding to the input parameter type corresponding to the target interface is searched from the service data, and the searched service data is used as the input parameter value corresponding to the input parameter type. For example, the business data includes a mechanism code and a region, a transaction element corresponding to the mechanism code, that is, a mechanism code input box, is a key transaction element, interface configuration information of a target interface corresponding to the mechanism code input box is acquired from back-end call information, an input parameter type in the interface configuration information includes a mechanism code type, and then the mechanism code is acquired from the business data input by the user to obtain an input parameter value corresponding to the target interface corresponding to the mechanism code input box, that is, the input parameter value is a mechanism code input by the user.
And S505, according to the message format of the target interface, packaging the interface identifier and the input parameter value of the target interface to obtain a service processing message.
In this embodiment, for each target interface corresponding to the transaction identifier, the interface identifier of the target interface and the input parameter value corresponding to the target interface are encapsulated according to the message format of the target interface, so as to obtain a service processing message corresponding to the target interface, so as to call the target interface by using the service processing message.
S506, according to the interface calling mode of the target interface, the service processing message is sent to the target end to call the target interface.
In this embodiment, when a service processing packet corresponding to a target interface is obtained, the service processing packet is sent to a terminal where the target interface is located according to an interface calling manner corresponding to the target interface, and a target end calls a related target interface on the target end, that is, an interface corresponding to an interface identifier in the service processing packet, so that service processing can be performed by using the target interface, that is, service data in the service processing packet is subjected to related processing by using a function provided by the target interface, for example, mechanism detailed information corresponding to a mechanism code is searched.
And S507, receiving the service response message sent by the target interface and outputting the service response message.
In this embodiment, after the service is successfully processed by calling the target interface, that is, after the service is successfully processed by the target terminal based on the target interface, a corresponding service response message is generated and sent to the electronic device. When receiving a service response message returned by a target end, namely a target interface on the target end, the electronic equipment analyzes the service response message to extract required data from the service response message, displays the extracted data on a corresponding transaction interface, realizes the successful calling of an external interface and the successful processing of the service, and effectively avoids the service limitation because a user can use an external system, namely the service provided by the target end.
When the target terminal is a database, the flow of calling the target interface of the database is shown in fig. 6:
STEP 1: the business person's selected transaction from the transaction list is determined.
STEP 2: and reading the front-end configuration information according to the selected transaction, generating a front-end interface based on the front-end configuration information, and returning the front-end interface to the user side.
STEP 3: and according to the service rule, namely the verification rule, verifying and verifying the service data input by the user and feeding back the user in real time.
STEP4, when the user submits the service data, determining that the user inputs the confirmation instruction;
STEP 5: and reading the configuration information and converting the front-end input into an external interface message (data script) according to the configuration information.
STEP 6: and completing interface calling (script execution) according to the configuration information.
STEP 7: and reading the configuration information and converting the interface (database) return into front-end output according to the configuration information.
In the embodiment, the transaction and configuration information, namely the physical table and the external interface, are completely decoupled, and independent evolution of the requirements and the physical table is realized. When the transaction needs to be updated, that is, when the requirement changes, for example, the content displayed on the transaction interface corresponding to the transaction is updated, the relevant configuration information corresponding to the transaction can be directly updated, so that the efficiency of transaction maintenance is improved. And because the configuration information, namely the physical table, is independent, the modification and maintenance of the configuration information corresponding to the user can be facilitated, and the management efficiency of the configuration information is effectively improved.
In the embodiment, the development of the transaction is solidified into the standardized configuration, so that the implementation details are shielded, namely, the development and the display of the transaction can be realized by using the relevant configuration information of the transaction, the development efficiency is improved, the dependence degree of a code mode on the development experience is reduced, and the risk is reduced.
In this embodiment, the production of the transaction is only the production of the relevant configuration information, and no additional program deployment is required, that is, the configuration information may be changed, and the program for loading the relevant configuration information of the transaction to form the corresponding transaction interface may not be changed, and the function may be modified without stopping the machine, so as to implement "hot deployment".
In this embodiment, when a confirmation instruction input by a user is received, which indicates that service processing needs to be performed based on service processing input by the user, the external interface that needs to be called for performing the service processing, that is, interface configuration information of the target interface, is determined, and a service processing packet corresponding to the target interface is generated according to the interface configuration information, so that the target interface on the target end is called by using the service processing packet, and docking access of the external interface is realized.
Fig. 7 is a schematic structural diagram of a service processing device according to an embodiment of the present invention, and as shown in fig. 7, the service processing device 700 includes: a processing module 701 and a transceiver module 702.
The processing module 701 is configured to obtain a transaction identifier of a transaction selected by a user, and obtain configuration information.
The processing module 701 is further configured to display a transaction interface corresponding to the transaction according to the configuration information and the transaction identifier.
The processing module 701 is further configured to, when receiving the confirmation instruction, acquire service data input by the user on the transaction interface, and determine interface configuration information of a target interface to be accessed corresponding to the transaction according to the configuration information.
The transceiver module 702 is configured to invoke the target interface according to the interface configuration information and the service data of the target interface.
The transceiving module 702 is further configured to receive a service response packet sent by the target interface, and output the service response packet.
In one possible design, the configuration information includes front-end configuration information.
The processing module 701 is further configured to:
and acquiring element configuration information of the transaction element corresponding to the transaction identifier from the front-end configuration information.
And page loading is carried out according to the element configuration information of the transaction elements so as to display a transaction interface corresponding to the transaction.
In one possible design, the processing module 701 is further configured to:
and for each transaction element corresponding to the transaction identifier, binding the transaction element with the verification rule when the verification rule corresponding to the transaction element exists in the front-end configuration information.
In one possible design, the interface configuration information includes a message format, an interface calling mode, an input parameter type, and an interface identifier.
The processing module 701 is further configured to:
and determining an input parameter value corresponding to the input parameter type corresponding to the target interface according to the service data.
And according to the message format of the target interface, packaging the interface identifier and the input parameter value of the target interface to obtain a service processing message.
And sending the service processing message to a target end according to the interface calling mode of the target interface so as to call the target interface.
In one possible design, the configuration information includes front-end associated configuration information and back-end calling configuration information.
The processing module 701 is further configured to:
and acquiring a key transaction element identifier corresponding to the transaction interface.
And determining an interface identifier corresponding to the key transaction element identifier from the front-end and back-end associated configuration information, and determining the interface identifier as a target interface identifier.
And acquiring interface configuration information corresponding to the target interface identifier from the back-end calling configuration information.
In one possible design, the transaction interface includes a plurality of transaction elements.
The processing module 701 is further configured to:
and acquiring a target transaction element corresponding to the business data, and acquiring a verification rule corresponding to the target transaction element, wherein the target transaction element is a transaction element of the input business data.
And verifying the service data corresponding to the target transaction element according to the verification rule corresponding to the target transaction element to obtain a verification result.
And if the verification result is successful, calling the target interface according to the interface configuration information and the service data of the target interface.
In one possible design, the processing module 701 is further configured to:
and acquiring a configuration information modification request, and modifying the configuration information according to the configuration information modification request.
The service processing device provided in the embodiment of the present invention can implement the service processing method in the above-described embodiment, and the implementation principle and technical effect are similar, which are not described herein again.
Fig. 8 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention. As shown in fig. 8, the electronic apparatus 800 of the present embodiment includes: a processor 801 and a memory 802. Wherein
The processor 801 is configured to execute the computer-executable instructions stored in the memory to implement the steps performed by the receiving device in the above embodiments. Reference may be made in particular to the description relating to the method embodiments described above.
Alternatively, the memory 802 may be separate or integrated with the processor 801.
When the memory 802 is provided separately, the electronic apparatus further includes a bus 803 for connecting the memory 802 and the processor 801.
The embodiment of the invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer execution instructions, and when a processor executes the computer execution instructions, the service processing method is realized.
The embodiment of the present invention further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the service processing method is implemented.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules is only one logical division, and other divisions may be realized in practice, for example, a plurality of modules may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each module may exist alone physically, or two or more modules are integrated into one unit. The unit formed by the modules can be realized in a hardware form, and can also be realized in a form of hardware and a software functional unit.
The integrated module implemented in the form of a software functional module may be stored in a computer-readable storage medium. The software functional module is stored in a storage medium and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present application.
It should be understood that the Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor, or in a combination of the hardware and software modules within the processor.
The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile storage NVM, such as at least one disk memory, and may also be a usb disk, a removable hard disk, a read-only memory, a magnetic or optical disk, etc.
The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, the buses in the figures of the present application are not limited to only one bus or one type of bus.
The storage medium may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and the storage medium may reside as discrete components in an electronic device or host device.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (11)
1. A method for processing a service, comprising:
acquiring a transaction identifier of a transaction selected by a user, and acquiring configuration information;
displaying a transaction interface corresponding to the transaction according to the configuration information and the transaction identifier;
when a confirmation instruction is received, acquiring business data input by a user on the transaction interface, and determining interface configuration information of a target interface to be accessed corresponding to the transaction according to the configuration information;
calling a target interface according to the interface configuration information of the target interface and the service data;
and receiving a service response message sent by the target interface and outputting the service response message.
2. The method of claim 1, wherein the configuration information comprises front-end configuration information;
the displaying of the transaction interface corresponding to the transaction according to the configuration information and the transaction identifier includes:
acquiring element configuration information of the transaction element corresponding to the transaction identifier from the front-end configuration information;
and page loading is carried out according to the element configuration information of the transaction element so as to display a transaction interface corresponding to the transaction.
3. The method of claim 2, further comprising:
and for each transaction element corresponding to the transaction identifier, when the front-end configuration information is determined to have a verification rule corresponding to the transaction element, binding the transaction element with the verification rule.
4. The method of claim 1, wherein the interface configuration information includes a message format, an interface calling method, an input parameter type, and an interface identifier;
the calling the target interface according to the interface configuration information of the target interface and the service data comprises:
determining an input parameter value corresponding to the input parameter type corresponding to the target interface according to the service data;
according to the message format of the target interface, packaging the interface identifier of the target interface and the input parameter value to obtain a service processing message;
and sending the service processing message to a target end according to an interface calling mode of a target interface so as to call the target interface.
5. The method of claim 1, wherein the configuration information comprises front-end association configuration information and back-end invocation configuration information;
the determining interface configuration information of the target interface to be accessed corresponding to the transaction according to the configuration information includes:
acquiring a key transaction element identifier corresponding to the transaction interface;
determining an interface identifier corresponding to the key transaction element identifier from the front-end and back-end associated configuration information, and determining the interface identifier as a target interface identifier;
and acquiring interface configuration information corresponding to the target interface identifier from the back-end calling configuration information.
6. The method of any of claims 1 to 5, wherein the transaction interface comprises a plurality of transaction elements;
the calling the target interface according to the interface configuration information of the target interface and the service data comprises:
acquiring a target transaction element corresponding to the business data, and acquiring a verification rule corresponding to the target transaction element, wherein the target transaction element is a transaction element of input business data;
verifying the service data corresponding to the target transaction element according to a verification rule corresponding to the target transaction element to obtain a verification result;
and if the verification result is successful, calling the target interface according to the interface configuration information of the target interface and the service data.
7. The method according to any one of claims 1 to 5, further comprising:
and acquiring a configuration information modification request, and modifying the configuration information according to the configuration information modification request.
8. A traffic processing device, comprising:
the processing module is used for acquiring a transaction identifier of a transaction selected by a user and acquiring configuration information;
the processing module is further used for displaying a transaction interface corresponding to the transaction according to the configuration information and the transaction identifier;
the processing module is further configured to, when receiving a confirmation instruction, acquire service data input by a user on the transaction interface, and determine interface configuration information of a target interface to be accessed corresponding to the transaction according to the configuration information;
the receiving and sending module is used for calling the target interface according to the interface configuration information of the target interface and the service data;
the transceiver module is further configured to receive a service response packet sent by the target interface, and output the service response packet.
9. An electronic device, comprising: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the business process method of any of claims 1 to 7.
10. A computer-readable storage medium having stored thereon computer-executable instructions which, when executed by a processor, implement the business process method of any one of claims 1 to 7.
11. A computer program product comprising a computer program, characterized in that the computer program realizes the service processing method of any of claims 1 to 7 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110724443.5A CN113360043B (en) | 2021-06-29 | 2021-06-29 | Service processing method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110724443.5A CN113360043B (en) | 2021-06-29 | 2021-06-29 | Service processing method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113360043A true CN113360043A (en) | 2021-09-07 |
| CN113360043B CN113360043B (en) | 2024-04-09 |
Family
ID=77536967
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110724443.5A Active CN113360043B (en) | 2021-06-29 | 2021-06-29 | Service processing method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113360043B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114860367A (en) * | 2022-05-07 | 2022-08-05 | 金蝶软件（中国）有限公司 | User interface event processing method, device and system |
| CN116107965A (en) * | 2023-04-07 | 2023-05-12 | 中国邮电器材集团有限公司 | Data management method, device and system and merchant server |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100159907A1 (en) * | 2008-12-18 | 2010-06-24 | Fidelisoft Inc. | Dynamic configurable transaction system |
| CN107392766A (en) * | 2017-07-25 | 2017-11-24 | 上海壹账通金融科技有限公司 | Method for processing business, adapter and computer-readable recording medium |
| CN109636317A (en) * | 2018-11-23 | 2019-04-16 | 山东中创软件工程股份有限公司 | Service control method, device, system and storage medium |
| CN110581890A (en) * | 2019-09-10 | 2019-12-17 | 中国建设银行股份有限公司 | Routing method and device for service request |
| CN112118142A (en) * | 2020-09-28 | 2020-12-22 | 中国银行股份有限公司 | Message transmission method and device |
-
2021
- 2021-06-29 CN CN202110724443.5A patent/CN113360043B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100159907A1 (en) * | 2008-12-18 | 2010-06-24 | Fidelisoft Inc. | Dynamic configurable transaction system |
| CN107392766A (en) * | 2017-07-25 | 2017-11-24 | 上海壹账通金融科技有限公司 | Method for processing business, adapter and computer-readable recording medium |
| CN109636317A (en) * | 2018-11-23 | 2019-04-16 | 山东中创软件工程股份有限公司 | Service control method, device, system and storage medium |
| CN110581890A (en) * | 2019-09-10 | 2019-12-17 | 中国建设银行股份有限公司 | Routing method and device for service request |
| CN112118142A (en) * | 2020-09-28 | 2020-12-22 | 中国银行股份有限公司 | Message transmission method and device |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114860367A (en) * | 2022-05-07 | 2022-08-05 | 金蝶软件（中国）有限公司 | User interface event processing method, device and system |
| CN114860367B (en) * | 2022-05-07 | 2023-10-03 | 金蝶软件（中国）有限公司 | User interface event processing method, device and system |
| CN116107965A (en) * | 2023-04-07 | 2023-05-12 | 中国邮电器材集团有限公司 | Data management method, device and system and merchant server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113360043B (en) | 2024-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10511453B2 (en) | Information processing system and charge calculation apparatus | |
| CN107632869B (en) | Method and equipment for loading user interface of POS application | |
| CN108073429B (en) | Payment mode configuration method, device, equipment and storage medium | |
| CN113360043B (en) | Service processing method and equipment | |
| WO2022134583A1 (en) | Insurance data information generation method, apparatus, server, and storage medium | |
| CN105378662A (en) | Bundle package generation | |
| CN110597511A (en) | Page automatic generation method, system, terminal equipment and storage medium | |
| CN109271564A (en) | Declaration form querying method and equipment | |
| WO2015134479A2 (en) | Mobile solution for purchase orders | |
| CN112465601A (en) | Electronic order generation method and device and storage medium | |
| CN113076731A (en) | Report file generation method and device, computer equipment and storage medium | |
| CN111104556A (en) | Service processing method and device | |
| CN110704486A (en) | Data processing method, device, system, storage medium and server | |
| CN113987054A (en) | Big data governance full-flow visualization method and device and storage medium | |
| CN116302079B (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN111598707B (en) | Page generation method and electronic equipment | |
| CN111324645A (en) | Data processing method and device for block chain | |
| CN113946723A (en) | Data query method, device, server, system and storage medium | |
| CN114756277A (en) | Page configuration method and device | |
| CN108509478B (en) | Splitting and calling method of rule engine file, electronic device and storage medium | |
| CN115114280A (en) | Report generation processing method, device and equipment | |
| KR101737575B1 (en) | Method and device for verifying data based on sql sentences generated automatically | |
| CN111652747B (en) | Electronic policy processing method, device, equipment and computer readable storage medium | |
| CN117519771A (en) | Information pushing method, related equipment, storage medium and computer product | |
| CN113408893A (en) | Risk early warning 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |