CN113283797A - Business approval method, device, equipment and storage medium - Google Patents
Business approval method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN113283797A CN113283797A CN202110656434.7A CN202110656434A CN113283797A CN 113283797 A CN113283797 A CN 113283797A CN 202110656434 A CN202110656434 A CN 202110656434A CN 113283797 A CN113283797 A CN 113283797A
- Authority
- CN
- China
- Prior art keywords
- approval
- service
- determining
- business
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 97
- 230000008520 organization Effects 0.000 claims description 50
- 230000007246 mechanism Effects 0.000 claims description 42
- 238000012795 verification Methods 0.000 claims description 41
- 238000012544 monitoring process Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 7
- 238000011161 development Methods 0.000 abstract description 15
- 230000006872 improvement Effects 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 37
- 235000014510 cooky Nutrition 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Operations Research (AREA)
- Computer Security & Cryptography (AREA)
- General Business, Economics & Management (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Marketing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the disclosure provides a business approval method, a business approval device, business approval equipment and a storage medium, which are applied to a warehousing robot. The method comprises the following steps: determining the business to be examined; determining a request address of a service detail page corresponding to the service to be approved recorded in a database of the mobile equipment; obtaining a service detail page based on the request address; and performing examination and approval operation on the service detail page to obtain an examination and approval result. According to the technical scheme of the embodiment of the disclosure, the access interface based on the existing server of the bank system accesses the server and performs business approval, so that the improvement of the interface of the bank system aiming at the mobile equipment is not needed, the development is convenient, and the cost is saved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for business approval.
Background
With the progress of network technology and the wide use of mobile devices, traditional banking services gradually enter the field of mobile terminals, the service scenes of the traditional banking services tend to be diversified, the traditional banking services are not limited to office areas or network points of banks any more, and the realization of mobile approval of banking services such as loan services and the like becomes an inevitable requirement for establishing a new-era digital bank.
In the current mobile terminal business approval process, the mobile terminal is mainly used for directly accessing the database of the background of the bank system, under the access mode, a large amount of complex and difficult-to-card security verification and business rule verification matched with the background of the bank system need to be added in the background of the mobile terminal, a system interface needs to be correspondingly modified, and the development cost is extremely high.
Disclosure of Invention
The embodiment of the disclosure provides a business approval method, a business approval device, a business approval apparatus and a storage medium, which realize that an access interface based on the existing server of a bank system accesses the server and performs business approval, so that the improvement of a bank system interface for mobile equipment is not required, the development is convenient, and the cost is saved.
In a first aspect, an embodiment of the present disclosure provides a service approval method, where the service approval method is applied to a mobile device, and the service approval method includes:
determining the business to be examined;
determining a request address of a service detail page corresponding to the service to be approved recorded in a database of the mobile equipment;
obtaining a service detail page based on the request address;
and performing examination and approval operation on the service detail page to obtain an examination and approval result.
Optionally, performing an approval operation on the service detail page to obtain an approval result, including: determining an element tag name corresponding to a service to be approved in a database; determining elements to be processed in the business detail page according to the element tag names, wherein the elements to be processed comprise a first element for inputting submission information and a second element for executing operation; inputting the business to be examined and approved and/or user information into the first element; and performing an approval operation on the second element, and determining an approval result output by the service detail page based on the approval operation.
Optionally, the business approval method further includes: monitoring the waiting time for carrying out the examination and approval operation on the service detail page; determining whether the examination and approval operation is executed or not within a time period when the waiting time length is less than the threshold value; and if the examination and approval operation is finished, stopping monitoring the waiting time and carrying out the next operation.
Optionally, before determining the service to be approved, the service approval method further includes: receiving a request sent to a background of the mobile equipment through a front-end interface, and determining user information contained in the request, wherein the user information contains a user number; inquiring whether the user number exists in the cache record or not based on the user number; and if the user number exists in the cache record, determining that the identity authentication is passed.
Optionally, the business approval method further includes: if the user number does not exist in the cache record, determining an encrypted password corresponding to the user number from a database of the mobile equipment through the user number, and sending an authentication request carrying the user number and the encrypted password to the server; and determining that the authentication request fed back by the server is authenticated.
Optionally, the business approval method further includes: and if the identity authentication result is that the identity authentication is passed, storing the user information into the cache record.
Optionally, before determining the pending service, the method includes: receiving a request sent to a background of the mobile equipment through a front-end interface, and determining mechanism information contained in the request, wherein the mechanism information comprises a user mechanism number; determining an organization selection request address corresponding to a user organization number contained in a database of the mobile equipment; and sending an organization selection request containing the user number and the user organization number to the organization selection request address to obtain an organization selection result.
Optionally, before sending the organization selection request including the user number and the user organization number to the organization selection request address, the method includes: determining user numbers and authority information corresponding to user mechanism numbers contained in a database of the mobile equipment; determining whether the authority information meets the authority requirement corresponding to the service to be approved in the database; if the authority information meets the authority requirement, determining that the authority passes the verification; or if the authority information meets the authority requirement, determining that the authority verification fails, and outputting prompt information that the authority verification fails.
In a second aspect, the present disclosure further provides a service approval apparatus, where the service approval apparatus includes:
the determining module is used for obtaining a service detail page based on a request address of a service detail page corresponding to the service to be examined and approved recorded in a database of the mobile equipment and the request address;
and the processing module is used for executing the examination and approval operation on the service detail page to obtain an examination and approval result.
Optionally, the determining module is specifically configured to: determining an element tag name corresponding to a service to be approved in a database; determining elements to be processed in the business detail page according to the element tag names, wherein the elements to be processed comprise a first element for inputting submission information and a second element for executing operation; correspondingly, the processing module is specifically used for inputting the service to be examined and approved and/or the user information into the first element; and performing an approval operation on the second element, and determining an approval result output by the service detail page based on the approval operation.
Optionally, the determining module is further configured to: monitoring the waiting time for carrying out the examination and approval operation on the service detail page; determining whether the examination and approval operation is executed or not within a time period when the waiting time length is less than the threshold value; and if the examination and approval operation is finished, stopping monitoring the waiting time and carrying out the next operation.
Optionally, the determining module is further configured to: before determining the service to be approved, receiving a request sent to a background of the mobile equipment through a front-end interface, and determining user information contained in the request, wherein the user information contains a user number; inquiring whether the user number exists in the cache record or not based on the user number; and if the user number exists in the cache record, determining that the identity authentication is passed.
Optionally, the determining module is further configured to: if the user number does not exist in the cache record, determining an encrypted password corresponding to the user number from a database of the mobile equipment through the user number, and sending an authentication request carrying the user number and the encrypted password to the server; and determining that the authentication request fed back by the server is authenticated.
Optionally, the determining module is further configured to: and if the identity authentication result is that the identity authentication is passed, storing the user information into the cache record.
Optionally, the determining module is further configured to: before determining the business to be approved, receiving a request sent to a mobile equipment background through a front-end interface, and determining mechanism information contained in the request, wherein the mechanism information comprises a user mechanism number; determining an organization selection request address corresponding to a user organization number contained in a database of the mobile equipment; and sending an organization selection request containing the user number and the user organization number to the organization selection request address to obtain an organization selection result.
Optionally, the determining module is further configured to: before sending an organization selection request containing a user number and a user organization number to an organization selection request address, determining authority information corresponding to the user number and the user organization number contained in a database of the mobile equipment; determining whether the authority information meets the authority requirement corresponding to the service to be approved in the database; if the authority information meets the authority requirement, determining that the authority passes the verification; or if the authority information meets the authority requirement, determining that the authority verification fails, and outputting prompt information that the authority verification fails.
In a third aspect, the present disclosure also provides a mobile device, including:
at least one processor;
and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to cause the mobile device to perform the business approval method of any one of the first aspects.
In a fourth aspect, the present disclosure further provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-readable storage medium is configured to implement the business approval method according to any one of the first aspects of the present disclosure.
In a fifth aspect, the present disclosure also provides a computer program product comprising computer executable instructions, which when executed by a processor, are configured to implement the business approval method according to any one of the first aspect of the present disclosure.
According to the business approval method, the business approval device, the business approval equipment, the business approval system and the storage medium, the business to be approved input and selected at the front end of the mobile equipment is determined, then the business detail page provided by the server is obtained through the request address according to the request address of the business detail page corresponding to the business to be approved recorded in the database, and the corresponding approval operation is automatically completed in the background of the mobile equipment based on the business detail page.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is an application scenario diagram of a service approval method according to an embodiment of the present disclosure;
FIG. 2 is a flowchart of a business approval method according to an embodiment of the present disclosure;
fig. 3 is a flowchart of a business approval method according to another embodiment of the present disclosure;
FIG. 4 is a flowchart of a business approval method according to another embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a business approval apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a mobile device according to an embodiment of the present disclosure.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
The following describes the technical solutions of the present disclosure and how to solve the above technical problems in specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present disclosure will be described below with reference to the accompanying drawings.
The existing banking business examination and approval based on mobile equipment generally adopts a simple mobile terminal direct calling mode, namely, a transaction is directly initiated to a mobile terminal background through Transmission Control Protocol (TCP), and then the mobile terminal background synchronously updates a bank system server database after a certain check rule, so as to complete examination, approval and issuing of loan. However, the verification rule of the mobile terminal background is set by a mobile terminal developer, and the complexity and the safety are far lower than those of the verification rule of the bank system server. If the mobile terminal and the bank system server have the same security, a large amount of complex security check and business rule check which are difficult to card need to be added in the background of the mobile terminal, and meanwhile, the interface of the bank system server also needs to be correspondingly modified, so that the development cost is extremely high. Meanwhile, the code development time of the bank system server is far earlier than that of a mobile terminal background code, the development of the computer industry is rapid, the mobile terminal and the bank system technology stack are often greatly different, the difficulty of adapting the interfaces of the mobile terminal and the bank system is high, much time is consumed, the same safety is ensured, a set of brand new interfaces are often required to be re-developed for a specific service function, the development difficulty is high, the code reusability is low, and therefore the software research and development efficiency is low.
In order to solve the above problem, an embodiment of the present disclosure provides a service approval method, where a mobile terminal background directly accesses a server of a banking system for verification, and when the verification is passed, an existing access interface of the banking system is obtained from the server for service approval, so as to reduce workload required for additionally developing a mobile terminal program, and effectively ensure security and reliability of a banking service approved based on a mobile device.
The following explains an application scenario of the embodiment of the present disclosure:
fig. 1 is an application scenario diagram of a service approval method according to an embodiment of the present disclosure. As shown in fig. 1, in the process of conducting the service approval, the mobile device 100 records user information, input information such as a service to be approved, and the like input by the user according to an input operation of the user 110 at the front end, and then sends the input information to the server 120 of the banking system for verification, and approves the corresponding service based on the access interface, thereby completing the service approval.
It should be noted that, in the scenario shown in fig. 1, the mobile device, the user, and the server are illustrated as an example, but the disclosure is not limited thereto, that is, the number and the location relationship of the mobile device, the user, and the server may be any. In addition, the application scenario may also include other devices, such as a data storage device, which may be an external memory with respect to the server 120 or the mobile device 100, or an internal memory integrated in the server 120 or the mobile device 100.
The service approval method provided by the present disclosure is described in detail below by specific embodiments. It should be noted that the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.
Fig. 2 is a flowchart of a business approval method according to an embodiment of the present disclosure. The business approval method is applied to the mobile equipment. As shown in fig. 2, the service approval method provided in this embodiment includes the following steps:
step S201, determining the service to be examined and approved.
The pending service is service related information obtained by the mobile device through input and selection of a user in the service approval related application at the front end. The service approval related application can be credit class management application of the mobile terminal, or a page group encapsulated application program which is separately developed by the mobile terminal and used for service approval. Particularly, when the user inputs and selects the service to be approved, the service approval related application does not interact with the bank system server, so that the service approval related application only needs to meet the technical stack requirement of the mobile terminal, and the development difficulty is low.
Furthermore, the service to be approved includes all relevant information required in the service approval program corresponding to the server, such as the specific type and age of the service, and the opinion of the approver of the last approval node.
The mobile device may be any mobile terminal device, such as a mobile phone, a tablet computer, and the like.
Optionally, the information corresponding to the pending service, which is obtained by the mobile device from the service approval related application, is stored in a database in the mobile device, so as to facilitate query and call.
Step S202, determining a request address of a service detail page corresponding to the service to be approved recorded in the database of the mobile equipment.
Illustratively, the database of the mobile device includes a preset dictionary table, where the dictionary table includes all service types to be approved that are pre-recorded by the mobile developer, and request addresses of service detail pages of the server corresponding to the service types to be approved that are pre-recorded by the server developer.
The service detail page is used for showing a page file which contains input information necessary for completing service examination and approval and carries out setting triggering operation. The service detail page can be one or more, is determined according to the approval service to be handled, and is the preset existing page.
Furthermore, the service detail page is the existing page of the server, so that the requirements of the bank system server on safety check, technical stack and the like are met.
Therefore, the service detail page request address corresponding to the service to be examined and approved can be obtained by querying the dictionary table in the database. Further, one service type to be examined may correspond to request addresses of multiple pages in the dictionary table, or may correspond to multiple optional secondary pages of a page in the same request address, for example, a service selection page fixed by a server end corresponding to a request address, and different service detail pages may be entered according to different services to be examined selected on the service selection page.
Therefore, the keyword positioning can be carried out on the tags of the pages corresponding to the service types to be approved, such as the names of page files with specific naming rules and the page files with specific tags or specific form IDs contained in the contents; and the type of the business to be examined and approved can be determined through the concrete links, items and business varieties corresponding to the current business to be examined and approved.
Optionally, the process can be implemented by an existing java-based developed open source tool HtmlUnit, and the HtmlUnit reads files of each object interface, so as to quickly find the service detail interface.
Step S203, based on the request address, a service detail page is obtained.
The mobile device obtains the corresponding service detail page by accessing the server corresponding to the request address, and the process of the mobile device is the same as that of obtaining the service detail page by the server based on the request address, so that the process can receive the check of the existing check rule of the server, and the safety of the process is ensured.
The process of obtaining the service detail page is an imperceptible process for a user of the mobile equipment and is completely finished in the background of the mobile equipment, so that the problem of matching with a mobile terminal technology stack does not need to be considered, and the development cost can be saved.
And step S204, performing examination and approval operation on the service detail page to obtain an examination and approval result.
The approval operation comprises inputting and selecting the relevant information of the to-be-approved service required to be input and selected in the service detail page, and completing the confirmation or click operation required by the service approval. And the approval result comprises a result corresponding to the approval operation or approval completion prompt information fed back by the server based on the approval operation.
Optionally, the approval result may correspond to a certain link in the approval process, such as a submission feedback result of the approval opinions of the primary approver; or the operation result after all links of the approval process are finished, such as approval finish prompt obtained after approval opinions are submitted.
Illustratively, when a business needs to be audited in the background, the basic flow is as follows: the authorized manager checks the to-be-handled examination and approval items and the examination and approval details through the corresponding equipment, checks the user information, conveniently judges based on the user information, and checks the flow of the to-be-handled examination and approval business, so as to check the compliance of the business examination and approval flow; then, the approval result is submitted, the result information is sent to the server, and the information which is successfully sent is displayed through the front-end interface of the mobile device, so that the whole process of the business approval which needs to be checked is completed, the process is actually realized based on the business approval related application in the embodiment, and after the approval idea is submitted, the mobile device starts the process from step S201 to step S204 in the embodiment, wherein the business to be handled corresponds to all the operation and input information of the authorized manager.
According to the business approval method provided by the embodiment of the disclosure, the business to be approved input and selected by the front end of the mobile equipment is determined, then the business detail page provided by the server end is obtained through the request address according to the request address of the business to be approved corresponding to the business detail page recorded in the database, and the corresponding approval operation is automatically completed in the background of the mobile equipment based on the business detail page.
Fig. 3 is a flowchart of a business approval method according to another embodiment of the present disclosure. The business approval method provided by the embodiment of the present disclosure is a refinement based on the embodiment shown in fig. 2. As shown in fig. 3, the service approval method provided in this embodiment includes the following steps:
and S301, determining the service to be approved.
Step S302, determining a request address of a service detail page corresponding to the service to be approved recorded in a database of the mobile equipment.
And step S303, obtaining a service detail page based on the request address.
Optionally, when the service detail page corresponding to the service to be approved further includes a secondary page that needs to select and input information, for example, a service of the secondary approver needs to be filled in and forwarded, at this time, the service detail page is obtained, which includes obtaining the service detail interface and a secondary interface corresponding to the service detail interface.
At this time, after entering a service detail page file in the service detail interface, the page parsing range is narrowed according to each element ID in the page file, then key elements such as a submit button page object are obtained according to a structure label and the like in the page file, and then a second-level page is entered from the service detail service by simulating and triggering a click type event, thereby completing service approval based on the second-level page.
In some embodiments, the information corresponding to the pending service in the dictionary table of the mobile device further includes tag keywords or key element information of the corresponding secondary page, so as to facilitate querying and positioning.
And S304, determining the element tag name corresponding to the service to be approved in the database.
The elements comprise page elements such as forms, input boxes and buttons which need to be interacted in the service detail page, and each element in the service detail page comprises a corresponding label; the dictionary table of the database comprises keywords of element tags corresponding to the service types to be approved, and the element tag names on the service detail pages can be determined through the keywords.
And step S305, determining the element to be processed in the service detail page according to the element tag name.
The elements to be processed comprise a first element for inputting the submission information and a second element for executing the operation.
The page elements in the access interface including the service detail page and the secondary page are analyzed through page analysis, for example, rapid positioning is performed through tags such as an ID (identity) or an NAME (NAME) of the page elements, or stepwise positioning is performed through relations such as parent-child and element types among the elements, a target element is finally obtained, whether triggering of operation is required through methods such as simulated clicking or submission information is input is judged through identifying the tags of the corresponding elements, the submission information required to be input is determined, for example, a user NAME, an organization, the type of a service to be approved or other contents which can correspond to the information input in a login interface, and the contents obtained from the determined related information of the service to be approved are conveniently filled into the corresponding elements.
And S306, inputting the information of the service to be examined and approved and/or the user into the first element.
The user information is information of a login user of the approval service-related application, namely information of an approver, such as identity and authority description of the approver, which need to be attached to approval opinions. When the user logs in to the application related to the approval service, the application is input into the mobile equipment.
And S307, performing an approval operation on the second element, and determining an approval result output by the service detail page based on the approval operation.
The approval operation comprises clicking a button in the second element and selecting a form related to the service to be approved, and the operations are related to approval and are generally called approval operation.
In some embodiments, when all the approval operations are completed, that is, when the operations including clicking the submit button are completed, the business detail page sends the approval operations and the information input in the first element to the server, and meanwhile, the page is automatically refreshed, and a prompt page of completing submission or completing approval is displayed, where the prompt page is an approval result.
The process of inputting the service to be approved and/or the user information, executing the approval operation and obtaining the approval result is automatically completed by the background of the mobile equipment. And the mobile equipment displays the information corresponding to the approval result to the approval personnel through the business approval related application only when the approval result is determined.
Optionally, when the approval operation is performed on the service detail page, monitoring the waiting duration of the approval operation performed on the service detail page; determining whether the examination and approval operation is executed or not within a time period when the waiting time length is less than the threshold value; and if the examination and approval operation is finished, stopping monitoring the waiting time and carrying out the next operation.
The waiting time duration refers to the time duration from the time when the approval operation is executed to the time when the page receives the approval operation and triggers the corresponding event.
Or the existing Asynchronous JavaScript And XML (Asynchronous JavaScript And XML, referred to as AJAX for short) method may be adopted to process the Asynchronous access.
In some embodiments, the method can also be used for the case that the business detail page needs to be linked with the server for information.
Therefore, the whole process of carrying out business approval based on the existing access interface of the server is realized in the mobile equipment.
Wherein, steps S304 to S307 are further detailed for step S204 in the corresponding embodiment of fig. 2.
In this embodiment, the service detail page is obtained by determining the service to be approved and the request address of the service detail page corresponding to the service to be approved, the element to be processed is determined based on the page analysis of the service detail page, and the approval result is obtained by executing the corresponding operation on the element to be processed, thereby completing the service approval. The process is realized by a mobile equipment background based on a page analysis technology without user participation, so that page login and operation of a server side are simulated at a mobile equipment side, and further, perceptive quick operation is realized; the approval operation can be carried out based on the existing service detail page of the server side, an access interface does not need to be developed again, the service development difficulty is reduced, meanwhile, the requirement of the server side for information required by approval service can be met, the safety of the service approval process is effectively guaranteed, and meanwhile, the development cost is saved.
Fig. 4 is a flowchart of a business approval method according to another embodiment of the present disclosure. As shown in fig. 4, the business approval method may include:
step S401, receiving a request sent to a background of the mobile device through a front-end interface, and determining user information contained in the request, wherein the user information contains a user number.
The request sent to the background of the mobile device through the front-end interface comprises header information, the header information is content contained in a fixed position in the request information, the header information comprises user information and mechanism information, and the user information comprises a user number.
Specifically, the front-end interface is a front-end interface corresponding to the business approval related application set on the mobile device based on the business to be approved, and comprises a user login interface and an approval interface.
And the information input by the user on the front-end interface is verified by a preset verification rule in the mobile equipment and then is stored in a database of the background of the mobile equipment in real time.
And when the user finishes inputting all information and selects to finish the business examination and approval or submit the business examination and approval result on the front-end interface, triggering the process of sending the request containing the business to be examined and approved to the background of the mobile equipment. At this time, the user encrypted password corresponding to the requested user number may be read from the database to determine the user information.
The user here is an authorized approver, not a bank client who applies for the transaction.
At this time, the login process realized by the user through the front-end interface is not actually directly connected with the server through the login interface for login, but obtains the information input by the user, and the process does not involve the interaction of the server side. When a user submits a request, user information is sent to a request address for identity verification, and the process of the identity verification is interacted with the server side.
And S402, inquiring whether the cache record has the user number or not based on the user information.
When the user information passes the authentication of the server end once, the server end returns a record file (cookie for short) related to the user information, the mobile device stores the cookie into the cache record, and at the moment, the user is in a login state. When the user accesses the cache again, the cache records can be directly inquired.
Step S403, if the user number exists in the cache record, it is determined that the authentication is passed.
If the user information exists in the cache record, the user is proved to have been subjected to identity authentication, and the identity authentication is passed, and the user is in a login state; therefore, the processes of accessing the server and verifying can be reduced, and the efficiency of the approval process is improved.
Further, the user information exists in the cache record, which also indicates that the user completes the mechanism selection process, so that only subsequent related confirmation and operation processes of the to-be-approved service are required.
Step S404, if the user number does not exist in the cache record, sending an identity authentication request carrying the user number to the server.
Specifically, an encrypted password corresponding to the user number is determined from a database of the mobile device through the user number, and an authentication request carrying the user number and the encrypted password is sent to the server.
Inquiring a relevant record table corresponding to the business approval relevant application in a database, and acquiring an encrypted password corresponding to a user; through the user number and the password after encryption processing, a HyperText Transfer Protocol (HTTP) request, i.e., an authentication request, is initiated to the server, and whether login is successful is determined by returning a result.
Further, the HTTP request is verified by the server at the server side, and after the verification is passed, if the verification is passed, the cookie returned by the server is received.
For example, when a user approves a specific service, if the user has performed a service approval operation based on the approval application, the mobile device already stores the corresponding user information and cookie, and at this time, a user authentication process does not need to be performed to the server. And if the user does not carry out corresponding service approval operation before, the mobile equipment sends the login account information to the server through an http request, the login account information is compared with the approval personnel information recorded in the server for verification, when the verification is passed, the verification passed information and the corresponding cookie are sent to the mobile equipment, and the cookie is stored in the cache record of the mobile equipment so as to facilitate repeated access.
Furthermore, the records in the cache records have time limit, and after the time limit is exceeded, the cache database deletes the corresponding records.
Step S405, determining that the result of the authentication request fed back by the server is that the authentication is passed.
Further, if the verification is determined to pass according to the verification information, the user information is stored in a cache database, and parameters such as expiration time and the like are set.
If the user logs in the same mobile device before, if the service approval process is stopped, the approval process is carried out again, the login information cookie related to the user is stored in the database for caching, and the login simulation is not needed before the record in the cache database expires.
Alternatively, when the verification fails, a prompt may be output that requires re-verification or failure of the approval operation, and no record of the input is saved.
Step S406, receiving a request sent to the background of the mobile device through the front-end interface, and determining mechanism information contained in the request, wherein the mechanism information comprises a user mechanism number.
The information of the mechanism where the user is located is the mechanism information corresponding to the examining and approving personnel, and can be the name, code or number of the mechanism. According to different information of the mechanism where the user is located, corresponding approval authorities are different, for example, some businesses can only approve in banks and branches, but cannot approve in branches. Therefore, after the user authentication is completed, the authority thereof needs to be confirmed.
Further, the organization information of the user is obtained by the user organization number in the requested header information.
Further, the determination of the agency information may be performed before the authentication process or after the authentication.
Step S407, determining the authority information corresponding to the user number and the user mechanism number contained in the database of the mobile device.
Wherein the process of determining the rights is performed before sending the request to the server. The validation of the rights is typically performed upon receipt of a request to be sent from the front-end interface to the back-end.
And step S408, determining that the permission information meets the permission requirement corresponding to the to-be-approved service in the database in the mobile equipment.
The determining process is carried out in the mobile equipment, and the permission information corresponding to the service to be examined and approved is determined by comparing the permission requirement with the permission requirement preset in the database.
Further, if the authority information meets the authority requirement, the authority verification is determined to be passed.
In some embodiments, when the authority verification passes, no message is fed back, and the subsequent operation is directly performed.
Further, if the authority information meets the authority requirement, the authority verification is determined not to pass, and prompt information that the authority verification does not pass is output.
In some embodiments, when the permission verification fails, the related process of the business approval is stopped; the prompt message that the output authority verification fails further comprises: automatically switching to a mechanism selection page in the front-end interface, reselecting a mechanism, submitting a request again after the selection is finished, and performing permission verification again; or directly stopping the business approval process.
Step S409, determining an organization selection request address corresponding to the user organization number contained in the database of the mobile equipment.
Further, the mechanism selection request address is obtained from a database dictionary table of the mobile device according to the user number and the user mechanism number in the request header information.
In some embodiments, the organization selection request address is a fixed value, and the difference between the different user numbers and the corresponding user organization numbers is that the parameters transmitted to the organization selection request address are different.
Step S410, sending an organization selection request containing the user number and the user organization number to the organization selection request address to obtain an organization selection result.
And carrying mechanism selection information of the user number and the user mechanism number, sending a mechanism selection request to a mechanism selection request address, realizing mechanism selection of the server side based on the sent mechanism selection information, and obtaining a mechanism selection result.
The mechanism selection result is generally information that the mechanism selection is completed and is fed back by the server. Since the authority of the user passes the authority verification built in the system in the process from the front end to the back end, when the request is sent to the server, the authority does not need to be verified, and only the user mechanism selection necessary for the server to handle the approval service needs to be completed.
Step S411, determining a request address of a service detail page corresponding to the service to be approved recorded in the database of the mobile device.
After the identity verification and the mechanism selection pass, the mobile equipment automatically determines a business detail page.
And step S412, obtaining a service detail page based on the request address.
And step S413, performing examination and approval operation on the service detail page to obtain an examination and approval result.
In some embodiments, the operations of steps S401 to S413 are steps performed after the user completes the operation in the application related to the business approval and clicks the submit or corresponding button; therefore, the steps of user operation and the steps of interaction between the mobile equipment and the server are thoroughly separated, and the technical stack and the safety requirements of the compatible server end system are considered when the development of mobile terminal business approval related applications is not needed, so that the development is convenient, and the cost is saved.
In this embodiment, the mobile terminal firstly queries the cache database, and if there is a corresponding record in the cache database, directly sends a request to the server to obtain an access interface, and if there is no corresponding record, then sends an application to the server to perform identity verification and mechanism selection, and determines a service detail page after the mechanism selection passes, and performs an approval operation based on the service detail page to complete service approval. By simultaneously considering the information of the mechanism where the user is located, the authority of the user is verified, and the service approval efficiency is improved; meanwhile, the request sent to the server can be fully verified at the server side, so that the safety and the anti-fake capacity can be fully ensured.
Fig. 5 is a schematic structural diagram of a service approval apparatus according to an embodiment of the present disclosure. As shown in fig. 5, the service approval apparatus 500 includes: a determination module 510 and a processing module 520. Wherein:
the determining module 510 is configured to obtain a service detail page based on a request address of the service detail page corresponding to the service to be approved and the service to be approved recorded in the database of the mobile device.
And the processing module 520 is configured to perform an approval operation on the service detail page to obtain an approval result.
Optionally, the processing module 520 is specifically configured to: determining an element tag name corresponding to a service to be approved in a database; determining elements to be processed in the business detail page according to the element tag names, wherein the elements to be processed comprise a first element for inputting submission information and a second element for executing operation; correspondingly, the processing module is specifically used for inputting the service to be examined and approved and/or the user information into the first element; and performing an approval operation on the second element, and determining an approval result output by the service detail page based on the approval operation.
Optionally, the determining module 510 is further configured to: monitoring the waiting time for carrying out the examination and approval operation on the service detail page; determining whether the examination and approval operation is executed or not within a time period when the waiting time length is less than the threshold value; and if the examination and approval operation is finished, stopping monitoring the waiting time and carrying out the next operation.
Optionally, the determining module 510 is further configured to: before determining the service to be approved, receiving a request sent to a background of the mobile equipment through a front-end interface, and determining user information contained in the request, wherein the user information contains a user number; inquiring whether the user number exists in the cache record or not based on the user number; and if the user number exists in the cache record, determining that the identity authentication is passed.
Optionally, the determining module 510 is further configured to: if the user number does not exist in the cache record, determining an encrypted password corresponding to the user number from a database of the mobile equipment through the user number, and sending an authentication request carrying the user number and the encrypted password to the server; and determining that the authentication request fed back by the server is authenticated.
Optionally, the determining module 510 is further configured to: and if the identity authentication result is that the identity authentication is passed, storing the user information into the cache record.
Optionally, the determining module 510 is further configured to: before determining the business to be approved, receiving a request sent to a mobile equipment background through a front-end interface, and determining mechanism information contained in the request, wherein the mechanism information comprises a user mechanism number; determining an organization selection request address corresponding to a user organization number contained in a database of the mobile equipment; and sending an organization selection request containing the user number and the user organization number to the organization selection request address to obtain an organization selection result.
Optionally, the determining module 510 is further configured to: before sending an organization selection request containing a user number and a user organization number to an organization selection request address, determining authority information corresponding to the user number and the user organization number contained in a database of the mobile equipment; determining whether the authority information meets the authority requirement corresponding to the service to be approved in the database; if the authority information meets the authority requirement, determining that the authority passes the verification; or if the authority information meets the authority requirement, determining that the authority verification fails, and outputting prompt information that the authority verification fails.
In this embodiment, the service approval apparatus can implement service approval based on the existing access interface of the server by combining the modules, and meanwhile, has no perception on the user, thereby facilitating the development of the corresponding service application on the mobile device and saving the development cost.
Fig. 6 is a schematic structural diagram of a mobile device according to an embodiment of the present disclosure. As shown in fig. 6, the mobile device 600 includes: a memory 610 and a processor 620.
Wherein the memory 610 stores computer programs executable by the at least one processor 620. The computer program is executed by the at least one processor 620 to cause the mobile device to implement the business approval method as provided in any of the embodiments above.
Wherein the memory 610 and the processor 620 may be connected by a bus 630. The bus 630 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus. The communication interface is used for realizing communication between the database access device and other equipment (such as a client, a read-write library and a read-only library).
The memory 610 may include a Random Access Memory (RAM) and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
The processor 620 may be a general-purpose processor including a central processing unit CPU, a Network Processor (NP), and the like; but also a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components.
The related descriptions may be understood by referring to the related descriptions and effects corresponding to the method embodiments, which are not repeated herein.
One embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the business approval method provided by any one of the above method embodiments.
The computer readable storage medium may be, among others, ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
One embodiment of the present disclosure provides a computer program product comprising computer executable instructions for implementing the business approval method as in the above method embodiment when executed by a processor.
In the several embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (12)
1. A business approval method is applied to mobile equipment and comprises the following steps:
determining the business to be examined;
determining a request address of a service detail page corresponding to the service to be approved recorded in a database of the mobile equipment;
obtaining the service detail page based on the request address;
and executing examination and approval operation on the service detail page to obtain an examination and approval result.
2. The business approval method of claim 1, wherein the performing an approval operation on the business detail page to obtain an approval result comprises:
determining an element tag name corresponding to the service to be approved in the database;
determining elements to be processed in the business detail page according to the element tag names, wherein the elements to be processed comprise a first element for inputting submission information and a second element for executing operation;
inputting the service to be examined and approved and/or user information into the first element;
and performing an approval operation on the second element, and determining an approval result output by the service detail page based on the approval operation.
3. The business approval method of claim 1, further comprising:
monitoring the waiting time for executing the examination and approval operation on the service detail page;
determining whether the approval operation is finished or not within a time period when the waiting time length is less than a threshold value;
and if the approval operation is finished, stopping monitoring the waiting time and carrying out the next operation.
4. The business approval method according to any one of claims 1 to 3, wherein before determining the business to be approved, the method further comprises:
receiving a request sent to the background of the mobile equipment through a front-end interface, and determining user information contained in the request, wherein the user information contains a user number;
inquiring whether a user number exists in a cache record or not based on the user number;
and if the user number exists in the cache record, determining that the identity authentication is passed.
5. The business approval method of claim 4, further comprising:
if the user number does not exist in the cache record, determining an encrypted password corresponding to the user number from a database of the mobile equipment through the user number, and sending an identity authentication request carrying the user number and the encrypted password to a server;
and determining that the result of the authentication request fed back by the server is authentication pass.
6. The business approval method of claim 5, further comprising:
and if the identity authentication result is that the identity authentication is passed, storing the user information into a cache record.
7. The business approval method of claim 4, wherein before determining the business to be approved, the method comprises:
receiving a request sent to the background of the mobile equipment through a front-end interface, and determining mechanism information contained in the request, wherein the mechanism information comprises a user mechanism number;
determining an organization selection request address corresponding to the user organization number contained in a database of the mobile equipment;
and sending an organization selection request containing the user number and the user organization number to the organization selection request address to obtain an organization selection result.
8. The business approval method of claim 7, wherein before sending the organization selection request including the user number and the user organization number to the organization selection request address, the method comprises:
determining the user number and authority information corresponding to the user mechanism number contained in a database of the mobile equipment;
determining whether the permission information meets permission requirements corresponding to the business to be approved in the database;
if the authority information meets the authority requirement, determining that the authority passes verification;
or if the authority information meets the authority requirement, determining that the authority verification fails, and outputting prompt information that the authority verification fails.
9. A business approval apparatus applied to a mobile device includes:
the determining module is used for obtaining a service detail page based on a request address of a service to be approved and a service detail page corresponding to the service to be approved recorded in a database of the mobile equipment;
and the processing module is used for executing the examination and approval operation on the service detail page to obtain an examination and approval result.
10. A mobile device, comprising:
at least one processor;
and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to cause the mobile device to perform the business approval method of any one of claims 1-8.
11. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, implement the business approval method of any one of claims 1-8.
12. A computer program product comprising computer executable instructions for implementing a business approval method as claimed in any one of claims 1 to 8 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110656434.7A CN113283797A (en) | 2021-06-11 | 2021-06-11 | Business approval method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110656434.7A CN113283797A (en) | 2021-06-11 | 2021-06-11 | Business approval method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113283797A true CN113283797A (en) | 2021-08-20 |
Family
ID=77284556
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110656434.7A Pending CN113283797A (en) | 2021-06-11 | 2021-06-11 | Business approval method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113283797A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106485388A (en) * | 2015-09-01 | 2017-03-08 | 北京奇虎科技有限公司 | The right management method of business approval system and device |
| CN106844471A (en) * | 2016-12-22 | 2017-06-13 | 北京市天元网络技术股份有限公司 | A kind of electronic operation and maintenance system form data processing method and server |
| CN107798509A (en) * | 2017-09-22 | 2018-03-13 | 新智云数据服务有限公司 | Employee's bootstrap method and device |
| CN107943600A (en) * | 2017-11-21 | 2018-04-20 | 杭州财人汇网络股份有限公司 | A kind of method and apparatus of tradomation processing |
| CN112036736A (en) * | 2020-08-28 | 2020-12-04 | 杭州指令集智能科技有限公司 | Workflow creating method and device |
-
2021
- 2021-06-11 CN CN202110656434.7A patent/CN113283797A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106485388A (en) * | 2015-09-01 | 2017-03-08 | 北京奇虎科技有限公司 | The right management method of business approval system and device |
| CN106844471A (en) * | 2016-12-22 | 2017-06-13 | 北京市天元网络技术股份有限公司 | A kind of electronic operation and maintenance system form data processing method and server |
| CN107798509A (en) * | 2017-09-22 | 2018-03-13 | 新智云数据服务有限公司 | Employee's bootstrap method and device |
| CN107943600A (en) * | 2017-11-21 | 2018-04-20 | 杭州财人汇网络股份有限公司 | A kind of method and apparatus of tradomation processing |
| CN112036736A (en) * | 2020-08-28 | 2020-12-04 | 杭州指令集智能科技有限公司 | Workflow creating method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200285978A1 (en) | Model training system and method, and storage medium | |
| CN109791591B (en) | Method and system for identity and credential protection and verification via blockchain | |
| US11257130B2 (en) | Method and system for review verification and trustworthiness scoring via blockchain | |
| US8755510B2 (en) | Methods and systems for providing customer relations information | |
| CN107016132B (en) | Online question bank quality improving method and system and terminal equipment | |
| WO2020077836A1 (en) | Service data management method, apparatus and device, and computer-readable storage medium | |
| US11669839B2 (en) | System and method for processing a digital transaction | |
| CN112150113A (en) | Method, device and system for borrowing file data and method for borrowing data | |
| CN112650732A (en) | Service processing method, device, equipment and storage medium | |
| CN113037505B (en) | Method and system for realizing trusted Web application | |
| CN110138743A (en) | Acquisition methods, device, computer equipment and the storage medium of resource bid file | |
| CN109801169A (en) | Financing lease application method, device, computer equipment and storage medium | |
| CN108170860A (en) | Data query method, apparatus, electronic equipment and computer readable storage medium | |
| CN112651716A (en) | Data processing method, device and storage medium | |
| CN111582831A (en) | Government affair mailbox management method, system and storage medium | |
| CN113283797A (en) | Business approval method, device, equipment and storage medium | |
| CN112632391A (en) | Data processing method, device and storage medium | |
| CN113987035A (en) | Block chain external data access method, device, system, equipment and medium | |
| TWI649668B (en) | Method of authentication and dialogue robot based on instant messaging program | |
| US20150317640A1 (en) | Methods and Systems for Providing Customer Relations Information | |
| CN111901299A (en) | Application authentication method and device, electronic equipment and storage medium | |
| CN118071264A (en) | Complaint data processing method, apparatus, device and computer readable storage medium | |
| CN117726337A (en) | Transaction information processing method, device, electronic equipment and storage medium | |
| US20190266602A1 (en) | Method and system for overseeing execution of graph-based contracts using hash chains | |
| CN116738949A (en) | Report processing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |