CN114816504A - Configuration method and execution method of docking process, electronic device and storage medium - Google Patents
Configuration method and execution method of docking process, electronic device and storage medium Download PDFInfo
- Publication number
- CN114816504A CN114816504A CN202210368854.XA CN202210368854A CN114816504A CN 114816504 A CN114816504 A CN 114816504A CN 202210368854 A CN202210368854 A CN 202210368854A CN 114816504 A CN114816504 A CN 114816504A
- Authority
- CN
- China
- Prior art keywords
- flow
- identifier
- editing
- information
- detailed information
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
- G06F3/0483—Interaction with page-structured environments, e.g. book metaphor
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a configuration method and an execution method of a docking process, electronic equipment and a storage medium, and belongs to the technical field of computers. According to the invention, the configuration operation of the whole docking process is visualized through the configuration page, and the configuration process of the docking process is standardized by using the process template, so that the complexity of the configuration technology is reduced, the configuration efficiency of the docking process is improved, and the channel docking requirement of a supplier can be quickly responded.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a configuration method and an execution method for a docking process, an electronic device, and a storage medium.
Background
Along with the development of the logistics industry and the expansion of the logistics service provider channels, and the frequent change of the docking requirements of the channels involved in the cooperation process of the providers, the logistics service provider channel docking requirements mainly appear as follows: interface access requirements of newly populated provider channels, interface upgrade requirements of provider channels, and requirements for interface field adjustments, among others. Channel maintenance personnel need to frequently configure the docking processes corresponding to the provider channel interfaces to meet the changing channel docking requirements.
In the related art, according to the channel docking requirements of the suppliers, the configuration of the docking process is completed in a hard coding mode, so that the maintenance of the channel docking mode of the suppliers is realized. However, the configuration method of the docking process based on the hard coding mode has the defects of high complexity of the configuration technology and large difference of configuration processes of different docking processes, so that the configuration efficiency of the docking process is low, and the channel docking requirement of a supplier cannot be quickly responded.
Disclosure of Invention
In order to solve the defects that the existing configuration method of the docking process has low configuration efficiency and cannot quickly respond to the channel docking requirements of suppliers, the invention provides a configuration method and an execution method of the docking process, electronic equipment and a storage medium.
In a first aspect, to solve the above technical problem, the present invention provides a configuration method of a docking procedure, where the method includes:
responding to the selection operation of a template identifier of a target flow template displayed on an initial page, displaying a configuration page, wherein the configuration page is provided with flow stages corresponding to the target flow template and flow detailed information identifiers corresponding to each flow stage, the initial page is provided with template identifiers of a plurality of preset flow templates, the flow stage corresponding to the target flow template is a step required for executing a butt joint flow, and the flow stage corresponding to each preset flow template is different;
responding to the selection operation aiming at the target process detailed information identifier in each process detailed information identifier, and displaying an editing page corresponding to the target process detailed information identifier;
receiving edit information of the flow detailed information corresponding to the target flow detailed information identification by a user through an edit page, wherein the flow detailed information is an operation rule required for executing a flow stage, and the operation rule is used for generating an output result of the flow stage;
and generating the docking flow according to the editing information of the flow detailed information corresponding to each flow detailed information identifier.
The invention has the beneficial effects that: the configuration operation of the whole docking process is visualized through the configuration page, and the configuration process of the docking process is standardized by using the process template, so that the complexity of the configuration technology is reduced, the configuration efficiency of the docking process is improved, and the channel docking requirement of a supplier can be quickly responded.
Further, the flow detailed information identifier comprises a data conversion logic identifier and a result request logic identifier;
receiving the editing information of the flow detailed information corresponding to the flow detailed information identification by the user through an editing page, wherein the editing information comprises the following steps:
receiving first editing information of flow detailed information corresponding to the data conversion logic identification by a user through an editing page, wherein the first editing information is an operation rule for converting an input parameter into a request parameter, and the input parameter is a parameter required for executing a flow stage corresponding to the data conversion logic identification;
and receiving second editing information of the flow detailed information corresponding to the result request logic identification by the user through the editing page, wherein the second editing information is an operation rule for generating an output result of the flow stage based on the request parameter.
The beneficial effect who adopts above-mentioned improvement scheme is: the detailed information of the flow required to be configured is displayed through the page, the configuration process of the docking flow is further specified, so that channel maintenance personnel can determine the detail of the flow required to be configured in each flow stage, and the configuration efficiency of the docking flow is improved.
Further, the flow detailed information identifier also comprises a request result checking logic identifier;
receiving the editing information of the flow detailed information corresponding to the flow detailed information identification by the user through an editing page, wherein the editing information comprises:
and receiving third editing information of the flow detailed information corresponding to the request result verification logic identification by the user through the editing page, wherein the third editing information is an operation rule for verifying an output result of the flow stage.
The beneficial effect who adopts above-mentioned improvement scheme is: and the logic identifier is verified by setting the request result so as to ensure the reliability of the output result of the configured flow stage.
Further, the request result checking logic identifier comprises an exception checking logic identifier and an exception handling logic identifier;
receiving third editing information of the flow detailed information corresponding to the request result verification logic identification by the user through the editing page, wherein the third editing information comprises:
receiving fourth editing information of the flow detailed information corresponding to the abnormal verification logic identification by the user through the editing page, wherein the fourth editing information is an operation rule for verifying whether an output result of the flow stage belongs to an abnormal response result;
and receiving fifth editing information of the flow detailed information corresponding to the exception handling logic identifier by the user through the editing page, wherein the fifth editing information is an operation rule for processing the exception response result.
The beneficial effect who adopts above-mentioned improvement scheme is: by setting the request result check logic identifier, the configured flow stage can realize an exception handling function, so that the configured docking flow better meets the functional requirements of channel service.
Further, the flow detailed information identifier also comprises a parameter checking logic identifier;
receiving the editing information of the flow detailed information corresponding to the flow detailed information identification by the user through an editing page, wherein the editing information comprises:
and receiving sixth editing information of the flow detailed information corresponding to the parameter verification logic identifier by the user through the editing page, wherein the sixth editing information is an operation rule for verifying the request parameter.
The beneficial effect who adopts above-mentioned improvement scheme is: and the logic identifier is verified by setting parameters to ensure the normal execution of the configured docking process.
Further, the flow detail information identifier also includes an end node identifier;
receiving the editing information of the process detailed information corresponding to the target process detailed information identification by the user through an editing page, wherein the editing information comprises the following steps:
responding to the selection operation aiming at the end node identification, displaying the flow result generation logic identification on the editing page;
responding to the selection operation of generating the logic identifier aiming at the flow result, and displaying an end node editing page corresponding to the flow result generation logic identifier;
and receiving seventh editing information of the flow detailed information corresponding to the flow result generation logic identifier by the user through the end node editing page, wherein the seventh editing information is an operation rule for generating an output result of the butt joint flow based on the output result of each flow stage.
The beneficial effect who adopts above-mentioned improvement scheme is: the last flow stage required to be executed by the butt joint flow is identified by setting the end node identification, so that the operation rule for generating the output result of the butt joint flow can be reasonably added, the configuration process of the butt joint flow is further standardized, and the configuration efficiency is improved.
Further, an execution logic identifier corresponding to each flow stage is also displayed on the configuration page, and the execution logic identifier is used for indicating that the docking flow comprises the flow stage corresponding to the execution logic identifier;
in response to the selection operation of the target process detailed information identifier in each process detailed information identifier, before displaying the editing page corresponding to the target process detailed information identifier, the method further includes:
and responding to the selection operation aiming at the execution logic identification, and displaying the flow detailed information identification corresponding to the execution logic identification on the configuration page.
The beneficial effect who adopts above-mentioned improvement scheme is: the execution logic identifier is set to identify the flow stages belonging to the configured docking flow, so that the flow stages actually included in the docking flow can be flexibly configured while the configuration process is standardized.
In a second aspect, the present invention provides a method for executing a docking process, where the method includes:
acquiring an input parameter;
selecting a target docking process matched with the input parameters from preset docking processes, wherein the docking processes are configured by adopting the configuration method of the docking processes in the first aspect;
and executing the target docking process based on the input parameters.
In a third aspect, the present invention provides a computer-readable storage medium, which stores instructions that, when executed on a terminal device, cause the terminal device to perform all or part of the steps of the configuration method of the docking procedure according to the first aspect, or cause the terminal device to perform all or part of the steps of the execution method of the docking procedure according to the second aspect.
In a fourth aspect, the present invention provides an electronic device, including a memory, a processor, and a program stored in the memory and running on the processor, where the processor includes a first processor and a second processor, the first processor implements all or part of the steps of the configuration method of the docking procedure according to the first aspect when executing the program, and the second processor implements all or part of the steps of the execution method of the docking procedure according to the second aspect when executing the program.
Drawings
Fig. 1 is a schematic flow chart of a configuration method of a docking flow according to an embodiment of the present invention;
fig. 2 is a schematic flow chart illustrating an execution method of a docking process according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The following examples are further illustrative and supplementary to the present invention and do not limit the present invention in any way.
A configuration method of a docking procedure according to an embodiment of the present invention is described below with reference to the drawings.
Referring to fig. 1, the present invention provides a configuration method of a docking procedure, including the following steps S1 to S4.
In step S1, in response to a selection operation for the template identifier of the target flow template displayed on the initial page, a configuration page is displayed, where the configuration page displays flow stages corresponding to the target flow template and flow detailed information identifiers corresponding to each flow stage, the initial page displays template identifiers of a plurality of preset flow templates, the flow stage corresponding to the target flow template is a step required for executing a docking flow, and the flow stage corresponding to each preset flow template is different.
In the embodiment, the flow template is established in advance according to the service types of the service channels owned by different suppliers. Taking a logistics provider providing a logistics service channel as an example, the logistics provider generally has service types such as number changing, clearance, general order, forecast, cancellation, basic data and the like, and each service needs a corresponding docking process to implement functions. Therefore, corresponding flow templates are respectively established for each service type, template identifications corresponding to the flow templates of different service types are displayed on an initial page, so that a channel maintainer can select a target flow template according to the service type, the configuration page guides the channel maintainer to configure a docking flow based on the flow detailed information identification corresponding to the displayed flow stage, and the configuration process of the docking flow is clearer and more standardized.
The process template may include information such as a service type, a process stage, and a name and a state of the process template, the template identifier may be a button on which the name of the process template is displayed, and the selection operation on the template identifier may be a click operation on the button.
In step S2, in response to a selection operation for a target flow detailed information identifier among the flow detailed information identifiers, an edit page corresponding to the target flow detailed information identifier is displayed.
In this embodiment, taking the selected target process template as the process template of the number change type as an example, the docking process of the number change type in the logistics service includes three steps of pre-check, remote number change and face sheet acquisition, that is, the target process template correspondingly includes three process stages of pre-check, remote number change and face sheet acquisition, and the detailed process information identifiers corresponding to the three process stages can be sequentially displayed in a row direction or a longitudinal direction on the configuration page according to the execution sequence of the three process stages in the docking process. The flow detail information identifier may be a button, and is used to jump to the corresponding editing page.
As a possible implementation manner, an execution logic identifier corresponding to each flow stage is also displayed on the configuration page, and the execution logic identifier is used for indicating that the docking flow includes the flow stage corresponding to the execution logic identifier; in response to the selection operation of the target process detailed information identifier in each process detailed information identifier, before displaying the editing page corresponding to the target process detailed information identifier, the method further includes:
and responding to the selection operation aiming at the execution logic identification, and displaying the flow detailed information identification corresponding to the execution logic identification on the configuration page.
In this embodiment, the channel maintenance staff may indicate which flow stages are actually required for the currently configured docking flow by selecting the execution logic identifier of the flow stage, so as to perform subsequent configuration operations on the required flow stages through the target flow detailed information identifier displayed on the configuration page.
As another possible implementation manner, an execution logic identifier and a skippable logic identifier corresponding to each process stage are displayed on the configuration page, where the execution logic identifier may be a check item displaying text content of a "regular node", the check item is checked by default, and indicates that the currently configured docking process includes the process stage, and a detailed process information identifier is correspondingly displayed on the configuration page; the logic identifier capable of being skipped may be a check item displaying the text content of a "node capable of being skipped", the check item is manually checked by a channel maintenance worker, when the check item capable of being skipped is checked, the check operation of the "conventional node" check item is cancelled, it indicates that the currently configured docking process does not include the process stage, and the configuration page does not display the detailed process information identifier of the process stage.
In step S3, the edit page receives edit information of the process detail information corresponding to the target process detail information identifier, where the process detail information is an operation rule required for executing a process stage, and the operation rule is used to generate an output result of the process stage.
Wherein the editing information may be a code block representing an operation rule required to execute one flow stage.
As a possible implementation, an input box of a call type and code are displayed on the edit page, the call type selection item is used for indicating a call type required for executing a flow phase, and the call type comprises a remote call (referring to a call provider's docking interface), an internal call (referring to a call internal system's docking interface) and a local call (referring to a call current system's built-in method/interface).
Optionally, in an embodiment, the flow detail information identifier includes a data conversion logic identifier and a result request logic identifier; receiving the editing information of the flow detailed information corresponding to the flow detailed information identification by the user through an editing page, wherein the editing information comprises:
receiving first editing information of flow detailed information corresponding to the data conversion logic identification by a user through an editing page, wherein the first editing information is an operation rule for converting an input parameter into a request parameter, and the input parameter is a parameter required for executing a flow stage corresponding to the data conversion logic identification;
and receiving second editing information of the flow detailed information corresponding to the result request logic identification by the user through the editing page, wherein the second editing information is an operation rule of an output result of the flow stage generated based on the request parameter.
It should be noted that a flow stage may include one or more flow details, and each flow detail corresponds to a flow detail information identifier.
As a possible implementation manner, a fixed number of flow detail information identifications of flow detail types, i.e. the types and the numbers of the flow details contained in the fixed flow stages, are set for each flow stage.
And the method also can set whether to execute a check option for each flow in detail, and correspondingly display the check option on a configuration page, thereby guiding channel maintenance personnel to set the flow details actually contained in the flow stage.
As another possible implementation mode, the flow detailed information identifier is set as an additionally-added component, in response to the newly-added operation of the channel maintenance personnel on the component, the configuration page displays a new set of flow detailed information identifiers (including the data conversion logic identifier and the result request logic identifier), and by adding multiple sets of flow detailed information identifiers, the various flow details contained in the flow stage are configured.
The configuration example of the flow detailed information including the three flow stages of pre-verification, remote number changing and acquisition is exemplarily described.
The detailed process for configuring the address pre-verification process for the channel maintainer is a pre-verification process stage and comprises the following steps:
selecting a data conversion logic identifier corresponding to the address preposition verification process in detail, inputting first editing information on an editing page, wherein the first editing information is information of country, province/continent, city, address and the like in the input parameters of the acquisition docking process, and converting the information into a related code of a request parameter conforming to a preset data format; selecting a result request logic identifier corresponding to the address pre-verification flow in detail, and inputting second editing information on an editing page, wherein the second editing information is a related code for verifying whether the address information represented by the request parameter is correct, so as to obtain an output result (such as a verification result of correct address information or wrong address information) of the pre-verification flow stage.
The channel maintainer remote number changing process stage, the detailed process of the authentication and number changing process comprises:
selecting a data conversion logic identifier corresponding to the authentication process details, and inputting first editing information on an editing page, wherein the first editing information is a related code configuring request header information (request parameters for requesting Token, which may be account information in the docking process input parameters) of the authentication process details; selecting a result request logic identifier corresponding to the address pre-verification process in detail, and inputting second editing information into an editing page, wherein the second editing information is a relevant code for acquiring response information of provider service based on the request header information, and the response information comprises authenticated Token, Token failure time, refreshed Token and the like;
adding a group of flow detailed information identifiers corresponding to the number changing flow details in a configuration page, selecting a data conversion logic identifier from the group of flow detailed information identifiers, and inputting first editing information in an editing page, wherein the first editing information is information such as order information, recipient information and sender information in the input parameters of the docking flow, and is converted into related codes of request parameters conforming to a preset data format; selecting a result request logic identifier in the set of flow detailed information identifiers, and inputting second editing information on an editing page, wherein the second editing information is a related code for acquiring response information of provider service based on the request parameter; the response information obtained in detail by the process of executing the authentication and the number changing is the output result obtained by the process stage of executing the remote number changing.
The detailed process of configuring the flow of uploading the Base64 file to the OSS for the channel maintainer to acquire the bill comprises the following steps:
selecting a data conversion logic identifier corresponding to the details of the uploaded Base64 file to OSS process, and inputting first editing information on an editing page, wherein the first editing information is related codes of parameters configuring Base64 file information to be uploaded (the Base64 file information comprises a response result obtained in the details of executing a number conversion process); selecting a result request logic identifier corresponding to the details of the flow of uploading the Base64 file to the OSS, and inputting second editing information on an editing page, wherein the second editing information is a relevant code for acquiring response information of an upstream system based on the request parameter, the response information comprises information such as an uploading result (success or failure), an uploading URL (uniform resource locator) and an uploading file type (such as PDF (portable document format), JPG (Java object graph) and GIF (graphic format)) and the response information is an output result obtained in the flow stage of executing the acquisition of the bill.
Optionally, in this embodiment, the flow detail information identifier further includes a request result checking logic identifier; receiving the editing information of the flow detailed information corresponding to the flow detailed information identification by the user through an editing page, wherein the editing information comprises:
and receiving third editing information of the flow detailed information corresponding to the request result verification logic identification by the user through the editing page, wherein the third editing information is an operation rule for verifying an output result of the flow stage.
In this embodiment, the verification configuration of the output result of the flow stage is provided for the flow details, so that the detailed execution condition (execution success or failure) of each flow can be detected, and the channel maintainer can configure the operation rule that the verification result of the output result is added to the output result through the third editing information to be used as the final output result of the flow stage, so that the channel maintainer can quickly position and modify the configuration information corresponding to the flow details with the execution failure, and the configuration process is clear and efficient.
Optionally, in this embodiment, the request result checking logic identifier includes an exception checking logic identifier and an exception handling logic identifier; receiving third editing information of the flow detailed information corresponding to the request result verification logic identification by the user through the editing page, wherein the third editing information comprises:
receiving fourth editing information of the flow detailed information corresponding to the abnormal verification logic identification by the user through the editing page, wherein the fourth editing information is an operation rule for verifying whether an output result of the flow stage belongs to an abnormal response result;
and receiving fifth editing information of the flow detailed information corresponding to the exception handling logic identifier by the user through the editing page, wherein the fifth editing information is an operation rule for processing the exception response result.
As a possible implementation, the abnormal response result may be an invalid payment request result indicating that the payment operation is unsuccessful, and the operation rule for processing the abnormal response result may be a code related to a response result of requesting to cancel the order corresponding to the payment request from the upstream system, and may use the response result as a final output result of the corresponding process stage.
Optionally, in this embodiment, the flow detail information identifier further includes a parameter checking logic identifier; receiving the editing information of the flow detailed information corresponding to the flow detailed information identification by the user through an editing page, wherein the editing information comprises:
and receiving sixth editing information of the flow detailed information corresponding to the parameter verification logic identifier by the user through the editing page, wherein the sixth editing information is an operation rule for verifying the request parameter.
The sixth editing information may be a related code for verifying whether the request parameter is legal (whether the parameter field conforms to the preset data format).
Optionally, in an embodiment, the flow detail information identifier further includes an end node identifier; receiving the editing information of the process detailed information corresponding to the target process detailed information identification by the user through an editing page, wherein the editing information comprises the following steps:
responding to the selection operation aiming at the end node identification, displaying the flow result generation logic identification on the editing page;
responding to the selection operation of generating the logic identifier aiming at the flow result, and displaying an end node editing page corresponding to the flow result generation logic identifier;
and receiving seventh editing information of the flow detailed information corresponding to the flow result generation logic identifier by the user through the end node editing page, wherein the seventh editing information is an operation rule for generating an output result of the butt joint flow based on the output result of each flow stage.
In this embodiment, the end node identifier may be a check item that displays the text content of the "end node", and the channel maintainer indicates that the flow stage corresponding to the end node identifier is the last flow stage that needs to be executed by the docking flow by checking the check item of the "end node", so that a logical identifier may be generated according to the flow result displayed on the page, and output result configuration of the docking flow is performed, because the flow result is usually associated with the output result of each flow stage that needs to be executed before. Therefore, the channel maintenance personnel are guided to carry out flow result configuration through the end node identification, and the configuration process can be more logical and clearer.
In step S4, a docking procedure is generated based on the edit information of the procedure details corresponding to each procedure details identifier.
As a possible implementation manner, the execution sequence of each piece of process detail information is determined according to the input sequence of the channel maintenance staff to the edit information of each piece of process detail information, and based on the execution sequence, the edit information of each piece of process detail information is converted into an execution script of a script engine, where the execution script is a configured docking process.
According to the configuration method of the docking process, the configuration operation of the whole docking process is visualized through the configuration page, the configuration process of the docking process is standardized by using the process template, so that the complexity of the configuration technology is reduced, the configuration efficiency of the docking process is improved, the channel docking requirements of suppliers can be responded quickly, the whole docking process can be completely online, normalized and streamlined through the page configuration, the docking detail interface of each channel is clearly checked, the situation that historical problems are difficult to trace is avoided, the docking process completed through online configuration can be completed, and the operations such as approval, version sending, testing, acceptance and the like can be performed subsequently, so that the research and development efficiency is improved.
In the foregoing embodiments, although the steps are numbered as S1, S2, etc., but only the specific embodiments are given in this application, and those skilled in the art may adjust the execution sequence of S1, S2, etc. according to the actual situation, which is also within the protection scope of the present invention, it is understood that some embodiments may include some or all of the above embodiments.
As shown in fig. 2, an execution method of a docking process provided in an embodiment of the present invention includes:
s10, acquiring input parameters;
s20, selecting a target docking procedure matched with the input parameter from the preset docking procedures, where the docking procedure is configured by using the configuration method of the docking procedure described in the above embodiment;
and S30, executing the target docking process based on the input parameters.
The system external interface is used for receiving input parameters to match the docking process, wherein the input parameters comprise parameters capable of determining the docking process, such as channel codes, keywords (AppKey) of docking service, service types and the like.
In this embodiment, the system sequentially executes each process stage of the target docking process according to the received input parameters, and for each process stage, executing the processes in the process stage includes:
1) executing switch logic judgment: using a rule engine to judge whether the flow details need to be executed or not, and executing the next flow details if the flow details do not need to be executed, wherein the mark for judging whether the flow details need to be executed or not is preset in the configuration process;
2) performing data conversion: converting by using a data conversion engine to generate request parameters required by the current flow stage;
3) and (3) performing parameter verification: using a rule engine to judge, checking the request parameters generated in the data conversion process, and judging whether the current request parameters are legal or not;
4) and executing a result request: calling a request domain (including http, soap, ftp, sftp and other request protocols), sending request parameters generated in the data conversion process to a provider/internal system/current system according to a specific request protocol, and analyzing response results into parameters by the request domain and returning the parameters to obtain a request result;
5) and performing request result verification: and judging whether the flow is successfully executed in detail or not by using a rule engine according to the request result.
And finishing the execution of each flow stage based on the detailed execution steps of the flows, converting the detailed response results of all the flows into output results according to the operation results generated by the configured flow results, and returning the output results to an upstream system.
Illustratively, the execution process of the number-changing docking flow is as follows:
1) the upstream request parameter of number changing is transmitted, and the DHL number changing process is started to run
2) "Pre-check" flow stage of execution flow
Calling a rule decision engine according to the parameter verification logic configured on the interface, judging whether the current parameter is legal, and if the current parameter is legal, continuing to execute the subsequent flow stage, and if the current parameter is legal, directly returning a verification error if the current parameter is illegal;
3) remote number changing process stage of execution process
3.1) executing the authentication flow: firstly, calling a rule engine to judge whether a detailed switch of the current process is opened, skipping the detailed switch of the current process if the detailed switch of the current process is not opened, calling a parameter conversion engine, converting a request parameter required by an authentication interface according to the currently configured parameter conversion logic, calling a request field to convert the request into an HTTP request message execution request to obtain a response result, calling the rule engine to judge whether the current response result is successful, directly returning if the response result is unsuccessful, namely finishing the execution of the butt joint process, outputting a result representing error information by the butt joint process, and otherwise, continuously executing the detailed follow-up process;
3.2) executing the "number changing" process: firstly calling a rule engine to judge whether a detailed switch of the current process is opened, skipping the detailed switch of the current process if the detailed switch of the current process is not opened, calling a parameter conversion engine, converting a request parameter required by a number conversion interface according to the currently configured parameter conversion logic, calling a request field into an HTTP request message to execute a request, obtaining a response result, calling the rule engine to judge whether the current response result is successful, directly returning if the response result is unsuccessful, and otherwise, continuously executing the detailed follow-up process.
4) Execute the "get list" flow stage of the flow
Execute "upload Base64 file to OSS" flow details: the calling rule engine judges whether a current flow detail switch is opened, skips the current flow detail if the current flow detail switch is not opened, calls the parameter conversion engine, converts request parameters required by an interface of uploading a Base64 file to an OSS according to the currently configured parameter conversion logic, converts a calling request domain into a local calling request message execution request to obtain a response result, judges whether the current response result is successful, directly returns if the response result is unsuccessful, and otherwise, continuously executes the subsequent flow detail.
5) Finally, judging whether the current flow is successfully executed, if so, generating logic according to the flow result configured by the page, and obtaining an output result corresponding to the successful result; if the execution fails, generating logic according to the flow result of the page configuration to obtain an output result corresponding to the failure result; the output result is returned to the upstream system.
In an embodiment of the present invention, a computer-readable storage medium is stored with instructions, and when the instructions are executed on a terminal device, the terminal device is caused to execute the steps of the configuration method of the docking flow in any one of the above embodiments, or the terminal device is caused to execute the steps of the execution method of the docking flow in any one of the above embodiments.
As shown in fig. 3, an electronic device 500 provided in an embodiment of the present invention includes a memory 510, a processor 520, and a program 530 stored in the memory 510 and running on the processor 520, where the processor 520 includes a first processor 5201 and a second processor 5202, and when the first processor 5201 executes the program 530, the first processor 5201 implements the steps of the configuration method of the docking flow in any of the embodiments, and when the second processor 5202 executes the program 530, the second processor 5202 implements the steps of the execution method of the docking flow in any of the embodiments.
The electronic device 500 may be a computer, a mobile phone, or the like, and correspondingly, the program 530 is computer software or a mobile phone App, and the parameters and the steps in the electronic device 500 according to the present invention may refer to the parameters and the steps in the embodiments of the configuration method and the execution method of the docking process, which are not described herein again.
As will be appreciated by one skilled in the art, the present invention may be embodied as a system, method or computer program product. Accordingly, the present disclosure may be embodied in the form of: may be embodied entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software, and may be referred to herein generally as a "circuit," module "or" system. Furthermore, in some embodiments, the invention may also be embodied in the form of a computer program product in one or more computer-readable media having computer-readable program code embodied in the medium.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (10)
1. A configuration method of a docking process, the method comprising:
responding to selection operation of a template identifier of a target flow template displayed on an initial page, and displaying a configuration page, wherein the configuration page is displayed with flow stages corresponding to the target flow template and flow detailed information identifiers corresponding to each flow stage, the initial page is displayed with template identifiers of a plurality of preset flow templates, the flow stage corresponding to the target flow template is a step required for executing a butt joint flow, and the flow stage corresponding to each preset flow template is different;
responding to the selection operation of a target process detailed information identifier in each process detailed information identifier, and displaying an editing page corresponding to the target process detailed information identifier;
receiving edit information of the flow detailed information corresponding to the target flow detailed information identification by a user through the edit page, wherein the flow detailed information is an operation rule required for executing a flow stage, and the operation rule is used for generating an output result of the flow stage;
and generating the docking flow according to the editing information of the flow detailed information corresponding to each flow detailed information identifier.
2. The method of claim 1, wherein the flow detail information identifier comprises a data conversion logic identifier and a result request logic identifier;
the receiving, by the editing page, the editing information of the process detailed information corresponding to the process detailed information identifier by the user includes:
receiving first editing information of the flow detailed information corresponding to the data conversion logic identifier by a user through the editing page, wherein the first editing information is an operation rule for converting an input parameter into a request parameter, and the input parameter is a parameter required for executing a flow stage corresponding to the data conversion logic identifier;
and receiving second editing information of the flow detailed information corresponding to the result request logic identifier by the user through the editing page, wherein the second editing information is an operation rule for generating an output result of the flow stage based on the request parameter.
3. The method of claim 2, wherein the flow detail information identifier further comprises a request result check logic identifier;
the receiving, by the editing page, the editing information of the process detailed information corresponding to the process detailed information identifier by the user includes:
and receiving third editing information of the flow detailed information corresponding to the request result verification logic identification by the user through the editing page, wherein the third editing information is an operation rule for verifying the output result of the flow stage.
4. The method of claim 3, wherein the request result check logic identification comprises an exception check logic identification and an exception handling logic identification;
the receiving, through the edit page, third edit information of the flow detail information corresponding to the request result check logic identifier by the user includes:
receiving fourth editing information of the flow detailed information corresponding to the abnormal verification logic identifier by the user through the editing page, wherein the fourth editing information is an operation rule for verifying whether an output result of the flow stage belongs to an abnormal response result;
and receiving fifth editing information of the detailed process information corresponding to the exception handling logic identifier by the user through the editing page, wherein the fifth editing information is an operation rule for processing the exception response result.
5. The method of claim 2, wherein the flow detail information identifier further comprises a parameter check logic identifier;
the receiving, by the editing page, the editing information of the process detailed information corresponding to the process detailed information identifier by the user includes:
and receiving sixth editing information of the flow detailed information corresponding to the parameter verification logic identifier by the user through the editing page, wherein the sixth editing information is an operation rule for verifying the request parameter.
6. The method according to any one of claims 1 to 5, wherein the flow detail information identifier further comprises an end node identifier;
the receiving, by the editing page, the editing information of the process detailed information corresponding to the target process detailed information identifier by the user includes:
responding to the selection operation aiming at the end node identification, and displaying a flow result generation logic identification on the editing page;
responding to the selection operation of generating the logic identifier aiming at the flow result, and displaying an end node editing page corresponding to the logic identifier generated by the flow result;
and receiving seventh editing information of the flow detailed information corresponding to the flow result generation logic identifier by the user through the end node editing page, wherein the seventh editing information is an operation rule for generating an output result of the docking flow based on the output result of each flow stage.
7. The method according to any one of claims 1 to 5, wherein an execution logic identifier corresponding to each flow stage is further displayed on the configuration page, and the execution logic identifier is used to indicate that the docking flow includes the flow stage corresponding to the execution logic identifier;
before the responding to the selection operation of the target process detailed information identifier in each process detailed information identifier and displaying the editing page corresponding to the target process detailed information identifier, the method further includes:
and responding to the selection operation aiming at the execution logic identifier, and displaying the flow detailed information identifier corresponding to the execution logic identifier on the configuration page.
8. An execution method of a docking process, the method comprising:
acquiring an input parameter;
selecting a target docking process matched with the input parameters from preset docking processes, wherein the docking process is configured by adopting the configuration method of the docking process of any one of claims 1 to 7;
and executing the target docking process based on the input parameters.
9. A computer-readable storage medium, characterized in that it has stored therein instructions that, when run on a terminal device, cause the terminal device to perform the steps of the configuration method of a docking procedure according to any one of claims 1 to 7, or cause the terminal device to perform the steps of the execution method of a docking procedure according to claim 8.
10. An electronic device comprising a memory, a processor and a program stored on the memory and running on the processor, wherein the processor comprises a first processor and a second processor, the first processor implementing the steps of the configuration method of the docking procedure according to any one of claims 1 to 7 when executing the program, and the second processor implementing the steps of the execution method of the docking procedure according to claim 8 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210368854.XA CN114816504A (en) | 2022-04-08 | 2022-04-08 | Configuration method and execution method of docking process, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210368854.XA CN114816504A (en) | 2022-04-08 | 2022-04-08 | Configuration method and execution method of docking process, electronic device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114816504A true CN114816504A (en) | 2022-07-29 |
Family
ID=82535431
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210368854.XA Pending CN114816504A (en) | 2022-04-08 | 2022-04-08 | Configuration method and execution method of docking process, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114816504A (en) |
-
2022
- 2022-04-08 CN CN202210368854.XA patent/CN114816504A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107592238B (en) | Automatic test method and system of interface, service terminal and memory | |
| WO2018210096A1 (en) | Rule engine-based rule configuration method, terminal and device, and storage medium | |
| CN109977012B (en) | Joint debugging test method, device, equipment and computer readable storage medium of system | |
| CN111858376A (en) | Request message generation method and interface test method | |
| JP2015204065A (en) | Test case generation device and test case generation method | |
| CN115860451A (en) | Flow operation method and device, electronic equipment and storage medium | |
| CN107357792B (en) | Data analysis method and device | |
| KR101766363B1 (en) | Method for simplifying work management using mobile device | |
| JP2000216854A (en) | Method, verification module, server, control module and storage means for verifying configuration data for communication system | |
| CN112241625A (en) | Method and system for automatically generating contract document based on java language | |
| CN114816504A (en) | Configuration method and execution method of docking process, electronic device and storage medium | |
| CN115617780A (en) | Data import method, device, equipment and storage medium | |
| CN112989781B (en) | Form data automatic execution method, device, electronic equipment and storage medium | |
| CN114185557A (en) | Software product deployment method, device, medium and electronic equipment | |
| CN112488325A (en) | Operation and maintenance work order processing method and device, computer equipment and storage medium | |
| CN114371866A (en) | Version reconfiguration test method, device and equipment of service system | |
| CN111159988A (en) | Model processing method and device, computer equipment and storage medium | |
| CN110737426A (en) | Program block creating method, program block creating device, computer equipment and storage medium | |
| CN110602057B (en) | Server login approval method and device, equipment and storage medium | |
| JP5243474B2 (en) | Infrastructure middleware parameter value improvement point presentation system | |
| CN115994097B (en) | Method and device for generating abnormal cash-out use cases based on error codes | |
| CN111427789B (en) | Method, device, computer equipment and storage medium for automatically verifying rule | |
| CN113256259B (en) | Online editing service system and implementation method thereof | |
| CN116225441B (en) | Code hosting method and system for online coding system | |
| JP7385245B2 (en) | Information processing device, information processing system, and information processing program |
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 |