CN116029845A

CN116029845A - Financial system-based push service processing method and related equipment

Info

Publication number: CN116029845A
Application number: CN202211287059.4A
Authority: CN
Inventors: 王光旸; 张洁瑛; 刘晶; 刘宁英; 曹佳文; 邢健; 孙海燕; 张侠; 王慧婷; 尤媛媛; 孔祥凯; 贺湘峻
Original assignee: Beijing China Power Information Technology Co Ltd; State Grid Materials Co Ltd
Current assignee: Beijing China Power Information Technology Co Ltd; State Grid Materials Co Ltd
Priority date: 2022-10-20
Filing date: 2022-10-20
Publication date: 2023-04-28

Abstract

The financial system can inquire the to-be-handled information stored in association with each examination account according to examination object information which is preset and contains at least one examination account with examination authority, then can determine to-be-handled information to be pushed in the inquired to-be-handled information according to a pushing to-be-handled record table aiming at a portal system, namely the latest to-be-handled information which is not pushed under the examination account, and pushes the to-be-handled information to the portal system through a cross-system technology so as to uniformly display each to-be-handled information of each examination account under the corresponding examination account in the portal system, so that a user can uniformly enter the to-be-handled information, wrong to-be-handled tasks are avoided, and service processing efficiency and reliability are improved.

Description

Financial system-based push service processing method and related equipment

Technical Field

The application relates to the technical field of computers, in particular to a pushing business processing method based on a financial system and related equipment.

Background

At present, an enterprise's financial system usually has an electronic image function, electronic processing is performed on various paper documents, archives, paper notes and other accessories, and long-term centralized management is realized by replacing the paper documents with the obtained electronic images.

Based on the method, when an enterprise employee needs to cancel a certain business document, the enterprise employee can enter an employee canceling system, image information of an accessory of the business document can be uploaded to a financial system, a corresponding approver is informed to enter a business approving system, approval touch operation is carried out on the business document to be approved uploaded by the employee, the corresponding image information is called from the financial system to carry out approval, the process is complicated, and approval efficiency and reliability are reduced.

Disclosure of Invention

In order to solve the technical problems and improve approval efficiency and reliability, the embodiment of the application provides the following technical scheme:

in one aspect, the present application proposes a push service processing method based on a financial system, the method comprising:

obtaining approval object information configured for a financial system; the approval object information comprises at least one approval account number with approval authority;

inquiring information to be handled which is respectively associated and stored by the at least one approval account;

determining to-be-pushed information in the queried to-be-pushed information according to a to-be-pushed record table aiming at the portal system; the pushing to-do record list comprises pushing records of all to-do information pushed to the portal system;

Pushing the to-be-pushed information to the portal system so as to display the associated to-be-handled information under the approval account number logged in the portal system.

Optionally, the determining the to-be-pushed information in the queried to-be-pushed information according to a to-be-pushed record table for the portal system includes:

detecting whether a pushing record of the approval account exists in a pushing to-do record table aiming at the portal system;

determining that a first trial account number of the push record does not exist in the push to-do record table, and determining the queried to-do information stored in association with the first trial account number as to-do information to be pushed;

determining that a second trial account of the pushing record exists in the pushing record table, and detecting whether pushing information contained in the pushing record of the second trial account is the same as the associated stored information to be handled;

and determining the to-be-handled information which is different from the pushing information contained in the pushing record of the second trial account as the to-be-pushed to-be-handled information.

Optionally, the method further comprises:

generating a corresponding withdrawal to-do request aiming at the detected push information contained in the push record which is different from the to-do information stored in association with the second trial account;

The withdrawal to-do request is sent to the portal system to request withdrawal of to-do information under the corresponding second trial account number in the portal system;

and obtaining the successful withdrawal prompt information fed back by the portal system, and pushing the corresponding to-be-pushed information to the portal system.

Optionally, the pushing the to-be-pushed information to the portal system includes:

obtaining a push time rule configured for push services of the portal system;

and pushing the information to be pushed to the portal system according to the pushing time rule.

encrypting the information to be pushed according to encryption information configured for the service type of the information to be pushed to obtain a ciphertext to be pushed;

and sending the ciphertext to be pushed to the portal system through a cross-system Webservice technology.

Optionally, the method further comprises:

obtaining a push service configuration request aiming at a portal system, and outputting a remote data transmission configuration page;

responding to the configuration input operation of the remote data transmission configuration page, and obtaining configuration information of push service aiming at the portal system; the configuration information comprises an interface address for pushing information to be handled to the portal service, a push service identifier of the portal system, a skip link address between the portal system and the financial system and a system identifier of the financial system aiming at a pushing mode or a withdrawing mode of the information to be handled;

The pushing the to-be-pushed information to the portal system includes:

pushing the information to be pushed to the portal system according to the configuration information.

Optionally, the method further comprises:

receiving a to-be-handled service query request from the portal system; the to-be-handled service query request comprises account information of logging in the portal system and a service identifier of the to-be-handled service for query;

determining that the account information belongs to an approval account of the business to be handled according to approval object information corresponding to the business identifier;

inquiring each piece of to-be-handled information of the to-be-handled business stored in association with the account information;

and sending the queried information to be handled to the portal system, and displaying the queried information to be handled by a client side logging in the portal system.

In yet another aspect, the present application further proposes a push service processing device based on a financial system, the device comprising:

the approval object information acquisition module is used for acquiring approval object information configured for the financial system; the approval object information comprises at least one approval account number with approval authority;

the to-be-handled information inquiry module is used for inquiring to-be-handled information stored in each of the at least one approval account in an associated mode;

The information to be pushed determining module is used for determining information to be pushed in the queried information to be pushed according to a pushing record to be done list aiming at the portal system;

the to-Do information pushing module is used for pushing the to-Do information to be pushed to the portal system so as to display the associated to-Do information under the approval account number logged in the portal system.

In yet another aspect, the present application further proposes an electronic device, including:

a communication module; an input assembly; an output assembly;

a memory for storing a program for implementing the push service processing method based on the financial system as described above;

and the processor is used for loading and executing the program stored in the memory to realize the pushing business processing method based on the financial system.

In yet another aspect, the present application further proposes a computer readable storage system, on which a computer program is stored, where the computer program is loaded and executed by a processor, to implement a push service processing method based on a financial system as described above.

Therefore, the financial system can inquire the to-be-handled information stored in association with each approval account according to the preset approval object information containing at least one approval account with approval authority, and then can determine the to-be-handled information to be pushed in the inquired to-be-handled information according to a pushing to-be-handled record table aiming at the portal system, namely the latest to-be-handled information which is not pushed under the approval accounts, and push the to-be-handled information to the portal system through a cross-system technology so as to uniformly display each to-be-handled information of each approval account under the corresponding approval account in the portal system, so that a user can uniformly enter the to-be-handled information, wrong to-be-handled tasks are avoided, and service processing efficiency and reliability are improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings may be obtained according to the provided drawings without inventive effort to a person skilled in the art.

FIG. 1 is a schematic architecture diagram of an alternative application environment suitable for the financial system-based push business processing method proposed in the present application;

FIG. 2 is a schematic hardware architecture of an alternative example of an electronic device suitable for use in the financial system-based push business processing method presented herein;

FIG. 3 is a flow chart of an alternative example of a financial system-based push business processing method as set forth in the present application;

FIG. 4 is a flow chart of yet another alternative example of a financial system-based push business processing method as set forth in the present application;

FIG. 5 is a flow chart of yet another alternative example of a financial system-based push business processing method set forth in the present application;

FIG. 6 is a flow chart of yet another alternative example of a financial system based push business processing method as set forth herein;

FIG. 7 is a schematic structural diagram of an alternative example of a financial system-based push service processing device according to the present application;

FIG. 8 is a schematic structural diagram of another alternative example of a financial system-based push service processing device according to the present application;

fig. 9 is a schematic structural diagram of another alternative example of the push service processing device based on the financial system.

Detailed Description

In practical application, for document image information transmitted by an employee reimbursement system and a financial system (i.e. an integrated management system) of an enterprise, namely, electronic images of various accessories (such as various invoices, data, various paper files of contracts and the like) of any document service uploaded by the employee, information pushing such as document pushing, document approval or document review can be performed through Webservice technology, so that when operating system documents, approval personnel of the enterprise are required to log in a plurality of systems to check, thereby causing the problems of high approval error rate, low approval efficiency and the like.

Moreover, since Webservice technology is a cross-programming language and cross-operating system platform remote call technology, that is, a cross-platform remote call technology, information transmission between different systems is realized by adopting a standard SOAP (Simple Object Access Protocol) protocol, the SOAP belongs to a w3c standard protocol and is an http-based application layer protocol, so that information in xml data format is transmitted between different systems, in order to meet the system interaction requirement of supporting different languages, a Webservice technology can be used for constructing a service call interface, and a caller (client) and a callee (server) both need to use Webservice technology, but cannot meet the requirement of high concurrent data transmission because the Webservice technology is used for transmitting xml data.

In order to improve the above problem, the present application proposes to configure at least one approval account with corresponding approval authority for each to-be-handled service supported by the finance system in advance, that is, to configure the approval authority of the enterprise leader in advance, determine each approval account of the approvers and the approval object with the approval authority thereof, that is, determine each to-be-approved service with the approval authority in the finance system, so that the finance system can associate and store the obtained to-be-handled information (such as document image information uploaded by the enterprise staff, i.e. to-be-approved image information, etc.) with the obtained to-be-handled account, and then the finance system can push the stored to the corresponding to-be-handled account of the portal system to be uniformly displayed, that is, the user logs in the approval account of the portal system, and can display all to-be-handled information stored in association with the approval account, so that the approver can perform approval and do not need to query and display each to-be-handled information under the name, thereby improving the approval efficiency and reliability.

In addition, in the process of pushing the to-be-handled information to the portal system by the financial system, the queried to-be-handled information can be compared with each pushing record in the pushing to-be-handled record list of the portal system, the to-be-pushed to the portal system is pushed after the to-be-pushed to-be-handled information is accurately determined, repeated pushing of the same to-be-handled information is avoided, the fact that the to-be-handled information checked by the portal system is the latest to-be-handled information is ensured, approval reliability is further improved, and resource waste is reduced.

Further, in order to improve the transmission security among the systems, the information and the information, the information to be pushed can be pushed after being strictly encrypted, for example, the information to be handled belonging to different service types is encrypted by configuring corresponding encrypted information aiming at the different service types, so that the encryption modes of the different service types are different, the confidentiality of cross-system information transmission is improved, and the information leakage is avoided.

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is to be understood that the embodiments described are merely some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Referring to fig. 1, a schematic architecture of an alternative application environment suitable for the push service processing method based on a financial system proposed in the present application, where the architecture in the application environment may include a financial system 100, a portal system 200, and at least one service terminal 300, where:

The financial system 100 can be an integrated information system, and can be coupled and integrated with multiple systems (such as an information system, an invoice system, a tax system and the like, as the case may be), so that various borrowing, various reimbursement, purchasing and paying of material service, payment application and other processes are not broken, and the functions of unified storage of original document images, full-process image review, ticket face information recognition and the like are supported.

In practical application of the present application, in combination with the above description of the technical solution of the present application, a BPM (Business Process Management ) module is configured in the above financial system 100, and is configured to configure approver information when a system document waits for approval of a business, for example, determine the approver having approval authority corresponding to the business to be handled, and a login account under the financial system, and record the login account of the approver as an approval account. Regarding the constituent structure of the financial system, reference may be made to the following description of the corresponding parts of the embodiments, which will not be described in detail.

Portal system 200 may be a single portal for providing an enterprise with access to various information resources of the enterprise, and a user may log in each service system from the portal system to implement operations such as to-be-handled service review and approval.

It can be seen that the operation interface of the portal system 200 may display the service identifier of each service system, so that the user may select to trigger and enter the corresponding service operation page. The service identifier may include a service name, an access address, a service icon, etc. corresponding to the service system, and the content of the service identifier and the display manner thereof on the operation interface of the portal system are not limited in the present application, and may be determined according to circumstances.

In practical application, a user can log in a financial system by using a service terminal, configure auditors with corresponding auditing rights aiming at different types of services of the financial system, and determine corresponding auditor information, such as auditing account numbers; information configuration of a Webservice technology is realized in a system configuration file so as to support data transmission between a portal system and a financial system, the determined information to be handled is pushed to the portal system, and the Dom4j technology and the Webservice technology are sequentially utilized for data analysis and data transmission.

The Webservice is a defined set of modularized APIs (Application Program Interface, application program interfaces), and can be called through a network to execute request services of a remote system, for example, after logging in a portal system, a to-do business processing operation is triggered, each piece of to-do information associated with a current login account stored in a financial system can be requested to be consulted, and the financial system can adopt Webservice technology to push the to-do information across items. The Dom4j is a Java XML API, which is used as an information decryption means to read XML files, and in this embodiment of the present application, the financial system may use a Dom4j message parsing technique to parse XML messages to obtain request contents, so as to feed back the information to be handled that is requested to be referred to or approved, and the specific application process is not described in detail in this application.

Therefore, after the user enters the portal system of the enterprise by using the service terminal 300 such as the smart phone, the tablet personal computer, the wearable device, the desktop computer and the like, the user can select to process the to-be-handled service, and access the server side of the financial system through the corresponding link address so as to obtain the to-be-handled information stored in association with the login account. The server supporting the operation of each business service that can be provided by the financial system can be an independent physical server, can be a server cluster integrated by a plurality of physical servers, can also be a cloud server supporting cloud computing service, and the like, and can be determined according to actual requirements.

