CN118349245A - User version upgrading method, system and storage medium for SaaS system - Google Patents
User version upgrading method, system and storage medium for SaaS system Download PDFInfo
- Publication number
- CN118349245A CN118349245A CN202410254666.3A CN202410254666A CN118349245A CN 118349245 A CN118349245 A CN 118349245A CN 202410254666 A CN202410254666 A CN 202410254666A CN 118349245 A CN118349245 A CN 118349245A
- Authority
- CN
- China
- Prior art keywords
- version
- user
- configuration
- data
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
According to the user version upgrading method, the system and the storage medium for the SaaS system, the current version identity and the target version identity which is scheduled to be updated are obtained according to the version upgrading instruction, the first operation environment is built according to the target version identity, the test environment information of the target version is obtained in the version database according to the target version identity, the verification environment information of the target version is obtained in the version database after the user test passing instruction is received to build the second operation environment, and finally the production environment information of the target version is obtained in the version database after the user verification passing instruction is received to build the third operation environment, so that a user can upgrade the system gradually in a three-stage building mode, the user can stop updating at any time when a problem occurs, the stability and the reliability of the new version are ensured, and the risk possibly brought by deploying the new version in the production environment is reduced.
Description
Technical Field
The present invention relates to the field of system upgrade, and in particular, to a user version upgrade method, system and storage medium for a SaaS system.
Background
The SaaS (software as a service) system is a software application mode for providing software services based on the internet, and is widely applied in various industries due to the advantages of low cost, high flexibility, expandability, automation integration and the like, and the continuous version iterative update of the system continuously provides better performance and user experience for users. However, in the process of upgrading the version of the SaaS system, the user often has abnormal upgrading conditions due to instability of the new version, data disorder, data loss, compatibility and other problems in the data transmission process, so that version updating failure is caused, and normal use of the user is affected.
Disclosure of Invention
The invention discloses a user version upgrading method for a SaaS system, which aims at the defects in the prior art and comprises the following steps:
Acquiring a current version identity and a target version identity which is scheduled to be updated according to a version upgrading instruction, and acquiring test environment information of a target version in a version database according to the target version identity to build a first operation environment, wherein the first operation environment is used for testing new version functions;
After receiving a user test passing instruction, acquiring verification environment information of a target version from a version database to build a second running environment, wherein the second running environment is used for verifying a new version function;
after receiving the user verification passing instruction, acquiring production environment information of the target version from the version database to build a third operation environment, wherein the third operation environment is used for carrying out final production and use on the new version.
Preferably, the step of obtaining the current version identity and the target version identity of the plan update according to the version upgrade instruction, and obtaining the test environment information of the target version in the version database according to the target version identity to build the first running environment specifically includes:
Acquiring a current version identity and a target version identity scheduled to be updated according to the version upgrading instruction;
acquiring test environment information of a target version from a version database according to the identity of the target version to build a first running environment and optional simulation configuration information;
Operating parameter configuration is carried out according to parameter configuration options selected by a user, wherein the parameter configuration options comprise a first configuration option and a second configuration option, if the user adopts the first configuration option, the selectable simulation configuration information is all input into a first operating environment for parameter configuration to form a test system of a target version, if the user adopts the second configuration option, user configuration data of the user under the current version are collected, the collected user configuration data are replaced by corresponding information in the selectable simulation configuration information and then are input into the first operating environment for parameter configuration to form the test system of the target version, and the user configuration data comprise but are not limited to user role and authority setting information, data type and constraint information, business logic and rule information of the current version.
Preferably, if the user adopts the second configuration option, collecting user configuration data of the user under the current version, replacing corresponding information in the optional simulation configuration information with the collected user configuration data, and then inputting the obtained user configuration data into the first operation environment for parameter configuration to form a test system of the target version, which specifically comprises: if the user adopts the second configuration option, acquiring user configuration data of the user under the current version, and converting the acquired user configuration data into configuration data of the target version according to a configuration information corresponding table of the target version and the current version; comparing the converted configuration data with optional simulation configuration information to obtain missing configuration data, and sending the missing configuration data type and optional corresponding simulation data like a user; and supplementing the missing configuration data newly supplemented by the user or the selected corresponding simulation data into the converted configuration data to form final target version configuration data, and inputting the final target version configuration data into the first operation environment to perform parameter configuration to form a target version test system.
Preferably, the method further comprises: the parameter configuration options further comprise third configuration options, and if the user adopts the third configuration options, the difference quantity of the configuration data of the target version and the current version is obtained; if the difference quantity of the configuration data is lower than a first threshold value, directly generating a parameter configuration interface for acquiring user input data; if the user configuration data is larger than the first threshold, the user configuration data of the user under the current version is directly collected, the obtained user configuration data is converted into the configuration data of the target version according to the configuration information corresponding table of the target version and the current version, and candidate simulation configuration data are provided for the user to select for the configuration data of the target version which is still missing after conversion.
Preferably, the configuration data includes system option data configured to be available only through acquisition user input in the configuration option and auxiliary configuration data configured to be available through acquisition user input in the configuration option and simulation data of an auxiliary configuration corresponding to the acquired system option data in the selectable simulation configuration information of the target version from the version database.
The invention also discloses a user version upgrading system for the SaaS system, which comprises a first building module, a second building module and a third building module, wherein the first building module is used for acquiring a current version identity and a target version identity which is scheduled to be updated according to a version upgrading instruction, and building a first running environment according to the target version identity and testing environment information of a target version in a version database, and the first running environment is used for testing new version functions; the second building module is used for obtaining verification environment information of the target version from the version database to build a second running environment after receiving a user test passing instruction, wherein the second running environment is used for verifying the new version function; the third building module is used for obtaining the production environment information of the target version from the version database to build a third operation environment after receiving the user verification passing instruction, and the third operation environment is used for carrying out final production and use on the new version.
Preferably, the first building module specifically includes an identity confirmation module, an environment building module, and a parameter configuration module, where the identity confirmation module is configured to obtain a current version identity and a target version identity for planning updating according to a version upgrading instruction; the environment construction module is used for acquiring test environment information of a target version from the version database according to the identity of the target version to construct a first running environment and optional simulation configuration information; the parameter configuration module is used for carrying out operation parameter configuration according to parameter configuration options selected by a user, the parameter configuration options comprise a first configuration option and a second configuration option, if the user adopts the first configuration option, the selectable simulation configuration information is all input into a first operation environment to carry out parameter configuration to form a test system of a target version, if the user adopts the second configuration option, user configuration data of the user under the current version are collected, the collected user configuration data are replaced by corresponding information in the selectable simulation configuration information and then are input into the first operation environment to carry out parameter configuration to form the test system of the target version, and the user configuration data comprise but are not limited to user role and authority setting information, data type and constraint information, business logic and rule information of the current version.
Preferably, the parameter configuration module further comprises a data conversion module, a data supplementing module and a data input module, wherein the data conversion module is used for acquiring user configuration data of the user under the current version if the user adopts the second configuration option, and converting the acquired user configuration data into configuration data of the target version according to the configuration information corresponding table of the target version and the current version; the data supplementing module is used for comparing the converted configuration data with the optional simulation configuration information to obtain missing configuration data and sending the missing configuration data type and the optional corresponding simulation data to a user; the data input module is used for supplementing the missing configuration data newly supplemented by the user or the selected corresponding simulation data into the converted configuration data to form final target version configuration data, and inputting the final target version configuration data into the first operation environment to perform parameter configuration to form a target version test system.
The invention also discloses a server, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the steps of the user version upgrading method for the SaaS system according to any one of the above when executing the computer program.
The invention also discloses a computer readable storage medium storing a computer program which when executed by a processor implements the steps of the user version upgrade method for the SaaS system as described in any one of the above.
According to the user version upgrading method, the system and the storage medium for the SaaS system, the current version identity and the target version identity which is scheduled to be updated are obtained according to the version upgrading instruction, the first operation environment is built according to the target version identity, the test environment information of the target version is obtained in the version database according to the target version identity, the verification environment information of the target version is obtained in the version database after the user test passing instruction is received to build the second operation environment, and finally the production environment information of the target version is obtained in the version database after the user verification passing instruction is received to build the third operation environment, so that a user can upgrade the system gradually in a three-stage building mode, the user can stop updating at any time when a problem occurs, the stability and the reliability of the new version are ensured, and the risk possibly brought by deploying the new version in the production environment is reduced.
Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
fig. 1 is a flow chart of a user version upgrade method for a SaaS system according to an embodiment of the present invention.
Fig. 2 is a schematic flow chart of step S1 according to an embodiment of the invention.
Fig. 3 is a schematic flowchart of step S13 according to an embodiment of the present invention.
Fig. 4 is a block diagram illustrating a user version upgrade system for a SaaS system according to another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more clear, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. It will be apparent that the described embodiments are some, but not all, embodiments of the invention. All other embodiments, which can be made by a person skilled in the art without creative efforts, based on the described embodiments of the present invention fall within the protection scope of the present invention.
Unless defined otherwise, technical or scientific terms used herein should be given the ordinary meaning as understood by one of ordinary skill in the art to which this invention belongs. The terms "first," "second," and the like in the description and in the claims, are not used for any order, quantity, or importance, but are used for distinguishing between different elements. Likewise, the terms "a" or "an" and the like do not denote a limitation of quantity, but rather denote the presence of at least one.
At present, in the process of upgrading the version of the SaaS system, due to the instability of the new version, the problems of data disorder, data loss, compatibility and the like in the data transmission process, the abnormal upgrading condition often occurs, and the use physical examination of the user on the upgraded version is affected.
The embodiment provides a user version upgrading method for a SaaS system, which comprises the following steps as shown in figure 1.
Step S1, a current version identity and a target version identity which is scheduled to be updated are obtained according to a version upgrading instruction, and a first running environment is built according to the test environment information of the target version obtained from a version database by the target version identity, wherein the first running environment is used for testing new version functions.
Specifically, the first operating environment is a testing environment, and the new version of SaaS system is first deployed in the testing environment to perform detailed functional test, performance test, safety test and the like, so as to ensure that the functions and performances of the new version meet expectations. The real data can be not called in the test environment, the simulation data stored in advance is used for carrying out functional simulation, the configuration time and complexity of the system are reduced, and a user can interrupt the upgrading process at any time in the test environment.
As shown in fig. 2, the step S1 specifically includes the following steps.
Step S11, the current version identity and the target version identity of the plan update are obtained according to the version upgrading instruction.
In the present embodiment, this step S11 may specifically include the following.
Step S111, user ID included in the version upgrade instruction is obtained, and corresponding user current version identity is searched and obtained from a user management library according to the user ID, wherein the user management library is configured to store mapping relations between each user and each version of the system.
Step S112, the target version identity of the user plan update in the version upgrade instruction is obtained.
In this embodiment, sequential upgrade and cross-version upgrade are supported simultaneously, and when the user does not know the functions of each version to be upgraded and cannot determine whether to upgrade or upgrade the target version, an upgrade feedback interface can be generated to provide the user with the upgrade function of each version to be upgraded for the user to compare and select the target version suitable for upgrade, and the method can further include the following.
Step S101, judging whether the version upgrading instruction contains target version identity information or not, and if the version upgrading instruction does not contain the target version identity information, inquiring the version information to be updated in a version database according to the version upgrading instruction and the current version identity of the user.
Step S102, the update functions described in the update function configuration table in the version information to be updated and the related function modules are collected to form an update feedback interface, wherein the update feedback interface comprises the version options and the corresponding update function module information.
Step S103, the identity of the target version to be upgraded is obtained according to the selection of the user in the upgrading feedback interface.
Specifically, after the identity of the target version is confirmed, each function module newly added or updated to the target version to be upgraded can be pre-demonstrated through the function demonstration component, so that the user can experience each characteristic of the new function of the new version in advance, and when the demonstration function does not meet the user expectation, the user can cancel the upgrade or select other version upgrades, and the user satisfaction is improved.
Step S201, a functional demonstration component of a corresponding version is obtained from a version database according to the version update demonstration instruction and the target version identity.
Step S202, inquiring and acquiring each intermediate version update information and each corresponding function demonstration component between the current version and the target version in a version database, and forming a newly-added function configuration table and a function demonstration component set according to the update information of each intermediate version and the target version, wherein the newly-added function configuration table comprises the newly-added function information after the current version is updated to the target version.
Step S203, respectively calling the corresponding function demonstration components from the function demonstration component set according to the newly added function configuration table to carry out simulation presentation.
In this embodiment, the user may further select different configuration modes to improve the demonstration efficiency or accuracy, and according to the function to be demonstrated and the corresponding demonstration configuration options selected from the newly added function configuration table, the corresponding function demonstration components are centrally called from the function demonstration components to perform analog presentation, where the demonstration configuration options include a first demonstration configuration mode and a second demonstration configuration mode, the first demonstration configuration mode is configured to perform function analog demonstration according to the analog configuration data pre-stored in the function demonstration components, and the second demonstration configuration mode is configured to acquire the corresponding data from the current version of the running system according to the configuration parameter table pre-stored in the function demonstration components to perform function analog demonstration as the configuration data for demonstration.
In this embodiment, when the user selects the second configuration option to obtain the current system data to improve the demonstration accuracy, the user input function may be added to supplement the data that cannot be obtained, such as the permission data, the newly added module data, etc., specifically, the second demonstration configuration mode is further configured to collect and obtain the corresponding data from the current version operation system according to the pre-stored configuration parameter table, if some parameters cannot be obtained, an information input interface is generated for the user to input the corresponding missing parameters, and the obtained missing parameters are added to the data collected from the current system as demonstration configuration data to perform the function simulation demonstration.
In this embodiment, the demonstration configuration options may further include a third demonstration configuration mode, and step S203 specifically further includes: and acquiring the demonstration configuration options, and acquiring corresponding data from the current version running system according to a configuration parameter table prestored in the function demonstration component if the demonstration configuration options are in a third demonstration configuration mode.
Recording acquired data into a configuration parameter table, acquiring a missing parameter name which is not acquired yet, acquiring corresponding data from prestored simulation configuration data according to the missing parameter name, and supplementing the corresponding data into the configuration parameter table to form configuration data for demonstration; and sending the configuration data for demonstration to a function demonstration component for simulation presentation.
In this embodiment, for some associated function modules, a comparison function may be further added to allow the user to select an optimal target version, which is specifically as follows:
Step S204, when the function demonstration component is simulated, if the function demonstration component has a comparison demonstration identification, the reference identification of the current function demonstration component is obtained, the comparison function module with the same reference identification in the current version operation system is queried according to the module identification, and the comparison function module is triggered to be started after the current user operation interface information is stored.
In this embodiment, the step S204 may specifically include the following steps.
Step S2041, when the function demonstration component is simulated, if the function demonstration component has a comparison demonstration identification, acquiring a reference identification of the current function demonstration component, and inquiring a comparison function module with the same reference identification in the current version operation system according to the module identification.
Step S2042, save the user operation interface information and operation record in the current version running system, start the comparison function module after the saving is completed, and send the same initial input data as the function demonstration component to the comparison function module.
Step S2043, after receiving the user demonstration closing instruction or the demonstration completion information sent by the function demonstration component, closing the function demonstration component and restoring the running system of the current version to the saved original user operation interface.
In the embodiment, for carrying out function demonstration and comparison demonstration of the association module with the current version, the user is helped to intuitively know the information of the updated content, so that the user can conveniently select the optimal target version.
Step S12, testing environment information of the target version is obtained from the version database according to the identity of the target version to build a first running environment and optional simulation configuration information.
Specifically, the test environment information of different versions is pre-stored in the version database, and corresponds to each version one by one, the optional simulation configuration information is used for parameter configuration of a subsequent first operation environment, and the construction of the optional simulation configuration information can specifically include the following.
Step S301, obtaining version information corresponding to a target version from a version database according to the identity of the target version, and collecting function module information related to a function configuration table in the version information to generate a function module list.
Step S302, obtaining simulation data information corresponding to each functional module of the target version from a simulation configuration database according to the functional module list to generate optional simulation configuration information, wherein the simulation configuration database contains simulation data information pre-stored by each functional module.
The configuration information of the target version is generated by selecting the pre-stored configuration data, so that the first running environment can use the configuration information to perform direct test, the test efficiency is improved, and the time of a user is saved.
Step S13, carrying out operation parameter configuration according to parameter configuration options selected by a user, wherein the parameter configuration options comprise a first configuration option and a second configuration option, if the user adopts the first configuration option, the selectable simulation configuration information is all input into a first operation environment to carry out parameter configuration to form a test system of a target version, if the user adopts the second configuration option, user configuration data of the user under the current version are collected, the collected user configuration data are replaced by corresponding information in the selectable simulation configuration information and then are input into the first operation environment to carry out parameter configuration to form the test system of the target version, and the user configuration data comprise but are not limited to user role and authority setting information, data type and constraint information, business logic and rule information of the current version.
The embodiment provides two data configuration modes, and a user can freely select the first configuration option or the second configuration option according to requirements. Under the first configuration option, the system directly calls simulation data information of each functional module in the prestored optional simulation configuration information to carry out parameter configuration so as to reduce the system configuration time and the test time to the maximum extent. Under the second configuration option, the system performs parameter configuration by collecting real-time data of the current system of the user, and although a certain level of cache time is needed, accurate experience can be brought to the user, so that the testing process is more practical.
As shown in fig. 3, the step S13 specifically includes the following steps.
Step S131, if the user adopts the second configuration option, the user configuration data of the user under the current version is collected, and the obtained user configuration data is converted into the configuration data of the target version according to the configuration information corresponding table of the target version and the current version.
Specifically, when the user selects the second configuration option, the system provides a more accurate test experience by collecting the user' S data, wherein step S131 further includes the following steps.
Step S1311, obtaining version information of the corresponding version in the version data according to the target version and the current version identity information, and generating a first configuration information corresponding table by using function module information designed on the function configuration table in the version information of the corresponding version of the liniment.
Step S1312, the conversion relation of each type of data is obtained from the conversion database according to the data types and the corresponding relation of each function module in the first configuration information corresponding table to generate a second configuration information corresponding table.
Step S1313, collecting the user configuration data under the current version of the user to generate a configuration data collection information table, where the collection information table includes names of each functional module corresponding to the current version and corresponding data.
Step S1314, obtaining the target version configuration data of the user configuration data conversion according to the second configuration information corresponding table and the configuration data acquisition information table.
Step S132, comparing the converted configuration data with optional simulation configuration information to obtain missing configuration data, and sending the missing configuration data type and optional corresponding simulation data to a user.
Specifically, when the data is the data of the function module newly added by the target version relative to the current version, the system cannot directly acquire the data and convert the data, and at this time, the data types of all the data in the function module can be acquired and configured through the prestored analog data.
In this embodiment, the data of the newly added function module may also be filled in by a user input manner, and step S132 further includes: and comparing the converted configuration data with optional simulation configuration information to obtain missing configuration data and generating an information input interface for a user to input corresponding missing parameters.
And step S133, supplementing the missing configuration data newly supplemented by the user or the selected corresponding simulation data into the converted configuration data to form final target version configuration data, and inputting the final target version configuration data into the first operation environment for parameter configuration to form a target version test system.
In this embodiment, the configuration data includes system option data configured to be available only through collection user input in the configuration option and auxiliary configuration data configured to be available through collection user input in the configuration option and simulation data of an auxiliary configuration corresponding to the collected system option data in the selectable simulation configuration information of the target version queried from the version database.
Specifically, the generated optional simulation configuration information or user configuration data collected by the system does not include certain authority data or certain personalized data affecting the normal operation of the system, so as to avoid the override of the test function by a user to view the limit information or the excessive distinction of each functional module of the system experience when the test is used normally, and the accuracy of the test is further improved by dividing the authority data or the personalized data affecting the normal operation of the system into system option data.
In this embodiment, for some conventional default data, such as the default unchanged data of the user, such as font setting, the mode of the auxiliary configuration data may be classified, so that the pre-stored analog configuration data may be directly called or input by means of user input when the function module data is not acquired, so as to reduce the complexity of the second configuration option.
In this embodiment, before the system upgrade, the user may pre-select the configuration mode of each type of data in the target version, and add or delete the system option data and the auxiliary configuration data by itself, and then further includes: generating a configuration module interaction interface according to the configuration option updating instruction, wherein the configuration module interaction interface comprises a deletion/new system option data option and a deletion/new auxiliary configuration data option, and the option to be selected in the deletion/new system option data option and the deletion/new auxiliary configuration data option comprises all function module options in the target version.
In this embodiment, a third configuration option is further provided, so that each data configuration mode is considered to ensure the test efficiency and accuracy at the same time to the maximum extent, and the step S13 further includes:
The parameter configuration options further comprise third configuration options, and if the user adopts the third configuration options, the difference quantity of the configuration data of the target version and the current version is obtained.
If the difference quantity of the configuration data is lower than a first threshold value, directly generating a parameter configuration interface for acquiring user input data; if the user configuration data is larger than the first threshold, the user configuration data of the user under the current version is directly collected, the obtained user configuration data is converted into the configuration data of the target version according to the configuration information corresponding table of the target version and the current version, and candidate simulation configuration data are provided for the user to select for the configuration data of the target version which is still missing after conversion.
Specifically, when the system detects that the configuration data of the target version and the current version are lower than the preset limit value, the user can directly input the configuration data of the difference by taking the configuration data difference of the different versions as a judgment standard, so that the test accuracy is further improved under the condition that the test complexity and the test time are not affected. When the system detects that the target version data and the current configuration data are higher than the preset limit value, the data are input in a mode of combining data acquisition and pre-storing analog data configuration, and meanwhile testing efficiency and accuracy are guaranteed.
And step S2, after receiving a user test passing instruction, acquiring verification environment information of the target version from the version database to build a second running environment, wherein the second running environment is used for verifying the new version function.
Specifically, the second operation environment is a verification environment, when the system receives a first operation environment test passing instruction sent by a user, the system enters the verification environment to simulate the interaction and scene of a real user, and the user confirms that the verification is further performed on the new version function. The user can interrupt the upgrading process at any time in the process.
And step S3, after receiving a user verification passing instruction, acquiring production environment information of the target version from the version database to build a third operation environment, wherein the third operation environment is used for carrying out final production and use on the new version.
Specifically, the third operation environment is a production environment, when the system receives a user verification passing instruction, namely, the new version also passes the test in the verification environment, the system enters a final production environment building stage, and formally provides services for all users.
The embodiment also designs a database table metadata checker for checking the database table metadata under the same version, so as to avoid serious problems of system failure and table field mapping error caused by inconsistent use of a plurality of client database table metadata of the same version in the version upgrading process
Step S4, checking the library table metadata of a plurality of tenants mapped by the system version, selecting one tenant data source as a reference data source, checking the library table metadata in other tenant data sources with the reference data source in sequence, wherein the checking content comprises but is not limited to the number of tables, the sequence of the table characters, the number of the table characters and the data type, and adjusting and modifying that the checking is not passed.
Specifically, the step S4 further includes the following steps.
Step S41, acquiring a plurality of pieces of tenant information for selecting and using the upgraded system version, and confirming the corresponding tenant database metadata storage position according to the tenant information.
Step S42, selecting the first data source as a reference data source for comparison and verification, recording when the fact that the table numbers of the first data source and the second data source are inconsistent is verified, and if the fact that the table numbers of the first data source, the third data source and the fourth data source are consistent is verified, considering that errors exist in the table numbers of the second data source; and if the table numbers of the first data source and the third data source are not consistent or the table numbers of the first data source and the fourth data source are not consistent, performing repeated verification again by taking the second data source as a reference data source until the table number with the correct rate larger than the set threshold value is confirmed as a final reference data source, and marking the data source with the different table number from the final reference data source as not passing the verification.
After the version is updated, the embodiment also provides a version rollback function, which is used for performing version rollback when the user is not satisfied with the target version after the version is updated, and further comprises the following steps.
Step S401, searching a corresponding problem function module in a system function table according to the recorded problem data fed back in the use of the current version, and acquiring an updated function configuration table of each historical version in the version update record.
The step S401 may specifically include:
Step S4011, inquiring the currently running system version and each history version information in the version database according to the rollback request, and collecting the update functions described on the update function configuration table in each history version information and the related function modules to form a version update record database and a rollback feedback interface.
Step S4012, the version update record database is searched according to the problem description of the user on the rollback feedback interface to obtain the corresponding problem function module, the function update description of the problem function module is fed back to the user, and the problem function module is confirmed according to the user feedback.
The rollback feedback interface comprises a deletion/modification configuration option group, wherein the deletion/modification configuration option group comprises a question function module option which can be selected by a user, and the question function module option comprises newly added or adjusted function module names related to each history version update; the rollback feedback interface is configured to take an option selected by a user as a question function module.
In this embodiment, the rollback feedback interface further includes a reserved configuration update option group, where the reserved configuration update option group includes reserved function module options that can be selected by the user and can be reserved in the rollback target version, and the reserved function module options include function module names that are added or adjusted in relation to each history version update.
The rollback feedback interface also comprises a first-stage problem acquisition interface and a second-stage function update interface. And searching a version update record database according to the problem description of the user on a first-stage problem acquisition interface of the rollback feedback interface to obtain update description contents in each version related to the update of the problem function module, and respectively forming a plurality of update description options by taking the version as a unit to form a second-stage function update interface by the update description of the problem function module in each version. And updating the description content retrieval version update record database according to the problem function module selected by the user on the second-level function update interface to confirm the corresponding first association history version.
Step S402, searching for an association history version related to the update or modification of the problem function module in each update function configuration table according to the problem function module, and recommending a previous version of the association history version to a user as a rollback target version.
The step S402 further includes:
Step S4021, judging whether the option information of the reserved functional module is acquired, if not, searching a first association history version related to the update or modification of the problem functional module in each update function configuration table according to the problem functional module, and recommending the previous version of the first association history version to a user as a rollback target version.
Step S4022, if the option information of the reserved function module is collected, searching a second association history version related to the new or modified reserved function module in each updated function configuration table according to the option of the reserved function module, where the first association history version is higher than the second association history version, obtaining an intermediate version set between the first association history version and the second association history version, and recommending the earliest version in the intermediate version set to the user as a rollback target version.
The step S402 further includes: if the first association history version is not higher than the second association history version or no intermediate version exists between the first association history version and the second association history version, information that the function module cannot be maintained is sent to the user, and if a rollback continuing instruction is received, a previous version of the first association history version is recommended to the user as a rollback target version. If the related history version related to the update or modification of the problem function module is searched in each updated function configuration table according to the problem function module and comprises a plurality of related history versions, the update description content aiming at the problem function module in each related history version is respectively fed back to a user by forming a version confirmation interface consisting of a plurality of update description content options in version units; and taking the version of the update description content of the problem function module selected by the user on the version confirmation interface as a first association history version.
Step S403, after obtaining the rollback version confirmation instruction, rollback the current user version to the rollback target version, and storing redundant tables and data after the current user version is rollback to the target version. In the process of rolling back the current user version to the rolling back target version, the fields and the corresponding values which are more than the rolling back target version in the table of the current user version are saved, and the default value is set when the new field is declared, the existing fields of the current user version are kept from being changed in data type, and the value range for saving the same data type is not reduced.
According to the user version upgrading method for the SaaS system, the current version identity and the target version identity which is scheduled to be updated are obtained according to the version upgrading instruction, the first operation environment is built by obtaining the test environment information of the target version in the version database according to the target version identity, further after the user test passing instruction is received, the verification environment information of the target version is obtained in the version database to build the second operation environment, finally after the user verification passing instruction is received, the production environment information of the target version is obtained in the version database to build the third operation environment, so that the user can upgrade the system gradually in a three-stage building mode, the user can stop updating at any time when a problem occurs, the stability and the reliability of the new version are ensured, and the risk possibly brought by directly deploying the new version in the production environment is reduced.
In another embodiment, as shown in fig. 4, a user version upgrade system for a SaaS system is also disclosed, including a first building module 1, a second building module 2, and a third building module 3. The first building module is used for obtaining a current version identity and a target version identity of a plan update according to a version upgrading instruction, and building a first running environment according to the target version identity and test environment information of a target version in a version database, wherein the first running environment is used for testing new version functions. The second building module is used for obtaining verification environment information of the target version from the version database to build a second running environment after receiving the user test passing instruction, and the second running environment is used for verifying the new version function. The third building module is used for obtaining the production environment information of the target version from the version database to build a third operation environment after receiving the user verification passing instruction, and the third operation environment is used for carrying out final production and use on the new version.
In this embodiment, the first building module specifically further includes an identity confirmation module, an environment building module, and a parameter configuration module. The identity confirmation module is used for acquiring the current version identity and the target version identity of the plan update according to the version upgrading instruction. The environment construction module is used for acquiring test environment information of the target version from the version database according to the target version identity to construct a first running environment and optional simulation configuration information. The parameter configuration module is used for carrying out operation parameter configuration according to parameter configuration options selected by a user, the parameter configuration options comprise a first configuration option and a second configuration option, if the user adopts the first configuration option, the selectable simulation configuration information is all input into a first operation environment to carry out parameter configuration to form a test system of a target version, if the user adopts the second configuration option, user configuration data of the user under the current version are collected, the collected user configuration data are replaced by corresponding information in the selectable simulation configuration information and then are input into the first operation environment to carry out parameter configuration to form the test system of the target version, and the user configuration data comprise but are not limited to user role and authority setting information, data type and constraint information, business logic and rule information of the current version.
In this embodiment, the parameter configuration module further includes a data conversion module, a data supplementing module, and a data input module. The data conversion module is used for acquiring user configuration data of the user under the current version if the user adopts the second configuration option, and converting the acquired user configuration data into configuration data of the target version according to the configuration information corresponding table of the target version and the current version. The data supplementing module is used for comparing the converted configuration data with the optional simulation configuration information to obtain missing configuration data and sending the missing configuration data type and the optional corresponding simulation data to a user. The data input module is used for supplementing the missing configuration data newly supplemented by the user or the selected corresponding simulation data into the converted configuration data to form final target version configuration data, and inputting the final target version configuration data into the first operation environment to perform parameter configuration to form a target version test system.
It should be noted that, in the present description, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different manner from other embodiments, and similar portions of each embodiment are referred to each other. For the user version upgrade system for the SaaS system disclosed in the embodiment, since it corresponds to the user version upgrade method for the SaaS system disclosed in the embodiment, the description is relatively simple, and the relevant points are referred to in the description of the foregoing method section.
In further embodiments, there is also provided a server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the user version upgrade method for SaaS systems as described in the above embodiments when the computer program is executed. Wherein the server may include, but is not limited to, a processor, a memory. It will be appreciated by those skilled in the art that the schematic is merely an example of a server and is not limiting of the server, and may include more or fewer components than shown, or certain components may be combined, or different components.
The user version upgrade system for SaaS systems may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a stand alone product. Based on such understanding, the present invention may implement all or part of the above-described embodiment of the method, or may be implemented by a computer program for instructing relevant hardware, where the computer program may be stored in a computer readable storage medium, and the computer program, when executed by a processor, may implement the steps of each of the above-described embodiments of the user version upgrade method for SaaS systems. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory, a random access memory, an electrical carrier wave signal, a telecommunication signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.
In summary, the foregoing description is only of the preferred embodiments of the present invention, and all equivalent changes and modifications made in accordance with the claims should be construed to fall within the scope of the invention.
Claims (10)
1. The user version upgrading method for the SaaS system is characterized by comprising the following steps of:
Acquiring a current version identity and a target version identity which is scheduled to be updated according to a version upgrading instruction, and acquiring test environment information of a target version in a version database according to the target version identity to build a first operation environment, wherein the first operation environment is used for testing new version functions;
After receiving a user test passing instruction, acquiring verification environment information of a target version from a version database to build a second running environment, wherein the second running environment is used for verifying a new version function;
after receiving the user verification passing instruction, acquiring production environment information of the target version from the version database to build a third operation environment, wherein the third operation environment is used for carrying out final production and use on the new version.
2. The method for upgrading a user version of a SaaS system according to claim 1, wherein the step of obtaining a current version identity and a target version identity for planning updating according to a version upgrading instruction, and obtaining test environment information of a target version in a version database according to the target version identity, and building a first running environment comprises the following steps:
Acquiring a current version identity and a target version identity scheduled to be updated according to the version upgrading instruction;
acquiring test environment information of a target version from a version database according to the identity of the target version to build a first running environment and optional simulation configuration information;
Operating parameter configuration is carried out according to parameter configuration options selected by a user, wherein the parameter configuration options comprise a first configuration option and a second configuration option, if the user adopts the first configuration option, the selectable simulation configuration information is all input into a first operating environment for parameter configuration to form a test system of a target version, if the user adopts the second configuration option, user configuration data of the user under the current version are collected, the collected user configuration data are replaced by corresponding information in the selectable simulation configuration information and then are input into the first operating environment for parameter configuration to form the test system of the target version, and the user configuration data comprise but are not limited to user role and authority setting information, data type and constraint information, business logic and rule information of the current version.
3. The method for upgrading a user version of a SaaS system according to claim 2, wherein if the user adopts the second configuration option, collecting user configuration data of the user under the current version, and inputting the collected user configuration data into the first operation environment for parameter configuration to form a test system of a target version after replacing corresponding information in the selectable simulation configuration information, wherein the method specifically comprises the following steps:
if the user adopts the second configuration option, acquiring user configuration data of the user under the current version, and converting the acquired user configuration data into configuration data of the target version according to a configuration information corresponding table of the target version and the current version;
comparing the converted configuration data with optional simulation configuration information to obtain missing configuration data, and sending the missing configuration data type and optional corresponding simulation data like a user;
And supplementing the missing configuration data newly supplemented by the user or the selected corresponding simulation data into the converted configuration data to form final target version configuration data, and inputting the final target version configuration data into the first operation environment to perform parameter configuration to form a target version test system.
4. The user version upgrade method for SaaS system according to claim 3, further comprising:
The parameter configuration options further comprise third configuration options, and if the user adopts the third configuration options, the difference quantity of the configuration data of the target version and the current version is obtained;
If the difference quantity of the configuration data is lower than a first threshold value, directly generating a parameter configuration interface for acquiring user input data; if the user configuration data is larger than the first threshold, the user configuration data of the user under the current version is directly collected, the obtained user configuration data is converted into the configuration data of the target version according to the configuration information corresponding table of the target version and the current version, and candidate simulation configuration data are provided for the user to select for the configuration data of the target version which is still missing after conversion.
5. The user version upgrade method for SaaS system according to claim 4, wherein:
The configuration data includes system option data configured to be available only through acquisition user input in the configuration options and auxiliary configuration data configured to be available through acquisition user input in the configuration options and simulation data of an auxiliary configuration corresponding to the acquired system option data in the selectable simulation configuration information of the target version from the version database.
6. A user version upgrade system for a SaaS system, comprising:
the first building module is used for obtaining a current version identity and a target version identity which is scheduled to be updated according to the version upgrading instruction, and building a first running environment according to the test environment information of the target version obtained from the version database by the target version identity, wherein the first running environment is used for testing the new version function;
The second building module is used for obtaining verification environment information of the target version from the version database to build a second running environment after receiving a user test passing instruction, wherein the second running environment is used for verifying the new version function;
The third building module is used for obtaining the production environment information of the target version from the version database to build a third operation environment after receiving the user verification passing instruction, and the third operation environment is used for carrying out final production and use on the new version.
7. The user version upgrade system for SaaS system of claim 6, wherein the first build module specifically comprises:
the identity confirmation module is used for acquiring the current version identity and the target version identity of the plan update according to the version upgrading instruction;
the environment construction module is used for acquiring test environment information of a target version from the version database according to the identity of the target version to construct a first running environment and optional simulation configuration information;
The parameter configuration module is used for carrying out operation parameter configuration according to parameter configuration options selected by a user, the parameter configuration options comprise a first configuration option and a second configuration option, if the user adopts the first configuration option, the selectable simulation configuration information is all input into a first operation environment to carry out parameter configuration to form a test system of a target version, if the user adopts the second configuration option, user configuration data of the user under the current version are collected, the collected user configuration data are replaced by corresponding information in the selectable simulation configuration information and then are input into the first operation environment to carry out parameter configuration to form the test system of the target version, and the user configuration data comprise but are not limited to user role and authority setting information, data type and constraint information, business logic and rule information of the current version.
8. The user version upgrade system for SaaS system of claim 7, wherein the parameter configuration module further comprises:
the data conversion module is used for acquiring user configuration data of the user under the current version if the user adopts the second configuration option, and converting the acquired user configuration data into configuration data of the target version according to the configuration information corresponding table of the target version and the current version;
The data supplementing module is used for comparing the converted configuration data with the optional simulation configuration information to obtain missing configuration data and sending the missing configuration data type and the optional corresponding simulation data to a user;
The data input module is used for supplementing the missing configuration data newly supplemented by the user or the selected corresponding simulation data into the converted configuration data to form final target version configuration data, and inputting the final target version configuration data into the first operation environment to perform parameter configuration to form a target version test system.
9. A server comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized by: the processor, when executing the computer program, implements the steps of the method according to any one of claims 1-5.
10. A computer-readable storage medium storing a computer program, characterized in that: the computer program implementing the steps of the method according to any of claims 1-5 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410254666.3A CN118349245A (en) | 2024-03-06 | 2024-03-06 | User version upgrading method, system and storage medium for SaaS system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410254666.3A CN118349245A (en) | 2024-03-06 | 2024-03-06 | User version upgrading method, system and storage medium for SaaS system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118349245A true CN118349245A (en) | 2024-07-16 |
Family
ID=91820048
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410254666.3A Pending CN118349245A (en) | 2024-03-06 | 2024-03-06 | User version upgrading method, system and storage medium for SaaS system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118349245A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119065695A (en) * | 2024-11-06 | 2024-12-03 | 蒲惠智造科技股份有限公司 | Cross-version upgrade method and system for examination system of SaaS software |
-
2024
- 2024-03-06 CN CN202410254666.3A patent/CN118349245A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119065695A (en) * | 2024-11-06 | 2024-12-03 | 蒲惠智造科技股份有限公司 | Cross-version upgrade method and system for examination system of SaaS software |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9075633B2 (en) | Configuration of life cycle management for configuration files for an application | |
| CN112699151B (en) | Data processing method, device, equipment and medium | |
| US8214508B2 (en) | Support apparatus, program, information processing system and support method | |
| CN106874281B (en) | Method and device for realizing database read-write separation | |
| CN113420026B (en) | Database table structure changing method, device, equipment and storage medium | |
| CN111158674A (en) | Component management method, system, device and storage medium | |
| CN112559641B (en) | Pull chain table processing method and device, readable storage medium and electronic equipment | |
| US20200409669A1 (en) | Technique for transforming a standard messaging component to a customized component | |
| CN111737227A (en) | Data modification method and system | |
| CN115712623B (en) | Batch data fault-tolerant collection method based on captured metadata change | |
| CN106406999A (en) | A computing system and a method for controlling thereof | |
| CN118349245A (en) | User version upgrading method, system and storage medium for SaaS system | |
| US7882063B2 (en) | System for synchronization of configuration values between a data base and its input utility | |
| CN112328295B (en) | Software updating method and device | |
| CN117971278A (en) | Multi-version management method, server and storage medium of multi-tenant SaaS system | |
| CN113836181A (en) | Data query method and device combining RPA and AI, electronic equipment and storage medium | |
| CN114089979A (en) | Persistent layer code updating method, system, terminal device and computer storage medium | |
| US20080148220A1 (en) | System infrastructure structure formulation supporting system and supporting method | |
| CN117271570A (en) | Data storage method, device, medium and computing equipment | |
| CN117827252B (en) | Function demonstration method, server and storage medium for system update | |
| CN115309732A (en) | Method, device and equipment for shunting based on configuration request and storage medium | |
| CN112817931B (en) | Incremental version file generation method and device | |
| CN116739397B (en) | Dynamic management method for new energy indexes | |
| CN117971279A (en) | Rollback method and device of system version and server | |
| CN106681914B (en) | Television picture quality debugging method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |