Visual arrangement method of auditing indexes and auditing index arrangement system

Abstract

The invention provides a visual arrangement method of auditing indexes and an auditing index arrangement system, and relates to the technical field of data management, and the method comprises the steps: responding to a received index configuration instruction for a target business, and displaying an index configuration page which comprises an index arrangement area and an arrangement component area; based on the user operation information, adding at least one target component to the index arrangement area from the arrangement component area; and generating an auditing index based on the configuration information of the user for the at least one target component, and binding the auditing index with the target service. The index configuration page with multiple arrangement components is provided for the user by pre-defining corresponding logics of different arrangement components, and the user can perform visual arrangement of the auditing indexes by selecting and configuring the arrangement components, so that the configuration process of the auditing rules is simplified, the configuration threshold of the auditing rules is reduced, and the user experience is improved. And the business process and the auditing process are decoupled through the auditing rule formed by the arrangement component, so that the flexible configuration of auditing indexes is improved.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a method for visualizing and arranging audit indicators and an audit indicator arrangement system. Background Technology

[0002] In the business processes of modern enterprises, each link needs to be "standardized" and "inspected". That is, compliance standards need to be established in advance for the data generated in each link, and the data needs to be audited based on the compliance standards.

[0003] Currently, the auditing of data generated by business processes mainly relies on pre-written verification code. However, this verification method is too tightly coupled with the business process. Once the business process or the data generated by the business process changes, the corresponding verification code needs to be rewritten. This requires a high level of expertise in changing data auditing rules and makes it impossible to easily change or flexibly configure data auditing rules. Summary of the Invention

[0004] This application provides a method and system for visualizing and arranging audit indicators to solve the problem of difficulty in changing data audit rules in the prior art.

[0005] Firstly, embodiments of this application provide a method for visualizing and arranging audit indicators, including:

[0006] In response to receiving a metric configuration instruction for the target business, the metric configuration page is displayed. The metric configuration page includes a metric orchestration area and an orchestration component area. The orchestration component area includes a variety of orchestration components, which include at least an operator component, a field component, and a constant component.

[0007] Based on user operation information, add at least one target component from the orchestration component area to the indicator orchestration area;

[0008] Audit metrics are generated based on the user's configuration information for at least one target component, and the audit metrics are then bound to the target business.

[0009] In one possible implementation, adding at least one target component from the orchestration component area to the indicator orchestration area based on user operation information includes: in response to detecting a user's selection operation on any component in the orchestration component area, adding the user-selected component as the target component to the indicator orchestration area; or, in response to detecting a user dragging any component in the orchestration component area to a specified position in the indicator orchestration area, adding that component as the target component to the indicator orchestration area.

[0010] In one possible implementation, after adding at least one target component from the orchestration component area to the indicator orchestration area, the method further includes: in response to the inclusion of a target field component in the at least one target component, displaying field configuration options for the target field component in the orchestration component area, the field configuration options including a variety of optional business fields for the user to specify a business field as configuration information for the target field component.

[0011] In one possible implementation, audit metrics are generated based on user configuration information for at least one target component, including: determining the extraction logic for specified business fields in each target field component based on user configuration information for each target field component and a pre-stored data dictionary, wherein the data dictionary predefines extraction logic for multiple optional business fields; and generating audit metrics based on the extraction logic for specified business fields in each target field component and the component content of other orchestration components in the orchestration component area, wherein other orchestration components include field components and / or constant components.

[0012] In one possible implementation, the multiple orchestration components also include an API component. After adding at least one target component from the orchestration component area to the metric orchestration area, the implementation further includes: in response to the inclusion of a target API component in at least one target component, displaying an API configuration page for the target API component in the orchestration component area. The API configuration page is used to configure a specified API address and business fields sent to the specified API address. The specified API address configured by the user in the API configuration page and the business fields sent to the specified API address are determined as the user's configuration information for the target API component.

[0013] In one possible implementation, the multiple orchestration components also include script components. After adding at least one target component from the orchestration component area to the indicator orchestration area, the method further includes: in response to the inclusion of a target script component in at least one target component, displaying a script configuration page for the target script component in the orchestration component area. The script configuration page includes a parameter configuration area and a script editing area. The parameter configuration area is used to configure custom parameters using at least one business field, and the script editing area is used to input script code containing the custom parameters. The custom parameters configured by the user in the script editing area and the script code input by the user in the parameter configuration area are determined as the user's configuration information for the target script component.

[0014] In one possible implementation, audit metrics are generated based on the user's configuration information for at least one target component, including: determining the extraction logic of business fields in each custom parameter according to the configuration information of each custom parameter in the parameter configuration area and the pre-stored data dictionary; and generating audit metrics according to the extraction logic of business fields in each custom parameter and the script code in the script editing area.

[0015] In one possible implementation, audit metrics are generated based on user configuration information for at least one target component, including: in an arrival timeliness audit scenario, determining the extraction logic of fields in a target field component, the target field component including an arrival time field component and a departure time field component; determining the operation logic of a target operator component and the constant content of a target constant component in the orchestration component area; generating arrival timeliness audit metrics based on the extraction logic of fields in the target field component, the operation logic of the target operator component, and the constant content of the target constant component; wherein, the arrival timeliness audit metrics are used to verify whether the time difference between the arrival time and departure time in the audited data is acceptable.

[0016] In one possible implementation, the orchestration components also include a latitude and longitude distance calculation component, which generates audit indicators based on the user's configuration information for at least one target component. This includes: in a power generation distance audit scenario, determining the field content of the data center latitude and longitude field in the latitude and longitude distance calculation component and the field extraction logic of the power generation latitude and longitude field; determining the operation logic of the target operator component and the constant content of the target constant component in the orchestration component area; and generating power generation distance audit indicators based on the field content of the data center latitude and longitude field, the field extraction logic of the power generation latitude and longitude field, the operation logic of the target operator component, and the constant content of the target constant component. The power generation distance audit indicators are used to verify whether the distance between the power generation location and the data center is acceptable, based on the data center latitude and longitude of the data center latitude and longitude field and the latitude and longitude of the power generation location in the audit data.

[0017] Secondly, embodiments of this application provide an audit indicator scheduling system, including:

[0018] The first display module is used to respond to the received indicator configuration instruction for the target business and display the indicator configuration page. The indicator configuration page includes an indicator orchestration area and an orchestration component area. The orchestration component area includes a variety of orchestration components, which include at least an operator component, a field component, and a constant component.

[0019] The component addition module is used to add at least one target component from the orchestration component area to the indicator orchestration area based on user operation information.

[0020] The indicator generation module is used to generate audit indicators based on the user's configuration information for at least one target component, and to bind the audit indicators to the target business.

[0021] The method based on the embodiments of this application provides users with an indicator configuration page with multiple orchestration components by pre-defining the corresponding logic of different orchestration components. Users can perform visual orchestration of audit indicators by selecting and configuring orchestration components, which simplifies the configuration process of audit rules, lowers the threshold for configuring audit rules, and decouples business processes from audit processes through audit rules composed of orchestration components, thereby improving the flexible configuration of audit indicators.

[0022] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application, it can be implemented according to the contents of the specification. In order to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0023] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this application. Wherein:

[0024] Figure 1 This is a flowchart illustrating an exemplary embodiment of the method for visualizing and arranging audit metrics provided in this application. Figure 1 ;

[0025] Figure 2 This is a schematic diagram of an indicator configuration page provided in an exemplary embodiment of this application;

[0026] Figure 3A This is a schematic diagram of the field configuration options provided in an exemplary embodiment of this application displayed in the orchestration component area. Figure 1 ;

[0027] Figure 3B This is a schematic diagram of the field configuration options provided in an exemplary embodiment of this application displayed in the orchestration component area. Figure 2 ;

[0028] Figure 4 This is a schematic diagram showing the type configuration options provided in an exemplary embodiment of this application in the orchestration component area;

[0029] Figure 5A This is a schematic diagram illustrating one configuration method of the arrival timeliness audit indicator provided in an exemplary embodiment of this application;

[0030] Figure 5B This is a schematic diagram illustrating another configuration method of the arrival timeliness audit indicator provided in an exemplary embodiment of this application;

[0031] Figure 6 This is a schematic diagram illustrating the configuration of power generation distance audit indicators provided in an exemplary embodiment of this application;

[0032] Figure 7This is a schematic diagram of an API configuration page provided in an exemplary embodiment of this application;

[0033] Figure 8 This is a schematic diagram of a script configuration page provided in an exemplary embodiment of this application;

[0034] Figure 9 This is a schematic diagram of another audit indicator arranged in the indicator arrangement area provided in an exemplary embodiment of this application;

[0035] Figure 10 This is a flowchart illustrating an exemplary embodiment of the method for visualizing and arranging audit metrics provided in this application. Figure 2 ;

[0036] Figure 11 This is a schematic diagram of an audit indicator arrangement system provided in an exemplary embodiment of this application;

[0037] Figure 12 This is a block diagram of an electronic device used to implement the embodiments of this application. Detailed Implementation

[0038] In the following description, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the concept or scope of this application. Therefore, the drawings and description are considered to be exemplary in nature and not restrictive.

[0039] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and all of them fall within the protection scope of the embodiments of this application.

[0040] Application scenarios

[0041] In modern enterprise production or business processes, management requirements such as "standards, execution, inspection, rewards and penalties, and improvement" are often imposed on each link. Auditing the business data generated in each process has become an indispensable task. "Standards" means clearly defining various audit indicators, which are essentially specific inspection rules. "Inspection" refers to calculating and comparing data based on actual data during execution according to established inspection rules. If the relevant data meets the inspection rules, the audit indicator is considered qualified; conversely, if it fails to meet the requirements, the audit indicator is deemed unqualified.

[0042] There are currently two main methods for defining and checking audit indicators. One is to write the audit indicator rules into paper documents or spreadsheets offline, and then manually calculate or compare them during the check. This method is inefficient and prone to errors.

[0043] Secondly, the relevant codes for audit indicators and inspection processes are hard-coded into the business process. This method is tightly coupled with the business process. Once the business process or business data changes, the relevant codes for audit indicators also need to be modified accordingly. Therefore, even if the audit rules are slightly changed, it still requires professionals with high coding knowledge to recode and configure them. Ordinary business personnel cannot make simple adjustments to the audit rules.

[0044] In addition, when new code is written manually, errors are prone to occur in the definition of audit rules. When the code related to audit indicators executes abnormally, it will also affect the normal flow of business processes.

[0045] Based on this, this application aims to provide a visual orchestration method and system for audit indicators, which can provide users with an indicator configuration page with various orchestration components. This allows users to use pre-configured orchestration components to perform visual orchestration of audit indicators, simplifying the configuration process of audit rules, lowering the threshold for changing audit rules, and enabling ordinary business personnel without coding knowledge to configure and modify audit indicators using the orchestration system. This improves the efficiency of audit indicator orchestration. In addition, the audit rules composed of orchestration components decouple the business process from the audit process, improving the flexibility of audit indicator configuration.

[0046] Exemplary methods

[0047] Figure 1 This is a flowchart illustrating a visualization arrangement method for audit indicators provided in an exemplary embodiment of this application. This embodiment can be applied to an audit indicator arrangement system, such as... Figure 1 As shown, the method includes the following steps:

[0048] Step S110: In response to receiving a metric configuration instruction for the target business, a metric configuration page is displayed. The metric configuration page includes a metric orchestration area and an orchestration component area. The orchestration component area includes a variety of orchestration components, which include at least an operator component, a field component, and a constant component.

[0049] Step S120: Based on user operation information, add at least one target component from the orchestration component area to the indicator orchestration area.

[0050] Here, the target business can be a newly added business process or an existing business process that requires new audit indicators. That is, a business can have one or more orchestrated audit indicators. When the business data corresponding to the business flows in, the business data needs to be audited based on all the audit indicators of the business, and the compliance of the business data is determined based on the audit results of each audit indicator. Users can enter indicator configuration commands in the user interface of the audit indicator orchestration system to display the indicator configuration page in the user interface.

[0051] Figure 2 This is a schematic diagram of an indicator configuration page provided in an exemplary embodiment of this application, such as... Figure 2 As shown, the left side of the indicator configuration page is the orchestration component area. This area can be further divided into operator component sections and parameter component sections. The operator component section can include various operator components such as +, -, *, / , etc., while the parameter component section can include field components (business fields) and constant components. The right side of the indicator configuration page is the indicator orchestration area. Users can select the desired orchestration components from the orchestration component area and add them to the indicator orchestration area, and then configure the added orchestration components.

[0052] In one possible implementation, step S120, based on user operation information, adds at least one target component from the orchestration component area to the indicator orchestration area, including: in response to detecting a user's selection operation on any component in the orchestration component area, adding the user-selected component as a target component to the indicator orchestration area.

[0053] Understandably, users can add target components to the indicator arrangement area by selecting various arrangement components in the arrangement component area. For example, the indicator arrangement area can pre-define component fill positions according to the arrangement order from left to right in the same row and from top to bottom between different rows. The initial state of the component fill positions is unfilled. When it is detected that a user has selected an arrangement component in the arrangement component area, that arrangement component can be filled into the first unfilled component fill position in the indicator arrangement area as the target component. Alternatively, users can first select a component fill position in the arrangement component area, and then select the target component to be filled into that component fill position in the arrangement component area.

