Application review methods, apparatuses, computing devices, and media

Abstract

The present disclosure provides an application auditing method, which can be applied to the financial field or other fields. The application auditing method comprises: obtaining an auditing flow table, the auditing flow table comprising an auditing flow table generated in response to a user application; determining an auditing result of the auditing flow table in response to receiving an auditing request for the auditing flow table; determining an auditing scenario based on the auditing flow table in the case that the auditing result is not completed; auditing the auditing flow table to obtain an updated auditing flow table in the case that the auditing scenario is determined; and re-determining the auditing result of the updated auditing flow table in response to receiving an auditing request for the updated auditing flow table. The present disclosure also provides an application auditing device, equipment, storage medium and program product.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the field of finance, in particular to the field of credit card, and more particularly to an application auditing method, an application auditing device, a computing device, a computer readable storage medium and a computer program product. BACKGROUND

[0002] In the related art, a user can apply for a credit card through various channels, but the application process needs to be completed in three to seven working days, and after the audit is completed, there is a card making and card mailing process, and if it involves a joint card, the interaction between the joint card and the joint merchant needs more time, even if the UnionPay no boundary card is audited quickly on the same day, it may not be approved quickly. These phenomena reflect the low timeliness of credit card application.

[0003] Various abnormal situations may occur during the credit card audit process, making the audit process more slow. For the audit end, the audit system cannot process abnormal data, and continuous error data will affect the audit speed of the system and cause the audit state to be inconsistent; for the applicant, if the application result is not received for a long time, a complaint may be initiated, and subsequent re-application may be directly rejected due to the existence of the same card, affecting the user experience. SUMMARY

[0004] In view of the above problems, the present disclosure provides an application auditing method, device, equipment, medium and program product to ensure the robustness of the system.

[0005] According to a first aspect of the present disclosure, an application auditing method is provided, comprising: obtaining an audit flow table, the audit flow table comprising an audit flow table generated in response to a user application; in response to receiving an audit request for the audit flow table, determining an audit result of the audit flow table; in the case that the audit result is not completed, determining an audit scene based on the audit flow table; in the case that the audit scene is determined, auditing the audit flow table to obtain an updated audit flow table; in response to receiving an audit request for the updated audit flow table, re-determining an audit result of the updated audit flow table.

[0006] According to an embodiment of the present disclosure, the application auditing method further comprises: in the case that the audit result is completed, determining a result push state of the audit flow table based on the audit flow table; in the case that the result push state is pushed but the push thread is not ended, determining a first push state, the first push state comprising a normal push and an abnormal push; in the case that the first push state is an abnormal push, updating the audit flow table and re-performing the result push; and in the case that the first push state is a normal push, closing the audit thread.

[0007] In an embodiment according to the present disclosure, when the result pushing state is pushed but the pushing thread is not ended, determining the first pushing state comprises: calculating a result pushing time interval according to a current system time and a start pushing time; and when the result pushing time interval exceeds a pushing validity period, determining that the first pushing state is a pushing exception.

[0008] In an embodiment according to the present disclosure, when the audit result is not completed, determining the audit scenario based on the audit flow table comprises: obtaining an audit scenario flag based on the audit flow table, the audit scenario flag comprising a plurality of audit scenario flags meeting user requirements; and determining the audit scenario based on the audit scenario flag, wherein the audit scenario comprises a first scenario and a second scenario.

[0009] In an embodiment according to the present disclosure, the audit flow table comprises a reset times field for indicating a reset times of the audit flow table, and the application audit method further comprises: when the audit scenario is the first scenario, calculating a first audit time interval according to a current system time and an application entry time; and when the first audit time interval exceeds a first preset time interval, auditing the reset times of the audit flow table, the first preset time interval being an audit processing validity period of the first scenario.

[0010] In an embodiment according to the present disclosure, the audit flow table further comprises an audit state field for indicating an audit state of the audit flow table; and when the first audit time interval exceeds the first preset time interval, auditing the reset times of the audit flow table comprises: when the reset times is less than or equal to a preset times, updating the reset times field and the audit state field of the audit flow table to obtain an updated audit flow table; and when the reset times is greater than the preset times, updating the audit state field of the audit flow table to obtain an updated audit flow table.

[0011] In an embodiment according to the present disclosure, the application audit method further comprises: when the audit scenario is the second scenario, calculating a second audit time interval according to a current system time and an application entry time; and when the second audit time interval exceeds a second preset time interval, updating the audit state field of the audit flow table to obtain an updated audit flow table, the second preset time interval being an audit processing validity period of the second scenario.

[0012] In an embodiment according to the present disclosure, the application audit method further comprises: obtaining an audit time interval of a historical audit flow table which is completed; determining an average value of the audit time interval and a standard deviation of the audit time interval according to the audit time interval; and determining the second preset time interval based on the average value of the audit time interval and the standard deviation of the audit time interval.

[0013] The second aspect of the present disclosure provides an application review device, comprising: a first obtaining module configured to obtain a review flow table, the review flow table comprising a review flow table generated in response to a user application; a first determining module configured to determine a review result of the review flow table in response to receiving a review request for the review flow table; a second determining module configured to determine a review scenario based on the review flow table in a case where the review result is that the review is not completed; a first review module configured to review the review flow table to obtain an updated review flow table in a case where the review scenario is determined; and a second review module configured to redetermine the review result of the updated review flow table in response to receiving a review request for the updated review flow table.

[0014] The third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory configured to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are caused to perform the above-mentioned application review method.

[0015] The fourth aspect of the present disclosure further provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-mentioned application review method.

[0016] The fifth aspect of the present disclosure further provides a computer program product comprising a computer program that, when executed by a processor, implements the above-mentioned application review method. BRIEF DESCRIPTION OF DRAWINGS

[0017] The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure taken in conjunction with the accompanying drawings, in which:

[0018] Figure 1 The system architecture of the application review method and the application review device according to embodiments of the present disclosure is schematically shown;

[0019] Figure 2 The flowchart of the application review method according to embodiments of the present disclosure is schematically shown;

[0020] Figure 3 The flowchart of the review method in a case where the review result is that the review is completed according to embodiments of the present disclosure is schematically shown;

[0021] Figure 4 The flowchart of the method for determining the first push state according to embodiments of the present disclosure is schematically shown;

[0022] Figure 5 The flowchart of the application review method according to embodiments of the present disclosure is schematically shown;

[0023] Figure 6A flowchart of a method of determining an audit scenario is schematically shown according to an embodiment of the present disclosure;

[0024] Figure 7 A flowchart of an audit method of a first scenario is schematically shown according to an embodiment of the present disclosure;

[0025] Figure 8 A flowchart of an audit method of a first scenario is schematically shown according to an embodiment of the present disclosure;

[0026] Figure 9 A flowchart of an audit method of a second scenario is schematically shown according to an embodiment of the present disclosure;

[0027] Figure 10 A flowchart of an audit method of a second scenario is schematically shown according to an embodiment of the present disclosure;

[0028] Figure 11 A flowchart of an audit method of a second scenario is schematically shown according to an embodiment of the present disclosure;

[0029] Figure 12 A flowchart of an audit method of a second scenario is schematically shown according to an embodiment of the present disclosure;

[0030] Figure 13 A flowchart of an audit method of a second scenario is schematically shown according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It is to be understood, however, that the description is merely exemplary and is intended to provide a thorough understanding of the present disclosure. The following description, given together with the accompanying drawings, is intended to provide a thorough understanding of the present disclosure. However, it is apparent that the one or more embodiments can be implemented without the specific details given below. Furthermore, in the following description, descriptions of well-known structures and techniques have been omitted to avoid unnecessarily obscuring the concept of the present disclosure.

[0032] The terms used herein are merely used to describe specific embodiments and are not intended to limit the present disclosure. The terms "include", "comprise" and the like used herein indicate the presence of the described features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0033] All terms used herein, including technical and scientific terms, have meanings that are commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having meanings consistent with the context of the present specification, and should not be interpreted in an idealized or overly formal manner.

[0034] In the case of using expressions similar to "at least one of A, B, and C, etc.", it is generally intended to include any of A, B, and C alone, a combination of at least two of A, B, and C, etc.

[0035] Embodiments of the present disclosure provide an application review method: obtaining a review flow table, the review flow table including a review flow table generated in response to a user application; in response to receiving a review request for the review flow table, determining a review result of the review flow table; in the case that the review result is that the review is not completed, determining a review scenario based on the review flow table; in the case that the review scenario is determined, reviewing the review flow table to obtain an updated review flow table; in response to receiving a review request for the updated review flow table, re-determining a review result of the updated review flow table.

[0036] The present disclosure is to first review the review flow table and determine the review result; in the case that the review result is not completed, update the review flow table after determining the review scenario; review the updated review flow table again to reconfirm the review result. Considering that the prior art can avoid the risk of incomplete review data due to upstream and downstream interface timeout and data missing, but lacks a closed loop for the entire process. Abnormal data cannot be processed, or the interaction of KAFKA sending is abnormal, and the application will remain in the system.

[0037] The present disclosure realizes the closed loop of the application review process by first determining the review result, then reviewing, and updating the review result after reviewing. After the review is completed, the review result is confirmed again at the initial node, which ensures that abnormal data is processed in time through the closed loop, and abnormal data occupies threads and affects user experience is avoided.

[0038] Figure 1 The system architecture of the application review method and the application review device according to the embodiments of the present disclosure is schematically shown.

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

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

[0041] The terminal devices 101, 102, 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smartphones, tablet computers, laptop computers, desktop computers, etc.

[0042] The server 105 can be a server providing various services, such as a background management server providing support for websites browsed by users using the terminal devices 101, 102, 103 (only as examples). The background management server can analyze and process received user requests and other data, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0043] It should be noted that the application review method provided by the embodiments of the present disclosure can generally be executed by the server 105. Correspondingly, the application review device provided by the embodiments of the present disclosure can generally be arranged in the server 105. The application review method provided by the embodiments of the present disclosure can also be executed by a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and / or the server 105. Correspondingly, the application review device provided by the embodiments of the present disclosure can also be arranged in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and / or the server 105.

[0044] For example, the review workflow table in this embodiment of the present disclosure can be stored in terminal devices 101, 102, and 103. The review workflow table is sent to server 105 through terminal devices 101, 102, and 103. Server 105 can respond to the received review request for the review workflow table based on the review workflow table, determine the review result of the review workflow table, and if the review result is that the review is not completed, determine the review scenario based on the review workflow table, respond to the review scenario, call the corresponding review rules to review the review workflow table, update the review workflow table, and pass the updated review workflow table to the review completion node. In addition, the audit flow table can also be received by server 105 and stored directly on server 105. Server 105 can directly respond to the audit request for the audit flow table based on the audit flow table, determine the audit result of the audit flow table, and if the audit result is that the audit is not completed, determine the audit scenario based on the audit flow table, respond to the audit scenario, call the corresponding audit rules to audit the audit flow table, update the audit flow table, and pass the updated audit flow table to the audit completion node.

[0045] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0046] The following will be based on Figure 1 The described system architecture, through Figures 2-13 The application review method of the disclosed embodiments is described in detail.

[0047] Figure 2 A flowchart illustrating an application review method according to an embodiment of this disclosure is shown schematically.

[0048] like Figure 2 As shown, the method includes operations S201 to S205.

[0049] In operation S201, obtain the review workflow table, which includes the review workflow table generated in response to the user's application.

[0050] According to embodiments of this disclosure, an approval workflow table is generated based on a user application form. This approval workflow table includes an approval workflow table generated in response to a user's application operation on the client. For example, when a user sends an application request, the approval system can extract the application information entered by the user, perform data cleaning and preprocessing, and generate an approval workflow table in a standard format.

[0051] According to an embodiment of the present disclosure, the audit flow table includes field names: fields of application number, flow state, application entry time, audit scene flag, and audit completion time, and a dictionary corresponding to the field names. The specific flow state includes but is not limited to review pass, audit reject application, audit pass application, successful opening, rejected and sent short message, etc.

[0052] In operation S202, in response to receiving an audit request for the audit flow table, the audit result of the audit flow table is determined.

[0053] According to an embodiment of the present disclosure, after obtaining the audit flow table, in response to the audit request of the audit flow table, it can be determined whether the audit process is completed according to the flow state of the audit flow table. For example, when the flow state is audit reject application, audit pass application, successful opening, rejected and sent short message, it indicates that the audit process has been completed, and the corresponding audit result is generated; when the audit result is review pass, it indicates that the audit is not completed. The audit result includes audit completion and audit not completed, but both audit completion and audit not completed can correspond to one or more flow states of the audit flow table.

[0054] In operation S203, in the case that the audit result is audit not completed, the audit scene is determined based on the audit flow table.

[0055] According to an embodiment of the present disclosure, in the case that the audit result is audit not completed, the audit scene corresponding to the audit flow table is determined based on the audit flow table. Specifically, the audit scene can be the audit scene determined when the audit flow table is generated in response to the user application, or the audit scene changed according to the audit condition in the audit process. For example, according to the audit flow table generated by the user application, it is determined that the audit scene is the first scene, but when the application condition does not meet the audit condition in the audit process, the audit scene can be changed according to the audit condition.

[0056] In operation S204, in the case that the audit scene is determined, the audit flow table is audited to obtain an updated audit flow table.

[0057] According to an embodiment of the present disclosure, different audit scenes correspond to different audit rules, and one audit scene can include multiple sub-scenes, and different sub-scenes can correspond to different audit sub-rules. For example, the audit process can include audit scene 1 and audit scene 2, and in the audit scene 1, it can further include audit sub-scene A and audit sub-scene B, and the audit rule corresponding to the audit scene 1 can include audit sub-rule A and audit sub-rule B. After determining the audit scene, the corresponding audit rule of the audit scene is called to audit the audit flow table, and an updated audit flow table is obtained.

[0058] In operation S205, in response to receiving the audit request for the updated audit flow table, the audit result of the updated audit flow table is re-determined.

[0059] According to the embodiments of the present disclosure, after the audit flow table is audited and the updated audit flow table is obtained, in response to receiving the audit request for the updated audit flow table, the audit system re-determines the audit result of the updated audit flow table, and the audit result is determined again. In order to facilitate the understanding of the present scheme, taking the audit of a credit card as an example, when the audit flow table is generated in response to the user's application, the audit result of the audit flow table is first determined; in the case that the audit result is not completed, the audit is continued; in the audit process, it is found that the user's credit data is abnormal, and the updated audit flow table is generated; the audit system processes the updated audit flow table and returns it to the initial confirmation audit result stage, and the audit result is re-confirmed. The audit system can confirm the audit result again through a closed loop, and abnormal data can be processed in time.

[0060] The embodiments of the present disclosure ensure the closed loop of the audit process, ensure the robustness of the system, reduce the stagnation time caused by audit abnormalities, and accelerate the audit speed by first determining the audit result during the audit, then entering the audit process, and finally generating the updated audit flow table and reconfirming the audit result. At the same time, the closed loop audit process can also process abnormal data to ensure the consistency of the audit state and improve the user experience.

[0061] Figure 3 An audit method flow chart is schematically shown according to the embodiments of the present disclosure when the audit result is an audit completion, as shown in Figure 3 The method includes operations S301-S304.

[0062] In operation S301, when the audit result is an audit completion, the result push state of the audit flow table is determined based on the audit flow table.

[0063] According to the embodiments of the present disclosure, after the audit result is determined to be an audit completion, the result push process is entered, and the result push state is determined according to the flow state field in the audit flow table. The result push state includes a pushed but not ended push thread and an ended push thread, and the result push state of the ended push thread indicates that the result state is successfully pushed to the client and does not need to be processed, and the thread is closed; the result push state of the pushed but not ended push thread indicates that the result state has been pushed to the client, but the push thread has not been ended.

[0064] According to an embodiment of the present disclosure, the audit flow table further comprises a result push flag and a start push time. For example, when the result push state is pushed but the push thread is not ended, the push flag is that the result has been pushed but is not successful, and when the result push state is ended, the push flag is that the result has been pushed successfully. The start push time field records the time when the result push is performed.

[0065] In operation S302, when the result push state is pushed but the push thread is not ended, the first push state is determined.

[0066] According to an embodiment of the present disclosure, the first push state comprises push normal and push abnormal. When the result push state is pushed but the push thread is not ended, the first push state is determined, and the reason why the push thread is not ended is further determined. Specifically, the first push state is push normal, which indicates that the result has been pushed and is normal, the push time is still within the push validity period, and the push thread is not ended because other nodes are not processed; and the first push state is push abnormal, which indicates that the result has been pushed but is abnormal, and the push abnormality needs to be processed.

[0067] In operation S303, when the first push state is push abnormal, the audit flow table is updated, and the result push is performed again.

[0068] According to an embodiment of the present disclosure, when it is confirmed that the first push state is push abnormal, the audit flow table is updated, the result push is performed again, and then the updated audit flow table is returned to the confirmation audit result stage to reconfirm the audit result. At the same time of updating the audit flow table, the audit system can update the result push state. For example, when the first push state is push abnormal, the audit system performs audit processing, updates the audit flow table, and then updates the result push state to not pushed; after the result push is performed again, a new result push state is obtained, which comprises pushed but the push thread is not ended or the push thread is ended.

[0069] In operation S304, when the first push state is push normal, the audit thread is closed.

[0070] According to an embodiment of the present disclosure, the first push state is push normal, which indicates that the result push thread is not abnormal at this time, and the audit thread is closed to avoid occupying the thread.

[0071] According to an embodiment of the present disclosure, KAFKA can be used for result push. For example, when the result push state is pushed but the push thread is not ended, the push flag is that the result has been pushed but is not successful, the first push state is further determined to be push abnormal, the audit flow table is updated, and the result push is performed again through KAFKA.

[0072] According to an embodiment of the present disclosure, still taking the credit card review as an example, after obtaining the review flow table, it is first determined whether the credit card review process is completed according to the review flow table; in the case of an incomplete review result, the next node is entered to determine the specific review scene of the credit card review; after determining the review scene, the review flow table is reviewed, and after the review is completed, the corresponding data of the completed review is updated in the review flow table, and the corresponding review processing is performed; return to the node of determining the review result again, and re-determine the review result of the updated review flow table. When the initial review result is determined to be completed, the credit card review result is determined, in the case of determining that the result push state is pushed but the push thread is not ended, in the case of determining that the first push state is push abnormal, the result of the credit card review this time is re-pushed to the product end, which can be "account opening success", and the push is normal, the review thread is closed; when it is determined that the result push state is the push thread is ended, the review thread is closed.

[0073] Figure 4 The method flowchart for determining the first push state according to an embodiment of the present disclosure is schematically shown. As shown in Figure 4 the method includes operations S401-S402.

[0074] In operation S401, the result push time interval is calculated according to the current system time and the start push time.

[0075] According to an embodiment of the present disclosure, the start push time of the result push can be obtained based on the review flow table, and then the current system time is obtained according to the system data, and the result push time interval is obtained by subtracting the start push time from the current system time. In the normal result push, the result push time interval can show a normal push time interval; when the result push is abnormal, the result push time interval will show an abnormal time interval length.

[0076] In operation S402, in the case that the result push time interval exceeds the push validity period, the first push state is determined to be push abnormal.

[0077] According to an embodiment of the present disclosure, the push validity period is the KAFKA push validity period. When the result push time interval is less than or equal to the push validity period, the first push state is determined to be push normal, and the thread is closed; when the result push time interval exceeds the push validity period, it indicates that the push has been overdue, and in this case, the result push is re-performed, the push state is updated to be not pushed, and the start push time in the review flow table is updated to be the current system time. After updating the review flow table, the updated review flow table is returned to the initial node of determining the review result, and the review result is re-confirmed to ensure the closed loop of the review process.

[0078] Figure 5A flow chart of an application review method according to an embodiment of the present disclosure is shown schematically. As shown in Figure 5 The method includes operations S501-S508.

[0079] In operation S501, it is determined whether the review result is completed. According to an embodiment of the present disclosure, corresponding to operation S202, in response to receiving a review request for the review transfer table, the review result of the review transfer table is determined.

[0080] In operation S502, the review scenario is determined. According to an embodiment of the present disclosure, corresponding to operation S203, in the case that the review result is not completed, the review scenario is determined based on the review transfer table.

[0081] In operation S503, the review transfer table is updated. According to an embodiment of the present disclosure, corresponding to operation S204, in the case that the review scenario is determined, the review transfer table is reviewed to obtain an updated review transfer table.

[0082] In operation S504, the review result is re-determined. According to an embodiment of the present disclosure, corresponding to operation S205, in response to receiving a review request for the updated review transfer table, the review result of the updated review transfer table is re-determined.