In practical application, the architecture composition of the application environment proposed in the present application is not limited to the composition structure shown in fig. 1, and other devices such as an operation and maintenance management device and a monitoring device may be configured according to practical requirements, which is not listed in the present application.

Referring to fig. 2, a hardware architecture diagram of an alternative example of an electronic device suitable for the financial system-based push processing method proposed in the present application may include, but is not limited to, the service terminal described above, and as shown in fig. 2, may include, but is not limited to: a communication module 310, an input component 320, an output component 330, a memory 340, and a processor 350, wherein:

the number of the communication module 310, the input assembly 320, the output assembly 330, the memory 340 and the processor 350 may be at least one, and the communication module 310, the input assembly 320, the output assembly 330, the memory 340 and the processor 350 may be connected to a communication bus of the electronic device, so as to realize communication connection between each other, and meet the data interaction requirement.

The communication module 310 may include a communication module capable of implementing data interaction by using a wireless communication network, such as a WIFI module, a 5G/6G (fifth generation mobile communication network/sixth generation mobile communication network) module, a GPRS module, etc., where the communication module 310 may further include a communication interface capable of implementing data interaction between internal components of an electronic device, such as a USB interface, a serial/parallel port, an I/O port, etc., and specific content included in the communication module 310 is not limited in this application.

The input component 320 may include at least one of a touch sensing unit, a keyboard, a mouse, a camera, a pickup, etc. that senses a touch event on the touch display panel, and may be determined according to a product type of the electronic device, a usage habit of a user to input information using the electronic device, etc.

The output component 330 may include at least one of a display, a speaker, a vibration mechanism, a lamp, etc., and the display may include a display panel, such as a touch display panel, etc., for displaying various business interfaces possessed by the financial system or an operation interface of the portal system of the enterprise, so as to implement corresponding interactive operations accordingly.

In this embodiment of the present application, a user may use at least one input component 320 to perform a corresponding input operation for the content output by the output component 330, for example, input a login account number and a password of a financial system, select displayed information to be handled for review and approval, and the like, and may be determined according to a scene interaction requirement, which is not described in detail herein.

Memory 340 may be used to store programs that implement the financial system-based push service processing methods described in the method embodiments below; the processor 350 may load and execute the program stored in the memory to implement the steps of the financial system based push service processing method described in the following corresponding method embodiments, and the specific implementation process may refer to the description of the corresponding parts of the following embodiments, which are not described in detail herein.

In embodiments of the present application, memory 340 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device or other volatile solid-state storage device. The processor 350 may be a central processing unit (Central Processing Unit, CPU), application-specific integrated circuit (ASIC), digital Signal Processor (DSP), application-specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA), or other programmable logic device, etc.

It should be understood that the structure of the electronic device shown in fig. 2 is not limited to the electronic device in the embodiment of the present application, and in practical applications, the electronic device may include more or fewer components than those shown in fig. 2, or may combine certain components, such as an antenna; a sensor module; power supply modules, etc., are not specifically recited herein.

Referring to fig. 3, a flowchart of an alternative example of a financial system-based push service processing method proposed in the present application, where the method may be performed by an electronic device, as shown in fig. 3, and the method may include:

step S31, obtaining approval object information configured for a financial system; the approval object information comprises at least one approval account number with approval authority;

In the practical application of the application, after the financial system completes the relevant configuration of the pushing service of the portal system, the to-be-checked image information of each bill reported by enterprise staff stored in a database can be used for waiting for the information, and the to-be-checked information of one or more to-be-checked services can be configured to be checked, namely, checking account numbers corresponding to checking authority of each to-be-checked service are provided, so that corresponding checking object information is formed. The configuration implementation method of the approval object information is not limited in the present application.

Step S32, inquiring information to be handled which is respectively associated and stored by at least one approval account;

according to the method, the approval account with approval authority is determined, namely, the account information registered by the user needing to inquire and process the information to be handled, the information to be handled which is required to be referred and processed by the corresponding user in the database can be determined according to the approval authority content, and the method specifically can enter a BPM module of a financial system to inquire whether the information to be handled exists under each approval account, and the inquiry implementation process is not described in detail.

Step S33, determining to-be-pushed information in the queried to-be-pushed information according to a to-be-pushed record table aiming at the portal system;

the pushing to-do record table may include pushing records of all to-do information pushed to the portal system, so that all to-do information stored in the database of the queried financial system is compared with historical pushed to-do information corresponding to all pushing records, and it is determined which of all to-do information is not pushed and which is pushed to-do information, so that repeated pushing of the same to-do information is avoided, and resource waste is caused.

The content of the push to-do record table of the portal system and the content of each push record contained in the push to-do record table are not limited, and the push to-do record table can be used as appropriate. Optionally, in practical application, the pushing to-do record table may further include service identifiers of different service types, and according to the service identifier, historical pushing information of a corresponding class of service is queried, and is compared with each piece of to-do information associated with the queried service identifier to determine to-be-pushed to-do information, such as to-do information which is not pushed.

Therefore, the application can enter a BPM system after the financial system, inquire the pre-configured to-be-handled information of the approval account numbers of the users, compare the locally inquired to-be-handled information with the push to-be-handled registration form of the portal system, execute the business processing logic corresponding to the comparison result, and determine whether to push the corresponding to-be-handled information to the current login place of the portal system and under the account numbers.

Step S34, pushing the information to be pushed to the portal system so as to display the associated information to be done under the approval account number logged in the portal system.

After the to-be-pushed information associated with the approval account is determined by combining the related description of the communication interaction method of each system under the application environment framework, the determined to-be-pushed information can be uniformly displayed under the corresponding approval account pushed to the portal system according to the preset pushing rule, so that the approver can uniformly enter to process the to-be-pushed information, and the service processing efficiency is improved.

Referring to fig. 4, for a flowchart of yet another alternative example of the financial system-based push service processing method proposed in the present application, this embodiment may describe an alternative refinement implementation method of the financial system-based push service processing method described above, and as shown in fig. 4, the refinement implementation method may include, but is not limited to:

step S41, obtaining approval object information configured for a financial system; the approval object information comprises at least one approval account number with approval authority;

step S42, inquiring information to be handled which is respectively associated and stored by at least one approval account;

regarding the implementation procedure of step S41 and step S42, the description of the corresponding parts of the above embodiments may be followed, and this embodiment will not be described in detail here.

Step S43, detecting whether a push record of an approval account exists in a push record to-be-handled table aiming at a portal system; if not, go to step S44; if yes, go to step S46;

step S44, determining that a first trial account number of a pushing record does not exist in the pushing record list, and determining the to-be-handled information stored in association with the queried first trial account number as the to-be-handled information to be pushed;

step S45, pushing the information to be pushed to a portal system according to a preset pushing time rule;

In combination with the above description of the push to-do record table, as the record has the to-do information pushed to the portal system by the financial system, namely the history push information, the record can be compared with the locally queried to-do information to determine that the push record of one or more push accounts does not exist in the push to-do record table, which indicates that no to-do information is pushed to the corresponding push account before, the queried to-do information of the corresponding examination account can be determined as the to-do information to be pushed, and then the to-do information to be pushed can be pushed to the corresponding examination account in the portal system for display according to the preset time interval and other timed push rules.

It can be seen that for the above step S34, it may include: the method for configuring the pushing time rule and the content thereof are not limited. The pushing time rules for different types of services can be the same or different, and can be determined according to the conditions, then the determined to-be-pushed information of the corresponding type of service can be pushed to a portal system according to the pushing time rules, and the to-be-pushed information is displayed under a corresponding approval account, so that the implementation process is not described in detail in the application.

Step S46, determining a second trial account with push records in the push to-do record table, and detecting whether push information contained in the push records of the second trial account is the same as the associated stored to-do information; if yes, not executing operation on the information to be handled; if not, go to step S47;

step S47, the information to be handled which is different from the pushing information contained in the pushing record of the second trial account is the information to be handled which is to be pushed;

determining that a pushing record of at least one approval account exists in the pushing record table according to the comparison result of the information to be handled and the pushing record table, and indicating that the information to be handled is pushed to the corresponding approval account in the past and is recorded as pushing information, so that consistency detection can be further carried out on the pushing information contained in the pushing record of the approval account and the queried corresponding information to be handled, and if the pushing information and the queried information to be handled are the same, indicating that the queried information to be handled is pushed and pushing operation is not needed; otherwise, if the two information are different, the fact that the information to be handled which is already pushed to the approval account is wrong is indicated, and the latest inquired corresponding information to be handled needs to be pushed to the approval account again, so that the inquired information to be handled which is stored in association with the approval account and is stored in the presence of the pushing record can be determined to be the information to be handled which is to be pushed.

Step S48, generating a corresponding withdrawal to-do request aiming at the detected push information contained in the push record which is different from the to-do information stored in association with the second trial account;

