CN116805077A - Service providing method, device and equipment for related documents in credit management flow - Google Patents

Abstract

The disclosure provides a service providing method, a device and equipment for related documents in a credit management process, wherein the method comprises the following steps: if the first component is monitored to be called, acquiring user characteristic information triggering the calling of the first component, wherein the first component is used for calling a first service of a related document; determining the document type and the current flow node of the related document; determining that the user has the authority to call the first service of the related document according to the user characteristic information, the document type and the current flow node; and providing the first service of the related document to the user. Through the method and the device, unified related document operation control can be realized, and service call safety of related documents is effectively improved.

Description

Service providing method, device and equipment for related documents in credit management flow

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for providing services of related documents in a credit management process.

Background

In the public credit management system, the operations of related documents (such as declaration, contract and the like) are involved in the flows of each stage of before, during and after the credit, and the related documents have different rights control requirements (such as creation rights, modification rights, deletion rights, reading rights, reference rights, read-only online previews and the like) in different process nodes, and the single operation rights can be subdivided into: no authority (no authority of any person in the process), authority (authority of any person in the process), authority of creator (authority of creator only), authority of customer manager (authority of customer manager only), authority of management team member (authority of management team including customer manager, applicable to customer documents), authority of mortgage management post (authority of mortgage management post, applicable to guaranty documents).

In the related art, a large amount of authority judging logic is coupled in each flow node, unified related document operation control is not supported, and therefore service call security of related documents is low.

Disclosure of Invention

The present disclosure aims to solve, at least to some extent, one of the technical problems in the related art.

Therefore, an object of the present disclosure is to provide a method, an apparatus, an electronic device, a non-transitory computer readable storage medium storing computer instructions, and a computer program product for providing services of related documents in a credit management process, which can implement unified related document operation control, and effectively improve service call security of related documents.

To achieve the above object, a method for providing services of related documents in a credit management flow according to an embodiment of a first aspect of the present disclosure includes: if the first component is monitored to be called, acquiring user characteristic information triggering the calling of the first component, wherein the first component is used for calling a first service of a related document; determining the document type and the current flow node of the related document; determining that a user has authority to invoke a first service of the related document according to the user characteristic information, the document type and the current flow node; and providing a first service of the related document to the user.

To achieve the above object, a service providing apparatus for a related document in a credit management flow according to an embodiment of a second aspect of the present disclosure includes: the acquisition module is used for acquiring user characteristic information triggering the invoking of the first component under the condition that the first component is invoked, wherein the first component is used for invoking a first service of a related document; a first determining module, configured to determine a document type and a current flow node of the related document; the second determining module is used for determining that the user has the authority to call the first service of the related document according to the user characteristic information, the document type and the current flow node; and a providing module for providing a first service of the related document to the user.

An electronic device according to an embodiment of a third aspect of the present disclosure includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing a service providing method for related documents in a credit management flow as proposed by an embodiment of the first aspect of the present disclosure when the program is executed by the processor.

An embodiment of a fourth aspect of the present disclosure proposes a non-transitory computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a service providing method for related documents in a credit management flow as proposed by an embodiment of the first aspect of the present disclosure.

An embodiment of a fifth aspect of the present disclosure proposes a computer program product which, when executed by a processor, performs a service providing method for relevant documents in a credit management flow as proposed by an embodiment of the first aspect of the present disclosure.

The service providing method, the device, the electronic equipment, the non-transitory computer readable storage medium and the computer program product for related documents in the credit management flow provided by the disclosure acquire the user characteristic information triggering the invoking of the first component if the first component is monitored to be invoked, wherein the first component is used for invoking the first service of the related documents, determining the document type and the current flow node of the related documents, determining that the user has the authority to invoke the first service of the related documents according to the user characteristic information, the document type and the current flow node, and providing the first service of the related documents to the user, so that unified related document operation control can be realized, and the service invoking safety of the related documents is effectively improved.

Additional aspects and advantages of the disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the disclosure.

Drawings

The foregoing and/or additional aspects and advantages of the present disclosure will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a flow diagram of a method for providing services of related documents in a credit management flow according to an embodiment of the disclosure;

FIG. 2 is a schematic diagram of a unified operator interface in an embodiment of the present disclosure;

