Machine account management method and device

Abstract

The invention discloses a standing book management method and device, and relates to the technical field of computers. A specific embodiment of the method comprises the following steps: based on a first organization identifier of a standing book application request, determining a first organization node corresponding to the first organization identifier and an ancestor node of the first organization node from an organization hierarchy tree; based on the template selection instruction, determining a target standing book template in a standing book template set; and generating a machine account corresponding to the first organization identifier based on the target machine account template and the entity data. According to the embodiment, the flexibility of creating the ledger by each hierarchical organization is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a ledger management method and device. Background Art

[0002] As a tool for recording and managing information, the ledger plays an important role in the modernization of grassroots governance. First, the ledger can provide data support to help managers understand and analyze the progress of grassroots work. Second, the ledger can promote information sharing and communication to ensure efficient work. In addition, the ledger can also provide a reference for the evaluation and improvement of grassroots governance.

[0003] At present, several ledger system technologies have been developed in the field of government services. The ledger data is realized through the link of "creating ledger management tasks-issuing-collecting-reporting and summarizing" by the superior department. The flexibility of ledger creation in this way is poor. Summary of the invention

[0004] The embodiments of the present application provide a ledger management method, apparatus, device and storage medium.

[0005] According to the first aspect, an embodiment of the present application provides a ledger management method, the method comprising: based on the first organization identifier of the ledger application request, determining the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organizational hierarchy tree; based on the template selection instruction, determining the target ledger template in the ledger template set; based on the target ledger template and entity data, generating a ledger corresponding to the first organization identifier.

[0006] According to the second aspect, an embodiment of the present application provides a ledger management device, which includes: a determination module, a selection module and a generation module, wherein the determination module is configured to determine the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organization hierarchy tree based on the first organization identifier of the ledger application request; the selection module is configured to determine the target ledger template in the ledger template set based on the template selection instruction; the generation module is configured to generate a ledger corresponding to the first organization identifier based on the target ledger template and entity data.

[0007] According to the third aspect, an embodiment of the present application provides an electronic device, which includes one or more processors; a storage device, on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement a ledger management method as in any embodiment of the first aspect.

[0008] According to the fourth aspect, an embodiment of the present application provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, a ledger management method as in any embodiment of the first aspect is implemented.

[0009] This application determines the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organizational hierarchy tree based on the first organization identifier of the ledger application request; determines the target ledger template in the ledger template set based on the template selection instruction; generates the ledger corresponding to the first organization identifier based on the target ledger template and entity data, thereby realizing the flexible application and creation of ledgers by organizations at all levels according to their respective levels.

[0010] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0012] Figure 2a is a flowchart of an embodiment of the ledger management method according to the present application;

[0013] Figure 2b is a schematic diagram of another embodiment of the ledger management method according to the present application;

[0014] Figure 2c is a schematic diagram of another embodiment of the ledger management method according to the present application;

[0015] Figure 3 It is a schematic diagram of an application scenario of the ledger management method according to the present application;

[0016] Figure 4 is a flowchart of another embodiment of the ledger management method according to the present application;

[0017] Figure 5 is a schematic diagram of an embodiment of a ledger management device according to the present application;

[0018] Figure 6 It is a structural diagram of a computer system suitable for implementing a server of an embodiment of the present application. DETAILED DESCRIPTION

[0019] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0020] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0021] Figure 1 An exemplary system architecture 100 to which an embodiment of the ledger management method of the present application can be applied is shown.

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

[0023] The terminal devices 101, 102, 103 interact with the server 105 via the network 104 to receive or send messages, etc. Various communication client applications may be installed on the terminal devices 101, 102, 103, for example, ledger management applications, communication applications, etc.

[0024] Terminal devices 101, 102, 103 can be hardware or software. When terminal devices 101, 102, 103 are hardware, they can be various electronic devices with display screens, including but not limited to mobile phones and laptops. When terminal devices 101, 102, 103 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (for example, to provide ledger management services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0025] Server 105 can be a server that provides various services. For example, based on the first organization identifier of the ledger application request, determining the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organizational hierarchy tree; based on the template selection instruction, determining the target ledger template in the ledger template set; based on the target ledger template and entity data, generating a ledger corresponding to the first organization identifier.

[0026] It should be noted that the server 105 can be hardware or software. When the server 105 is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or it can be implemented as a single server. When the server is software, it can be implemented as multiple software or software modules (for example, used to provide account management services), or it can be implemented as a single software or software module. No specific limitation is made here.

