Report processing method and device, computer equipment and storage medium

Abstract

The invention provides a report processing method and device, computer equipment and a storage medium. The method comprises the following steps: judging whether a report access request sent to a target system by a user through a specified platform is received or not; if yes, performing parameter analysis on the report access request based on the target system to obtain a report ID, a platform identifier and user information; judging whether a target platform identifier matched with the platform identifier exists in a registered platform list or not; if yes, judging whether the report ID is published and allowing the specified platform to access the report; if yes, performing role verification on the user based on the user information; if the user passes the role verification, performing permission verification on the user based on the user information; and if the user passes the permission verification, obtaining a target report corresponding to the report ID from the target system, and displaying the target report in a specified platform. According to the method, the report of the target system can be quickly and accurately deployed to other platforms, and the security and compliance of report access are ensured.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a report processing method, device, computer equipment and storage medium. Background Art

[0002] In the field of Business Intelligence (BI), data visualization reports, as key information display tools, play an irreplaceable role in helping enterprise decision makers quickly understand data trends and gain insights into business conditions. With the deepening of digital transformation, enterprises have an increasing demand for data visualization reports, which not only require rich content and diverse forms of reports, but also emphasize the sharing and embedding capabilities of reports to facilitate the seamless transmission of key information between different platforms.

[0003] The mainstream business intelligence systems on the market currently generally use links to achieve the sharing and cross-platform embedding of data visualization reports. This mechanism allows users to share reports with other users or embed them in third-party applications and portals by generating specific URL links. Although this method improves the availability and flexibility of reports to a certain extent, it also has limitations in permission control. When sharing reports through links, it is often difficult for the system to accurately control the access rights of different users or platforms to reports. Once the link is leaked or improperly disseminated, unauthorized users may easily access sensitive data, seriously threatening the security of corporate data. In addition, even if the system provides basic access control functions, such as password protection or login verification, it often lacks fine-grained permission settings and cannot meet the needs of enterprises to implement differentiated permission management for different user roles.

[0004] Therefore, the existing link-based processing method for sharing and cross-platform embedding of data visualization reports has the problems of low intelligence and low security. Summary of the invention

[0005] The main purpose of the present invention is to provide a report processing method, device, computer equipment and storage medium, aiming to solve the technical problems of low intelligence and low security in the existing link-based processing method for sharing and cross-platform embedding of data visualization reports.

[0006] To achieve the above object, the present invention provides a report processing method, the method comprising:

[0007] Determine whether a report access request sent by a user to a target system through a designated platform is received; wherein the report access request carries a report ID, a platform identifier of the designated platform, and user information of the user;

[0008] If yes, performing parameter parsing on the report access request based on the target system to obtain the report ID, the platform identifier and the user information;

[0009] Determine whether there is a target platform identifier matching the platform identifier in a preset registered platform list;

[0010] If so, determine whether the report ID has been published and whether the specified platform is allowed to access the report;

[0011] If so, performing role verification on the user based on the user information;

[0012] If the user passes the role verification, then the user's authority verification is performed based on the user information;

[0013] If the user passes the authority verification, the target report corresponding to the report ID is obtained from the target system, and the display processing corresponding to the target report is performed in the designated platform.

[0014] Optionally, before determining whether the report ID has been published and allowing the designated platform to access the report, the method further includes:

[0015] Obtaining a preset SDK document from the target system;

[0016] Building a docking environment corresponding to the target system in the designated platform;

[0017] Based on the interface specification in the SDK document and the docking environment, interface docking processing with the target system is performed on the designated platform.

[0018] Optionally, the determining whether the report ID has been published and the designated platform is allowed to access the report includes:

[0019] Determine whether the report ID exists in a preset report database;

[0020] If so, determine that the report ID has been published, and obtain report access permission information corresponding to the specified platform;

[0021] Determine whether there is target information matching the report ID in the report access permission information;

[0022] If so, it is determined that the designated platform is allowed to access the report; otherwise, it is determined that the designated platform is not allowed to access the report.

[0023] Optionally, the performing role verification on the user based on the user information includes:

[0024] Call the preset role database;

[0025] Performing information query on the role database based on the user information to determine whether there is a user record matching the user information in the role database;

[0026] If there is a user record matching the user information, extracting role information corresponding to the user information from the user record;

[0027] Determining whether the role information includes a role corresponding to the access request report;

[0028] If the role information includes the role corresponding to the access request report, it is determined that the user has passed the role verification;

[0029] If the role corresponding to the access request report is not included in the role information, it is determined that the user has not passed the role verification.

[0030] Optionally, the performing authority verification on the user based on the user information includes:

[0031] Determine whether the user belongs to the target user group corresponding to the requested report;

[0032] If so, based on the user information, obtain the permission tag set of the user;

[0033] Determining whether the permission tag corresponding to the access request report is included in the permission tag set;

[0034] If the permission tag corresponding to the access request report is included in the permission tag set, it is determined that the user has passed the permission verification;

[0035] If the permission tag corresponding to the access request report is not included in the permission tag set, it is determined that the user has not passed the permission verification.