FIG. 3 is a flow chart of a method for providing services of related documents in a credit management flow according to another embodiment of the disclosure;

FIG. 4 is a flow chart of a method for providing services of related documents in a credit management flow according to another embodiment of the disclosure;

FIG. 5 is a component interaction diagram in an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of another component interaction in an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of another component interaction in an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of a component architecture in an embodiment of the present disclosure;

FIG. 9 is a schematic diagram of a service providing apparatus of related documents in a credit management process according to an embodiment of the disclosure;

fig. 10 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present disclosure.

Detailed Description

Embodiments of the present disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for explaining the present disclosure and are not to be construed as limiting the present disclosure. On the contrary, the embodiments of the disclosure include all alternatives, modifications, and equivalents as may be included within the spirit and scope of the appended claims.

It should be noted that, in the present disclosure, all the actions of obtaining information and rights and providing services are performed under the premise of conforming to the corresponding data protection rule policy of the country of the location and obtaining the authorization given by the owner of the corresponding device.

Fig. 1 is a flow chart illustrating a service providing method of related documents in a credit management flow according to an embodiment of the present disclosure.

The present embodiment is exemplified by the fact that the service providing method of the relevant document in the credit management flow is configured in the service providing apparatus of the relevant document in the credit management flow, and the service providing method of the relevant document in the credit management flow in the present embodiment may be configured in the service providing apparatus of the relevant document in the credit management flow, and the service providing apparatus of the relevant document in the credit management flow may be provided in the server, or may also be provided in the electronic device, without limitation. The present embodiment takes an example in which the service providing method of the related document in the credit management flow is configured in the electronic device. Among them, electronic devices such as smartphones, tablet computers, personal digital assistants, electronic books, and the like have hardware devices of various operating systems.

The execution body of the embodiment of the present disclosure may be, for example, a server or a central processing unit (Central Processing Unit, CPU) in an electronic device in hardware, or may be, for example, a server or a related background service in an electronic device in software, which is not limited.

As shown in fig. 1, the service providing method of the relevant document in the credit management flow includes:

s101: and if the first component is monitored to be called, acquiring user characteristic information triggering the calling of the first component, wherein the first component is used for calling a first service of the related document.

In some embodiments, a component for invoking a certain service of a related document may be referred to as a first component, where the first component may be any one of multiple components, and different components may be used to invoke different services of the related document, where the multiple services are different from each other, which is not limited.

In some embodiments, the call situation of the first component in the multiple components may be monitored, where different components are used to call different services of the related document, and the first service belongs to the multiple services, which is not limited.

In some embodiments, the service may be, for example, one or more of a new document service, an update document service, an import document service, a review document service, a delete document service, a bulk download service, a document ordering service, and accordingly, the first service may be any of the foregoing services, and a component for providing the first service may be referred to as a first component, which is not limited.

In some embodiments, for the operation of the related document, a unified operation interface may be provided, and related computer program codes for the operation of the related document are unified and packaged, so that each component can safely use the service provided by the related document, which is not limited.

In some embodiments, the unified operation interface may be as shown in fig. 2, fig. 2 is a schematic diagram of the unified operation interface in the embodiment of the disclosure, and in fig. 2, a plurality of components are included, where each component may correspondingly provide services: the document service is not limited to a new document service, an updated document service, an introduced document service, a document retrieval service, a document deletion service, a batch download service, and a document ordering service.

In the embodiment of the disclosure, if the first component is monitored to be invoked, user feature information triggering the invocation of the first component is acquired, wherein the user feature information can be used for describing feature conditions of a user triggering the invocation of the first component, such as user preference conditions, user personalized features and the like, and the user feature information can be used as a reference to determine whether the user has authority to invoke a first service of a related document, and the user is not limited.

In the embodiment of the disclosure, the user characteristic information includes one or more of user identity information, such as creator identity, modifier identity, etc., and user post category, such as customer manager, management team member, mortgage management post, etc., without limitation.

In some embodiments, when the user feature information triggering the invoking of the first component is obtained, basic information (such as user account information, user biological information, etc.) of the user may be identified, and the user feature information is determined according to the basic information, which is not limited.

In some embodiments, user biometric information (e.g., user images, facial features, etc.) may also be collected in real-time to determine user feature information, etc., without limitation.

Of course, any other possible manner may be used to obtain the user feature information of the triggering and calling first component, which is not limited.

S102: the document type and current flow node of the relevant document are determined.

In some embodiments, if the first component is called, the user feature information triggering the calling of the first component is obtained, and the document type and the current flow node of the related document can be determined, where the document type is used for marking the classification condition to which the related document belongs, for example, a declaration book, an agreement, etc., and the current flow node is used for marking the flow node where the current system is located in the condition that the first component is called, for example, before a credit, during a credit, after a credit, etc., which are not limited.

In some embodiments, the determined user characteristic information, document type of the relevant document, and current flow node may be used together to determine whether the user has permission to invoke the first service of the relevant document, without limitation.

S103: and determining that the user has the authority to call the first service of the related document according to the user characteristic information, the document type and the current flow node.

In some embodiments, the preset authority content may be obtained, and according to the user feature information, the document type and the current flow node, whether the user to which the user feature information belongs has the invoking authority of the first service of the related document is determined by combining with the preset authority content, which is not limited.

In some embodiments, the user may be dynamically configured with the authority to invoke the first service of the related document with reference to the user feature information, the document type, and the current flow node, for example, if the user feature information matches with candidate feature information capable of having the authority to invoke the first service of the related document, the user is granted the authority to invoke the first service of the related document, without limitation.

Of course, determining that the user has the right to invoke the first service of the related document according to the user feature information, the document type and the current flow node may be implemented in any other possible manner, which is not limited.

S104: a first service of related documents is provided to a user.

After determining that the user has the authority to invoke the first service of the related document according to the user characteristic information, the document type and the current flow node, the first service of the related document can be provided to the user, which is not limited.

Alternatively, in other embodiments, if it is determined that the user does not have authority to invoke the first service of the related document according to the user feature information, the document type, and the flow node, the first service of the related document may not be provided to the user, which is not limited.

In some embodiments, the authority to invoke the first service of the related document may be dynamically configured for the user with reference to the user feature information, the document type, and the current flow node, for example, if the user feature information does not match with the candidate feature information capable of having the authority to invoke the first service of the related document, the authority to invoke the first service of the related document is released for the user without limitation.

Of course, any other possible manner may be used to determine that the user does not have the authority to invoke the first service of the related document according to the user feature information, the document type and the current flow node, which is not limited.

In this embodiment, if it is monitored that the first component is called, user feature information triggering to call the first component is obtained, where the first component is used to call a first service of a related document, determine a document type and a current flow node of the related document, determine, according to the user feature information, the document type and the current flow node, that a user has authority to call the first service of the related document, and provide the first service of the related document to the user, so that unified related document operation control can be implemented, and service call security of the related document is effectively improved.

Fig. 3 is a flow chart illustrating a service providing method of related documents in a credit management flow according to another embodiment of the present disclosure.

As shown in fig. 3, the service providing method of the relevant document in the credit management flow includes:

s301: and if the first component is monitored to be called, acquiring user characteristic information triggering the calling of the first component, wherein the first component is used for calling a first service of the related document.

S302: the document type and current flow node of the relevant document are determined.

The descriptions of S301 to S302 may be specifically referred to the above embodiments, and are not repeated herein.

S303: rights information required for a first service using the relevant document is determined.

Wherein the required authority information is used for describing the condition of the authority required for the first service using the relevant document, for example, if the first service is a newly added document service, the required authority information can be, for example, a creation authority, if the first service is an updated document service, the required authority information can be, for example, a modification authority, if the first service is an introduced document service, the required authority information can be, for example, a reference authority, if the first service is an invoked document service, the required authority information can be, for example, a reading authority, and if the first service is a deleted document service, the required authority information can be, for example, a deletion authority, without limitation.

In some embodiments, the first service of the related document may be parsed to determine the required rights for using the first service of the related document, so as to form the required rights information, which is not limited.

S304: and determining whether the user has the authority to call the first service of the related document according to the required authority information, the user characteristic information, the document type and the flow node.

That is, the user characteristic information, the document type and the flow node may be combined to analyze whether the user to which the user characteristic information belongs has the authority described by the required authority information, obtain a determination result, and determine whether the user has the authority to invoke the first service of the related document according to the determination result, which is not limited.

In some embodiments, the user feature information may be one or more, such as the user identity information may be creator identity, modifier identity, etc., the user post category may be, for example, a customer manager, a management team member, a mortgage management post, etc., then the desired rights information may be further subdivided, such as the desired rights information is a creation right, then rights may be configured for different user feature information such that a portion of the user feature information corresponds to having creation rights, and another portion of the user feature information may not have creation rights, and for other desired rights information settings, fine-grained rights management of the desired rights information may be achieved.

In some embodiments, when determining whether the user has the authority to invoke the first service of the relevant document according to the required authority information, the user feature information, the document type and the flow node, the fine-grained authority configured for the required authority information may be retrieved according to the user feature information, the document type and the flow node to determine whether the user has the authority to invoke the first service of the relevant document, which is not limited.

S305: if it is determined that the user has the right to invoke the first service of the relevant document, the first service of the relevant document is provided to the user.

S306: if it is determined that the user does not have the right to invoke the first service of the relevant document, the first service of the relevant document is not provided to the user.

The descriptions of S305-S306 may be specifically referred to the above embodiments, and are not repeated here.

In this embodiment, if it is monitored that the first component is called, user feature information triggering to call the first component is obtained, where the first component is used to call a first service of a related document, determine a document type and a current flow node of the related document, determine authority information required for using the first service of the related document, determine whether a user has authority to call the first service of the related document according to the required authority information, the user feature information, the document type and the flow node, and provide the first service of the related document to the user when it is determined that the user has authority to call the first service of the related document, and not provide the first service of the related document to the user when it is determined that the user does not have authority to call the first service of the related document, so that unified operation control of the related document can be implemented, and service call security of the related document is effectively improved. The method can also configure the personalized first service use permission of the related document for the user characteristic information, the document type and the current flow node, can realize fine-grained permission management, and improves the flexibility and convenience of the related document permission management.

Fig. 4 is a flow chart illustrating a service providing method of related documents in a credit management flow according to another embodiment of the present disclosure.

As shown in fig. 4, the service providing method of the relevant document in the credit management flow includes:

s401: and if the first component is monitored to be called, acquiring user characteristic information triggering the calling of the first component, wherein the first component is used for calling a first service of the related document.

S402: the document type and current flow node of the relevant document are determined.

S403: rights information required for a first service using the relevant document is determined.

The descriptions of S401 to S403 may be specifically referred to the above embodiments, and are not repeated herein.

S404: obtaining a permission configuration table corresponding to the document type and the flow node, wherein the permission configuration table comprises: one or more candidate authority information, wherein the candidate authority information is associated with one or more candidate feature information and an authority type corresponding to the candidate feature information, and the authority type is used for indicating whether the authority is available.

In some embodiments, the candidate authority information represents the authority condition contained in the authority configuration table, and the candidate feature information represents feature information possibly possessed by candidate users, for example, one or more users as comparison references, which is not limited.

In some embodiments, a permission configuration table can be designed for three dimensions of a flow node, candidate feature information and a document type, and initially, a configuration template is provided to realize permission representation through a configuration method, the flow node uses configured default document permissions, and in the running process of the flow, dynamic adjustment of document permissions can be supported, so that users with different user feature information can obtain different document contents or modify different document contents, and the method is not limited.

An illustration of the rights configuration table may be as shown in table 1 below:

TABLE 1

The above-mentioned document types (Identity document, ID) in table 1 are used to identify document types, the task numbers represent numbers of the process nodes, a process node may also be regarded as a task node, a permission configuration table is correspondingly configured for each document type and process node, the creation permission, modification permission, deletion permission, reading permission, reference permission and the like contained in the permission configuration table may be an optional example of candidate permission information, the candidate feature information may be, for example, a creator, a client manager, a management team member, a mortgage manager and the like contained in the description corresponding to the above-mentioned "creation permission", different permission types may be set in the permission configuration table in advance for different candidate feature information, the permission types corresponding to the candidate feature information may be represented by the reference numerals 00, 01, 02 and the like in the above-mentioned table, and the permission types may be used to indicate whether specific conditions have permission or not, which is not limited.