step S49, the withdrawal request is sent to a portal system to request withdrawal of the information to be handled under the corresponding second trial account in the portal system;

step S410, obtaining successful withdrawal prompt information fed back by the portal system, and pushing the corresponding to-be-pushed information to the portal system.

According to the detection mode, the fact that the information to be handled which is correlated with at least one examination account is pushed to the portal system is determined, but the pushed information to be handled is inconsistent with the information to be handled which is queried newly, in order to ensure the reliability of the information to be handled which is queried by an examination person and the reliability of the examination operation which is performed by the examination person, correct information to be handled is pushed again after the original push information is pushed back, namely, a request for withdrawing the information to be handled is sent to the portal system, namely, the request for withdrawing the information to be handled which contains the examination account which is withdrawn and the information to be withdrawn and the like, corresponding information which exists in the portal system is withdrawn, namely, the information to be handled which exists in the examination account in the portal system is deleted, and after the success of withdrawing the information to be handled is determined, the financial system pushes the latest information which is stored in the examination account which is correlated with the query account to the portal system, so that the information to be the latest information to be examined in each account is guaranteed, and the reliability of the information to be handled is improved for the following examination person and the examination person.

Referring to fig. 5, a flowchart of still another alternative example of the financial system-based push service processing method proposed in the present application, the method is still described from the perspective of an electronic device, and as shown in fig. 5, the method may include:

step S51, a push service configuration request aiming at a portal system is obtained, and a remote data transmission configuration page is output;

step S52, responding to the configuration input operation of the remote data transmission configuration page, and obtaining configuration information of push service aiming at the portal system;

in the embodiment of the present application, the configuration information may include, but is not limited to: pushing an interface address of information to be handled to a portal service; a pushing mode or a withdrawing mode aiming at the information to be handled (namely, a method name for pushing the information to be handled or withdrawing the information to be handled to a portal system by configuring a financial system); push service identification (e.g., namespace) of portal systems; a skip link address between the portal system and the financial system (such as a link address for configuring the portal system to click a link to skip to a to-be-handled interface under a login approval account in the financial system); system identification of the financial system, etc.

In practical application, a time timing task can be pre-configured to obtain a pushing time rule configured for a pushing service of the portal system, so that the interface can be started in a subsequent timing manner, and information to be handled is pushed to the portal system in a timing manner. In addition, the information of the Webservice remote data transmission technology is completed, so that the data analysis and the data transmission can be sequentially carried out by utilizing the Dom4j technology and the Webservice technology, after at least the two configurations are completed, table data creation configuration is carried out on a database of the financial system, and approval object information such as an approver with approval authority, an approval account and the like is determined.

Step S53, obtaining approval object information configured for the financial system; the approval object information comprises at least one approval account number with approval authority;

step S54, inquiring information to be handled which is respectively associated and stored by at least one approval account;

step S55, determining to-be-pushed information in the queried to-be-pushed information according to a to-be-pushed record table aiming at the portal system;

regarding the implementation process of the step S53 to the step S55, reference may be made to the description of the corresponding parts of the above embodiments, which are not described herein.

Step S56, encryption processing is carried out on the information to be pushed according to the encryption information configured for the service type of the information to be pushed, so as to obtain a ciphertext to be pushed;

step S57, sending the ciphertext to be pushed to the portal system according to the pushing time rule by using a cross-system Webservice technology and the configuration information.

In the embodiment of the present application, in order to improve the security of data transmission between systems, after determining to-be-pushed information according to the above description, the financial system may perform strict encryption processing on the to-be-pushed information according to encryption information customized in advance for a project to which the financial system belongs, and then push the to the portal system, and in the pushing process, the obtained to-be-pushed ciphertext may be sent to the portal system at regular time according to a pre-configured pushing method by using a cross-system Webservice technology, so that the implementation process will not be described in detail in the present application.

Referring to fig. 6, for a flowchart of another alternative example of the financial system-based push service processing method provided in the present application, this embodiment takes an application scenario in which an approver refers to and processes each to-be-handled information under its own approval authority as an example, and describes the financial system-based push service processing method, as shown in fig. 6, the method may include:

step S61, receiving a to-be-handled business query request from a portal system; the to-be-handled service query request comprises account information of a login portal system and a service identifier of the to-be-handled service for query;

in practical application, a user logs in a portal system of an enterprise, wants to complete each task to be handled under the self approval authority, and can click and trigger a service identifier of a corresponding service to be handled (such as a power grid project management service) displayed on an operation interface of the portal system, and send account information including an account logged in by the user and a service query request to be handled of the triggered service identifier to a financial system according to a link address included in the configuration information, but the method is not limited to the query request triggering mode described in the embodiment.

Step S62, determining that account information belongs to an approval account of the business to be handled according to approval object information corresponding to the business identifier;

Because the approval object information comprises each approval account number with corresponding approval authority configured by the financial system aiming at different types of businesses in advance, the financial system analyzes the received inquiry request of the business to be handled to obtain the business identifier of the business to be handled requested to inquire and the account number information of the user to be inquired, the approval object information corresponding to the business identifier can be determined first, and each approval account number contained in the approval object information is compared with the account number information to determine whether the account number information belongs to the approval account number of the business to be handled, namely whether the user currently requesting to inquire the information to be handled has the corresponding approval authority, namely whether the user is an approver pre-configured for the business to be handled.

Step S63, inquiring each piece of information of the business to be handled, which is stored in association with the account information;

step S64, the queried information to be handled is sent to the portal system, and the queried information to be handled is displayed by a client side logging in the portal system.

The financial system determines that the user requesting for inquiring the to-be-handled information of the to-be-handled service (such as a power grid service) has approval authority, and then inquires each to-be-handled information of the to-be-handled service stored in association with the account information from the database, and according to, but not limited to, the pushing manner described above, for example, by combining a cross-system technology, an encryption technology and/or a timing technology, the inquired to-be-handled information (such as an xml format data message) is sent to the portal system, and the portal system analyzes the received to-be-handled information by using the Dom4j so as to display each received to-be-handled information on a client side logged in the portal system for the user to review and approval.

Therefore, after the user logs in the portal system of the enterprise, all to-be-handled items under the logged-in account in the financial system can be uniformly obtained according to the logged-in account information and the service identification of the to-be-handled service, so that the user can process the to-be-handled items, the processing of the to-be-handled items is avoided, and the reliability and the efficiency of the to-be-handled service processing are improved.

Referring to fig. 7, a schematic structural diagram of an alternative example of a financial system-based push service processing apparatus proposed in the present application may include:

an approval object information acquisition module 71 for acquiring approval object information configured for a financial system; the approval object information comprises at least one approval account number with approval authority;

the to-be-handled information query module 72 is configured to query to-be-handled information stored in association with each of the at least one approval account;

the to-be-pushed information determining module 73 is configured to determine to-be-pushed information in the queried to-be-pushed information according to a to-be-pushed record table for the portal system;

the to-Do information pushing module 74 is configured to push the to-Do information to the portal system, so as to display each associated to-Do information under the approval account logged in the portal system.

Optionally, as shown in fig. 8, the information to be pushed determining module 73 may include:

the first detection unit 731 is configured to detect whether a push record of the approval account exists in a push to-do record table for the portal system;

a first determining unit 732, configured to determine that a first to-be-handled account number of the push record does not exist in the push to-be-handled record table, and determine the to-be-handled information stored in association with the queried first to-be-handled account number as to-be-pushed to-be-handled information;

a second detection unit 733, configured to determine that a second trial account number of the push record exists in the push to-do record table, and detect whether push information included in the push record of the second trial account number is the same as the associated stored to-do information;

and a second determining unit 734, configured to determine the to-Do information different from the pushing information included in the pushing record of the second trial account as the to-Do information to be pushed.

In some embodiments, as shown in fig. 8, the apparatus may further include:

a withdrawal to-do request generating module 75, configured to generate a corresponding withdrawal to-do request for the detected push information contained in the push record that is different from the to-do information stored in association with the second trial account;

A withdrawal to-do request sending module 76, configured to send the withdrawal to-do request to the portal system, so as to request withdrawal of to-do information under the corresponding second trial account number in the portal system;

and the success withdrawal prompting information obtaining module 77 is configured to obtain a success withdrawal prompting information fed back by the portal system, and push the corresponding to-be-pushed to-be-handled information to the portal system.

In still other embodiments, in conjunction with the method described above, as shown in fig. 9, the to-Do information pushing module 74 may include:

a push time rule obtaining unit 741, configured to obtain a push time rule configured for a push service of the portal system;

the first pushing unit 742 is configured to push the to-be-pushed information to the portal system according to the pushing time rule.

In still other embodiments, the to-Do information pushing module 74 may also include:

the encryption processing unit is used for carrying out encryption processing on the information to be pushed according to encryption information configured for the service type of the information to be pushed to obtain a ciphertext to be pushed;

and the second pushing unit is used for sending the ciphertext to be pushed to the portal system through a remote data transmission Webservice technology.

In still other embodiments, the apparatus may further include:

the output module is used for obtaining a pushing service configuration request aiming at the portal system and outputting a remote data transmission configuration page;

the configuration information obtaining module is used for responding to the configuration input operation of the remote data transmission configuration page and obtaining configuration information of push service aiming at the portal system;

the configuration information may include an interface address for pushing the to-be-handled information to the portal service, a push service identifier of the portal system for a pushing manner or a withdrawing manner of the to-be-handled information, a skip link address between the portal system and the financial system, a system identifier of the financial system, and the like.

Based on this, the to-Do information pushing module 74 may also include:

and the third pushing unit is used for pushing the information to be pushed to the portal system according to the configuration information.

Based on the descriptions of the above embodiments, the above apparatus may further include:

the to-be-handled business query request receiving module is used for receiving the to-be-handled business query request from the portal system; the to-be-handled service query request comprises account information for logging in the portal system and a service identifier of the to-be-handled service for requesting query;

The approval account determining module is used for determining that the account information belongs to the approval account of the business to be handled according to the approval object information corresponding to the business identifier;

the query module is used for querying each piece of to-be-handled information of the to-be-handled business stored in association with the account information;

and the sending module is used for sending the queried information to be handled to the portal system, and displaying the queried information to be handled by a client side logging in the portal system.

It should be noted that, regarding the various modules, units, and the like in the foregoing embodiments of the apparatus, the various modules and units may be stored as program modules in a memory, and the program modules stored in the memory may be executed by a processor to implement corresponding functions, or may be implemented by a combination of the program modules and hardware, and regarding the functions implemented by each program module and a combination thereof, and the achieved technical effects, the description of corresponding parts of the foregoing method embodiments may be referred to, which is not repeated in this embodiment.

The embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, where the computer program is loaded and executed by a processor, to implement each step of the foregoing financial system-based push service processing method, and a specific implementation process may refer to descriptions of corresponding parts of the foregoing embodiment, which is not repeated in this embodiment.

Finally, it should be noted that, in the embodiments described above, the terms "a," "an," "the," and/or "the" are not specific to a singular but may include a plural number unless the context clearly indicates otherwise. In general, the terms "comprises" and "comprising" merely indicate that the steps and elements are explicitly identified, and they do not constitute an exclusive list, as other steps or elements may be included in a method or apparatus. The inclusion of an element defined by the phrase "comprising one … …" does not exclude the presence of additional identical elements in a process, method, article, or apparatus that comprises an element.

Wherein, in the description of the embodiments of the present application, "/" means or is meant unless otherwise indicated, for example, a/B may represent a or B; "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" means two or more than two.

The terms "first," "second," and the like, herein are used for descriptive purposes only and are not necessarily for distinguishing one operation, element or module from another, and not necessarily for describing or implying any actual such relationship or order between such elements, elements or modules. And is not to be taken as indicating or implying a relative importance or implying that the number of technical features indicated is such that the features defining "first", "second" or "a" may explicitly or implicitly include one or more such features.

In addition, various embodiments in the present specification are described in a progressive or parallel manner, and each embodiment is mainly described in a different manner from other embodiments, and identical and similar parts between the various embodiments are only required to be mutually referred. The apparatus, the electronic device, the storage medium, and the system disclosed in the embodiments correspond to the methods disclosed in the embodiments, so that the description is simpler, and the relevant points are only referred to in the description of the method section.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the particular solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A push business processing method based on a financial system, the method comprising:

2. The method according to claim 1, wherein the determining to-be-pushed information in the queried to-be-pushed information according to a push to-be-pushed record table for a portal system includes:

3. The method according to claim 2, wherein the method further comprises:

4. The method of any of claims 1-3, wherein pushing the to-be-pushed to-Do information to the portal system comprises:

obtaining a push time rule configured for push services of the portal system;

5. The method of any of claims 1-3, wherein pushing the to-be-pushed to-Do information to the portal system comprises:

6. A method according to any one of claims 1-3, wherein the method further comprises:

The pushing the to-be-pushed information to the portal system includes:

7. The method of claim 6, wherein the method further comprises:

8. A push business processing device based on a financial system, the device comprising:

9. An electronic device, comprising:

a communication module; an input assembly; an output assembly;

a memory for storing a program implementing the financial system-based push service processing method of any one of claims 1-7;

a processor, configured to load and execute the program stored in the memory, and implement the push service processing method based on a financial system according to any one of claims 1 to 7.

10. A computer readable storage system having stored thereon a computer program, wherein the computer program is loaded and executed by a processor to implement the financial system based push service processing method according to any of claims 1-7.