[0083] In operation S505, it is determined whether the push thread is completed. According to an embodiment of the present disclosure, corresponding to operation S301, in the case that the review result is completed, the result push state of the review transfer table is determined based on the review transfer table.

[0084] In operation S506, it is ended. It is indicated that in the case that the push thread is completed, the review process is closed, indicating that the review process is ended. And in the case that the first push state is push normal, the review process is closed, indicating that the review process is ended. According to an embodiment of the present disclosure, corresponding to operation S304, in the case that the first push state is push normal, the review thread is closed.

[0085] In operation S507, it is determined whether the first push state is abnormal. According to an embodiment of the present disclosure, corresponding to operation S302, in the case that the result push state is pushed but the push thread is not ended, the first push state is determined.

[0086] In operation S508, the review transfer table is updated for result push. According to an embodiment of the present disclosure, corresponding to operation S303, in the case that the first push state is push abnormal, the review transfer table and the push state are updated, and the result push is re-performed.

[0087] According to an embodiment of the present disclosure, still taking the credit card review as an example, when it is determined in S501 that the review result is not completed, the review part is entered, specifically, after confirming the review scenario in S502, S503 is entered to perform review, the review flow table is updated, and then S504 is entered to re-determine the review result, and S501 is returned to determine.

[0088] When the review result is completed, S505 is entered to determine the result push state, and whether the push thread is completed is determined according to the result push state. When it is determined that the result push state is the push thread completed, S506 is entered to close the review thread; when it is determined that the result push state is the push thread completed but the result push is not completed, S507 is entered to determine whether the credit card review result push is timed out. The push timeout means that the result push has been performed, but the result push is timed out, the push is abnormal, and the push is not timed out means that the result push has been performed, and the push is normal; in the case of result push timeout, S508 is entered to update the review flow table corresponding to the credit card application, update the push result to not pushed, take appropriate processing to re-perform the result push, and then the review process returns from S508 to S501 to re-confirm the review result. In the case of result push not timed out, S606 is entered to close the review process.

[0089] The embodiment of the present disclosure not only returns the updated review flow table after review to the confirmation result stage to form a closed loop of the review process, but also forms a closed loop of the confirmation result stage and the result push part to ensure that the result push part can be processed in time when there is an exception, forming an automatic closed loop review process to ensure the robustness of the system. By setting the push validity period, the result push time interval is compared with the push validity period, and in the case of overage, the result push is re-performed to process the data with push exception in time; the updated review flow table is returned to the confirmation result stage to re-confirm the review result, which can ensure that the information is completed and the consistency of the upstream and downstream states is maintained.

[0090] Figure 6 A flowchart of a method for determining a review scenario according to an embodiment of the present disclosure is schematically shown. As shown in Figure 6 , the method includes operations S601-S602.

[0091] In operation S601, a review scenario flag is obtained based on a review flow table.

[0092] According to an embodiment of the present disclosure, the review scenario flag is obtained from the review flow table, and the review scenario flag is used to indicate the review scenario corresponding to the review flow table. For example, the review scenario flag can be 0 or 1, the review scenario flag being 0 corresponds to the first review scenario, and the review scenario flag being 1 corresponds to the second review scenario. The specific review scenario can be determined according to the actual review process.

[0093] At operation S602, the audit scene is determined based on the audit scene flag, where the audit scene includes a first scene and a second scene.

[0094] According to an embodiment of the present disclosure, the audit scene is determined to be the first scene or the second scene based on the obtained audit scene flag. For the convenience of understanding the present scheme, taking the first scene as online card issuance and the second scene as batch card issuance as an example, the online card issuance scene needs to call each application interface, and the returned result is used for approval, and the batch card issuance scene needs to send a batch file to each application, and the returned batch file is loaded for approval. The audit scene flag corresponds to the online card issuance scene when the audit scene flag is 0, and the audit scene flag corresponds to the batch card issuance scene when the audit scene flag is 1. Specifically, after determining that the audit scene flag is 1, the audit system confirms that the audit scene is batch card issuance, and the audit rules of the batch card issuance scene are used to audit the audit flow table.

[0095] Figure 7 The audit method flowchart of the first scene according to an embodiment of the present disclosure is schematically shown. As shown in Figure 7 the method includes operations S701-S702.

[0096] At operation S701, in the case where the audit scene is the first scene, the first audit time interval is calculated according to the current system time and the application form entry time.

[0097] According to an embodiment of the present disclosure, after obtaining the current system time and the application form entry time, the first audit time interval is obtained by subtracting the application form entry time from the current system time, where the first audit time interval indicates the time from entering the application form and generating the audit flow table to the current node. The first audit time interval is compared with the first preset time interval, which is used to determine whether the first audit time interval is overdue. In the case where the first audit time interval does not exceed the first preset time interval, the audit is ended.

[0098] According to an embodiment of the present disclosure, the first preset time interval is set to 1 day, including two stages of work period and non-work period, which is used to ensure that the relevant information can be queried in the non-work period when the relevant information cannot be queried in the work period, and ensure that the approval process can query the relevant information.

[0099] At operation S702, in the case where the first audit time interval exceeds the first preset time interval, the reset times of the audit flow table are audited.

[0100] According to an embodiment of the present disclosure, the first preset time interval is a valid period of the audit process of the first scenario. The first audit time interval exceeding the first preset time interval indicates that the query information is overdue, and the audit flow table needs to be audited by calling the first audit rule corresponding to the first scenario. For example, taking credit card audit as an example, the audit of the credit card needs to query the credit information of the user, and when the first scenario is audited, the first audit time interval is overdue, which indicates that the query time of the credit information is overdue, and in this case, the credit information needs to be queried again or enter the corresponding audit node.

[0101] According to an embodiment of the present disclosure, the audit flow table further comprises a reset times field for providing a reset function. For example, the reset times can provide a function of resetting the query of the credit information.

[0102] Figure 8 An audit method flowchart is schematically shown when the first audit time interval exceeds the first preset time interval according to an embodiment of the present disclosure. As shown in Figure 8 The method comprises S801-S802.

[0103] In operation S801, when the reset times is less than or equal to a preset number of times, the reset times field and the audit state field of the audit flow table are updated to obtain an updated audit flow table.

[0104] According to an embodiment of the present disclosure, the audit flow table further comprises an audit state field for indicating the audit state of the audit flow table.

[0105] According to an embodiment of the present disclosure, the preset number of times can be set as n, n is a value obtained by dividing the information query valid day t by the first preset time interval, and the setting of n can ensure that the reset function in the audit process is within the information query valid day. For example, taking credit card audit as an example, t is the credit query valid day, the first preset time interval is 1 day, and the preset number of times n is t / 1. When the audit scenario is the first scenario, the first scenario is divided into a first sub-scenario and a second sub-scenario according to whether the reset times is greater than the preset number of times. When the reset times is less than or equal to the preset number of times, the information is reset and queried, the flow state in the audit flow table is updated, and the reset times is increased, and finally the updated audit flow table is returned to reconfirm the audit result.

[0106] In operation S802, when the reset times is greater than the preset number of times, the audit state field of the audit flow table is updated to obtain an updated audit flow table.

[0107] According to an embodiment of the present disclosure, the credit information of the query user needs to be queried within the credit validity date. Credit information query exceeding the credit validity date will affect the credit record of the customer. When the reset number is greater than the preset number, it indicates that the reset number has reached the limit, and the current audit process needs to be closed, the current audit process is ended, the audit result is reconfirmed, the audit scene is replaced, or the manual audit stage is entered.

[0108] Figure 9 The flowchart of the audit method of the second scene according to an embodiment of the present disclosure is schematically shown. As shown in Figure 9 , the method comprises S901-S902.

[0109] In operation S901, when the audit scene is the second scene, the second audit time interval is calculated according to the current system time and the application entry time.

[0110] According to an embodiment of the present disclosure, after determining that the audit scene is the second scene according to the audit scene flag, the application entry time is obtained based on the audit transfer table, the current system time is obtained, the current system time is subtracted from the application entry time, and the second audit time interval of the audit transfer table is obtained. The second audit time interval indicates the time interval from entering the application and generating the audit transfer sheet to the current node under the second scene audit process.

[0111] In operation S902, when the second audit time interval exceeds the second preset time interval, the audit state field of the audit transfer table is updated to obtain an updated audit transfer table.

[0112] According to an embodiment of the present disclosure, the second preset time interval is the audit processing validity period of the second scene. When the second audit time interval exceeds the second preset time interval, it indicates that the current second scene audit is overdue, and the audit data may be abnormal. The current audit process is closed in time, and the transfer state of the audit transfer table is updated.

[0113] The prior art is always in an error state for data exceptions, or needs to wait for manual processing. The waiting for manual processing and the manual processing process will prolong the audit time. The present disclosure sets the second preset time interval to ensure that the system can automatically close the audit process of the abnormal processing, and returns the audit transfer table corresponding to the abnormal processing to the determination audit result stage to re-determine the audit result. The method of the present disclosure not only can automatically process the abnormal process, but also can reduce the processing time of the abnormality and reduce the audit time.

[0114] Figure 10 The flowchart of the audit method for determining the second preset time interval according to an embodiment of the present disclosure is schematically shown. As shown in Figure 10 , the method comprises S1001-S1003.

[0115] In operation S1001, an audit time interval of a historical audit flow table of which the audit is completed is acquired.

[0116] According to an embodiment of the present disclosure, in a case where the audit scene is the second scene, an audit time interval of a historical audit flow table in the current audit scene is acquired from the audit system.

[0117] In operation S1002, according to the audit time interval, an average value of the audit time interval and a standard deviation of the audit time interval are determined.

[0118] According to an embodiment of the present disclosure, acquiring the second preset time interval first needs to acquire the audit time intervals of a plurality of historical audit flow tables of which the audit is completed from the database, and call an average value function (AVG function) and a standard deviation function (STDDEV function) in the database. The AVG function and the STDDEV function are used to calculate the audit time intervals of the historical audit flow tables, and the average value and the standard deviation data of the historical audit flow tables are obtained respectively.

[0119] In operation S1003, based on the average value of the audit time interval and the standard deviation of the audit time interval, the second preset time interval is determined.

[0120] According to an embodiment of the present disclosure, the second preset time interval is obtained by adding the average value of the audit time interval and three times the standard deviation of the audit time interval, and this method of acquiring the second preset time interval is called the three-sigma method. The second preset time interval obtained by the three-sigma method can eliminate abnormal data in the audit process, avoid long-time audit caused by abnormal data, and reduce long-time audit caused by manual processing delay.

[0121] The present disclosure sets the second preset time interval by using the three-sigma method, clearly defines the appropriate waiting time, and when the second audit time interval exceeds the second preset time interval, automatically closes the long-time processing order, reduces the processing time of the entire audit process, and ensures the consistency of upstream and downstream data in the audit process.

[0122] Figure 11 The audit method flowchart according to an embodiment of the present disclosure is schematically shown. As shown in the figure, the method includes operations S1101-S1113. Figure 11

[0123] In operation S1101, it is determined whether the audit result is completed. According to an embodiment of the present disclosure, in response to receiving the audit request for the audit flow table, the audit result of the audit flow table is determined according to operation S202.

[0124] ​In operation S1102, it is determined whether the audit scene is the first scene. After the audit result is determined to be completed in S1101, S1102 is entered to obtain the audit scene flag from the audit flow table to determine whether it is the first scene. According to an embodiment of the present disclosure, S1102 can include operations S601-S602.

[0125] In operation S1103, it is determined whether the first audit time interval is greater than the first preset time interval. In the condition that the audit scene is the first scene, the first scene is divided into two different cases S1104 and S1105 by determining whether the first audit time interval is greater than the first preset time interval. According to an embodiment of the present disclosure, S1103 can include operations S701-S702, the first audit time interval is calculated according to the current system time and the start input time, and in the case that the first audit time interval is greater than the preset time, S1104 is entered.

[0126] In operation S1104, it is determined whether the reset number is greater than the preset number. According to the relationship between the reset number and the preset number, two different sub-scenes S1106 and S1107 are obtained.

[0127] In operation S1105, it is ended. After it is determined in S1103 that the first audit time interval is less than or equal to the first preset time interval, S1105 is entered to close the audit thread.

[0128] In operation S1106, when the reset number is less than or equal to the preset number, S1106 is entered to audit and update the audit flow table. According to an embodiment of the present disclosure, S1106 can include operation S801, in the case that the reset number is less than or equal to the preset number, the reset number field and the audit state field of the audit flow table are updated to obtain an updated audit flow table, and the updated audit flow table is returned to S1101 to determine the audit result again.

[0129] In operation S1107, when the reset number is greater than the preset number, S1107 is entered, indicating that the current reset number has exceeded the preset number, and the audit flow table needs to be updated and the current audit process is ended. According to an embodiment of the present disclosure, S1107 can include operation S802, in the case that the reset number is greater than the preset number, the audit state field of the audit flow table is updated, S1110 is entered to end the audit, so that the system confirms that the current audit process has ended.

[0130] In operation S1108, it is determined whether the second audit time interval is greater than the second preset time interval. The second audit time interval is obtained according to the current system time and the start input time, and the second preset time interval is calculated according to the audit time interval of the historical audit flow table. According to an embodiment of the present disclosure, S1108 can include operations S901 and S1001-S1003.

[0131] In operation S1109, the audit flow table is updated. According to an embodiment of the present disclosure, S1109 can include operation S902, in the case that the second audit time interval exceeds the second preset time interval, the audit flow table is audited, the audit flow table is updated, and the audit end node S1110 is entered, indicating that the audit thread of the current audit scene has ended.

[0132] In operation S1110, the audit is ended. The audit end node indicates that the audit process under the current audit scene has ended, and the updated audit flow table obtained in the current audit scene needs to be transferred to S1101 to reconfirm the audit result. According to an embodiment of the present disclosure, S1110 corresponds to operation S205 described above.

[0133] In operation S1111, it is determined whether the push thread is completed. In the case that the audit result is confirmed to be completed at S1101, S1111 is entered to determine the result push state of the audit flow table, and it is determined whether the push thread is completed according to the result push state of the audit flow table. According to an embodiment of the present disclosure, S1111 corresponds to operation S301 described above.

[0134] In operation S1112, the result is pushed. In the case that the result push state is determined to be pushed but the push thread is not ended, the result is pushed after the first push state is determined. In the case that the first push state is push abnormal, the result push indicates that the updated audit flow table is updated and the result push is performed again; in the case that the first push state is push normal, the result push indicates that the normal process, and the push does not need to be performed again, and the thread is ended. According to an embodiment of the present disclosure, S1112 corresponds to operations S302-S303 described above.

[0135] In operation S1113, the process ends. If the result push status is determined to be that the push thread has not ended, the push thread is terminated. According to an embodiment of this disclosure, taking credit card review as an example, when S1101 determines the review result is incomplete, the process proceeds to S1102 to confirm whether the review scenario is the first scenario; then, in S1103, if the review scenario is the first scenario, it is determined whether the first review time interval is greater than the first preset time interval. If it does not time out, the process proceeds to S1105 to end the review process; if it times out, the process proceeds to S1104 to determine whether the credit information query has exceeded a preset number of times; after entering S1104, if the preset number of queries has not been exceeded, the process can proceed to S1106 to reset the review and update the review flow table, returning the updated review flow table to S1101, returning to the initial confirmation of review result node; after entering S1104, if the preset number of queries has been exceeded, the process needs to proceed to S1107 to update the review flow table and then proceed to the S1110 review end node. After entering S1110, the audit flow table also needs to return to the S1101 confirmation audit result node so that the confirmation audit result node can re-evaluate the updated audit flow table and complete the entire audit loop.

[0136] This disclosure ensures that the required information can still be retrieved from multiple channels within the specified time limit by setting a second preset time. By adding a reset count field and setting the relationship between the reset count and the preset count, a reset function is provided or the review process is automatically closed when the system cannot handle abnormal data. This achieves automatic handling of data anomalies and ensures consistency of data across the review process. The preset count setting also avoids the risk of users having to conduct secondary credit checks, improving the user experience.

[0137] Figure 12 A schematic block diagram of an application review apparatus according to an embodiment of the present disclosure is shown.

[0138] like Figure 12 As shown, the application review device 1200 includes a first acquisition module 1201, a first determination module 1202, a second determination module 1203, a first review module 1204, and a second review module 1205.

[0139] The first acquisition module 1201 is used to acquire an approval workflow table, which includes an approval workflow table generated in response to a user application. According to embodiments of this disclosure, the first acquisition module 1201 may, for example, execute the above-mentioned reference... Figure 2 The operation described is S201.

[0140] The first determining module 1202 is configured to determine the audit result of the audit flow table in response to receiving an audit request for the audit flow table. According to embodiments of this disclosure, the first determining module 1202 may, for example, perform the actions described above. Figure 2 The operation described is S202.

[0141] The second determining module 1203 is configured to determine the audit scene based on the audit flow table in a case where the audit result is that the audit is not completed. According to an embodiment of the present disclosure, the second determining module 1203 may, for example, perform the operation S203 described above. Figure 2

[0142] The first audit module 1204 is configured to perform audit on the audit flow table to obtain an updated audit flow table in a case where the audit scene is determined. According to an embodiment of the present disclosure, the first audit module 1204 may, for example, perform the operation S204 described above. Figure 2

[0143] The second audit module 1205 is configured to re-determine the audit result of the updated audit flow table in response to receiving an audit request for the updated audit flow table. According to an embodiment of the present disclosure, the second audit module 1205 may, for example, perform the operation S205 described above. Figure 2

[0144] According to an embodiment of the present disclosure, the application audit device 1200 further includes a third determining module, a first state determining module, a second state determining module, and a third state determining module.

[0145] The third determining module is configured to determine the result pushing state of the audit flow table based on the audit flow table in a case where the audit result is that the audit is completed. According to an embodiment of the present disclosure, the third determining module may, for example, perform the operation S301 described above. Figure 3

[0146] The first state determining module is configured to determine a first pushing state including pushing normal and pushing abnormal in a case where the result pushing state is that the pushing is completed but the pushing thread is not ended. According to an embodiment of the present disclosure, the first state determining module may, for example, perform the operation S302 described above. Figure 3

[0147] The second state determining module is configured to update the audit flow table and re-perform the result pushing in a case where the first pushing state is pushing abnormal. According to an embodiment of the present disclosure, the second state determining module may, for example, perform the operation S303 described above. Figure 3

[0148] The third state determining module is configured to close the audit thread in a case where the first pushing state is pushing normal. According to an embodiment of the present disclosure, the third state determining module may, for example, perform the operation S304 described above. Figure 3

[0149] ​​​​​​​According to an embodiment of the present disclosure, the first state determining module further comprises a first time determining unit and a first state determining unit.

[0150] The first time determining unit is configured to calculate the result pushing time interval according to the current system time and the start pushing time. According to an embodiment of the present disclosure, the first time determining unit may, for example, perform the operation S401 described above with reference to. Figure 4

[0151] The first state determining unit is configured to determine the first pushing state as pushing abnormal in the case that the result pushing time interval exceeds the pushing validity period. According to an embodiment of the present disclosure, the first state determining unit may, for example, perform the operation S402 described above with reference to. Figure 4

[0152] According to an embodiment of the present disclosure, the second determining module 1203 comprises a scene flag determining unit and a scene determining unit.

[0153] The scene flag determining unit is configured to obtain an audit scene flag based on the audit flow table, the audit scene flag comprising a plurality of audit scene flags meeting user requirements. According to an embodiment of the present disclosure, the scene flag determining unit may, for example, perform the operation S601 described above with reference to. Figure 6

[0154] The scene determining unit is configured to determine an audit scene based on the audit scene flag, wherein the audit scene comprises a first scene and a second scene. According to an embodiment of the present disclosure, the scene determining unit may, for example, perform the operation S602 described above with reference to. Figure 6

[0155] According to an embodiment of the present disclosure, the first audit module 1204 comprises a first scene time determining unit and a first scene audit unit.

[0156] The first scene time determining unit is configured to calculate a first audit time interval according to the current system time and the application form entry time in the case that the audit scene is the first scene. According to an embodiment of the present disclosure, the first scene time determining unit may, for example, perform the operation S701 described above with reference to. Figure 7

[0157] The first scene audit unit is configured to audit the reset times of the audit flow table in the case that the first audit time interval exceeds a first preset time interval, the first preset time interval being an audit processing validity period of the first scene. According to an embodiment of the present disclosure, the first scene audit unit may, for example, perform the operation S702 described above with reference to. Figure 7

[0158] According to an embodiment of the present disclosure, the first scene audit unit comprises a first determining sub-unit and a second determining sub-unit.​​​​​​

[0159] The first determining sub-unit is configured to update the reset times field and the audit state field of the audit flow table to obtain an updated audit flow table, in a case where the reset times is less than or equal to the preset times. According to embodiments of the present disclosure, the first determining sub-unit may, for example, perform the operation S801 described above with reference to the first determining sub-unit. Figure 8

[0160] The second determining sub-unit is configured to update the audit state field of the audit flow table to obtain an updated audit flow table, in a case where the reset times is greater than the preset times. According to embodiments of the present disclosure, the second determining sub-unit may, for example, perform the operation S802 described above with reference to the second determining sub-unit. Figure 8

[0161] According to embodiments of the present disclosure, the first audit module 1204 comprises a second scenario time determining unit and a second scenario audit unit.

[0162] The second scenario time determining unit is configured to calculate a second audit time interval according to the current system time and the application form entry time, in a case where the audit scenario is the second scenario. According to embodiments of the present disclosure, the second scenario time determining unit may, for example, perform the operation S901 described above with reference to the second scenario time determining unit. Figure 9

[0163] The second scenario audit unit is configured to update the audit state field of the audit flow table to obtain an updated audit flow table, in a case where the second audit time interval exceeds a second preset time interval, the second preset time interval being an audit processing validity period of the second scenario. According to embodiments of the present disclosure, the second scenario audit unit may, for example, perform the operation S902 described above with reference to the second scenario audit unit. Figure 9

[0164] According to embodiments of the present disclosure, the second scenario audit unit comprises a first time determining sub-unit, a second time determining sub-unit and a third time determining sub-unit.

[0165] The first time determining sub-unit is configured to obtain an audit time interval of a historical audit flow table of which the audit is completed. According to embodiments of the present disclosure, the first time determining sub-unit may, for example, perform the operation S1001 described above with reference to the first time determining sub-unit. Figure 10

[0166] The second time determining sub-unit is configured to determine a mean value of the audit time interval and a standard deviation of the audit time interval according to the audit time interval. According to embodiments of the present disclosure, the second time determining sub-unit may, for example, perform the operation S1002 described above with reference to the second time determining sub-unit. Figure 10

[0167] ​​​​​​The third time determining sub-unit is configured to determine a second preset time interval based on the average value of the audit time intervals and the standard deviation of the audit time intervals. According to embodiments of the present disclosure, the third time determining sub-unit may, for example, perform the above-mentioned operation S1003. Figure 10 The operation S1003 is described.

[0168] Any multiple modules of the first obtaining module 1201, the first determining module 1202, the second determining module 1203, the first auditing module 1204, the second auditing module 1205, the third determining module, the first state determining module, the second state determining module, the third state determining module, the first time determining unit, the first state determining unit, the scene flag determining unit, the scene determining unit, the first scene time determining unit, the first scene auditing unit, the first determining sub-unit, the second determining sub-unit, the second scene time determining unit, the second scene auditing unit, the first time determining sub-unit, the second time determining sub-unit, and the third time determining sub-unit according to the embodiments of the present disclosure can be combined in one module, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of the modules can be combined with at least part of the functions of other modules, and implemented in one module. According to the embodiments of the present disclosure, at least one of the first obtaining module 1201, the first determining module 1202, the second determining module 1203, the first auditing module 1204, the second auditing module 1205, the third determining module, the first state determining module, the second state determining module, the third state determining module, the first time determining unit, the first state determining unit, the scene flag determining unit, the scene determining unit, the first scene time determining unit, the first scene auditing unit, the first determining sub-unit, the second determining sub-unit, the second scene time determining unit, the second scene auditing unit, the first time determining sub-unit, the second time determining sub-unit, and the third time determining sub-unit can be at least partially implemented as a hardware circuit, for example, a field programmable gate array (FPGA), a programmable logic array (PLA), a system on chip, a system on board, a system on package, an application specific integrated circuit (ASIC), or any other reasonable manner of hardware or firmware that can be integrated or packaged with a circuit, or implemented in any one of software, hardware, and firmware or in a proper combination of any of the foregoing. Alternatively, at least one of the first obtaining module 1201, the first determining module 1202, the second determining module 1203, the first auditing module 1204, the second auditing module 1205, the third determining module, the first state determining module, the second state determining module, the third state determining module, the first time determining unit, the first state determining unit, the scene flag determining unit, the scene determining unit, the first scene time determining unit, the first scene auditing unit, the first determining sub-unit, the second determining sub-unit, the second scene time determining unit, the second scene auditing unit, the first time determining sub-unit, the second time determining sub-unit, and the third time determining sub-unit can be at least partially implemented as a computer program module that can perform corresponding functions when the computer program module is run.

[0169] Figure 13A block diagram schematically illustrating an electronic device suitable for implementing the application review method according to an embodiment of the present disclosure is shown.

[0170] As shown in Figure 13 The electronic device 1300 according to an embodiment of the present disclosure includes a processor 1301 that can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 1302 or loaded from a storage section 1308 into a random access memory (RAM) 1303. The processor 1301 can include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor, and / or a related chipset, and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), and / or the like. The processor 1301 can also include an on-board memory for cache use. The processor 1301 can include a single processing unit or multiple processing units for executing different actions of the method processes according to embodiments of the present disclosure.

[0171] In the RAM 1303, various programs and data required for the operation of the electronic device 1300 are stored. The processor 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. The processor 1301 performs various operations of the method processes according to embodiments of the present disclosure by executing programs in the ROM 1302 and / or the RAM 1303. Note that the programs can also be stored in one or more memories other than the ROM 1302 and the RAM 1303. The processor 1301 can also perform various operations of the method processes according to embodiments of the present disclosure by executing programs stored in the one or more memories.

[0172] According to an embodiment of the present disclosure, the electronic device 1300 can further include an input / output (I / O) interface 1305, which is also connected to the bus 1304. The electronic device 1300 can further include one or more of the following components connected to the I / O interface 1305: an input section 1306 including a keyboard, a mouse, etc.; an output section 1307 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN card, a modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to the I / O interface 1305 as necessary. A removable recording medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 1310 as necessary, so that a computer program read therefrom is installed into the storage section 1308 as necessary.

[0173] The present disclosure also provides a computer readable storage medium, which can be included in the device / apparatus / system described in the above embodiments, or exist separately without being assembled into the device / apparatus / system. The above computer readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of the present disclosure.

[0174] According to the embodiments of the present disclosure, the computer readable storage medium can be a non-volatile computer readable storage medium, which can include, but is not limited to, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any appropriate combination thereof. In the present disclosure, the computer readable storage medium can be any tangible medium that contains or stores a program, which can be used by or in connection with an instruction execution system, apparatus, or device. For example, according to the embodiments of the present disclosure, the computer readable storage medium can include one or more memories of the ROM 1302 and / or the RAM 1303 described above and / or one or more memories other than the ROM 1302 and the RAM 1303.

[0175] The embodiments of the present disclosure also include a computer program product, which includes a computer program containing program codes for executing the methods shown in the flowcharts. When the computer program product is run in a computer system, the program codes are used to make the computer system implement the application review method provided by the embodiments of the present disclosure.

[0176] The above functions defined in the system / apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1301. According to the embodiments of the present disclosure, the system, apparatus, module, unit, etc. described above can be implemented by computer program modules.

[0177] In one embodiment, the computer program can rely on tangible storage media such as optical storage media, magnetic storage media, etc. In another embodiment, the computer program can also be transmitted, distributed, and downloaded in the form of signals on a network medium, and be downloaded and installed through the communication part 1309 and / or installed from the detachable medium 1311. The program codes contained in the computer program can be transmitted by any appropriate network medium, including but not limited to wireless, wired, etc., or any appropriate combination thereof.

[0178] In such embodiments, the computer program can be downloaded and installed from the network through the communication part 1309, and / or installed from the detachable medium 1311. When the computer program is executed by the processor 1301, the above-described functions defined in the system of the embodiments of the present disclosure are executed. According to the embodiments of the present disclosure, the system, device, apparatus, module, unit, and the like described above can be implemented by computer program modules.

[0179] According to the embodiments of the present disclosure, the program code for executing the computer program provided by the embodiments of the present disclosure can be written in any combination of one or more programming languages, and specifically, these computer programs can be implemented using high-level procedural and / or object-oriented programming language, and / or assembly / machine language. The programming language includes, but is not limited to, such as Java, C++, python, "C" language or similar programming language. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In the case involving a remote computing device, the remote computing device can be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, connected to the Internet through an Internet service provider).

[0180] The flowcharts and the block diagrams in the drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams can represent a module, a segment, or a portion of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the drawings. For example, two blocks noted in succession can in fact be executed substantially concurrently or in the reverse order, depending on the functionality involved. It should also be noted that each block in the flowcharts or block diagrams, and combinations of blocks in the flowcharts or block diagrams, can be implemented by dedicated hardware-based systems that perform the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0181] Those skilled in the art can understand that the features described in various embodiments of the present disclosure and / or claims can be combined or / and integrated, even if such combinations or integrations are not explicitly described in the present disclosure. In particular, the features described in various embodiments of the present disclosure and / or claims can be combined and / or integrated in various combinations, without departing from the spirit and teachings of the present disclosure. All these combinations and / or integrations fall within the scope of the present disclosure.

[0182] The above describes embodiments of the present disclosure. However, these embodiments are merely for illustrative purposes, and are not intended to limit the scope of the present disclosure. Although each embodiment is described above separately, this does not mean that the measures in each embodiment cannot be used advantageously in combination. The scope of the present disclosure is defined by the appended claims and their equivalents. Those skilled in the art can make various substitutions and modifications without departing from the scope of the present disclosure, and all such substitutions and modifications shall fall within the scope of the present disclosure.

Claims

1. An application review method, comprising: Obtain the review process table, which includes a review process table generated in response to a user application and an updated review process table. The review process table includes a reset count field and a review status field, which are used to represent the reset count and review status of the review process table, respectively. In response to receiving an audit request for the audit workflow form, the audit result of the audit workflow form is determined; wherein, when the audit status is audit rejection, audit approval, account opening successful, or rejection and SMS sent, the audit result is audit completed; when the audit status is review approved, the audit result is audit incomplete. If the review result is that the review is not completed, the review scenario is determined based on the review workflow table; Given a defined review scenario, the review workflow table is reviewed to obtain an updated review workflow table. In response to receiving an audit request for the updated audit workflow table, the audit result of the updated audit workflow table is re-determined; The audit workflow form is audited to obtain an updated audit workflow form, which includes: If the review scenario is the first scenario, calculate the first review time interval based on the current system time and the application entry time; If the first review time interval exceeds the first preset time interval and the number of resets is less than or equal to the preset number of resets, the reset number field and the review status field of the review flow table are updated to obtain an updated review flow table. The first preset time interval is the validity period of the review processing for the first scenario. If the first review time interval exceeds the first preset time interval and the number of resets exceeds the preset number, update the review status field of the review flow table to obtain an updated review flow table; If the review scenario is the second scenario, calculate the second review time interval based on the current system time and the application entry time; If the second review time interval exceeds the second preset time interval, the review status field of the review flow table is updated to obtain an updated review flow table. The second preset time interval is the validity period of the review processing for the second scenario.

2. The method according to claim 1, further comprising: If the review result is that the review is completed, the result push status of the review workflow table is determined based on the review workflow table; When the result push status is pushed but the push thread has not ended, a first push status is determined, which includes push normal and push abnormal. If the first push status is "push abnormal", update the review workflow table and re-push the results; and If the first push status is normal, close the review thread.

3. The method according to claim 2, wherein, When the result push status is "push has been pushed" but the push thread has not ended, the first push status is determined as follows: Calculate the result push interval based on the current system time and the start push time; and If the result push time interval exceeds the push validity period, the first push status is determined to be a push abnormality.

4. The method according to claim 1, wherein, When the review result is that the review is not completed, the process of determining the review scenario based on the review workflow table includes: Based on the review flow table, review scenario markers are obtained, including multiple review scenario markers that meet user needs; Based on the audit scenario marker, an audit scenario is determined, wherein the audit scenario includes a first scenario and a second scenario.

5. The method according to claim 1, further comprising: Obtain the historical review process log showing the review time intervals after the review is completed; Based on the stated review time intervals, determine the average value and standard deviation of the review time intervals; as well as A second preset time interval is determined based on the average value of the audit time interval and the standard deviation of the audit time interval.

6. An application review device, comprising: The first acquisition module is used to acquire the review process table, which includes an review process table generated in response to a user application and an updated review process table. The review process table includes a reset count field and an review status field, which are used to represent the reset count and review status of the review process table, respectively. The first determining module is used to respond to receiving an audit request for the audit flow table and determine the audit result of the audit flow table; wherein, when the audit status is audit rejection, audit approval, account opening success, or rejection and SMS sent, the audit result is audit completed; when the audit status is review approved, the audit result is audit incomplete. The second determining module is used to determine the audit scenario based on the audit flow table when the audit result is that the audit is not completed. The first review module is used to review the review flow table when the review scenario is determined, and to obtain an updated review flow table. The second review module is used to respond to receiving a review request for the updated review flow table and to redetermine the review result of the updated review flow table. The audit workflow form is audited to obtain an updated audit workflow form, which includes: If the review scenario is the first scenario, calculate the first review time interval based on the current system time and the application entry time; If the first review time interval exceeds the first preset time interval and the number of resets is less than or equal to the preset number of resets, the reset number field and the review status field of the review flow table are updated to obtain an updated review flow table. The first preset time interval is the validity period of the review processing for the first scenario. If the first review time interval exceeds the first preset time interval and the number of resets exceeds the preset number, update the review status field of the review flow table to obtain an updated review flow table; If the review scenario is the second scenario, calculate the second review time interval based on the current system time and the application entry time; If the second review time interval exceeds the second preset time interval, the review status field of the review flow table is updated to obtain an updated review flow table. The second preset time interval is the validity period of the review processing for the second scenario.

7. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 5.

9. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 5.

Images