For example, if the description of the creation right in the right configuration table is configured 02, it indicates that the creator has rights (only the creator has rights), if the description of the creation right in the right configuration table is configured 03, it indicates that the client manager has rights (only the client manager has rights), and so on.

It should be noted that, the rights types included in the descriptions of the above various candidate rights information show all possible cases, and in the process of configuring the rights configuration table specifically, a part of possible cases may also be set according to the requirements of actual rights management, and different candidate rights information and rights types may be set for different document types and different flow nodes, respectively, which is not limited.

S405: and determining whether the user has the authority for calling the first service of the related document according to the required authority information, the user characteristic information and the authority configuration table.

After the rights configuration table corresponding to the document type and the flow node is acquired, the related data may be correspondingly searched from the rights configuration table, so as to determine whether the user has the right to invoke the first service of the related document based on the related data, which is not limited.

In some embodiments, candidate authority information matched with the required authority information may be first determined from the authority configuration table, then candidate feature information matched with the user feature information is determined from one or more candidate feature information associated with the matched candidate authority information, and whether the user has authority to invoke the first service of the related document is determined according to the authority type corresponding to the matched candidate feature information, so that unified management of authority of the user to use the service of the related document is achieved, and authority management efficiency and effect are improved.

In some embodiments, if the corresponding rights type indicates that the user has the right to call the first service of the related document, and if the corresponding rights type indicates that the user does not have the right to call the first service of the related document, the method and the device can conveniently and accurately determine whether the user has the right to call the first service of the related document.

For example, if the required authority information is the creation authority, the candidate authority information obtained from the authority configuration table is also the creation authority, and the creator, the client manager, the management team member, the mortgage manager, and the like included in the description corresponding to the creation authority may further determine which candidate feature information the user feature information matches, if the user feature information is the client manager and the description corresponding to the creation authority already includes "03 client manager has authority (only the client manager has authority)", it is determined that the authority type corresponding to the client manager is 03, that is, it means that the client manager has the creation authority for the relevant document and only the client manager has the creation authority, which is not limited.

Therefore, by configuring the unified authority configuration table, the computer program code for realizing the document authority control can be stripped from the process, so that the computer program code for realizing the operation of the process becomes concise and easy to maintain, the computer program code for realizing the document authority control can be used as an independent service, and the reusability of the computer program code for realizing the document authority control can be effectively improved; the control requirement of the continuous change of the authority is met through a collocation mode; a unified document security control mechanism is also provided that can support dynamically adjusting document rights.

S406: if it is determined that the user has the right to invoke the first service of the relevant document, the first service of the relevant document is provided to the user.

S407: if it is determined that the user does not have the right to invoke the first service of the relevant document, the first service of the relevant document is not provided to the user.

The descriptions of S406 to S407 may be specifically referred to the above embodiments, and are not repeated herein.

In this embodiment, if it is monitored that the first component is called, user feature information triggering to call the first component is obtained, where the first component is used to call a first service of a related document, determine a document type and a current flow node of the related document, determine rights information required for using the first service of the related document, and obtain a rights configuration table corresponding to the document type and the flow node, where the rights configuration table includes: the method comprises the steps of determining whether a user has authority to call a first service of a related document according to required authority information, user characteristic information and an authority configuration table, providing the first service of the related document to the user when the user has the authority to call the first service of the related document, and not providing the first service of the related document to the user when the user does not have the authority to call the first service of the related document, wherein the authority type is used for indicating whether the user has the authority. The method can also configure the personalized first service use permission of the related document for the user characteristic information, the document type and the current flow node, can realize fine-grained permission management, and improves the flexibility and convenience of the related document permission management. By configuring the unified authority configuration table, the computer program code for realizing the document authority control can be stripped from the process, so that the computer program code for realizing the operation of the process becomes concise and easy to maintain, the computer program code for realizing the document authority control can be used as an independent service, and the reusability of the computer program code for realizing the document authority control can be effectively improved; the control requirement of the continuous change of the authority is met through a collocation mode; a unified document security control mechanism is also provided that can support dynamically adjusting document rights.