[0036] Optionally, the acquiring a target report corresponding to the report ID from the target system and performing display processing corresponding to the target report on the designated platform includes:

[0037] Acquire a target report corresponding to the report ID from a report database in the target system;

[0038] Determining a display position corresponding to the target report in a target page on the designated platform;

[0039] Adjusting the target report based on the target page to obtain a corresponding first report;

[0040] Calling the report rendering interface of the target system;

[0041] Based on the report rendering interface, the first report is rendered to the display position in the target page.

[0042] Optionally, adjusting the target report based on the target page to obtain a corresponding first report includes:

[0043] Obtaining the page style of the target page;

[0044] Adjusting the style of the target report based on the page style to obtain an adjusted second report;

[0045] Preview the second report to determine whether the second report meets the preset display requirements;

[0046] If so, the adjusted second report is used as the first report.

[0047] In addition, to achieve the above-mentioned purpose, the present invention also provides a report processing device, the report processing device comprising:

[0048] A first judgment module is used to judge whether a report access request sent by a user to a target system through a designated platform is received; wherein the report access request carries a report ID, a platform identifier of the designated platform, and user information of the user;

[0049] A processing module, configured to, if yes, parse the report access request parameters based on the target system to obtain the report ID, the platform identifier and the user information;

[0050] A second determination module is used to determine whether there is a target platform identifier matching the platform identifier in a preset registered platform list;

[0051] A third judgment module is used to judge whether the report ID has been published and the designated platform is allowed to access the report;

[0052] A first verification module, configured to verify the role of the user based on the user information;

[0053] A second verification module, configured to perform authority verification on the user based on the user information if the user passes the role verification;

[0054] The display module is used to obtain the target report corresponding to the report ID from the target system if the user passes the authority verification, and perform display processing corresponding to the target report in the designated platform.

[0055] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0056] The computer device includes a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps of any one of the report processing methods proposed in the embodiments of the present application are implemented.

[0057] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0058] The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the steps of any one of the report processing methods proposed in the embodiments of the present application are implemented.

[0059] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0060] The present invention provides a report processing method, apparatus, computer equipment and storage medium, the method comprising: firstly determining whether a report access request is received from a user to a target system through a designated platform; wherein the report access request carries a report ID, a platform identifier of the designated platform and user information of the user; if so, performing parameter parsing on the report access request based on the target system to obtain the report ID, the platform identifier and the user information; then determining whether there is a target platform identifier matching the platform identifier in a preset registered platform list; if so, determining whether the report ID has been published and the designated platform is allowed to access the report; if so, performing role verification on the user based on the user information; if the user passes the role verification, performing permission verification on the user based on the user information; if the user passes the permission verification, obtaining a target report corresponding to the report ID from the target system, and performing display processing corresponding to the target report in the designated platform. This application, when receiving a report access request from a user to a target system through a designated platform, will parse the report access request parameters based on the target system to obtain the report ID, platform identifier, and user information, and then match the platform identifier based on the use of the registered platform list, and detect whether the report ID has been published and the designated platform is allowed to access the report to perform the corresponding system authority verification, and then perform role verification and authority verification on the user based on the user information, and only when it is detected that the system authority verification, role verification, and authority verification are all passed, will the target report corresponding to the report ID be obtained from the target system, and the display processing corresponding to the target report will be performed in the designated platform. In this way, the data visualization report of the target system can be quickly and accurately deployed to other platforms, intelligently realizing the cross-platform visualization and analysis of report data, and ensuring the security and compliance of report access. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0062] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0063] Figure 2 is a flow chart of a report processing method provided by an embodiment of the present invention;

[0064] Figure 3 is a structural schematic diagram of an embodiment of a report processing device according to the present application;

[0065] Figure 4 This is a basic structural block diagram of the computer device in this embodiment. DETAILED DESCRIPTION

[0066] The report processing method provided by the embodiment of the present invention is applied to the report processing device. Unless otherwise defined, all technical and scientific terms used in this document have the same meaning as those generally understood by technicians in the technical field of this application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" in the specification and claims of this application and the above-mentioned drawings and any variations thereof are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of this application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0067] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0068] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0069] like Figure 1As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0070] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social online platform software, etc.

[0071] Terminal devices 101, 102, 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 (Moving Picture Experts Group Audio Layer IV), laptop computers, desktop computers, etc.

[0072] The server 105 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal devices 101 , 102 , and 103 .

[0073] It should be noted that the report processing method provided in the embodiment of the present application is generally executed by a server / terminal device, and accordingly, the report processing device is generally arranged in the server / terminal device.

[0074] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0075] In the field of Business Intelligence (BI), data visualization reports, as key information display tools, play an irreplaceable role in helping enterprise decision makers quickly understand data trends and gain insights into business conditions. With the deepening of digital transformation, enterprises have an increasing demand for data visualization reports, which not only require rich content and diverse forms of reports, but also emphasize the sharing and embedding capabilities of reports to facilitate the seamless transmission of key information between different platforms.