[0054] In one possible implementation, step S120, based on user operation information, adds at least one target component from the orchestration component area to the indicator orchestration area, including: in response to detecting that the user drags any component in the orchestration component area to a specified position in the indicator orchestration area, adding that component as a target component to the indicator orchestration area.

[0055] Understandably, users can also add target components by dragging components from the orchestration component area to the indicator orchestration area. For example, when a user selects any orchestration component in the orchestration component area, a copy of that orchestration component can be generated and configured to follow the mouse pointer. The user can then drag the copy to the desired location in the indicator orchestration area and click the mouse again to place it.

[0056] This drag-and-drop component addition method allows users to more intuitively and flexibly build the logical structure of audit metrics in the metric orchestration area, quickly completing component layout and combination without writing complex code. After adding a target component, the system responds in real time and displays the added component in the metric orchestration area, facilitating subsequent configuration and adjustments. For example, when a user drags a field component to the metric orchestration area, the field component will be presented visually. The user can further click on the component to expand its configuration options, such as selecting a specific business field name, setting the field's data type, etc., thereby completing detailed configuration of the field component and laying the foundation for the subsequent generation of audit metrics.

[0057] It should be noted that the various ways of adding orchestration components to the indicator orchestration area listed above are to meet the needs of user interfaces with different operating modes (such as mouse operation and touch operation). The specific way of adding can be configured according to the actual situation, and this application is not limited thereto.

[0058] For example, after adding at least one target component from the orchestration component area to the indicator orchestration area in step S120, the user can configure the added target component in the indicator orchestration area. The following describes how... Figure 2 The configuration methods of the field component and constant component shown in the figure are explained.

[0059] Field Component: In response to at least one target component including a target field component, the field configuration options of the target field component are displayed in the orchestration component area. The field configuration options include a variety of optional business fields, which allow users to specify business fields as configuration information for the target field component.

[0060] Figure 3A This is a schematic diagram showing the field configuration options provided in an exemplary embodiment of this application displayed in the orchestration component area, as shown below. Figure 3A As shown, you can select the specified business field of the target component from various business fields such as "protection level", "alarm information" and "fault occurrence time" through the drop-down list of field configuration options. Based on this configuration, the target component actually represents the specified business field that needs to be extracted from the business data during data auditing.

[0061] In one possible implementation, such as Figure 3B As shown, the configuration of field components can also include variable attributes for specified business fields. For example, variable attributes can be set to characters, minutes, hours, timestamps, etc. In certain specific business scenarios with data stamps, the time range of the extracted business fields can also be specified, thereby limiting the function represented by the target component to extract specified business fields within the specified time range.

[0062] Constant Component: In response to at least one target component including a target constant component, type configuration options associated with the target constant component are displayed in the orchestration component area. The type configuration options include a variety of optional constant types, which allow the user to specify the constant type of the input content in the target constant component from among the various optional constant types.

[0063] The constant component works in conjunction with the logical operator component and the field component to form audit metrics. The constant component can be used to input constant content, such as characters or numbers. Figure 4 This is a schematic diagram showing the type configuration options provided in an exemplary embodiment of this application in the orchestration component area, as follows: Figure 4 As shown, the data format of the input information in the constant component can be configured as character, time format, number format with decimal point, etc.

[0064] Step S130: Generate audit metrics based on the user's configuration information for at least one target component, and bind the audit metrics to the target business.

[0065] Here, after completing the orchestration and configuration of each target component in the indicator orchestration area, the user can issue an audit indicator generation command to the audit indicator orchestration system. This allows the system to generate audit indicators based on the orchestration and corresponding logic of each target component in the indicator orchestration area, and bind the newly generated audit indicators to the target business. After receiving the business data of the target business, the audit indicator can then be used to audit the business data.

[0066] For example, in step S130, generating audit metrics based on the user's configuration information for at least one target component includes: determining the extraction logic of specified business fields in each target field component according to the user's configuration information for each target field component and the pre-stored data dictionary, wherein the data dictionary predefines extraction logic for multiple optional business fields; generating audit metrics based on the extraction logic of specified business fields in each target field component and the component content of other orchestration components in the orchestration component area, wherein other orchestration components include field components and / or constant components.

[0067] Understandably, since the fields in business data can be predetermined, the data dictionary can pre-write corresponding extraction code for each field based on its characteristics within the corresponding business data (such as the field's hierarchy in nested data structures and its name). Therefore, after the user configures the target field component in the metric orchestration area, the system can determine the extraction logic for the specified business field within the target field component based on the user's configuration information and the data dictionary.

[0068] Since the operator components correspond to different operation logics based on different types of operators, after determining the extraction logic of the specified business fields in each field component, audit indicators can be generated based on the extraction logic of the specified business fields and the operation logic of the target operator component.

[0069] It should be noted that, in the above embodiments, the audit indicators can be composed of a single field component, indicating that the business data needs to be verified to contain the business field specified by the field component; the audit indicators can also be constructed by field components and operator components, for example, configuring the audit indicator as the value of a certain business field is less than the value of another business field; the audit indicators can also be constructed by field components, constant components and operator components, defining the audit indicators by constructing the logical relationship between the specified business field and the constant.

[0070] This visual component orchestration approach allows users to intuitively build audit indicator logic that meets business needs without writing complex code. For example, in a financial data audit scenario, users can select "Field Components," "Greater Than Operator Components," and "Constant Components" from the orchestration component area. After adding these three components to the indicator orchestration area, configuring the "Field Components" to associate with the "Transaction Amount" field in the financial data, and setting the value of the "Constant Components" to 10000, the basic audit indicator "Transaction Amount > 10000" can be quickly generated, enabling automatic screening of large transactions. For more complex multi-condition combination scenarios, users can also add more logical operator components (such as AND, OR, etc.) to logically associate multiple basic indicators, forming composite audit rules such as "Transaction Amount > 10000 AND Transaction Time During Non-Working Hours." The system will automatically parse and generate the corresponding audit calculation logic based on the logical relationships between components, ensuring the accuracy and executability of the audit indicators.

[0071] In some embodiments, step S130, which generates audit indicators based on the user's configuration information for at least one target component, includes: in an arrival timeliness audit scenario, determining the extraction logic of fields in a target field component, the target field component including an arrival time field component and a departure time field component; determining the operation logic of a target operator component and the constant content of a target constant component in the orchestration component area; and generating arrival timeliness audit indicators based on the extraction logic of fields in the target field component, the operation logic of the target operator component, and the constant content of the target constant component; wherein, the arrival timeliness audit indicators are used to verify whether the time difference between the arrival time and the departure time in the audit data is qualified.

[0072] For example, in a logistics and delivery business scenario, users can add "Departure Time" and "Arrival Time" field components on the indicator configuration page, link them using the "-" operator component, add a "Constant Component" and set its value to "24" (in hours), and then select the "≤" operator component to connect the time difference calculation result with the constant component. This generates an arrival timeliness audit indicator of "Arrival Time - Departure Time ≤ 24 hours". When the logistics data to be audited flows into the system, the system automatically extracts the departure and arrival time fields from each data entry, calculates the time difference between the two, and compares it with the constant 24 hours. If the time difference exceeds 24 hours, an audit alarm is triggered, thereby achieving automated monitoring of logistics and delivery timeliness.

[0073] Figure 5A This is a schematic diagram illustrating a configuration method for arrival timeliness audit indicators provided in an exemplary embodiment of this application, such as... Figure 5A As shown, the indicator orchestration area includes two field components, one constant component, and one operator component. The specified business fields corresponding to the two field components are "Arrival Time" and "Departure Time". The constant component has a user-input constant of "30". The operator component uses the less than or equal to operator. Assuming the user configures the constant unit in this constant component to be "minutes", based on... Figure 5A The arrangement shown here means that "if the arrival time is less than or equal to (departure time + 30 minutes), the audit result is satisfactory".

[0074] In some embodiments, in addition to the inherent operator, field, and constant components in the orchestration component area, corresponding audit components can also be additionally configured in the orchestration component for some common audit scenarios, such as... Figure 2 The time addition / subtraction component and latitude / longitude distance calculation component are shown in the figure.

[0075] For example, time-based audit metrics can also be configured using time-addition / subtraction components, such as... Figure 5BAs shown, the indicator orchestration area includes a field component, an operator component, and a time addition / subtraction component. The field component specifies the "arrival time" as the designated business field. The operator component uses the less than or equal to operator. The time addition / subtraction component can also specify a business field, for example... Figure 5B The specified business field for the time adjustment component is "departure time". The component also allows configuration of variable attributes for the specified business field and the time adjustment value. For example, if the time adjustment component is configured as "departure time + 30 minutes", then... Figure 5B The audit indicators formed in the process also mean that "if the arrival time is ≤ (departure time + 30 minutes), then the audit result is qualified," which is... Figure 5B Audit indicators and Figure 5A Although the configuration methods for the audit indicators in the two systems are different, the audit rules are essentially the same.

[0076] This approach, which uses pre-defined components for common scenarios, further lowers the barrier to entry for orchestrating complex audit logic and improves user efficiency. For example, in the timeliness audit scenario of logistics and delivery, users no longer need to manually combine departure time fields, time constants, and addition operators. They can quickly complete rule building by directly selecting the time addition / subtraction component and configuring relevant parameters, reducing the steps of component selection and logic assembly. At the same time, the introduction of these scenario-based components makes the logical expression of audit indicators more intuitive and easy to understand. Even business personnel without a technical background can quickly understand the business meaning represented by the indicators, reducing communication costs in cross-departmental collaboration. Furthermore, the system supports the extension function of custom components. Business personnel can encapsulate commonly used component combination logic into new custom components based on their unique audit needs and save them to the orchestration component area for subsequent reuse, further enhancing the system's flexibility and adaptability to meet the diverse audit indicator orchestration needs of different industries and business models.

[0077] In some embodiments, step S130, which generates audit indicators based on the user's configuration information for at least one target component, further includes: in a power generation distance audit scenario, determining the field content of the data center latitude and longitude field in the latitude and longitude distance calculation component and the field extraction logic of the power generation latitude and longitude field; determining the operation logic of the target operator component and the constant content of the target constant component in the orchestration component area; generating power generation distance audit indicators based on the field content of the data center latitude and longitude field, the field extraction logic of the power generation latitude and longitude field, the operation logic of the target operator component, and the constant content of the target constant component; wherein, the power generation distance audit indicators are used to verify whether the distance between the power generation location and the data center is qualified based on the data center latitude and longitude of the data center latitude and longitude field and the latitude and longitude of the power generation location in the audit data.

[0078] For example, users can add a latitude and longitude distance calculation component on the indicator configuration page. This component will automatically associate with the preset "data center latitude and longitude" field. Users also need to configure another field component as the extraction field for "power generation latitude and longitude". Next, add a "constant component" and set its value to "500" (in meters). Select the "≤" operator component to connect the latitude and longitude distance calculation result with the constant component. This will generate the power generation distance audit indicator "the distance between the power generation location and the data center is ≤ 500 meters". When the system receives the power generation data to be audited, it will automatically calculate the actual straight-line distance between the power generation location's latitude and longitude and the data center's latitude and longitude using the built-in geographic distance algorithm of the latitude and longitude distance calculation component. This distance will be compared with the constant 500 meters. If the distance exceeds the threshold, the power generation location is determined to be non-compliant with the safe distance requirement, triggering the corresponding audit warning mechanism so that relevant personnel can intervene promptly.

[0079] Figure 6 This is a schematic diagram illustrating the configuration of power generation distance audit indicators provided in an exemplary embodiment of this application, as shown below. Figure 6 As shown, the indicator arrangement area includes an operator component, a constant component, and a latitude and longitude distance calculation component. The latitude and longitude distance calculation component can set latitude and longitude scenarios, such as field content being longitude or latitude, field content being longitude and latitude, or field content being an image containing latitude and longitude, etc., thereby extracting content containing longitude and / or dimensions from the data to be audited by setting the latitude and longitude scenario configuration.

[0080] In the latitude and longitude distance calculation component, the current latitude and longitude can be set to the latitude and longitude of the computer room. The target latitude and longitude is the latitude and longitude at which power generation begins (i.e., the latitude and longitude field to be extracted from the data to be audited). The operator component uses the less than or equal to operator, and the value in the constant component is "200". Assuming the user configures the constant unit in this constant component to "meters", then... Figure 6 The meaning of the power generation distance audit index is that "if the distance between the latitude and longitude of the power generation location and the latitude and longitude of the generator room is less than or equal to 200 meters, the audit result is qualified."

[0081] Through the latitude and longitude distance calculation component, the system can automatically extract the corresponding latitude and longitude information from business data according to the configured latitude and longitude scenario, and calculate the actual distance by combining it with the latitude and longitude of the data center. For example, when the latitude and longitude fields in the data to be audited are stored in nested JSON format, the component can accurately extract the values ​​according to the predefined field hierarchy path in the data dictionary; if the latitude and longitude information is contained in the EXIF ​​data of an image, the component calls a dedicated parsing tool to read the relevant parameters. The application of this scenario-based component not only simplifies the orchestration process of complex geospatial calculation logic, but also ensures the accuracy and consistency of distance calculation. During the configuration process, users do not need to pay attention to the details of the underlying algorithm implementation; they can complete the definition of audit rules simply through intuitive parameter settings, which greatly reduces the usage threshold for business personnel. After the user completes the configuration of all components, the system will automatically compare the latitude and longitude distance calculation results with the thresholds set by the constant components to generate the final audit judgment results, and supports real-time display of intermediate parameters in the calculation process (such as the extracted latitude and longitude values ​​and distance calculation results) in the indicator orchestration area, which is convenient for users to verify rules and troubleshoot problems.

[0082] In practical business applications, this component-based visual orchestration mode can significantly improve the reusability of audit rules. When different business scenarios have similar audit logic, users can save the configured audit indicators as templates and directly call and fine-tune the component parameters when configuring new business scenarios, avoiding repetitive work. For example, in the e-commerce order audit scenario, the audit indicator structures of "order amount > 5000" and "refund amount > 3000" are similar. Users can reuse the combined template of "field component + operator component + constant component". They only need to modify the value of the constant component and the business field associated with the field component to quickly complete the configuration of new indicators, which greatly shortens the cycle of building audit rules in new business scenarios. At the same time, the system will perform real-time verification of the component logic configured by the user. If a logical conflict is detected between components (such as the data type of the field component not matching that of the operator component), the system will immediately notify the user through pop-up windows or red prompts to help the user correct the error in time, further reducing the error rate of manual configuration and ensuring that the generated audit indicators can accurately reflect the business rules.

[0083] The method in this embodiment provides users with an indicator configuration page with multiple orchestration components by pre-defining the corresponding logic of different orchestration components. Users can perform visual orchestration of audit indicators by selecting and configuring orchestration components, which simplifies the configuration process of audit rules, lowers the threshold for configuring audit rules, and decouples business processes from audit processes through audit rules composed of orchestration components, thereby improving the flexible configuration of audit indicators.

[0084] In one possible implementation, such as Figure 2As shown, the orchestration component area also includes an extension component area, which includes API components and script components. After adding at least one target component from the orchestration component area to the indicator orchestration area in step S120, the user can configure the added target component in the indicator orchestration area. The following describes the configuration of the target component. Figure 2 The configuration methods for API components and script components are illustrated below:

[0085] API Component: In response to at least one target component including a target API component, the API configuration page of the target API component is displayed in the orchestration component area. The API configuration page is used to configure a specified API address and the business fields sent to the specified API address. The specified API address configured by the user in the API configuration page and the business fields sent to the specified API address are determined as the user's configuration information for the target API component.

[0086] Understandably, for some complex and frequently used processing logic, in order to reduce the computational burden on the system, such operations are often placed in external systems or external services. Figure 7 The diagram shows an API configuration page. The API component can be a special component in which users can configure the API address and specify business fields. The role of this API component in audit metrics is to extract specified fields from the data to be audited and send the specified fields to the configured API address, thereby calling the external service corresponding to the API address to process based on the specified fields.

[0087] For example, in financial risk control and auditing scenarios, when it's necessary to call the credit scoring interface of an external credit reporting system, users can enter the API address of that system in the API component's configuration page and specify business fields such as "user ID number" and "name" to be sent. When the system executes audit indicators, it automatically extracts these specified fields from the business data, encapsulates them into request parameters according to a preset format, and sends them to the configured API address. After receiving the credit scoring results returned by the external service, it then uses these results as part of the audit indicators in subsequent logical calculations, such as "a risk warning is triggered if the credit score is <600". This approach allows the audit system to flexibly integrate external professional service capabilities, expands the business coverage of audit indicators, and avoids repeatedly developing complex algorithms within the system, thus improving overall audit efficiency.

[0088] In this embodiment, the API component can configure some complex logic processing to be executed by external services, simplifying the computational logic required in the system and reducing the system's computational pressure. External services can be reflected in different audit indicators in the form of API components, thereby further supporting the flexible configuration of audit indicators.

[0089] Script Component: In response to at least one target component including a target script component, the script configuration page of the target script component is displayed in the orchestration component area. The script configuration page includes a parameter configuration area and a script editing area. The parameter configuration area is used to configure custom parameters using at least one business field, and the script editing area is used to input script code containing custom parameters. The custom parameters configured by the user in the script editing area and the script code entered by the user in the parameter configuration area are determined as the user's configuration information for the target script component.

[0090] Understandably, for audit metrics that are difficult to form simply by combining operator components and field components, this application also provides a special orchestration method. That is, a coded script component can be introduced on the basis of orchestration components such as operator components and character components that do not require coding. In this way, users can input script codes in the script component to form the corresponding audit logic, and then combine it with the corresponding logic in other orchestration components to form audit metrics.

[0091] Figure 8 This is a schematic diagram of a script configuration page provided in an exemplary embodiment of this application, such as... Figure 8 As shown, the upper area of ​​the script configuration page is the parameter configuration area. In this area, business fields can be specified to form custom parameters, which can then be named. The script editing area can then utilize these custom parameters in conjunction with the Java programming language for coding. For example, Figure 8 In the parameter configuration area, you can specify business fields such as photo watermark time and oil collector time, and name them by parameter name to form custom parameters. Then, in the script editing area, you can enter custom parameters in the programming language to implement the reference of business fields, and define the processing logic of these business fields through the programming language.

[0092] In one possible implementation, when the target component in the indicator orchestration area is a script component, audit indicators are generated based on the user's configuration information for at least one target component. This includes: determining the extraction logic of business fields in each custom parameter according to the configuration information of each custom parameter in the parameter configuration area and the pre-stored data dictionary; and generating audit indicators according to the extraction logic of business fields in each custom parameter and the script code in the script editing area.

[0093] Here, the business fields corresponding to each parameter can be obtained based on the configuration information of the custom parameters, and the extraction logic of these business fields can be obtained by combining the data dictionary. The script editing area contains the script code of the custom parameters, which actually contains the processing logic of the business fields corresponding to the custom parameters. Therefore, audit indicators can be generated based on the extraction logic of the business fields in the custom parameters and the script code in the script editing area.

[0094] For example, for audit indicators that test the correctness of power generation scenarios, the script code in the script editing area can be:

[0095]

[0096]

[0097] The audit logic corresponding to the audit indicators for verifying the correctness of the power generation scenario includes:

[0098] (1) Initialization and log output

[0099] First, a prompt message indicating the start of the test is printed, along with a list of photos (oilPhotos) of the generator and the current power generation scene type (sceneType). These logs are used to track the test process and for debugging.

[0100] (2) Core logical variables

[0101] Define a variable `temp` and initialize it to `true`, which will serve as a flag for the final detection result (`true` indicates a successful detection, `false` indicates a failed detection).

[0102] (3) Image traversal and detection

[0103] Loop through each image in oilPhotos, print the current image's ID (fileId) and type (fileType), and reset the image's isShow property (used to control the image's display status on the interface).

[0104] (4) Scene-specific detection logic

[0105] Scenario 1: "Send Module" Detection

[0106] When the scene type is "Power Module" and the image type is "Photo of Switching Power Supply Wiring Connection":

[0107] Call the AI ​​model function faBoxModelOutFunction, pass in the image ID and the parameter class_name, get the scene type result of AI analysis, set the image isShow to '1' (indicating that the image needs to be displayed), record the scene type of AI analysis to the sceneTypeAI property, print the AI ​​analysis result, and if the analysis result does not match the expected scene type (sceneType), set temp to false.

[0108] Scenario 2: "Publish Box" Detection

[0109] When the scene type is "Publish Box" and the image type is "Power Supply / Meter Box Wiring Photo", a similar detection process as described above is executed. The AI ​​model function faBoxModelOutFunction is called, passing in the image ID and the parameter class_name, to obtain the scene type result of AI analysis, setting the image isShow to '1' (indicating that the image needs to be displayed), recording the scene type of AI analysis to the sceneTypeAI attribute, and printing the AI ​​analysis result. If the analysis result does not match the expected scene type (sceneType), then temp is set to false.

[0110] (5) Return results

[0111] After the loop ends, the value of the temp variable is returned as the final result of the entire scene detection.

[0112] It should be noted that audit indicators can be constructed independently using script components, or they can be constructed by combining script code with other components. Figure 9 This is a schematic diagram of another audit indicator arranged in the indicator arrangement area provided in an exemplary embodiment of this application, such as... Figure 9 As shown, the indicator arrangement area contains a script component "Script1", a field component "Arrival Time" and a constant component "30". Assuming that the user configures the constant unit in the constant component to "minutes", the meaning of the audit indicator constructed by these components and the operator component is that if (the calculation result of Script1 + 30 minutes) ≤ arrival time, then the audit result is qualified.

[0113] In this embodiment, since the script component can support the orchestration of complex audit logic, the audit indicator orchestration system can support the no-code orchestration of simple audit logic through components such as operators, constants and fields, and can also supplement the orchestration capability of complex audit logic through the script component, thereby improving the applicability and scalability of the audit indicator orchestration system.

[0114] The method described in this embodiment, by setting API components and script components in the extended component area, enables the audit indicator orchestration system to maintain ease of use while possessing strong scalability and flexibility. Whether connecting to external services through API components or writing custom logic using script components, it breaks the limitations of the traditional fixed component model, allowing users to flexibly choose the appropriate orchestration method based on the actual business complexity. For business personnel with weaker technical backgrounds, basic and scenario-based components can be used to quickly build routine audit indicators; while for technically capable users or those handling complex business logic, API and script components can be used to achieve more advanced customization needs, thus achieving a balance between efficiency and flexibility across different user groups and business scenarios. Furthermore, the system supports version management of extended component configuration information. Users can save API configurations or script code versions from different periods, and perform version rollback or comparative analysis when needed, facilitating the tracking of configuration change history and ensuring the traceability and standardized management of audit indicator logic.

[0115] In one possible implementation, audit indicators can be divided into positive indicators and negative indicators, such as... Figure 2 As shown, the lower part of the indicator arrangement area also includes audit result configuration options. This allows you to configure whether the audit result is qualified or unqualified when the audit indicators are met. If the configuration shows that the verification result is qualified when the audit indicators are met, then the audit indicator is a positive indicator, as shown in Figure 5. Figure 9 All audit indicators in the system are positive audit indicators. If the audit rules corresponding to the audit indicator are met, the audit result of the business data for that audit indicator is considered qualified. If the verification result is unqualified when the audit indicator is met, it can be understood that the verification result is unqualified only when the business data meets the audit indicator, and the verification result is qualified in all other cases.

[0116] For example, in a logistics delivery timeliness audit scenario, if "delivery overdue > 2 hours" is set as a reverse indicator, then when business data meets this audit rule, the system determines the audit result of that delivery as unqualified, while delivery overdue less than 2 hours is automatically judged as qualified. This flexible configuration of positive and negative indicators allows the audit system to accurately adapt to the definition requirements of "qualified" and "unqualified" in different business scenarios, further enhancing the alignment between audit rules and actual business logic. During configuration, users can directly switch indicator types through the audit result configuration options according to business objectives, without adjusting the logical relationships between components, greatly simplifying the process of building audit indicators for different judgment criteria. Simultaneously, when displaying audit results, the system clearly labels the indicator type (positive / reverse), helping users quickly understand the judgment logic of the audit rules and avoiding misjudgments due to confusion about indicator types.

[0117] In one possible implementation, such as Figure 10 As shown, the visualization and arrangement method for audit indicators provided in this application also includes:

[0118] Step S1001: In response to receiving an indicator management instruction for the target business, display an indicator management page associated with the target business. The indicator management page includes at least one audit indicator bound to the target business.

[0119] Step S1002: In response to the detection of a deletion command for any audit indicator in the indicator management page, the audit indicator is unbound from the target business.

[0120] Step S1003: In response to detecting an editing instruction for any audit indicator in the indicator management page, the indicator editing page for that audit indicator is displayed, and the indicator editing page includes at least one orchestration component corresponding to that audit indicator.

[0121] Here, the target business can be a business process with configured audit metrics. Since a business can have multiple audit metrics, this application can... Figure 1 The steps in the process involve adding audit indicators to existing business processes. Alternatively, the indicator management command can be used to display the indicator management page for the target business, allowing for the management of existing audit indicators.

[0122] Understandably, if a certain audit indicator for the target business is no longer needed, it can be deleted from the indicator management page. This will unbind the indicator from the target business, and the corresponding audit process will not be executed when business data is received from the target business subsequently. If a certain audit indicator for the target business needs to be changed, and the changes between the changed and original indicators are minor, the original indicator can be edited directly. The audit editing page is similar to the indicator configuration page, including an indicator arrangement area and an arrangement component area. The difference is that when the indicator configuration page is initially displayed, the indicator arrangement area does not contain any configured arrangement components; while when the audit editing page is initially displayed, the indicator arrangement area contains the configured arrangement components for that audit indicator, allowing users to edit and modify the original audit indicator.

[0123] In this embodiment, the audit indicator orchestration system has been enhanced with the ability to manage the configured audit indicators. The audit indicators can be changed according to the changing needs of the audit rules, decoupling the business process from the audit process and further improving the configuration flexibility of the audit indicators.

[0124] The specific settings and implementation methods of the embodiments of this application have been described above from different perspectives. Using the methods provided in the above embodiments, by pre-defining the corresponding logic of different orchestration components, a metric configuration page with multiple orchestration components is provided to the user. Users can perform visual orchestration of audit metrics by selecting and configuring orchestration components, simplifying the configuration process of audit rules, lowering the threshold for audit rule configuration, and decoupling business processes from audit processes through audit rules composed of orchestration components, thereby improving the flexible configuration of audit metrics.

[0125] Exemplary System

[0126] As an implementation of the above methods, such as Figure 11 As shown in the embodiments of this application, an audit indicator arrangement system is also provided, including:

[0127] The first display module 1101 is used to display an indicator configuration page in response to receiving an indicator configuration instruction for the target business. The indicator configuration page includes an indicator arrangement area and an arrangement component area. The arrangement component area includes a variety of arrangement components, which include at least an operator component, a field component, and a constant component.

[0128] The component adding module 1102 is used to add at least one target component from the orchestration component area to the indicator orchestration area based on user operation information.

[0129] The indicator generation module 1103 is used to generate audit indicators based on the user's configuration information for at least one target component, and to bind the audit indicators to the target business.

[0130] In one possible implementation, the component adding module 1102 is further configured to: in response to detecting a user's selection operation on any component in the orchestration component area, add the user-selected component as the target component to the indicator orchestration area; or, in response to detecting a user dragging any component in the orchestration component area to a specified position in the indicator orchestration area, add that component as the target component to the indicator orchestration area.

[0131] In one possible implementation, the indicator generation module 1103 is further configured to: in response to the target component being a field component, display the field configuration options of the target component in the orchestration component area, wherein the field configuration options are used to select a specified business field of the target component from a variety of business fields; and determine the specified business field as the user's configuration information for the target component.

[0132] In one possible implementation, the target component includes a target operator component and a target field component. The indicator generation module 1103 is further used to: determine the extraction logic of the specified business field of each target field component based on the user's configuration information for each target field component and the pre-stored data dictionary, wherein the data dictionary predefines the extraction logic of multiple business fields; and generate audit indicators based on the extraction logic of the specified business fields of each target field component and the corresponding operation logic of each target operator component.

[0133] In one possible implementation, the various orchestration components also include an API component, and the metric generation module 1103 is further configured to: in response to the target component being an API component, display the API configuration page of the target component in the orchestration component area, wherein the API configuration page is used to configure a specified API address and a specified business field sent to the specified API address; and determine the specified API address and the specified business field as the user's configuration information for the target component.

[0134] In one possible implementation, the orchestration components also include script components, and the indicator generation module 1103 is further configured to: in response to the target component being a script component, display the script configuration page of the target component in the orchestration component area, the script configuration page including a script editing area and a parameter configuration area, the parameter configuration area being used to configure custom parameters using at least one business field, and the script editing area being used to input script code containing custom parameters; and determine the user's configuration information for the target component based on the custom parameters in the script editing area and the script code in the parameter configuration area.

[0135] In one possible implementation, the target component includes a target script component, and the indicator generation module 1103 is further used to: determine the extraction logic of the business fields in each custom parameter based on the configuration information of each custom parameter in the parameter configuration area and the pre-stored data dictionary; and generate audit indicators based on the extraction logic of the business fields in each custom parameter and the script code in the script editing area.

[0136] In one possible implementation, the indicator generation module 1103 is further configured to: in response to the target component being a constant component, display type configuration options associated with the target component in the orchestration component area, the type configuration options being used to configure the data format of the input information in the associated target component; and determine the user's configuration information for the target component based on the input information in the target component and the input information in the type configuration options.

[0137] In one possible implementation, the system further includes a second display module, which, in response to receiving an indicator management instruction for the second business, displays an indicator management page associated with the second business, the indicator management page including at least one audit indicator bound to the second business;

[0138] The indicator editing module is used to unbind the audit indicator from the second business in response to the detection of a deletion command for any audit indicator in the indicator management page; and to display the indicator editing page for the audit indicator in response to the detection of an editing command for any audit indicator in the indicator management page, wherein the indicator editing page includes at least one orchestration component corresponding to the audit indicator.

[0139] In one possible implementation, the indicator generation module 1103 is further configured to: determine the extraction logic of fields in the target field component in the arrival timeliness audit scenario, the target field component including arrival time field component and departure time field component; determine the operation logic of the target operator component and the constant content of the target constant component in the orchestration component area; and generate arrival timeliness audit indicators based on the extraction logic of fields in the target field component, the operation logic of the target operator component, and the constant content of the target constant component; wherein, the arrival timeliness audit indicators are used to verify whether the time difference between the arrival time and departure time in the data to be audited is qualified.

[0140] In one possible implementation, the various orchestration components also include a latitude and longitude distance calculation component. The indicator generation module 1103 is further used to: determine the field content of the latitude and longitude field of the computer room in the latitude and longitude distance calculation component and the field extraction logic of the latitude and longitude field of the power generation; determine the operation logic of the target operator component and the constant content of the target constant component in the orchestration component area; generate a power generation distance audit indicator based on the field content of the computer room latitude and longitude field, the field extraction logic of the power generation latitude and longitude field, the operation logic of the target operator component, and the constant content of the target constant component; wherein, the power generation distance audit indicator is used to verify whether the distance between the power generation location and the computer room is qualified based on the latitude and longitude of the computer room in the latitude and longitude field and the latitude and longitude of the power generation location in the data to be audited.

[0141] The functions of each unit, module, or sub-module in the embodiments of this application can be found in the corresponding descriptions in the above method embodiments, and they have corresponding beneficial effects, which will not be repeated here.

[0142] Exemplary electronic devices and computer-readable storage media

[0143] Figure 12 This is a block diagram of an electronic device used to implement embodiments of this application. Figure 12 As shown, the electronic device includes a memory 1201 and a processor 1202. The memory 1201 stores a computer program that can run on the processor 1202. When the processor 1202 executes the computer program, it implements the method described in the above embodiments. The number of memories 1201 and processors 1202 can be one or more.

[0144] The electronic device also includes:

[0145] The communication interface 1203 is used to communicate with external devices and exchange and transmit data.

[0146] If the memory 1201, processor 1202, and communication interface 1203 are implemented independently, they can be interconnected via a bus to communicate with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 12 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0147] Optionally, in a specific implementation, if the memory 1201, processor 1202, and communication interface 1203 are integrated on a single chip, then the memory 1201, processor 1202, and communication interface 1203 can communicate with each other through an internal interface.

[0148] This application also provides a chip including a processor for calling and executing instructions stored in a memory, causing a communication device with the chip installed to perform the method provided in this application.

[0149] This application also provides a chip, including: an input interface, an output interface, a processor, and a memory. The input interface, output interface, processor, and memory are connected through an internal connection path. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method provided in this application.

[0150] It should be understood that the aforementioned processor can be a CPU, or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting Advanced Reduced Instruction Set Machines (ARM) architecture.

[0151] Further, optionally, the aforementioned memory may include read-only memory and random access memory. The memory may be volatile memory or non-volatile memory, or may include both. Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available. Examples include Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0152] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions according to this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.

[0153] In addition to the methods and apparatus described above, embodiments of this disclosure may also provide a computer program product, including computer program instructions that, when executed by a processor, cause the processor to perform the steps of the image processing methods of the various embodiments of this disclosure described in the "Exemplary Methods" section above.

[0154] Computer program products can be written in any combination of one or more programming languages ​​to perform the operations of embodiments of this disclosure. These programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0155] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.

[0156] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0157] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functionality involved.

[0158] The logic and / or steps described in the flowchart or otherwise herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a processor-included system or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0159] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware, the program being stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiments.

[0160] Furthermore, the functional units in the various embodiments of this application can be integrated into a single processing module, or each unit can exist physically separately, or two or more units can be integrated into a single module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. This storage medium can be a read-only memory, a disk, or an optical disk, etc.

[0161] The above description is merely an exemplary embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope described in this application, and these should all be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for visualizing and arranging audit indicators, characterized in that, include: In response to receiving a metric configuration instruction for a target business, a metric configuration page is displayed. The metric configuration page includes a metric orchestration area and an orchestration component area. The orchestration component area includes a variety of orchestration components, which include at least an operator component, a field component, and a constant component. Based on user operation information, at least one target component is added from the orchestration component area to the indicator orchestration area; Audit metrics are generated based on the user's configuration information for at least one target component, and the audit metrics are bound to the target business.

2. The method according to claim 1, characterized in that, The step of adding at least one target component from the orchestration component area to the indicator orchestration area based on user operation information includes: In response to detecting a user's selection of any component in the orchestration component area, the user-selected component is added to the indicator orchestration area as the target component; Alternatively, in response to detecting that a user drags any component in the orchestration component area to a specified position in the indicator orchestration area, the component is added to the indicator orchestration area as the target component.

3. The method according to claim 1, characterized in that, After adding at least one target component from the orchestration component area to the index orchestration area, the method further includes: In response to the inclusion of a target field component in the at least one target component, field configuration options for the target field component are displayed in the orchestration component area. The field configuration options include a variety of optional business fields, which allow the user to specify a business field from the variety of optional business fields as configuration information for the target field component.

4. The method according to claim 3, characterized in that, The generation of audit metrics based on user configuration information for the at least one target component includes: Based on the user's configuration information for each target field component and the pre-stored data dictionary, the extraction logic for the specified business fields in each target field component is determined. The data dictionary predefines the extraction logic for the various optional business fields. Audit metrics are generated based on the extraction logic of the specified business fields in each of the target field components and the component content of other orchestration components in the orchestration component area, wherein the other orchestration components include field components and / or constant components.

5. The method according to claim 1, characterized in that, The multiple orchestration components also include API components. After adding at least one target component from the orchestration component area to the indicator orchestration area, the method further includes: In response to the inclusion of a target API component in the at least one target component, an API configuration page for the target API component is displayed in the orchestration component area. The API configuration page is used to configure a specified API address and the business fields sent to the specified API address. The specified API address configured by the user in the API configuration page, along with the business fields sent to the specified API address, are determined as the user's configuration information for the target API component.

6. The method according to claim 1, characterized in that, The multiple orchestration components also include script components. After adding at least one target component from the orchestration component area to the indicator orchestration area, the method further includes: In response to the inclusion of a target script component in the at least one target component, a script configuration page for the target script component is displayed in the orchestration component area. The script configuration page includes a parameter configuration area and a script editing area. The parameter configuration area is used to configure custom parameters using at least one business field, and the script editing area is used to input script code containing the custom parameters. The custom parameters configured by the user in the script editing area and the script code entered by the user in the parameter configuration area are determined as the user's configuration information for the target script component.

7. The method according to claim 6, characterized in that, The generation of audit metrics based on user configuration information for the at least one target component includes: Based on the configuration information of each custom parameter in the parameter configuration area and the pre-stored data dictionary, determine the extraction logic of the business fields in each custom parameter; Audit metrics are generated based on the extraction logic of the business fields in each of the custom parameters and the script code in the script editing area.

8. The method according to claim 1, characterized in that, The generation of audit metrics based on user configuration information for the at least one target component includes: In the scenario of arrival timeliness audit, the extraction logic of fields in the target field component is determined, and the target field component includes an arrival time field component and a departure time field component; Determine the computational logic of the target operator component and the constant content of the target constant component in the orchestration component area; Based on the extraction logic of the fields in the target field component, the operation logic of the target operator component, and the constant content of the target constant component, an arrival timeliness audit indicator is generated; wherein, the arrival timeliness audit indicator is used to verify whether the time difference between the arrival time and the departure time in the data to be audited is qualified.

9. The method according to claim 1, characterized in that, The various orchestration components also include a latitude and longitude distance calculation component, and the generation of audit indicators based on the user's configuration information for the at least one target component includes: In the scenario of power generation distance audit, the field content of the latitude and longitude field of the computer room and the field extraction logic of the power generation latitude and longitude field in the latitude and longitude distance calculation component are determined; Determine the computational logic of the target operator component and the constant content of the target constant component in the orchestration component area; Based on the field content of the data center latitude and longitude field, the field extraction logic of the power generation latitude and longitude field, the operation logic of the target operator component, and the constant content of the target constant component, a power generation distance audit index is generated; wherein, the power generation distance audit index is used to verify whether the distance between the power generation location and the data center is qualified based on the data center latitude and longitude of the data center latitude and longitude field and the latitude and longitude of the power generation location in the audit data.

10. An audit indicator scheduling system, characterized in that, The system includes: The first display module is used to display an indicator configuration page in response to receiving an indicator configuration instruction for a target business. The indicator configuration page includes an indicator arrangement area and an arrangement component area. The arrangement component area includes a variety of arrangement components, which include at least an operator component, a field component, and a constant component. The component adding module is used to add at least one target component from the orchestration component area to the indicator orchestration area based on user operation information. The indicator generation module is used to generate audit indicators based on the user's configuration information for the at least one target component, and to bind the audit indicators to the target business.

Images