The embodiment of the disclosure also provides a component interaction method, and the service providing method of the related documents in the credit management flow is realized based on the component interaction method. Mainly relates to the following components: document rights front-end component, document rights back-end component, document rights configuration library, content Provider (CP) provide component services (business approval, contract, credit, post-rating and credit, etc.). The component interaction method mainly comprises the following steps: according to the document authority corresponding to the required configuration flow node, filling in a document authority control template (an optional example of an authority configuration table), importing authority configuration into a database, and adding white list configuration; through front-end use, each component of the CP is introduced into a document authority front-end component according to the need, the interaction process of the mode is shown in FIG. 5, and FIG. 5 is a component interaction schematic diagram in the embodiment of the disclosure; the back end is directly used, each component of the CP invokes the document authority back end service in the process, the interaction process of the mode is shown in FIG. 6, and FIG. 6 is another interaction schematic diagram of the components in the embodiment of the disclosure; in the process of running the flow, different document authorities may be required under different service scenes of the same flow node, the process of dynamically adjusting the document authorities is shown in fig. 7, and fig. 7 is an interaction schematic diagram of another component in the embodiment of the disclosure; the above schematic diagrams for the CP components may be shown in fig. 8, where fig. 8 is a schematic diagram of the component architecture in the embodiment of the disclosure.

Fig. 9 is a schematic diagram of a service providing apparatus related to documents in a credit management procedure according to an embodiment of the disclosure.

As shown in fig. 9, the service providing apparatus 90 of the relevant document in the credit management flow includes:

and the acquiring module 901 is configured to acquire user feature information triggering to invoke the first component when the first component is invoked, where the first component is used to invoke a first service of the related document.

A first determining module 902 is configured to determine a document type and a current flow node of the related document.

A second determining module 903, configured to determine, according to the user feature information, the document type, and the current flow node, that the user has a right to invoke the first service of the related document.

A providing module 904 is configured to provide a first service of related documents to a user.

It should be noted that the explanation of the service providing method of the related document in the credit management flow is also applicable to the service providing device of the related document in the credit management flow of the present embodiment, and will not be repeated here.

In this embodiment, if it is monitored that the first component is called, user feature information triggering to call the first component is obtained, where the first component is used to call a first service of a related document, determine a document type and a current flow node of the related document, determine, according to the user feature information, the document type and the current flow node, that a user has authority to call the first service of the related document, and provide the first service of the related document to the user, so that unified related document operation control can be implemented, and service call security of the related document is effectively improved.

Fig. 10 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present disclosure. The electronic device 12 shown in fig. 10 is merely an example and should not be construed to limit the functionality and scope of use of embodiments of the present disclosure in any way.

As shown in fig. 10, the electronic device 12 is in the form of a general purpose computing device. Components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 that connects the various system components, including the memory 28 and the processing unit 16.

Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include industry Standard architecture (Industry Standard Architecture; hereinafter ISA) bus, micro channel architecture (Micro Channel Architecture; hereinafter MAC) bus, enhanced ISA bus, video electronics standards Association (Video Electronics Standards Association; hereinafter VESA) local bus, and peripheral component interconnect (Peripheral Component Interconnection; hereinafter PCI) bus.

Electronic device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

Memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (Random Access Memory; hereinafter: RAM) 30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (not shown in FIG. 10, commonly referred to as a "hard disk drive").

