A method for implementing dynamic web risk reporting

Abstract

The application discloses a kind of dynamic web risk report implementation methods, comprising the following steps: S1: through system management background configuration web report version information;S2: compile deployment web;S3: generate evaluation report;S4: web report application.The beneficial effects of the application are: relative to pdf report and static html report, dynamic web is stored by data snapshot, and the same version of report is used front end template and corresponding resource file, which can save server storage resources, and through dynamic data request and dynamic assembly, it is convenient to preview.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of enterprise consulting services, and particularly relates to a dynamic web risk report implementation method. BACKGROUND

[0002] Enterprise risk assessment belongs to the field of enterprise consulting services. Enterprises will encounter various risks in daily production and operation, such as strategic risks, financial crises, asset risks and market risks. For various risks of enterprises, professional assessment agencies have scientific assessment methods to obtain objective and effective assessment results, so as to help enterprise operators improve the ability to manage and identify target enterprise risks, and further improve the enterprise operation level.

[0003] The enterprise risk assessment report is a direct and effective way for the assessment agency to output the assessment results. Through the enterprise risk assessment report, important information such as the assessment level, operation situation and financial information of the enterprise can be directly observed.

[0004] The enterprise risk assessment report currently output by market agencies is mainly in the form of PDF and static web report. There are also few reports in the form of word, which are mainly output by some non-professional agencies. The main difference between the word report and the PDF report is that the PDF report is not easy to be modified, so the PDF report is widely favored and applied by professional assessment agencies. However, the PDF report also has some problems, such as: 1. When the report content is large, the loading time of the report is too long when the report is opened through the browser, which affects the user experience; 2. The generation of the PDF report takes a long time, which is not convenient for the preview of the background personnel. SUMMARY

[0005] The present application aims to overcome the shortcomings of the prior art and provide a dynamic web risk report implementation method.

[0006] The present application achieves the above-mentioned purpose by the following technical solution: a dynamic web risk report implementation method, comprising the following steps:

[0007] S1: configuring web report version information through a system management background;

[0008] S2: compiling and deploying the web;

[0009] S3: generating an assessment report;

[0010] S4: applying the web report.

[0011] Preferably, in step S1, the system management background generates version information through a snowflake algorithm.

[0012] Preferably, in step S2, the following steps are further included:

[0013] S21: The project reporter pulls the project report web code and compiles the web project to obtain a report version;

[0014] S22: The project reporter sends a request to the version manager, the version manager parses parameters according to the request, if it is a new version, the version information of the state to be published is queried, and the result is fed back to the project reporter, if it is not a new version, the specified version number is queried and the version information of the state to be published is queried, and the result is fed back to the project reporter;

[0015] S23: The project reporter judges whether it is a new version, if it is not a new version, the folder of the specified version number is renamed through the file server, and a new folder is created and renamed with the specified version number, if it is a new version, a new folder is directly created and renamed with the specified version number;

[0016] S24: The compiled project file is copied into the specified folder, and the publishing state is synchronized with the version manager.

[0017] Preferably, step S3 further comprises the following steps:

[0018] S31: The report center obtains data and assembles report data, and queries the latest published report version number;

[0019] S32: The report center sends a request to the version manager, the version manager queries whether the published state is the latest version according to the request, if yes, feeds back to the report center, and the report center queries the latest published report version number according to the feedback;

[0020] S33: The snapshot data calls the blockchain service to be chained, and the persistent mongo service;

[0021] S34: The web report is generated and published.

[0022] Preferably, step S4 further comprises the following steps:

[0023] S41: Whether to preview the evaluation report is determined through the web browser, if preview is selected, a request is sent to the version controller, the version controller queries the latest published version information according to the request, and feeds back to the web browser, the web browser obtains the version number of the latest version report according to the feedback, if preview is not selected, a request is sent to the report center, the report center queries the version number corresponding to the report according to the report ID, and feeds back to the web browser, the web browser obtains the corresponding report version number according to the feedback;

[0024] S42: The file address of the web report is spliced, and the resource file is requested and loaded;

[0025] S43: Request page data, and then render page data.

[0026] Preferably, step S43 further comprises the following steps:

[0027] S43.1: The web browser sends a request to the report center, if the report center selects preview, then call the evaluation center, query evaluation data, process and assemble the data, and feedback to the web browser, if the report center does not select preview, then query the database to obtain snapshot data, and end running.

[0028] The present application has the following advantages: compared with pdf reports and static html reports, the dynamic web stores data by taking snapshots, deploys report pages in the cloud by version, and uses a set of front-end templates and corresponding resource files for reports of the same version, thereby saving server storage resources, and through dynamic data request and dynamic assembly, preview is facilitated. BRIEF DESCRIPTION OF DRAWINGS

[0029] Figure 1 Structure diagram of dynamic web report implementation process;

[0030] Figure 2 Structure diagram of compiled and deployed web process;

[0031] Figure 3 Structure diagram of generated evaluation report process;

[0032] Figure 4 Structure diagram of web report application. DETAILED DESCRIPTION

[0033] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below in connection with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. The components of the embodiments of the present application described and shown in the drawings can be arranged and designed in various different configurations.

[0034] Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the present application.

[0035] It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.

[0036] It should be noted that similar reference numerals and letters refer to like items throughout the accompanying drawings, and once an item is defined in one drawing, it is not necessary to further define and explain it in subsequent drawings.

[0037] In the description of the present application, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer" and the like indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, or the orientation or positional relationship commonly understood by those skilled in the art, and are only for the convenience of describing the present application and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as a limitation on the present application. In addition, the terms "first", "second" and the like are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0038] In the description of the present application, it should be noted that unless otherwise explicitly specified and limited, the terms "arrangement", "installation", "connection", "connection" should be broadly understood, for example, it can be fixedly connected, or it can be detachably connected, or integrally connected; it can be mechanically connected, or it can be electrically connected; it can be directly connected, or it can be indirectly connected through an intermediate medium; it can be the communication inside two elements. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.

[0039] In this embodiment, as shown in Figure 1 A method for implementing a dynamic web risk report includes the following steps:

[0040] S1: Configure web report version information through system management background;

[0041] S2: Compile and deploy web;

[0042] S3: Generate evaluation report;

[0043] S4: Web report application. Compared with pdf report and static html report, dynamic web stores data by snapshot, deploys report page in the cloud by version, and uses a set of front-end templates and corresponding resource files for reports of the same version, which can save server storage resources, and through dynamic data request and dynamic assembly, preview is facilitated.

[0044] Further, in step S1, the system management background generates version information through the snowflake algorithm. Specifically, the system management background generates version information through the snowflake algorithm can ensure system global uniqueness, thereby saving server storage resources. The snowflake algorithm is an existing algorithm and is not improved here, and thus will not be described again.

[0045] Still further, as shown in Figure 2 , in step S2, the following steps are further included:

[0046] S21: Pull the project report web code through the project publisher and compile the web project to obtain the report version;

[0047] S22: The project publisher sends a request to the version manager, the version manager parses the parameters according to the request, if it is a new version, queries the version information whose state is to be published, and feeds back the result to the project publisher, if it is not a new version, queries the specified version number and queries the version information whose state is to be published successfully, and feeds back the result to the project publisher;

[0048] S23: The project publisher judges whether it is a new version, if it is not a new version, the folder with the specified version number is renamed through the file server, a new folder is created, and the specified version number is renamed, if it is a new version, a new folder is directly created, and the specified version number is renamed;

[0049] S24: Copy the compiled project file into the specified folder, and synchronize the publishing state with the version manager.

[0050] In this embodiment, as shown in Figure 3 , in step S3, the following steps are further included:

[0051] S31: Obtain data through the report center and assemble report data, and query the latest published report version number;

[0052] S32: The report center sends a request to the version manager, the version manager queries whether the published state is the latest version according to the request, if yes, feeds back to the report center, and the report center queries the latest published report version number according to the feedback;

[0053] S33: Snapshot data calls the blockchain service to be chained and persists the mongo service;

[0054] S34: Generate a web report and publish it.

[0055] Further, as shown in Figure 4 , in step S4, the following steps are further included:

[0056] S41: Determine whether to preview the evaluation report via the web browser. If preview is selected, a request is sent to the version controller. The version controller queries the information of the most recently successfully released version based on the request and sends it back to the web browser. The web browser obtains the version number of the latest version report based on the feedback. If no preview is selected, a request is sent to the report center. The report center queries the version number corresponding to the report by the report ID based on the request and sends it back to the web browser. The web browser obtains the corresponding report version number based on the feedback.

[0057] S42: Concatenate the file address of the web report, request the resource file, and load it;

[0058] S43: Request page data and then render the page data. Further, step S43 includes the following steps: S43.1: The web browser sends a request to the reporting center. If the reporting center selects preview, it calls the evaluation center, queries the evaluation data, processes and assembles the data, and then sends it back to the web browser. If the reporting center does not select preview, it queries the database to obtain snapshot data and terminates the process.

[0059] Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for implementing dynamic web risk reporting, characterized in that: Includes the following steps: S1: Configure web report version information through the system management backend; S2: Compile and deploy web applications; S3: Generate an evaluation report; S4: Web reporting application; Step S2 further includes the following steps: S21: Pull the project report web code through the project publisher, compile the web project, and obtain the report version; S22: The project publisher sends a request to the version manager. The version manager parses the parameters according to the request. If it is a new version, it queries the version information with the status of pending release and sends the result back to the project publisher. If it is not a new version, it queries the specified version number and the version information with the status of successful release, and then sends the result back to the project publisher. S23: The project publisher determines whether it is a new version. If it is not a new version, it renames the folder with the specified version number through the file server, then creates a new folder and renames it with the specified version number. If it is a new version, it directly creates a new folder and renames it with the specified version number. S24: Copy the compiled project files to the specified folder and synchronize the release status with the version manager; Step S3 further includes the following steps: S31: Obtain data from the report center and assemble report data, then query the latest released report version number; S32: The report center sends a request to the version manager. The version manager queries whether the published status is the latest version based on the request. If so, it sends feedback to the report center. The report center queries the latest published report version number based on the feedback. S33: Snapshot data is uploaded to the blockchain service and persisted to the MongoDB service; S34: Generate a web report and publish it; Step S4 also includes the following steps: S41: Determine whether to preview the evaluation report via the web browser. If preview is selected, a request is sent to the version controller. The version controller queries the information of the most recently successfully released version based on the request and sends it back to the web browser. The web browser obtains the version number of the latest version report based on the feedback. If no preview is selected, a request is sent to the report center. The report center queries the version number corresponding to the report by the report ID based on the request and sends it back to the web browser. The web browser obtains the corresponding report version number based on the feedback. S42: Concatenate the file address of the web report, request the resource file, and load it; S43: Request page data, then render the page data.

2. The method for implementing a dynamic web risk report according to claim 1, characterized in that: In step S1, the system management backend generates version information using the snowflake algorithm.

3. The method for implementing a dynamic web risk report according to claim 2, characterized in that: Step S43 further includes the following steps: S43.1: The web browser sends a request to the report center. If the report center selects preview, it calls the evaluation center, queries the evaluation data, processes and assembles the data, and then feeds it back to the web browser. If the report center does not select preview, it queries the database to obtain snapshot data and ends the process.

Images