[0027] It should be noted that the ledger management method provided in the embodiment of the present disclosure can be executed by the server 105, or by the terminal devices 101, 102, 103, or by the server 105 and the terminal devices 101, 102, 103 cooperating with each other. Accordingly, the various parts (such as various units, sub-units, modules, sub-modules) included in the ledger management device can be all set in the server 105, or all set in the terminal devices 101, 102, 103, or respectively set in the server 105 and the terminal devices 101, 102, 103.

[0028] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0029] Figure 2a A flowchart 200 of an embodiment of a ledger management method that can be applied to the present application is shown. In this embodiment, the ledger management method includes the following steps:

[0030] Step 201, based on the first organization identifier of the ledger application request, determine the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organization hierarchy tree.

[0031] In this embodiment, the execution subject (such as Figure 1 The server 105 or terminal devices 101, 102, 103 shown in the figure can monitor the ledger claim requests submitted by each organization in real time or periodically, and in response to monitoring the ledger claim requests, based on the first organization identifier of the ledger claim request, determine the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organization hierarchy tree.

[0032] The organizational hierarchy tree is constructed based on organizational nodes corresponding to organizational identifiers and the hierarchical relationship between organizational nodes, and the organizational identifiers correspond to the organizational nodes one by one.

[0033] Specifically, the organizational hierarchy tree is as follows: Figure 2b As shown, if the first organization ID of the ledger claim request is d 2 000, the execution subject can determine the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organization hierarchy tree according to the first organization identifier in the ledger application request, that is, d 2 000 The corresponding organization node and d 1 00 d 0 0 corresponds to the organization node.

[0034] Here, each organization node in the organization hierarchy tree may correspond to one or more ledger templates.

[0035] In some optional methods, the ledger template can be created in the following way: based on the template configuration request, configure the ledger template corresponding to the organization identifier.

[0036] In this implementation, after establishing the organizational hierarchy tree, the execution entity may monitor the template configuration request in real time or periodically, and configure the ledger template corresponding to the organizational identifier in response to the template configuration request monitored.

[0037] The template configuration request may include entity categories and attribute items.

[0038] Here, the entity category is used to indicate the type of entity managed by the ledger under the current template. The entity category may include categories such as people, places, objects, and organizations, and each category may have a corresponding classification number.

[0039] The attribute item is used to indicate the attribute field of the entity managed by the ledger under the current template. The attribute item is a list of attributes. Each attribute can include the attribute name, attribute value type (for example, text, phone number, address, etc.), whether it is required, etc.

[0040] Specifically, Figure 2c As shown, in response to detecting the template configuration request, the execution subject can present the ledger template configuration interface (the configuration interface can support the configuration items of the new / edited template, the deletion of the template, etc.) through the user interaction interface provided by the web page development and proxy service technology such as react+nginx, and configure the ledger template corresponding to the organization identifier according to the template configuration request, such as the organization identifier is d 1 00 , the entity category is person, and the attribute items are name-text type, ID number-ID number type, date of birth-date type, phone-phone type, etc.

[0041] Here, the execution entity can provide server-side logic through back-end service development technologies such as springboot / flask, and support the creation / editing / deletion operations in the database.

[0042] This implementation method realizes flexible configuration of the ledger template by configuring the ledger template corresponding to the organization identifier based on the template configuration request.

[0043] Step 202, based on the template selection instruction, determine the target ledger template in the ledger template set.

[0044] In this embodiment, after determining the first organization node and the ancestor node of the first organization node, the execution entity can determine the ledger template set according to the ledger template corresponding to the first organization node and the ledger template corresponding to the ancestor node of the first organization node.

[0045] Furthermore, the execution entity may present a set of ledger templates and monitor the template selection instructions for the target ledger template in real time or periodically, and in response to monitoring the template selection instructions, determine the target ledger template in the set of ledger templates according to the template selection instructions.

[0046] Specifically, the ledger template set includes templates corresponding to the first organization node, such as ledger template 1 and ledger template 2, and templates corresponding to the ancestor nodes of the first organization node, such as ledger template 3 and ledger template 4. In response to detecting a template selection instruction, a target ledger template is determined in the ledger template set, such as ledger template 4.

[0047] Step 203: Generate a ledger corresponding to the first organization identifier based on the target ledger template and entity data.

[0048] In this embodiment, after determining the target ledger template, the execution entity may push the target ledger template to the organization corresponding to the first organization identifier.

[0049] After receiving the target ledger template, the organization corresponding to the first organization identifier can initialize the basic information of the target ledger template (for example, ledger name, ledger number, etc.) to complete the application for the target ledger template. After the application is completed, the organization corresponding to the first organization identifier becomes the administrator of the target ledger template and fills in the entity data on the target ledger template.

[0050] Furthermore, the execution entity may generate a ledger corresponding to the first organization identifier based on the target ledger template and entity data.

[0051] Continue to see Figure 3 , Figure 3 It is a schematic diagram of an application scenario of the ledger management method according to this embodiment.

[0052] exist Figure 3 In the application scenario of , the execution subject 301 can monitor the ledger application requests submitted by each organization in real time or regularly, and in response to monitoring the ledger application request, based on the first organization identifier 302 of the ledger application request, such as d 2 000, determine the first organization node corresponding to the first organization identifier and the ancestor node 304 of the first organization node from the organization hierarchy tree 303, such as d 2 000 The corresponding organization node and d 1 00 d 0 0. Among them, the organizational hierarchy tree 303 is constructed based on the organizational nodes corresponding to the organizational identifier and the hierarchical relationship between the organizational nodes. After determining the first organization node and the ancestor node 304 of the first organization node, the execution subject can determine the ledger template set according to the ledger template corresponding to the first organization node and the ledger template corresponding to the ancestor node of the first organization node and present the ledger template set. If a template selection instruction 305 is detected, the target ledger template 306 is determined in the ledger template set according to the template selection instruction 305. After determining the target ledger template 306, the execution subject can push the target ledger template to the organization corresponding to the first organizational identifier to fill in the entity data 307. Further, the execution subject can generate a ledger 308 corresponding to the first organizational identifier based on the target ledger template 306 and the entity data 307.

[0053] The ledger management method disclosed in the present invention determines the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organizational hierarchy tree based on the first organization identifier of the ledger application request; determines the target ledger template from the ledger template set based on the template selection instruction; generates the ledger corresponding to the first organization identifier based on the target ledger template and entity data, thereby realizing the flexible application and creation of ledgers by organizations at all levels according to their respective levels.

[0054] Further references Figure 4 , which shows a process 400 of another embodiment of the ledger management method. In this embodiment, the process 400 of the ledger management method may include the following steps:

[0055] Step 401, based on the first organization identifier of the ledger application request, determine the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organization hierarchy tree.

[0056] In this embodiment, the implementation details and technical effects of step 401 can refer to the description of step 201 and will not be repeated here.

[0057] Step 402, based on the template selection instruction, determine the target ledger template in the ledger template set.

[0058] In this embodiment, the implementation details and technical effects of step 402 can refer to the description of step 202 and will not be repeated here.

[0059] Step 403: Generate a ledger corresponding to the first organization identifier based on the target ledger template and entity data.

[0060] In this embodiment, the implementation details and technical effects of step 403 may refer to the description of step 203 and will not be repeated here.

[0061] Step 404, in response to detecting an operation request for a target object, determining whether a second organization node corresponding to a second organization identifier of the operation request and a target organization node corresponding to the target object meet a preset condition.

[0062] In this embodiment, the execution entity can detect operation requests for the target object in real time or periodically. If an operation request for the target object is detected, it determines whether the second organization node corresponding to the second organization identifier of the operation request and the target organization node corresponding to the target object meet preset conditions.

[0063] Among them, the target object is the target ledger or target organization node.

[0064] Here, the preset condition may include one of the following: the second organization node is the same as the target organization node, and the second organization node is an ancestor node of the target organization node.

[0065] Step 405: In response to determining that the preset condition is met, executing the operation indicated by the operation request on the target object.

[0066] In this embodiment, if the second organization node corresponding to the second organization identifier of the operation request and the target organization node corresponding to the target object meet preset conditions, the operation indicated by the operation request is performed on the target object.

[0067] Among them, the operation request may include an access request, an editing request, a statistical information extraction request, a folding display request, etc., which is not limited in this application.

[0068] In some optional methods, performing the operation indicated by the operation request on the target object includes: in response to determining that the target object is a target organization node, presenting the ledger corresponding to the target organization node and the subordinate organization nodes of the target organization node in the organization hierarchy tree.

[0069] In this implementation, if the target object is a target organization node, the execution subject may present the ledger corresponding to the target organization node and the ledger corresponding to the subordinate organization nodes of the target organization node in the organizational hierarchy tree in a variety of ways, such as directly presenting the ledger list corresponding to the target organization node and the ledger statistical information corresponding to each subordinate organization node; directly presenting the ledger statistical information corresponding to the target organization node and each subordinate organization node; directly presenting the ledger list corresponding to the target organization node and each subordinate organization node, etc.

[0070] Among them, the ledger statistical information can include multiple types, such as the number of ledgers, the number of entities, the number of ledger templates, statistical indicators of each template, etc.

[0071] Specifically, in response to detecting the target organization node d 1 00 The operation request, and the second organization identifier of the operation request (such as d 1 00 ) and the target organization node meet the preset conditions, the execution subject can present the ledger list corresponding to the target organization node and the subordinate organization nodes of the target organization node in the organization hierarchy tree (such as d 2 000 d 2 001 d 3 0010 d 3 0011 )The ledger statistical information of the corresponding ledger.

[0072] This implementation method responds to determining that the target object is a target organization node by presenting the ledgers corresponding to the target organization node and the subordinate organization nodes of the target organization node in the organizational hierarchy tree, which helps users to understand the ledger application status, data collection status, field aggregation statistics of entities in the ledger and other ledger information of the current department organization and the subordinate department organizations of the current department organization.

[0073] In some optional methods, the operation indicated by the operation request is performed on the target object, including: in response to determining that the target object is a target ledger, presenting update prompt information for the target ledger; in response to receiving an update confirmation instruction, updating the target ledger based on the update prompt information.

[0074] In this implementation, if an operation request for the target ledger is detected, update prompt information for the target ledger is presented. Further, if an update confirmation instruction is detected, the target ledger is updated according to the update prompt information.

[0075] Among them, the update prompt information can be generated based on the target entity that has changed in the data source of the ledger, and the organizational scope corresponding to the target entity is included in the organizational scope corresponding to the target ledger.

[0076] Here, the organizational scope, that is, the scope corresponding to the organizational node, can be determined according to the specific application scenario, for example, the jurisdiction scope, geographical scope, functional scope, etc., and this application does not limit this.

[0077] Specifically, the executing entity can build a fact library to store the data source of the entity data for constructing the ledger (the entity data included in the data source is greater than or equal to the entity data in the target ledger), and monitor the changes in the fact library in real time (the fact library may include two tables, one for recording the attributes of each dimension of the entity, and the other for recording the organizational scope corresponding to the entity). If the fact library changes, the changed entity is extracted, and the organizational scope of the changed entity, for example, the location of the entity, is matched with the organizational scope corresponding to the target ledger, such as the jurisdiction. If the two match successfully, that is, the location of the entity is included in the jurisdiction, the changed entity is determined as the target entity, and update prompt information for the target ledger is generated based on the target entity.

[0078] Here, the update prompt information is used to indicate that there is expired data in the target ledger, and recommends operations such as deletion, modification, and creation of entity data in the target ledger.

[0079] The update prompt information may include one or more recommendation items, each of which may include the update recommendation type (for example, deletion, addition, modification, etc.), recommended content (entity attribute value), the ledger ID of the target ledger, a blocking mark indicating whether to block the recommendation, and other information.

[0080] Specifically, in response to detecting an operation request for a target ledger, the executing entity presents update prompt information for the target ledger, wherein the update prompt information includes multiple recommendation items. If the user selects a recommendation item and clicks Ignore, the recommendation item is set to be blocked; if the user selects a recommendation item and clicks Accept, the corresponding entity of the target ledger is deleted / added / modified according to the recommendation type.

[0081] If the recommended type is a new operation, you can directly create a new entity and insert it into the target ledger with the entity attribute values ​​of the recommended content; if the recommended type is a delete operation, match the existing entity in the target ledger according to the entity attribute values ​​of the recommended content, and delete the entity; if the recommended type is a modify operation, match the existing entity in the target ledger according to the entity attribute values ​​of the recommended content, and replace the attribute values ​​of the entity with the entity attribute values ​​of the recommended content.

[0082] In addition, it should be pointed out that after receiving the recommendation item, the execution subject may mark the blocking mark of the recommendation item to avoid receiving the recommendation item again after receiving the recommendation item.

[0083] This implementation method presents update prompt information for the target ledger in response to determining that the target object is the target ledger; in response to receiving an update confirmation instruction, the target ledger is updated based on the update prompt information, thereby achieving timely dynamic update of the target ledger.

[0084] In some optional methods, performing the operation indicated by the operation request on the target object includes: in response to determining that the target object is a target ledger, setting the target ledger to an editable state; in response to receiving an editing instruction, performing the operation indicated by the editing instruction on the target ledger.

[0085] In this implementation, if an operation request for the target ledger is detected, the target ledger can be set to an editable state; further, if an editing instruction is detected, the operation indicated by the editing instruction is performed on the target ledger, such as deletion, addition, modification, etc.

[0086] Specifically, the execution entity can be identified in the organization 2 000 Two entities are added to the corresponding permanent population ledger, for example, Zhang XX and Li XX.

[0087] This implementation method sets the target ledger to an editable state in response to determining that the target object is a target ledger; in response to receiving an editing instruction, performs the operation indicated by the editing instruction on the target ledger, thereby achieving effective editing of the target ledger.

[0088] from Figure 4 It can be seen that Figure 2a Compared with the corresponding embodiments, the process 400 of the ledger management method in this embodiment reflects that in response to detecting an operation request for a target object, it is determined whether the second organization node corresponding to the second organization identifier of the operation request and the target organization node corresponding to the target object meet the preset conditions; in response to determining that the preset conditions are met, the operation indicated by the operation request is performed on the target object, so that each organization can perform corresponding operations on the organization node or ledger according to its corresponding authority scope, thereby realizing flexible configuration of the ledger and improving the flexibility and effectiveness of ledger management.

[0089] Further references Figure 5 As an implementation of the methods shown in the above figures, the present application provides an embodiment of a ledger management device, which is similar to Figure 2a Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0090] like Figure 5 As shown, the ledger management device 500 of this embodiment includes: a determination module 501, a selection module 502 and a generation module 503.

[0091] Among them, the determination module 501 can be configured to determine the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organizational hierarchy tree based on the first organization identifier of the ledger application request.

[0092] The selection module 502 can be configured to determine a target ledger template from a set of ledger templates based on a template selection instruction.

[0093] The generation module 503 may be configured to generate a ledger corresponding to the first organization identifier based on the target ledger template and the entity data.

[0094] In some optional modes of this embodiment, the device also includes: an execution module, which is configured to, in response to detecting an operation request for a target object, determine whether the second organization node corresponding to the second organization identifier of the operation request and the target organization node corresponding to the target object meet preset conditions; in response to determining that the preset conditions are met, perform the operation indicated by the operation request on the target object.

[0095] In some optional aspects of this embodiment, the execution module is further configured to present the ledgers corresponding to the target organization node and the subordinate organization nodes of the target organization node in the organization hierarchy tree in response to determining that the target object is a target organization node.

[0096] In some optional aspects of this embodiment, the execution module is further configured to present update prompt information for the target ledger in response to determining that the target object is a target ledger; and in response to receiving an update confirmation instruction, update the target ledger based on the update prompt information.

[0097] In some optional aspects of this embodiment, the execution module is further configured to, in response to determining that the target object is a target ledger, set the target ledger to an editable state; in response to receiving an editing instruction, execute the operation indicated by the editing instruction on the target ledger.

