CN115657901A - Service change method and device based on unified parameters - Google Patents
Service change method and device based on unified parameters Download PDFInfo
- Publication number
- CN115657901A CN115657901A CN202211286375.XA CN202211286375A CN115657901A CN 115657901 A CN115657901 A CN 115657901A CN 202211286375 A CN202211286375 A CN 202211286375A CN 115657901 A CN115657901 A CN 115657901A
- Authority
- CN
- China
- Prior art keywords
- service
- service change
- information
- change request
- metadata item
- 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
- 230000008859 change Effects 0.000 title claims abstract description 114
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000012508 change request Methods 0.000 claims abstract description 99
- 230000015654 memory Effects 0.000 claims description 14
- 238000003860 storage Methods 0.000 claims description 14
- 238000012795 verification Methods 0.000 claims description 8
- 238000004458 analytical method Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 6
- 238000006243 chemical reaction Methods 0.000 claims description 5
- 238000005516 engineering process Methods 0.000 abstract description 3
- 230000006854 communication Effects 0.000 description 9
- 238000012423 maintenance Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 238000011161 development Methods 0.000 description 7
- 230000018109 developmental process Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012545 processing 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
- 230000003287 optical effect Effects 0.000 description 3
- 230000007613 environmental effect Effects 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present disclosure relates to the field of financial technology, and in particular, to a method and an apparatus for changing a service based on unified parameters. Wherein the method comprises converting parameters involved in different services into metadata items not related to the services; determining a service change request according to service change type selection information input by service personnel; determining scene information and a metadata item corresponding to the service change request according to the service change request, wherein the scene information comprises environment information and system information; matching to a corresponding data source according to the metadata item, the environment information and the system information; and storing the content input by the business personnel for the metadata item in the corresponding data source. By using the embodiment of the text, the business personnel can directly change the business application according to the business requirement, thereby completing the business requirement.
Description
Technical Field
The present disclosure relates to the field of financial technology, and in particular, to a method and an apparatus for changing a service based on unified parameters.
Background
With the rapid development of banking industry, the social functions borne by banks are increasing day by day, the systems are complex day by day, and the parameter maintenance is an indispensable part for maintaining the stable operation of the systems.
At present, the parameter maintenance of the bank system is generally summarized and concluded by business personnel, then converted into an SQL script by developers, and finally executed by operation and maintenance personnel in a unified way in a target system to maintain parameters.
The modification of the parameters needs to be participated by three personnel of business, development and operation and maintenance, so misunderstanding is easily caused in the communication process, the parameter modification process is repeated and tortuous, and the parameter modification process is complicated and fussy. In addition, because the complexity of the bank system is high, the parameter maintenance among the systems and the parameter maintenance among the business modules are independent, so that the parameter maintenance is lack of unified management, and meanwhile, because the parameter management is lack of version control, the system development process and the stability of the existing system are greatly influenced.
How to improve the maintenance efficiency of the bank system parameters in the prior art is a problem which needs to be solved urgently.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments herein provide a service change method and apparatus based on unified parameters, which are used to save labor cost and time cost of service change.
The embodiment of the present disclosure provides a service change method based on unified parameters, including,
converting parameters involved in different services into metadata items not related to the services;
determining a service change request according to service change type selection information input by service personnel;
determining scene information and a metadata item corresponding to the service change request according to the service change request, wherein the scene information comprises environmental information and system information;
matching to a corresponding data source according to the metadata item, the environment information and the system information;
and storing the content input by the business personnel for the metadata item in the corresponding data source.
As an aspect of embodiments herein, converting parameters involved in different services to metadata items unrelated to the service further comprises,
acquiring codes of different services;
identifying a parameter name in the code;
and deleting the content related to the service in the parameter name to obtain a metadata item unrelated to the service.
As an aspect of embodiments herein, the service change request includes service change type information, scenario information, and metadata items.
As an aspect of the embodiments herein, determining that the service change request further includes, based on the service change type selection information input by the service person,
acquiring login information input by the service personnel;
and verifying whether the service personnel has the authority to carry out corresponding service change or not according to the login information and the service change type selection information, if the service personnel passes the verification, determining a service change request, and if the verification fails, rejecting the service change request.
As an aspect of the embodiments herein, determining that the metadata item corresponding to the service change request and the scenario information according to the service change request further includes,
analyzing the service change request to obtain the environment information and the system information;
and analyzing the service change request to obtain the metadata item needing to be changed in the service change request.
As an aspect of embodiments herein, matching to a corresponding data source based on the metadata item, the environment information, and the system information further comprises,
acquiring a corresponding alternative data source set according to the environment information and the system information;
and matching the corresponding data source in the alternative data source set according to the metadata item.
As an aspect of the embodiments herein, storing the content entered by the business person for the metadata item in the corresponding data source further comprises,
acquiring the content input by the service personnel for the metadata item;
and writing the content input by the metadata item into a corresponding field in the corresponding data source.
Embodiments herein also provide a unified parameter based service change apparatus, including,
a conversion unit for converting parameters involved in different services into metadata items not related to the services;
the service change request unit is used for determining a service change request according to service change type selection information input by service personnel;
the analysis unit is used for determining scene information and a metadata item corresponding to the service change request according to the service change request, wherein the scene information comprises environment information and system information;
the matching unit is used for matching to a corresponding data source according to the metadata item, the environment information and the system information;
and the storage unit is used for storing the content input by the business personnel aiming at the metadata item in the corresponding data source.
Embodiments herein also provide a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the above-mentioned method when executing the computer program.
Embodiments herein also provide a computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, implement the above-described method.
By utilizing the embodiment of the text, the business personnel can directly change the business application according to the business requirement so as to complete the business requirement, and the business personnel do not need to put forward the requirement like the prior art, and the developers can generate the script for completing the business requirement, and then the maintainer updates the script into the system so as to realize the business requirement put forward by the business personnel; because the service personnel do not know how the parameters in the original service code are named, when the parameters in a certain service need to be changed, the parameters can be unrelated to the specific service by converting the parameters into metadata items, and the service personnel can change the parameters in the service without knowing the parameter naming rule at the bottom of the service code.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the embodiments or technical solutions in the prior art are briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic structural diagram of a unified parameter based service change system according to an embodiment of the present disclosure;
fig. 2 is a flowchart illustrating a service change method based on unified parameters according to an embodiment of the present disclosure;
FIG. 3 is a schematic interface diagram illustrating a service change according to an embodiment of the present disclosure;
fig. 4 is a flowchart illustrating a service change method based on unified parameters according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a service change apparatus based on unified parameters according to an embodiment of the present disclosure;
fig. 6 illustrates a computer device provided in an embodiment herein.
[ description of reference ]
101. A user terminal;
102. a service change device;
103. a data source;
104. a service front end;
501. a conversion unit;
502. a service change request unit;
503. an analysis unit;
504. a matching unit;
505. a storage unit;
602. a computer device;
604. a processor;
606. a memory;
608. a drive mechanism;
610. an input/output module;
612. an input device;
614. an output device;
616. a presentation device;
618. a graphical user interface;
620. a network interface;
622. a communication link;
624. a communication bus.
Detailed Description
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 only a part of the embodiments of the present invention, and not all of the embodiments. 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 scope of protection given herein.
Fig. 1 is a schematic structural diagram of a unified parameter based service change system according to an embodiment of the present invention, and in the present diagram, the system includes a user terminal 101, a service change apparatus 102, a service-related data source 103, and a service front end 104. The service personnel uses the user terminal 101 to make a service change request for the parameters to be maintained, and the service change request can be realized by devices such as a notebook computer, a desktop computer and a tablet computer; the service change device 102 extracts parameters in the data source 103 related to the service, converts the extracted parameters into metadata items unrelated to the service, and stores the metadata items in the service change device 102, so that a service worker can select parameters to be changed when making a service change request, the service worker can match the corresponding data source 103 according to the service change request of the service worker and update the changed parameters to the data source 103 without knowing the corresponding relation between the data source 103 and the corresponding service front end 104 and knowing the naming rule of the parameters in the data source 103 and only selecting the metadata items according to the service requirement to be changed, thereby changing the service; the data source 103 is used for storing parameter data required in the service, wherein the parameters may have different expression forms according to different services; the service front end 104 is configured to call the parameter data in the data source 103 according to the user requirement, and complete a service function required by the user, such as a change of a personal integral storage and integral access product, a new increase of the personal integral storage and integral access product, and the like.
Through the system of the embodiment, the service personnel can directly change the service application according to the service requirement so as to complete the service requirement, and the service requirement is not required to be met as in the prior art, the requirement is provided by the service personnel, the script for completing the service requirement is generated by the development personnel, and then the script is updated into the system by the maintenance personnel, so that the service requirement provided by the service personnel can be met; since the service personnel does not know how the parameters in the original service code are named, when the parameters in a certain service need to be changed, the parameters can be independent of the specific service by converting the parameters into the metadata items, so that the service personnel can change the parameters in the service without knowing the parameter naming rules of the bottom layer of the service code, for example, in the service 1, the parameter of the user name is the service 1_ user name, while in the service 2, the parameter of the user name is the service 2_ user ID, after the parameter of the user name is converted into the service independent, the user name can be referred to by the UserName, and the service personnel can write the user name acquired by the metadata item into the data source corresponding to the service N only by selecting the metadata item in the service N needing to be changed.
Fig. 2 is a flowchart of a service change method based on unified parameters according to an embodiment of the present disclosure, where a parameter name associated with a service is converted into a metadata item unrelated to the service, and a service person can match scenario information of a service change to a data source of a corresponding service, so as to change parameters related to the service, thereby achieving the purpose of changing the service. The method specifically comprises the following steps:
As an embodiment herein, converting parameters involved in different services into metadata items that are not related to the service further comprises,
acquiring codes of different services;
identifying a parameter name in the code;
and deleting the content related to the service in the parameter name to obtain a metadata item unrelated to the service.
In this embodiment, the program code of each service is obtained through a code reading interface, which may be implemented by a program to read other program codes. The parameter name matching module can be realized by program codes, and identifies parameters included in the service program codes through a preset metadata list, for example, a character string matching mode is adopted. Since different service program codes may be developed by different development teams, the parameter names may have characteristics and requirements of respective services, parameters having the same meaning may be added with different character strings in front of or behind the character strings having specific meanings to form parameter names related to the services according to needs and different teams, a service person may not know a specific naming rule for a certain parameter in each service program code clearly, which is very disadvantageous for service change for the service person, the service person is a work post most closely contacted with a client, and needs to flexibly change the services according to requirements of the client and market conditions, for example, modification of an existing service, improvement of a newly added service on the basis of the existing service, and the like.
The metadata list refers to a common name of a parameter representing a specific meaning, wherein the stored metadata item is a common name of a parameter having a specific meaning in each service, and is independent of the service, for example, the representative meaning of the metadata item current _ interest is a current interest rate, the parameter name in the service 1 program code is service 1 current _ interest, the parameter name in the service 2 program code is current _ interest _ service 2, the actual meaning of the parameter (current _ interest) in any service is consistent, and all parameter names including the metadata item meaning in the service program code can be obtained by matching each metadata item recorded in the metadata list in the service program code.
The parameter name processing module deletes the content related to the service in the parameter name output by the parameter name matching module, for example, deletes the _ service 2 in the current _ interest _ service 2, so that the parameter name obtained by matching in the service 2 program code is converted into a metadata item _ current _ interest "in a metadata list unrelated to the service, thereby, the service personnel can directly change the parameter content used by the service according to the requirement of service change without referring to the complete specific parameter name in the service.
As an embodiment herein, the service change request includes service change type information, scenario information, and metadata items, wherein the service change scenario information further includes a new addition request or a change request.
In this embodiment, a service person may adjust a service according to factors such as a requirement of a client and a change in a market, which may involve a change in assignment of existing parameters of the service, such as increasing or decreasing a current interest value; and adding a new service product, for example, using some existing service as a template, calling required metadata items to form service parameters, and setting values of the parameters to form the new service product.
As an embodiment herein, determining that the service change request further includes, based on the service change type selection information input by the service person,
acquiring login information input by the service personnel;
and verifying whether the service personnel has the authority to carry out corresponding service change or not according to the login information and the service change type selection information, if the service personnel passes the verification, determining a service change request, and if the verification fails, rejecting the service change request.
In this embodiment, a service person logs in the system to input a user name and a password, and inputs service change type selection information, for example, the change type selection information is to select a new entire-access service product, and the system verifies whether the logged-in service person has permission to perform an event of the service change type according to the service change type selected by the service person, that is, the new entire-access service product. For example, the service authority of the user can be searched in a service personnel authority table, if the service change type of the newly added whole storage and retrieval service product is not in the authority range of the user, the verification fails, and a service change refusal request is fed back to the service personnel through a page; and if the service change type of the newly added and integrally stored service product is within the authority range of the user, determining the service change request.
As an embodiment herein, determining that the metadata item corresponding to the service change request and the scenario information according to the service change request further includes,
analyzing the service change request to obtain the environment information and the system information;
and analyzing the service change request to obtain the metadata item needing to be changed in the service change request.
In this embodiment, the service change request includes environment information and system information, where the environment information may include, for example, a development environment, a test environment, a production environment, and the like, and the system information may include, for example, a deposit system, a client system, a public service system, and the like, and the service change request further includes metadata items to be changed, that is, a service person needs to change one or more parameters related to one or more services according to a requirement of the service change, where the change refers to modifying or adding some metadata items, and these metadata items are embodied in service program codes as parameter names related to the services, but in this step, since the correlation between the metadata items and the services is deleted, the metadata items here only represent a true meaning represented by the required change parameters when the service person changes the services, and not a true parameter name in a service. The service change request is determined by service change type selection information, for example, as shown in fig. 3, a drop-down box is provided for the service personnel to select when changing the service, wherein the drop-down box includes a selection item of the service change type, a selection item of the environment information and the system information, and a drop-down box for adding a metadata item as a parameter in the service program code. By analyzing the drop-down selection frame of the service change type in the interface, the service change type to be performed currently can be obtained as a service adding request or a service change request; by analyzing the scene drop-down selection box in the interface, the scene for which the service change to be performed currently is performed can be obtained, namely, the service change is performed for which system in which environment; through the analysis of a metadata item drop-down box in the interface, the metadata items involved in the currently-to-be-performed service change can be obtained, and the input content of the metadata item change can be obtained.
As an embodiment herein, matching to the corresponding data source according to the metadata item, the environment information, and the system information further comprises,
acquiring a corresponding alternative data source set according to the environment information and the system information;
and matching the corresponding data source in the alternative data source set according to the metadata item.
In this embodiment, since the banking system includes multiple environments, the data sources corresponding to different environments are all different and do not affect each other, and the correspondence between different services and data sources in different environments is a many-to-many relationship. The banking system also includes a plurality of systems, each of which includes a plurality of data sources. Therefore, a data source cannot be determined by specifying a certain service, a corresponding alternative data source set needs to be selected according to environment information and system information carried in a service change request, the data source may include a plurality of databases corresponding to the certain service in a certain environment, and the plurality of databases form the alternative data source set. For example, the development environment and the deposit system indicated by the scene information in the business change request in the interface are obtained, and a plurality of databases related to the scene can be obtained as alternative data sources. And adding service information needing to be changed when selecting the environment information, so that the alternative data source can be obtained.
The metadata items acquired in the metadata item drop-down selection box can be matched in the alternative data source set, each database in the alternative data source set may include parameter names associated with services, the parameter names and the metadata items have certain relevance, matching can be performed in a keyword matching mode and a character string matching mode, and a data source simultaneously having a plurality of associated metadata items is used as a data source corresponding to the service change request.
As one embodiment herein, storing the content entered by the business person for the metadata item in the corresponding data source further comprises,
acquiring the content input by the service personnel for the metadata item;
and writing the content input by the metadata item into a corresponding field in the corresponding data source.
In this embodiment, a plurality of metadata items indicated by the metadata item in the service change request in the interface are acquired, a database including all the metadata items is matched from the alternative data source, and the acquired content of the metadata item change in the interface is written into the corresponding database, so that a service worker can complete the service change by simple setting.
As one embodiment herein, before writing the content entered by the metadata item into the corresponding field, further comprising,
and the backup service changes the data source before, and forms a historical version of the data source which is sorted according to the time sequence.
In this embodiment, when an error occurs in the service change, the historical version of the data source at the specified time is used to recover the data source, so that the problem that the data source version cannot be rolled back to a long-time data source version due to limited cache area of a database rollback or a rollback mechanism can be avoided.
As an embodiment herein, determining scene information according to the service change request and metadata items corresponding to the service change request further includes,
determining a reference service product by combining the scene information and the reference service product information input by the service personnel;
and filling the parameter content in the reference service product into the content of the metadata item corresponding to the service change request.
In this embodiment, when a service person selects a scene drop-down selection box in an interface, a scene to which a service change is currently performed is determined, and then reference service product information selected by the service person is obtained in a mode of an input box or a mode of the drop-down selection box, where the reference service product information may include, for example, a certain service product in the scene as a reference service product, or a keyword related to a service input by the service person, and then the corresponding service product may be screened from the scene as the reference service product. After the reference service product is determined according to a matching or selecting mode, all parameters in a program code of the reference service product and specific contents of the parameters, such as specific set values of parameter interest rates, can be acquired, the specific contents of the parameters are filled into an input box of a metadata item selected by a service person to serve as pre-input contents of the metadata item, and after the service person edits the metadata item contents to be changed, the input contents of all the metadata items are stored into a corresponding data source. By the scheme, the content of the parameters in the service change input by the service personnel can be saved, the parameter content which does not need to be changed can be directly kept in the original state, and only the parameter content which needs to be changed is edited and input, so that the processing time of the service personnel on the service change is saved, and the working efficiency is improved.
Fig. 4 is a flowchart of a service change method based on unified parameters according to an embodiment of the present disclosure, where in the flowchart, when a service change is performed by a service staff, a service change application is performed on a user terminal of the service staff, a service change approval is performed on a service change device, after the approval is passed, a service change request is rechecked, and whether the service change request is written into a data source is determined according to a result of the rechecking. The method specifically comprises the following steps:
In this step, parameters involved in different services are converted beforehand into metadata items that are not related to the service. For example, the product STATUS in the personal entire access and entire access service is converted into the metadata item STATUS, and the certificate STATUS in the certificate type table change service is converted into the metadata item STATUS. Wherein the metadata item STATUS is service independent.
In this step, the service person initiates a service change request to the service change device through the user terminal. The service person inputs service change type selection information through a user terminal interface as shown in fig. 3, for example, a selection item including a service change type, a selection item for environment information and system information, and a drop-down selection box for adding a metadata item as a parameter in the service program code. The user terminal interface can also comprise a pull-down selection box for referring to the service product information, and service personnel can call out the parameter contents corresponding to all related parameters in the program code of the reference service product by selecting the reference service product and automatically fill the parameter contents into the metadata item contents corresponding to the metadata item.
And step 403, canceling the service change request.
In this step, the service personnel may also cancel the service change request by clicking a service change cancel button.
And step 404, the service change device performs login verification according to the login information of the service personnel.
In this step, the service person logs in the system to input a user name and a password, and inputs service change type selection information, for example, the change type selection information is to select a new entire-access service product, and the system verifies whether the logged-in service person has the authority to perform the transaction of the service change type according to the service change type selected by the service person, that is, the new entire-access service product.
In step 405, a service change request is accepted.
In this step, the service change device processes the service change request, and by analyzing the drop-down selection box of the change type in the interface, the service change type to be currently performed can be obtained as a new request or a change request; by analyzing the scene drop-down selection box in the interface, the scene for which the service change to be performed currently is performed can be obtained, namely, the service change is performed for which system in which environment; through analysis of a metadata item drop-down selection box in the interface, the metadata items involved in the currently-to-be-performed service change can be obtained.
In this step, for the analyzed service change type, environment information, system information, and metadata item, whether there is an error of inputting content, such as exceeding an allowable value range, whether the data type does not meet the requirement, whether the content input by the metadata item significantly exceeds a corresponding parameter value in a reference service product, etc., if there is a problem, the step proceeds to step 407, and the current service change request is rejected; if there is no problem, step 408 is entered to submit the business change request.
And feeding back a message for rejecting the current service change request to a user terminal of a service person, and informing the service person of the reason why the current service change request is rejected.
In this step, through the development environment and the deposit system indicated by the scene information in the service change request in the interface obtained in the previous step, a plurality of databases related to the scene can be obtained as alternative data sources. The metadata items acquired from the metadata item drop-down selection box can be matched in an alternative data source set, each database in the alternative data source set may include a plurality of parameter names associated with services, the parameter names and the metadata items have certain association, that is, the parameter names and the metadata items have the same meaning, and the naming rules have differences but are substantially the same, for example, all have core keywords expressing meanings, and the data sources having a plurality of associated metadata items at the same time can be matched in a keyword matching manner and a character string matching manner, and are used as data sources corresponding to the service change request.
When the corresponding data source is matched from the alternative data source set, if the current service change request is a new service product, a data source (database) is newly generated, and the data source is marked to be associated with the environment information and the system information, the parameter name in the newly generated data source is determined according to the parameter name in the program code of the reference service product, or the metadata item is converted into the parameter name in the data source, that is, the parameter name is written in the newly generated data source by adding a prefix or a suffix of the metadata item.
And step 409, accepting and canceling the service change request.
In this step, in parallel with the above-described steps 407 and 408, when the service person makes a request for receiving a service change, the service person may make a request for canceling the reception, terminate the reception of the service change request, and return to step 405.
And step 410, updating the corresponding data source with the submitted service change request.
In this step, a plurality of metadata items indicated by the metadata item in the service change request in the interface are acquired, a data source (database) including all the metadata items is matched from the alternative data sources, and the acquired content of the metadata item change in the interface is written into the corresponding data source, so that the purpose that service personnel can complete the service change through simple setting is achieved.
In step 411, the service change request is ended.
In this step, the flow of the service change request is ended, for example, if the content of the metadata item written in the data source is correct, the service change request is ended normally; if the service change request is cancelled, the service change request is triggered to end; and if the acceptance of the service change request is refused, triggering the service change request to end.
Fig. 5 is a schematic structural diagram of a service change apparatus based on unified parameters according to an embodiment of the present disclosure, where the apparatus in this embodiment may utilize a desktop computer, a server, and other devices to implement a function of helping a service worker change a service, and specifically includes:
the conversion unit 501 is used for converting parameters involved in different services into metadata items unrelated to the services;
a service change request unit 502, configured to determine a service change request according to service change type selection information input by a service person;
an analyzing unit 503, configured to determine, according to the service change request, scene information and a metadata item corresponding to the service change request, where the scene information includes environment information and system information;
a matching unit 504, configured to match to a corresponding data source according to the metadata item, the environment information, and the system information;
a storage unit 505, configured to store, in the corresponding data source, the content that is input by the service staff for the metadata item.
By the device of the embodiment, service personnel can change the parameters of the service without knowing the parameter name in the program code of each service product, so that the time and labor cost for developing the service product are saved.
As shown in fig. 6, a computer device provided in this embodiment is shown, and an apparatus for performing a service change in this embodiment may be a computer device in this embodiment, and perform the method described herein. The computer device 602 may include one or more processors 604, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 602 may also include any memory 606 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 606 may include any one or combination of the following: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 602. In one case, when the processor 604 executes the associated instructions, which are stored in any memory or combination of memories, the computer device 602 may perform any of the operations of the associated instructions. The computer device 602 also includes one or more drive mechanisms 608, such as a hard disk drive mechanism, an optical disk drive mechanism, or the like, for interacting with any of the memories.
The computer device 602 may also include an input/output module 610 (I/O) for receiving various inputs (via input devices 612) and for providing various outputs (via output devices 614). One particular output mechanism may include a presentation device 616 and an associated Graphical User Interface (GUI) 618. In other embodiments, input/output module 610 (I/O), input device 612, and output device 614 may also be excluded, as just one computer device in a network. Computer device 602 may also include one or more network interfaces 620 for exchanging data with other devices via one or more communication links 622. One or more communication buses 624 couple the above-described components together.
Embodiments herein also provide computer readable instructions, wherein a program thereof causes a processor to perform a method as described above when the instructions are executed by the processor.
It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.
It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.
Those of ordinary skill in the art will appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the components and steps of the various examples have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components 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 units, and may also be an electric, mechanical or other form of connection.
The units described as separate parts may or may not be physically separate, and parts displayed as units 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 elements may be selected according to actual needs to achieve the objectives of the embodiments herein.
In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The principles and embodiments of the present disclosure are explained in detail by using specific embodiments, and the above description of the embodiments is only used to help understanding the method and its core idea; meanwhile, for the general technical personnel in the field, according to the idea of this document, there may be changes in the concrete implementation and the application scope, in summary, this description should not be understood as the limitation of this document.
Claims (10)
1. A service change method based on unified parameters is characterized by comprising,
converting parameters involved in different services into metadata items unrelated to the services;
determining a service change request according to service change type selection information input by service personnel;
determining scene information and a metadata item corresponding to the service change request according to the service change request, wherein the scene information comprises environment information and system information;
matching to a corresponding data source according to the metadata item, the environment information and the system information;
and storing the content input by the business personnel for the metadata item in the corresponding data source.
2. A unified parameter based service change method according to claim 1, wherein converting parameters involved in different services into metadata items not related to services further comprises,
acquiring codes of different services;
identifying a parameter name in the code;
and deleting the content related to the service in the parameter name to obtain a metadata item unrelated to the service.
3. The unified parameter-based service change method of claim 1, wherein the service change request comprises service change type information, scenario information and metadata items.
4. The unified parameter based service change method according to claim 3, wherein the determining the service change request further comprises, based on the service change type selection information inputted by the service personnel,
acquiring login information input by the service personnel;
and verifying whether the service personnel has the authority to carry out corresponding service change or not according to the login information and the service change type selection information, if the service personnel passes the verification, determining a service change request, and if the verification fails, rejecting the service change request.
5. The unified parameter based service change method according to claim 3, wherein the determining the scene information and the metadata item corresponding to the service change request further comprises,
analyzing the service change request to obtain the environment information and the system information;
and analyzing the service change request to obtain the metadata item needing to be changed in the service change request.
6. The unified parameter-based service change method of claim 5, further comprising matching to corresponding data sources according to the metadata item, the environment information and the system information,
acquiring a corresponding alternative data source set according to the environment information and the system information;
and matching the corresponding data source in the alternative data source set according to the metadata item.
7. The unified parameter based service change method according to claim 6, wherein storing the contents entered by the service personnel for the metadata item in the corresponding data source further comprises,
acquiring the content input by the service personnel for the metadata item;
and writing the content input by the metadata item into a corresponding field in the corresponding data source.
8. A service change device based on unified parameters is characterized by comprising,
a conversion unit for converting parameters involved in different services into metadata items not related to the services;
the service change request unit is used for determining a service change request according to the service change type selection information input by service personnel;
the analysis unit is used for determining scene information and a metadata item corresponding to the service change request according to the service change request, wherein the scene information comprises environment information and system information;
the matching unit is used for matching to a corresponding data source according to the metadata item, the environment information and the system information;
and the storage unit is used for storing the content input by the business personnel aiming at the metadata item in the corresponding data source.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of the preceding claims 1-7 when executing the computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, is adapted to carry out the method of any of the preceding claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211286375.XA CN115657901B (en) | 2022-10-20 | 2022-10-20 | Service changing method and device based on unified parameters |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211286375.XA CN115657901B (en) | 2022-10-20 | 2022-10-20 | Service changing method and device based on unified parameters |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115657901A true CN115657901A (en) | 2023-01-31 |
| CN115657901B CN115657901B (en) | 2023-07-11 |
Family
ID=84989933
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211286375.XA Active CN115657901B (en) | 2022-10-20 | 2022-10-20 | Service changing method and device based on unified parameters |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115657901B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101552701A (en) * | 2008-04-03 | 2009-10-07 | 华为技术有限公司 | Method, system and device for recording parameter maintenance variation |
| CN101751241A (en) * | 2009-12-09 | 2010-06-23 | 南京联创科技集团股份有限公司 | Implementation method of DATACOM (data communication) data command platform |
| CN107153701A (en) * | 2017-05-10 | 2017-09-12 | 焦点科技股份有限公司 | A kind of IT system management and method for managing and monitoring based on metadata |
| US20210149883A1 (en) * | 2018-12-20 | 2021-05-20 | Advanced New Technologies Co., Ltd. | Data structure reading methods and apparatuses, data structure update methods and apparatuses, and electronic devices |
| CN115146242A (en) * | 2022-06-30 | 2022-10-04 | 平安银行股份有限公司 | A method, device and electronic device for dynamically configuring parameters |
-
2022
- 2022-10-20 CN CN202211286375.XA patent/CN115657901B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101552701A (en) * | 2008-04-03 | 2009-10-07 | 华为技术有限公司 | Method, system and device for recording parameter maintenance variation |
| CN101751241A (en) * | 2009-12-09 | 2010-06-23 | 南京联创科技集团股份有限公司 | Implementation method of DATACOM (data communication) data command platform |
| CN107153701A (en) * | 2017-05-10 | 2017-09-12 | 焦点科技股份有限公司 | A kind of IT system management and method for managing and monitoring based on metadata |
| US20210149883A1 (en) * | 2018-12-20 | 2021-05-20 | Advanced New Technologies Co., Ltd. | Data structure reading methods and apparatuses, data structure update methods and apparatuses, and electronic devices |
| CN115146242A (en) * | 2022-06-30 | 2022-10-04 | 平安银行股份有限公司 | A method, device and electronic device for dynamically configuring parameters |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115657901B (en) | 2023-07-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11558429B2 (en) | Data processing and scanning systems for generating and populating a data inventory | |
| US12153629B1 (en) | Systems and user interfaces for dynamic and interactive table generation and editing based on automatic traversal of complex data structures and incorporation of metadata mapped to the complex data structures | |
| US11876910B2 (en) | Systems, methods, and apparatuses for implementing a multi tenant blockchain platform for managing Einstein platform decisions using distributed ledger technology (DLT) | |
| CN110495132B (en) | System and method for generating, uploading and executing code blocks within distributed network nodes | |
| US12124434B2 (en) | Blockchain-based systems and methods for communicating, storing and processing data over a blockchain network | |
| US10783116B2 (en) | Systems and methods for managing data | |
| US7315978B2 (en) | System and method for remote collection of data | |
| US20060005036A1 (en) | Enterprise security management system using hierarchical organization and multiple ownership structure | |
| CN105723335A (en) | Data flow exploration | |
| CN101110021A (en) | Method for visually programming instruction set for process | |
| CN114303164A (en) | Supplier invoice reconciliation and payment using event driven platform | |
| JP7161538B2 (en) | Systems, apparatus and methods for processing and managing web traffic data | |
| Lytvyn et al. | Development of the system to integrate and generate content considering the cryptocurrent needs of users | |
| AU2015331028A1 (en) | Electronic processing system for electronic document and electronic file | |
| US20240356931A1 (en) | Systems, methods, apparatuses and computer program products for executing data verification operations between independent computing resources | |
| US20180165180A1 (en) | Batch File Creation Service | |
| CN111064725A (en) | Code zero intrusion interface verification method and device | |
| CN114385722A (en) | Interface attribute consistency checking method and device, electronic equipment and storage medium | |
| US20210124752A1 (en) | System for Data Collection, Aggregation, Storage, Verification and Analytics with User Interface | |
| MX2013008701A (en) | Inventory data access layer. | |
| CN111882294B (en) | Method and device for flow approval | |
| CN110852701A (en) | Product demand management method, device and system | |
| CN115657901A (en) | Service change method and device based on unified parameters | |
| CN114416805A (en) | Data checking method and device, computer equipment and storage medium | |
| CN114579398A (en) | Log storage method, device, equipment and storage medium |
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 |