[0076] The mainstream business intelligence systems on the market currently generally use links to achieve the sharing and cross-platform embedding of data visualization reports. This mechanism allows users to share reports with other users or embed them in third-party applications and portals by generating specific URL links. Although this method improves the availability and flexibility of reports to a certain extent, it also has limitations in permission control. When sharing reports through links, it is often difficult for the system to accurately control the access rights of different users or platforms to reports. Once the link is leaked or improperly disseminated, unauthorized users may easily access sensitive data, seriously threatening the security of corporate data. In addition, even if the system provides basic access control functions, such as password protection or login verification, it often lacks fine-grained permission settings and cannot meet the needs of enterprises to implement differentiated permission management for different user roles.

[0077] Therefore, the existing link-based processing method for sharing and cross-platform embedding of data visualization reports has the problems of low intelligence and low security.

[0078] Continue to refer Figure 2 , shows a flow chart of an embodiment of the report processing method proposed in the present application. The embodiment of the present application can acquire and process relevant data based on artificial intelligence technology.

[0079] The report processing method provided by the embodiment of the present invention comprises the following steps:

[0080] S210, determining whether a report access request sent by a user to a target system through a designated platform is received; wherein the report access request carries a report ID, a platform identifier of the designated platform, and user information of the user.

[0081] In this step, the target system is specifically a business intelligence system. And a data visualization report is created in the business intelligence system in advance. Specifically, the process of creating a data visualization report in the business intelligence system includes: 1. Requirements collection: Communicate with users or business departments to clarify the requirements of data visualization reports, including report types (such as line charts, bar charts, etc.), displayed data fields, data filtering conditions, etc. 2. Data source preparation: Ensure that the business intelligence system is connected and the data source is correctly configured, and the data source should contain all the data required for the report. 3. Report design: In the report design tool of the business intelligence system, select the appropriate chart type according to the requirements, drag the data field to the corresponding position, and set the data filtering conditions and chart style. 4. Preview and adjust: Preview the designed report, check whether the data display is correct and whether the chart style is beautiful, and adjust it as needed. 5. Save and publish: Save and publish the designed report to the report library of the business intelligence system for access by other platforms.

[0082] In addition, it is necessary to further complete the credit authorization process in the business intelligence system, including: (1) Platform registration: register other platforms that need to be connected in the business intelligence system and record the unique identifier of the platform. (2) Permission setting: set access rights for the registered platform, including the list of reports allowed to be accessed, data filtering conditions, etc. (3) Generate access credentials: generate access credentials (such as API keys, tokens, etc.) for the platform to authenticate identity when accessing reports. (4) Recording and notification: record the platform's access rights and access credential information, and notify the platform to obtain this information.

[0083] The report access request is an access request triggered by a user through a designated platform for accessing a target report corresponding to a report ID in the target system in the designated platform. The user information may refer to the user's identity authentication information, such as a user name, password, token, etc. The designated platform may refer to a purchase and sales system, a CRM system, etc.

[0084] S220: parse the report access request based on the target system to obtain the report ID, the platform identifier, and the user information.

[0085] In this step, the target system may be called to perform parameter parsing on the report access request to extract the report ID, platform identifier and user information carried in the report access request.

[0086] S230: Determine whether there is a target platform identifier matching the platform identifier in the preset registered platform list.

[0087] In this step, a list of registered platforms is maintained in the target system in advance, i.e., the registered platform list, and each platform has a unique identifier (such as an API key, client ID, etc.). It can be detected whether the platform identifier in the report access request matches an identifier in the registered platform list. If they match, the subsequent verification process continues, and if they do not match, the report access request is regarded as an illegal request and an error message is returned.

[0088] S240: If yes, determine whether the report ID has been published and whether the designated platform is allowed to access the report.

[0089] In this step, the specific implementation process of judging whether the report ID has been published and allowing the designated platform to access the report will be described in further detail in subsequent specific embodiments of the present invention, and will not be elaborated on here.

[0090] S250: If yes, perform role verification on the user based on the user information.

[0091] In this step, the specific implementation process of the role verification of the user based on the user information will be further described in detail in the subsequent specific embodiments of the present invention, and will not be elaborated on here.

[0092] S260: If the user passes the role verification, the user is subject to authority verification based on the user information.

[0093] In this step, the specific implementation process of the above-mentioned authorization verification of the user based on the user information will be further described in detail in the subsequent specific embodiments of the present invention, and will not be elaborated on here.

[0094] S270: If the user passes the authority verification, a target report corresponding to the report ID is obtained from the target system, and a display process corresponding to the target report is performed in the designated platform.

[0095] In this step, the specific implementation process of obtaining the target report corresponding to the report ID from the target system and performing the display processing corresponding to the target report in the designated platform will be further described in detail in the subsequent specific embodiments of the present invention and will not be elaborated on here.

[0096] In an embodiment of the present invention, it is first determined whether a report access request is received from a user to a target system through a designated platform; wherein the report access request carries a report ID, a platform identifier of the designated platform, and user information of the user; if so, the report access request is parameter-parsed based on the target system to obtain the report ID, the platform identifier, and the user information; then it is determined whether there is a target platform identifier matching the platform identifier in a preset registered platform list; if so, it is determined whether the report ID has been published and the designated platform is allowed to access the report; if so, the user is role-verified based on the user information; if the user passes the role verification, the user is permission-verified based on the user information; if the user passes the permission verification, the target report corresponding to the report ID is obtained from the target system, and display processing corresponding to the target report is performed in the designated platform. This application, when receiving a report access request from a user to a target system through a designated platform, will parse the report access request parameters based on the target system to obtain the report ID, platform identifier, and user information, and then match the platform identifier based on the use of the registered platform list, and detect whether the report ID has been published and the designated platform is allowed to access the report to perform the corresponding system authority verification, and then perform role verification and authority verification on the user based on the user information, and only when it is detected that the system authority verification, role verification, and authority verification are all passed, will the target report corresponding to the report ID be obtained from the target system, and the display processing corresponding to the target report will be performed in the designated platform. In this way, the data visualization report of the target system can be quickly and accurately deployed to other platforms, intelligently realizing the cross-platform visualization and analysis of report data, and ensuring the security and compliance of report access.

[0097] Optionally, before determining whether the report ID has been published and allowing the designated platform to access the report, the method further includes:

[0098] Obtain a preset SDK document from the target system.

[0099] In this step, the target system is specifically a business intelligence system, and the pre-built SDK document can be obtained from the target system, wherein the SDK document includes SDK functions, interface specifications, data visualization report embedding specifications, permission verification mechanism, etc.

[0100] SDK is the abbreviation of Software Development Kit. SDK is actually a collection of tools to assist front-end and back-end software development, which includes relevant documents, best practices and tools. Systems or applications that use the SDK need to fully understand its clear specifications. Relevant documents can help developers understand how to use the SDK functions, best practices will provide implementation methods and cases for the functions, and tools allow developers to more efficiently complete the docking of SDK functions. The use of SDK functions has greatly improved the convenience of developer research and development and greatly improved the developer's work efficiency. In fact, SDK technology can be understood as the "industry specification" or "module integration capability" of a certain function or system. By adhering to and using this technology, the development workload is greatly reduced and the developer's work efficiency is improved.

[0101] The present invention packages and processes data visualization report embedding specifications, permission verification specifications, etc. by applying SDK technology, aiming to create a general functional specification to realize the rapid application and deployment of business intelligence system data visualization reports on other enterprise platforms. Using SDK to realize the interaction between business intelligence system data visualization reports and other platforms helps to provide safe and standardized general capabilities, and can achieve rapid docking and rapid deployment when interacting between platforms. Compared with traditional linking methods, it improves the security and diversity of data, meets the use requirements of data visualization reports in various business scenarios, provides developers between different systems with convenient data visualization report embedding specifications, and can maximize the opening of capabilities to other platforms within a certain range, truly realizing the efficient reuse of business intelligence system data visualization capabilities and the functional empowerment of other platforms.

[0102] A docking environment corresponding to the target system is built in the designated platform.

[0103] In this step, an environment for connecting to the business intelligence system can be built on the above-mentioned designated platform, including network configuration, server resources, etc.

[0104] Based on the interface specification in the SDK document and the docking environment, interface docking processing with the target system is performed on the designated platform.

[0105] In this step, you can implement the interface connection with the business intelligence system on the above-mentioned designated platform according to the interface specifications in the SDK document, including data request, report rendering, etc. In addition, you can further evaluate the business intelligence system functions that need to be connected in the designated platform according to business needs and the actual situation of the designated platform. Then select the functions that need to be connected in the SDK, such as report display, data filtering, data export, etc. And according to the best practices in the SDK, configure the parameters required for the function, such as report ID, data filtering conditions, etc.

[0106] In an embodiment of the present invention, a preset SDK document is obtained from the target system; a docking environment corresponding to the target system is then built in the designated platform; and then, based on the interface specifications in the SDK document and the docking environment, an interface docking process with the target system is performed on the designated platform. The present invention obtains a preset SDK document from the target system, and builds a docking environment corresponding to the target system in the designated platform; and then, based on the interface specifications in the SDK document and the docking environment, an interface docking process with the target system is performed on the designated platform, thereby effectively ensuring that the designated platform can access the data visualization reports of the target system, and subsequently, the data visualization reports of the target system can be quickly, standardizedly, and securely deployed and applied on other platforms, thereby improving the intelligence of report access.

[0107] Optionally, the determining whether the report ID has been published and the designated platform is allowed to access the report includes:

[0108] It is determined whether the report ID exists in a preset report database.

[0109] In this step, the report database is a pre-maintained database of published reports, and each report has a unique ID. The report ID carried in the report access request can be further checked to determine the publishing status corresponding to the report ID. The publishing status includes published or unpublished.

[0110] If so, it is determined that the report ID has been published, and the report access permission information corresponding to the specified platform is obtained.

[0111] In this step, if the report ID exists in the report database, it is determined that the report ID has been published. The access rights are set in advance for the registered platform, including the list of reports allowed to be accessed, data screening conditions and other information, and it is ensured that the permission settings meet business requirements and do not leak sensitive data. Specifically, the access rights can be queried by using the platform identifier to obtain the report access rights information corresponding to the specified platform.

[0112] Determine whether there is target information matching the report ID in the report access permission information;

[0113] In this step, it is possible to obtain a corresponding inspection result by checking whether there is target information matching the report ID in the obtained report access permission information, wherein the inspection result may include: there is target information matching the report ID in the report access permission information, or there is no target information matching the report ID in the report access permission information.

[0114] If so, it is determined that the designated platform is allowed to access the report; otherwise, it is determined that the designated platform is not allowed to access the report.

[0115] In this step, if it is detected that there is target information matching the report ID in the report access permission information, it indicates that the designated platform has the permission to access the target report corresponding to the report ID, and then it is determined that the designated platform is allowed to access the report. If it is detected that there is no target information matching the report ID in the report access permission information, it indicates that the designated platform does not have the permission to access the target report corresponding to the report ID, and then it is determined that the designated platform is not allowed to access the report.

[0116] In an embodiment of the present invention, it is determined whether the report ID exists in a preset report database; if so, it is determined that the report ID has been published, and the report access permission information corresponding to the specified platform is obtained; subsequently, it is determined whether there is target information matching the report ID in the report access permission information; if so, it is determined that the specified platform is allowed to access the report, otherwise it is determined that the specified platform is not allowed to access the report. The present invention detects and processes the report ID carried in the report access request based on the use of the report database and the report access permission information corresponding to the specified platform, and can efficiently and accurately complete the detection and processing of whether the report ID has been published and the specified platform is allowed to access the report, thereby ensuring the accuracy of the obtained detection result.

[0117] Optionally, the performing role verification on the user based on the user information includes:

[0118] Call the preset role database.

[0119] In this step, a role database containing user roles is maintained in advance. The role database stores the authentication information of all users and the corresponding role assignments.

[0120] Based on the user information, the role database is queried to determine whether there is a user record matching the user information in the role database.

[0121] In this step, the user information may refer to the user's identity authentication information, such as user name, password, token (such as JWT, OAuth token), etc. The user information may be used as a query condition to search for corresponding user records in the role database and obtain corresponding search results. The search results include the existence of user records matching the user information in the role database, or the absence of user records matching the user information in the role database.

[0122] If there is a user record matching the user information, role information corresponding to the user information is extracted from the user record.

[0123] In this step, if it is detected that there is a user record matching the user information in the role database, role information is further extracted from the user record according to the user information to obtain role information corresponding to the user.

[0124] It is determined whether the role information includes a role corresponding to the access request report.

[0125] In this step, it is possible to further detect whether the extracted role information contains the role required for the access request report and generate a corresponding detection result, wherein the detection result includes whether the role corresponding to the access request report is included in the role information or whether the role corresponding to the access request report is not included in the role information.

[0126] If the role information includes the role corresponding to the access request report, it is determined that the user has passed the role verification.

[0127] In this step, if it is detected that the role corresponding to the access request report is included in the role information, it means that the user's role meets the conditions of the access request report, and then it is determined that the user has passed the role verification.

[0128] If the role corresponding to the access request report is not included in the role information, it is determined that the user has not passed the role verification.

[0129] In this step, if it is detected that the role corresponding to the access request report is not included in the role information, it means that the user's role does not meet the conditions of the access request report, and then it is determined that the user has not passed the role verification. In addition, a response containing error information is automatically generated and returned to the designated platform of the request. The error information may include the reason for the failure, the recommended solution steps, etc.

[0130] In an embodiment of the present invention, a preset role database is called; then, information query is performed on the role database based on the user information to determine whether there is a user record matching the user information in the role database; if there is a user record matching the user information, the role information corresponding to the user information is extracted from the user record; subsequently, it is determined whether the role information contains the role corresponding to the access request report; if the role information contains the role corresponding to the access request report, it is determined that the user has passed the role verification; and if the role information does not contain the role corresponding to the access request report, it is determined that the user has not passed the role verification. The present invention performs corresponding information query on user information based on the use of a role database, and then can perform role analysis based on the role information extracted from the obtained information query results, so as to quickly and accurately complete the role verification for the user, effectively ensure the accuracy of the generated role verification results, and thus help ensure the security and compliance of report access.

[0131] Optionally, the performing authority verification on the user based on the user information includes:

[0132] Determine whether the user belongs to the target user group corresponding to the requested report.

[0133] In this step, multiple user groups are pre-built according to actual business processing requirements. User groups are divided according to business logic or organizational structure, and each user group may have a different set of permission tags. The target user group is the specific user group required to request a report.

[0134] If so, based on the user information, obtain the permission tag set of the user.

[0135] In this step, if it is detected whether the user belongs to the target user group corresponding to the requested report, a matching permission tag set is further queried based on the user information. The permission tag is a more fine-grained permission control mechanism that can authorize specific reports, data or operations.

[0136] It is determined whether the permission tag set includes the permission tag corresponding to the access request report.

[0137] In this step, the corresponding tag detection result can be obtained by detecting whether the user's permission tag set contains the permission tag required for the access request report. The tag detection result includes that the permission tag corresponding to the access request report is included in the permission tag set, or that the permission tag corresponding to the access request report is not included in the permission tag set.

[0138] If the permission tag corresponding to the access request report is included in the permission tag set, it is determined that the user has passed the permission verification.

[0139] In this step, if it is detected that the permission tag corresponding to the access request report is included in the permission tag set, it means that the user's permission tag meets the conditions of the access request report, and then it is determined that the user has passed the permission verification.

[0140] If the permission tag corresponding to the access request report is not included in the permission tag set, it is determined that the user has not passed the permission verification.

[0141] In this step, if it is detected that the permission tag corresponding to the access request report is not included in the permission tag set, it indicates that the user's permission tag does not meet the conditions for accessing the request report, and then it is determined that the user has not passed the permission verification. If the user has not passed the permission verification, the user's request to access the target report corresponding to the report ID will be automatically and intelligently rejected.

[0142] In an embodiment of the present invention, it is determined whether the user belongs to the target user group corresponding to the request report; if so, based on the user information, the permission tag set of the user is obtained; subsequently, it is determined whether the permission tag corresponding to the access request report is included in the permission tag set; if the permission tag corresponding to the access request report is included in the permission tag set, it is determined that the user has passed the permission verification; and if the permission tag corresponding to the access request report is not included in the permission tag set, it is determined that the user has not passed the permission verification. The present invention performs permission verification on the user by combining user group detection and permission tag detection, and can accurately detect whether the user has the permission required for the access request report, effectively improving the accuracy of the generated permission verification results, thereby ensuring the security and compliance of report access.

[0143] Optionally, the acquiring a target report corresponding to the report ID from the target system and performing display processing corresponding to the target report on the designated platform includes:

[0144] A target report corresponding to the report ID is obtained from a report database in the target system.

[0145] In this step, the report ID can be used to extract the report corresponding to the report ID from the report database of the target system and use it as the target report. The report database is a pre-maintained database of published reports, and each report has a unique ID.

[0146] A display position corresponding to the target report is determined in a target page on the designated platform.

[0147] In this step, there is no specific limitation on the setting method of the above display position, which can be set according to actual display requirements. Preferably, the corresponding display position can be determined according to the user's usage habits and the overall style of the target page.

[0148] Adjusting the target report based on the target page to obtain a corresponding first report;

[0149] In this step, the specific implementation process of adjusting the target report based on the target page to obtain the corresponding first report will be further described in detail in subsequent specific embodiments of the present invention, and will not be elaborated on here.

[0150] Call the report rendering interface of the target system.

[0151] In this step, the report rendering interface is a pre-built interface that has the function of rendering a report and embedding it into a page.

[0152] Based on the report rendering interface, the first report is rendered to the display position in the target page.

[0153] In this step, the first report can be rendered to the display position in the target page by calling the report rendering interface, and the correctness of data and the aesthetics of the style during the report rendering process can be further ensured.

[0154] In an embodiment of the present invention, the target report corresponding to the report ID is obtained from the report database in the target system; then the display position corresponding to the target report is determined in the target page on the specified platform; then the target report is adjusted based on the target page to obtain the corresponding first report; the report rendering interface of the target system is subsequently called; finally, based on the report rendering interface, the first report is rendered to the display position in the target page. This application obtains the target report corresponding to the report ID from the report database in the target system, then determines the display position corresponding to the target report in the target page on the specified platform, and adjusts the target report based on the target page to obtain the first report, and then based on the use of the report rendering interface of the target system, renders the first report to the display position in the target page, thereby automatically and intelligently ensuring that the target report of the target system can be safely and quickly deployed to other platforms, and realizing cross-platform data visualization and analysis, thereby improving the security and intelligence of report access.

[0155] Optionally, adjusting the target report based on the target page to obtain a corresponding first report includes:

[0156] Get the page style of the target page.

[0157] In this step, the page style of the target page can be obtained by performing style analysis or style query on the target page.

[0158] The target report is style-adjusted based on the page style to obtain an adjusted second report.

[0159] In this step, the target report can be adjusted in terms of color, font, etc. according to the page style of the target page to ensure that the report style of the target report is consistent with the overall style of the page, thereby improving the user experience and obtaining an adjusted second report.

[0160] The second report is previewed to determine whether the second report meets the preset display requirements.

[0161] In this step, the adjusted second report can be further previewed to check whether the data display in the second report is correct and whether the chart style is beautiful, and adjustments can be made as needed. If it is detected that the data display in the second report is correct and the chart style is beautiful, it is determined that the second report meets the display requirements, otherwise it is determined that the second report does not meet the display requirements.

[0162] If so, the adjusted second report is used as the first report.

[0163] In this step, if it is detected that the second report meets the display requirements, the adjusted second report is used as the final first report.

[0164] In an embodiment of the present invention, the page style of the target page is obtained; then the style of the target report is adjusted based on the page style to obtain an adjusted second report; the second report is subsequently previewed to determine whether the second report meets the preset display requirements; if so, the adjusted second report is used as the first report. The present invention obtains an adjusted second report by adjusting the style of the target report based on the obtained page style of the target page, and then previewing the second report, and if it is detected that the second report meets the preset display requirements, the adjusted second report is used as the final first report, thereby achieving intelligent and accurate completion of the adjustment process of the target report, effectively ensuring the accuracy of the obtained first report, and helping to improve the user experience.

[0165] In some optional implementations, the user information obtained is subject to the user's consent and complies with relevant laws and policies.

[0166] In addition, the present invention realizes the rapid connection of the data visualization report function of the business intelligence system through SDK technology, maximizes the functional permissions of other platforms, and realizes the efficient reuse of the business intelligence system while meeting the needs of multiple business scenarios.

[0167] Further references Figure 3 , as a response to the above Figure 2 In order to realize the method shown in the figure, the present application provides an embodiment of a report processing device 300, which is similar to Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0168] An embodiment of the present invention provides a report processing device 300, the report processing device 300 comprising:

[0169] The first judgment module 310 is used to judge whether a report access request sent by a user to a target system through a specified platform is received; wherein the report access request carries a report ID, a platform identifier of the specified platform, and user information of the user;

[0170] Processing module 320, configured to, if yes, perform parameter parsing on the report access request based on the target system to obtain the report ID, the platform identifier and the user information;

[0171] The second determination module 330 is used to determine whether there is a target platform identifier matching the platform identifier in the preset registered platform list;

[0172] The third judgment module 340 is used to judge whether the report ID has been published and the designated platform is allowed to access the report;

[0173] A first verification module 350, configured to verify the role of the user based on the user information;

[0174] A second verification module 360, configured to perform authority verification on the user based on the user information if the user passes the role verification;

[0175] The display module 370 is used to obtain the target report corresponding to the report ID from the target system if the user passes the authority verification, and perform display processing corresponding to the target report in the designated platform.

[0176] Optionally, the report processing device 300 further includes:

[0177] An acquisition module, used for acquiring a preset SDK document from the target system;

[0178] A building module, used to build a docking environment corresponding to the target system in the specified platform;

[0179] The docking module is used to perform interface docking processing with the target system on the designated platform based on the interface specification in the SDK document and the docking environment.

[0180] Optionally, the third determination module 340 includes:

[0181] A first judgment submodule is used to judge whether the report ID exists in a preset report database;

[0182] A first acquisition submodule is used to determine that the report ID has been published and obtain the report access permission information corresponding to the specified platform;

[0183] A second judgment submodule is used to judge whether there is target information matching the report ID in the report access permission information;

[0184] The first determination submodule is configured to determine that if yes, the designated platform is allowed to access the report, otherwise, the designated platform is not allowed to access the report.

[0185] Optionally, the first verification module 350 includes:

[0186] The first calling submodule is used to call a preset role database;

[0187] A third judgment submodule is used to query the role database based on the user information to determine whether there is a user record matching the user information in the role database;

[0188] an extraction submodule, configured to extract role information corresponding to the user information from the user record if there is a user record matching the user information;

[0189] A fourth determination submodule is used to determine whether the role information includes a role corresponding to the access request report;

[0190] A second determination submodule, configured to determine that the user has passed the role verification if the role corresponding to the access request report is included in the role information;

[0191] The third determination submodule is configured to determine that the user has not passed the role verification if the role corresponding to the access request report is not included in the role information.

[0192] Optionally, the second verification module 360 ​​includes:

[0193] A fifth judgment submodule, used to judge whether the user belongs to the target user group corresponding to the requested report;

[0194] A second acquisition submodule is used to acquire the permission tag set of the user based on the user information;

[0195] A sixth judgment submodule, used to judge whether the permission tag corresponding to the access request report is included in the permission tag set;

[0196] A fourth determination submodule, configured to determine that the user has passed the authority verification if the authority tag corresponding to the access request report is included in the authority tag set;

[0197] The fifth determination submodule is configured to determine that the user has not passed the permission verification if the permission tag corresponding to the access request report is not included in the permission tag set.

[0198] Optionally, the display module 370 includes:

[0199] A third acquisition submodule is used to acquire a target report corresponding to the report ID from a report database in the target system;

[0200] A determination submodule, used to determine a display position corresponding to the target report in the target page on the designated platform;

[0201] An adjustment submodule, configured to adjust the target report based on the target page to obtain a corresponding first report;

[0202] The second calling submodule is used to call the report rendering interface of the target system;

[0203] A rendering submodule is used to render the first report to the display position in the target page based on the report rendering interface.

[0204] Optionally, the adjustment submodule includes:

[0205] An acquisition unit, used to acquire the page style of the target page;

[0206] An adjustment unit, configured to adjust the style of the target report based on the page style to obtain an adjusted second report;

[0207] A judging unit, configured to perform a preview process on the second report to judge whether the second report meets a preset display requirement;

[0208] The determining unit is configured to, if yes, use the adjusted second report as the first report.

[0209] To solve the above technical problems, the present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0210] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 4 with components 41-43, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0211] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0212] The memory 41 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as a hard disk or memory of the computer device 4. In other embodiments, the memory 41 can also be an external storage device of the computer device 4, such as a plug-in hard disk equipped on the computer device 4, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), etc. Of course, the memory 41 can also include both the internal storage unit of the computer device 4 and its external storage device. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as the program code of the report processing method, etc. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or are to be output.

[0213] The processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to run the program code stored in the memory 41 or process data, such as running the program code of the report processing method.

[0214] The network interface 43 may include a wireless network interface or a wired network interface. The network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0215] The present application also provides another implementation, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores the application crash processing program, and the application crash processing program can be executed by at least one processor to enable the at least one processor to perform the steps of the report processing method as described above.

[0216] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware online platform, and of course, by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0217] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0218] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A report processing method, characterized in that: include: Determine whether a report access request sent by a user to a target system through a designated platform is received; wherein the report access request carries a report ID, a platform identifier of the designated platform, and user information of the user; If yes, performing parameter parsing on the report access request based on the target system to obtain the report ID, the platform identifier and the user information; Determine whether there is a target platform identifier matching the platform identifier in a preset registered platform list; If so, determine whether the report ID has been published and whether the specified platform is allowed to access the report; If so, performing role verification on the user based on the user information; If the user passes the role verification, then the user's authority verification is performed based on the user information; If the user passes the authority verification, the target report corresponding to the report ID is obtained from the target system, and the display processing corresponding to the target report is performed in the designated platform.

2. The method according to claim 1, characterized in that Before determining whether the report ID has been published and allowing the designated platform to access the report, the method further includes: Obtaining a preset SDK document from the target system; Building a docking environment corresponding to the target system in the designated platform; Based on the interface specification in the SDK document and the docking environment, interface docking processing with the target system is performed on the designated platform.

3. The method according to claim 1, characterized in that The determining whether the report ID has been published and the designated platform is allowed to access the report includes: Determine whether the report ID exists in a preset report database; If so, determine that the report ID has been published, and obtain report access permission information corresponding to the specified platform; Determine whether there is target information matching the report ID in the report access permission information; If so, it is determined that the designated platform is allowed to access the report; otherwise, it is determined that the designated platform is not allowed to access the report.

4. The method according to claim 1, characterized in that: The performing role verification on the user based on the user information includes: Call the preset role database; Performing information query on the role database based on the user information to determine whether there is a user record matching the user information in the role database; If there is a user record matching the user information, extracting role information corresponding to the user information from the user record; Determining whether the role information includes a role corresponding to the access request report; If the role information includes the role corresponding to the access request report, it is determined that the user has passed the role verification; If the role corresponding to the access request report is not included in the role information, it is determined that the user has not passed the role verification.

5. The method according to claim 1, characterized in that The verifying the authority of the user based on the user information includes: Determine whether the user belongs to the target user group corresponding to the requested report; If so, based on the user information, obtain the permission tag set of the user; Determining whether the permission tag corresponding to the access request report is included in the permission tag set; If the permission tag corresponding to the access request report is included in the permission tag set, it is determined that the user has passed the permission verification; If the permission tag corresponding to the access request report is not included in the permission tag set, it is determined that the user has not passed the permission verification.

6. The method according to claim 1, characterized in that The step of acquiring a target report corresponding to the report ID from the target system and performing display processing corresponding to the target report on the designated platform includes: Acquire a target report corresponding to the report ID from a report database in the target system; Determining a display position corresponding to the target report in a target page on the designated platform; Adjusting the target report based on the target page to obtain a corresponding first report; Calling the report rendering interface of the target system; Based on the report rendering interface, the first report is rendered to the display position in the target page.

7. The method according to claim 6, characterized in that The adjusting the target report based on the target page to obtain a corresponding first report includes: Obtaining the page style of the target page; Adjusting the style of the target report based on the page style to obtain an adjusted second report; Preview the second report to determine whether the second report meets the preset display requirements; If so, the adjusted second report is used as the first report.

8. A report processing device, characterized in that: include: A first judgment module is used to judge whether a report access request sent by a user to a target system through a designated platform is received; wherein the report access request carries a report ID, a platform identifier of the designated platform, and user information of the user; A processing module, configured to, if yes, parse the report access request parameters based on the target system to obtain the report ID, the platform identifier and the user information; A second determination module is used to determine whether there is a target platform identifier matching the platform identifier in a preset registered platform list; A third judgment module is used to judge whether the report ID has been published and the designated platform is allowed to access the report; A first verification module, configured to verify the role of the user based on the user information; A second verification module, configured to perform authority verification on the user based on the user information if the user passes the role verification; The display module is used to obtain the target report corresponding to the report ID from the target system if the user passes the authority verification, and perform display processing corresponding to the target report in the designated platform.

9. A computer device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the report processing method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the report processing method according to any one of claims 1 to 7 are implemented.

Images