[0098] In some optional methods of this embodiment, the ledger template is created in the following manner: based on the template configuration request, the ledger template corresponding to the organization identifier is configured.

[0099] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, storage and other aspects of user personal information involved in the technical solution of this disclosure are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security and national security.

[0100] According to an embodiment of the present application, the present application also provides an electronic device and a readable storage medium.

[0101] like Figure 6 , is a block diagram of an electronic device according to the ledger management method of an embodiment of the present application.

[0102] 600 is a block diagram of an electronic device according to the ledger management method of an embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0103] like Figure 6 As shown, the electronic device includes: one or more processors 601, a memory 602, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In other embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 6 A processor 601 is taken as an example.

[0104] The memory 602 is a non-transient computer-readable storage medium provided in the present application. The memory stores instructions executable by at least one processor to enable the at least one processor to execute the ledger management method provided in the present application. The non-transient computer-readable storage medium of the present application stores computer instructions, which are used to enable a computer to execute the ledger management method provided in the present application.

[0105] The memory 602 is a non-transient computer-readable storage medium that can be used to store non-transient software programs, non-transient computer executable programs and modules, such as program instructions / modules corresponding to the ledger management method in the embodiment of the present application (for example, the attached Figure 5 The processor 601 executes various functional applications and data processing of the server by running the non-transient software programs, instructions and modules stored in the memory 602, that is, the ledger management method in the above method embodiment is implemented.

[0106] The memory 602 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the use of the electronic device managed by the ledger, etc. In addition, the memory 602 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 602 may optionally include a memory remotely arranged relative to the processor 601, and these remote memories may be connected to the electronic device managed by the ledger via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0107] The electronic device of the ledger management method may further include: an input device 603 and an output device 604. The processor 601, the memory 602, the input device 603 and the output device 604 may be connected via a bus or other means. Figure 6 The example of connecting through bus is taken in the following.