Although not shown in fig. 10, a magnetic disk drive for reading from and writing to a removable nonvolatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable nonvolatile optical disk (e.g., a compact disk read only memory (Compact Disc Read Only Memory; hereinafter CD-ROM), digital versatile read only optical disk (Digital Video Disc Read Only Memory; hereinafter DVD-ROM), or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the various embodiments of the disclosure.

A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods in the embodiments described in this disclosure.

The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a person to interact with the electronic device 12, and/or any devices (e.g., network card, modem, etc.) that enable the electronic device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks, such as a local area network (Local Area Network; hereinafter: LAN), a wide area network (Wide Area Network; hereinafter: WAN) and/or a public network, such as the Internet, via the network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 over the bus 18. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

The processing unit 16 executes various functional applications and data processing by running programs stored in the memory 28, for example, implementing the service providing method of the relevant documents in the credit management flow mentioned in the foregoing embodiment.

To achieve the above-described embodiments, the present disclosure also proposes a non-transitory computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a service providing method for related documents in a credit management flow as proposed in the foregoing embodiments of the present disclosure.

To implement the above-described embodiments, the present disclosure also proposes a computer program product that, when executed by a processor, performs a service providing method for relevant documents in a credit management flow as proposed by the previous embodiments of the present disclosure.

It should be noted that in the description of the present disclosure, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present disclosure, unless otherwise indicated, the meaning of "a plurality" is two or more.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present disclosure in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present disclosure.

It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.

Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.

Furthermore, each functional unit in the embodiments of the present disclosure may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present disclosure. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although embodiments of the present disclosure have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the present disclosure, and that variations, modifications, alternatives, and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the present disclosure.

Claims (12)

1. A method for providing services of related documents in a credit management process, the method comprising:

if the first component is monitored to be called, acquiring user characteristic information triggering the calling of the first component, wherein the first component is used for calling a first service of a related document;

Determining the document type and the current flow node of the related document;

determining that a user has authority to invoke a first service of the related document according to the user characteristic information, the document type and the current flow node; and

providing a first service of the related document to the user.

2. The method of claim 1, wherein the method further comprises:

determining that a user does not have permission to invoke a first service of the related document according to the user characteristic information, the document type and the flow node;

the user is not provided with the first service of the relevant document.

3. The method of any one of claims 1-2, wherein the method further comprises:

monitoring the calling condition of a first component in a plurality of components, wherein different components are used for calling different services of related documents, the first service belongs to a plurality of services, and the services comprise at least one of the following:

newly adding a document service;

updating the document service;

introducing a document service;

retrieving a document service;

deleting the document service;

a batch downloading service;

a document ordering service.

4. The method of any of claims 1-2, wherein determining whether a user has permission to invoke the first service of the related document based on the user characteristic information, the document type, and the flow node comprises:

determining rights information required for a first service using the related document;

and determining whether the user has the authority to call the first service of the related document according to the required authority information, the user characteristic information, the document type and the flow node.

5. The method of claim 4, wherein determining whether a user has rights to invoke the first service of the associated document based on the required rights information, the user characteristic information, the document type, and the flow node comprises:

obtaining a permission configuration table corresponding to the document type and the flow node, wherein the permission configuration table comprises: one or more candidate authority information, wherein the candidate authority information is associated with one or more candidate feature information and an authority type corresponding to the candidate feature information, and the authority type is used for indicating whether the authority is available or not;

And determining whether the user has the authority for calling the first service of the related document according to the required authority information, the user characteristic information and the authority configuration table.

6. The method of claim 5, wherein determining whether the user has the right to invoke the first service of the related document based on the required right information, the user characteristic information, and the right configuration table comprises:

determining candidate authority information matched with the required authority information from the authority configuration table;

determining candidate feature information matched with the user feature information from one or more candidate feature information associated with the matched candidate authority information;

and determining whether the user has the authority for calling the first service of the related document according to the authority type corresponding to the matched candidate characteristic information.

7. The method of claim 6, wherein determining whether the user has the right to invoke the first service of the related document according to the right type corresponding to the matched candidate feature information comprises:

if the corresponding authority type indicates that the user has the authority, determining that the user has the authority for calling the first service of the related document;

If the corresponding rights type indicates no rights, it is determined that the user does not have rights to invoke the first service of the relevant document.

8. The method of claim 1, wherein the user characteristic information comprises at least one of:

user identity information;

user post category.

9. A service providing apparatus for related documents in a credit management process, the apparatus comprising:

the acquisition module is used for acquiring user characteristic information triggering the invoking of the first component under the condition that the first component is invoked, wherein the first component is used for invoking a first service of a related document;

a first determining module, configured to determine a document type and a current flow node of the related document;

the second determining module is used for determining that the user has the authority to call the first service of the related document according to the user characteristic information, the document type and the current flow node; and

and the providing module is used for providing the first service of the related document to the user.

10. An electronic 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 enable the at least one processor to perform the method of any one of claims 1-8.

11. A non-transitory computer readable storage medium storing computer instructions, wherein the computer instructions are for causing the computer to perform the method of any one of claims 1-8.

12. A computer program product comprising a computer program which, when executed by a processor, implements the steps of the method according to any of claims 1-8.