[0108] The input device 603 can receive input digital or character information, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a track ball, a joystick, and other input devices. The output device 604 may include a display device, an auxiliary lighting device (e.g., an LED), and a tactile feedback device (e.g., a vibration motor). The display device may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display, and a plasma display. In some embodiments, the display device may be a touch screen.

[0109] Various implementations of the systems and techniques described herein can be realized in digital electronic circuit systems, integrated circuit systems, dedicated ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0110] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for programmable processors and can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, device, and / or means (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0111] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0112] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0113] A computer system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.

[0114] According to the technical solution of the embodiment of the present application, the flexibility of creating ledgers for organizations at all levels is effectively improved.

[0115] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution disclosed in this application can be achieved, and this document is not limited here.

[0116] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A ledger management method, the method comprising: Based on the first organization identifier in the ledger application request, determine the first organization node corresponding to the first organization identifier and the ancestor node of the first organization node from the organization hierarchy tree, the organization hierarchy tree being constructed based on the organization nodes corresponding to the organization identifier and the hierarchical relationship between the organization nodes; Based on the template selection instruction, determine a target ledger template in a ledger template set, wherein the ledger template set includes the ledger template corresponding to the first organization node and the ledger template of the ancestor node; Based on the target ledger template and entity data, a ledger corresponding to the first organization identifier is generated.

2. The method according to claim 1, further comprising: In response to detecting an operation request for a target object, determining whether a second organization node corresponding to a second organization identifier of the operation request and a target organization node corresponding to the target object meet a preset condition, wherein the target object is a target ledger or a target organization node, and the preset condition includes one of the following: the second organization node is the same as the target organization node, and the second organization node is an ancestor node of the target organization node; In response to determining that the preset condition is met, the operation indicated by the operation request is performed on the target object.

3. The method according to claim 2, wherein: Performing the operation indicated by the operation request on the target object includes: In response to determining that the target object is a target organization node, a ledger corresponding to the target organization node and subordinate organization nodes of the target organization node in an organization hierarchy tree is presented.

4. The method according to claim 2, wherein: Performing the operation indicated by the operation request on the target object includes: In response to determining that the target object is a target ledger, presenting update prompt information for the target ledger, the update prompt information being generated based on a target entity that has changed in a data source of the ledger, and the organization scope corresponding to the target entity is included in the organization scope corresponding to the target ledger; In response to receiving the update confirmation instruction, the target ledger is updated based on the update prompt information.

5. The method according to claim 2, wherein: Performing the operation indicated by the operation request on the target object includes: In response to determining that the target object is a target account, setting the target account to an editable state; In response to receiving the editing instruction, the operation indicated by the editing instruction is performed on the target ledger.

6. The method according to any one of claims 1 to 5, wherein: The account template is created in the following way: Based on the template configuration request, a ledger template corresponding to the organization identifier is configured, and the configuration request includes an entity category and attribute items.

7. A ledger management device, comprising: A determination module configured to determine, based on a first organization identifier in a ledger application request, a first organization node corresponding to the first organization identifier and an ancestor node of the first organization node from an organization hierarchy tree, wherein the organization hierarchy tree is constructed based on organization nodes corresponding to the organization identifier and hierarchical relationships between organization nodes; A selection module is configured to determine a target ledger template from a ledger template set based on a template selection instruction, wherein the ledger template set includes the ledger template corresponding to the first organization node and the ledger template of the ancestor node; A generation module is configured to generate a ledger corresponding to the first organization identifier based on the target ledger template and entity data.

8. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor so that the at least one processor can perform the method according to any one of claims 1 to 6.

9. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 6.

Images