Online document processing method, device and electronic device

Abstract

The present disclosure provides an online document processing method, device and electronic device, which can be used in the financial field or other fields. The method includes: receiving a document processing request, the document processing request includes a user identifier and a document identifier; in response to the document processing request, determining a user attribute corresponding to the user identifier, and determining a current document stage of an online document identified by the document identifier; and determining the processing authority of the user identifier for the online document based on a first mapping relationship, the user attribute and the current document stage, so as to assign the processing authority to a user corresponding to the user identifier.

Description

Technical Field

[0001] The present disclosure relates to the field of cloud computing, and more specifically, to an online document processing method, device and electronic device. Background Art

[0002] As the continuous delivery pipeline of processes, methods and systems (Development Operations, DevOps) is widely recognized by the industry, continuous delivery of versions with close collaboration between development and operation and maintenance is a major trend in version management.

[0003] In the process of implementing the concept of the present disclosure, the inventors found that there are at least the following problems in the related art: In the related art, the document management method of multiple parties related to the document has deficiencies in management efficiency, authority accuracy, and document accuracy. Summary of the invention

[0004] In view of this, the present disclosure provides an online document processing method, device and electronic device for improving the management efficiency, authority accuracy and document accuracy of multiple parties in document management.

[0005] One aspect of the present disclosure provides an online document processing method, wherein the online document includes at least one document stage, and the method includes: first, receiving a document processing request, wherein the document processing request includes a user identifier and a document identifier. Then, in response to the document processing request, determining a user attribute corresponding to the user identifier, and determining a current document stage of the online document identified by the document identifier. Next, determining the processing authority of the user identifier for the online document based on a first mapping relationship, the user attribute, and the current document stage, so as to assign the processing authority to the user corresponding to the user identifier.

[0006] One aspect of the present disclosure provides an online document processing device, including a processing request receiving module, a processing request response module and a processing authority determination module. The processing request receiving module is used to receive a document processing request, and the document processing request includes a user identifier and a document identifier. The processing request response module is used to respond to the document processing request, determine the user attribute corresponding to the user identifier, and determine the current document stage of the online document identified by the document identifier, and the online document includes at least one document stage. The processing authority determination module is used to determine the processing authority of the user identifier for the online document based on a first mapping relationship, the user attribute and the current document stage, so as to assign the processing authority to the user corresponding to the user identifier.

[0007] Another aspect of the present disclosure provides an electronic device, including one or more processors and a storage device, wherein the storage device is used to store executable instructions, and when the executable instructions are executed by the processor, the method described above is implemented.

[0008] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above-mentioned method when executed.

[0009] Another aspect of the present disclosure provides a computer program, which includes computer executable instructions, and the instructions are used to implement the method described above when executed.

[0010] The online document processing method, device and electronic device provided by the embodiments of the present disclosure divide online documents into multiple document stages. The same user has different processing permissions for different document stages, thus forming an online transferable document, so that the current user's processing permissions for the online document can be determined based on the user attributes and the current document stage of the online document, thereby realizing a pipelined, multi-party visible, multi-party joint maintenance method, achieving control over the accuracy of online documents at each stage, and achieving flexibility and efficiency in version document release and production by verifying and confirming online documents.

[0011] The online document processing method, device and electronic device provided by the embodiments of the present disclosure provide a unified online template, improve the standardization of version document writing, improve the quality of version documents, and all operations from document creation and editing to production implementation are performed through a unified system, replacing the online and offline alternating document maintenance method. Version document problems no longer require feedback from other system processes, thereby reducing manual operations and lowering the cost of version document maintenance.

[0012] The online document processing method, device and electronic device provided by the embodiments of the present disclosure perform permission control on personnel in different roles, and release version document viewing permissions to all roles, so that all personnel can see the version document throughout its life cycle, and the document maintenance process is transparent, so that the environment can be prepared in advance and the efficiency of testing and production can be improved.

[0013] The online document processing method, device and electronic device provided by the embodiments of the present disclosure have different processing permissions for multiple partners at each document stage during the document pipeline process to ensure the accuracy of document permissions, and jointly maintain and confirm the same document to ensure the accuracy of the document, and realize that the document is put into production as soon as it is confirmed, breaking the working barriers between the three parties, enabling version document issues to be responded to quickly, improving the assistance from development to operation and maintenance, and ensuring the safe production of products corresponding to the document. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0015] Figure 1The following schematically shows a logic diagram of an online document processing method in the prior art;

[0016] Figure 2 The application scenarios of the online document processing method, device and electronic device according to the embodiments of the present disclosure are schematically shown;

[0017] Figure 3 An exemplary system architecture to which an online document processing method, apparatus, and electronic device according to an embodiment of the present disclosure can be applied is schematically shown;

[0018] Figure 4 A flowchart of an online document processing method according to an embodiment of the present disclosure is schematically shown;

[0019] Figure 5 A schematic diagram schematically shows a first mapping relationship according to an embodiment of the present disclosure;

[0020] Figure 6 A schematic diagram schematically illustrates document identification according to an embodiment of the present disclosure;

[0021] Figure 7 A schematic diagram of a document pipeline according to an embodiment of the present disclosure is schematically shown;

[0022] Figure 8 A schematic diagram schematically shows document stage association information according to an embodiment of the present disclosure;

[0023] Fig. 9 A block diagram schematically shows an online document processing apparatus according to an embodiment of the present disclosure; and

[0024] Fig.10 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0025] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0026] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0027] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0028] In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). In the case of using expressions such as "at least one of A, B, or C, etc.", it should generally be interpreted in accordance with the meaning of the expression generally understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.). The terms "first" and "second" are used only for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more features.

[0029] Figure 1 The following schematically shows a logic diagram of an online document processing method in the prior art.

[0030] like Figure 1 As shown, in the prior art, when processing documents online, in order to ensure that the online documents processed by different users are the latest and the content is continuous, users are usually required to download the documents first, edit them locally, and then upload the edited documents for other users to download and edit.

[0031] However, the document processing methods of existing technologies cannot meet the special needs in some scenarios. For example, when the DevOps continuous delivery pipeline is widely recognized by the industry, the continuous delivery of versions with close collaboration between development and operation and maintenance is a major trend in version management. The traditional staged management method of version documents by development, testing and operation and maintenance parties has deficiencies in efficiency, authority accuracy, and document accuracy. For example, in the daily version management process, the following problems are often encountered.

[0032] On the one hand, after the version document is written by the R&D personnel and delivered to the testers along with the version, and before the version is finally released to the operation and maintenance personnel after the testing is completed, the testers and the operation and maintenance personnel are not clear about the specific environmental preparations that need to be made, and they do not grasp the content of the version document in a timely manner, resulting in poor timeliness of version deployment.

[0033] On the one hand, since the version document is sent out along with the test patch through the version transmission system, testers need to download the version document from the version transmission system to perform verification locally. When the version finally needs to be released to the operation and maintenance personnel, the final production version document must be manually written and uploaded to the version transmission system for handover to the operation and maintenance. Both accuracy and timeliness need to be improved.

[0034] On the one hand, when problems are found in the version document during the testing process, it is necessary to submit the problem through the problem management system. The version document information, problem location and problem details need to be described in the problem management system. The problem needs to go through the relevant approval process in the problem management system before it can be transferred to the R&D personnel. The operation process is complicated and the problem cannot be fed back to the R&D personnel in a timely and effective manner. The revised version document needs to be issued with the next patch version. If it needs to be issued on the next day, the response speed of the version document problem is limited.

[0035] Figure 2 The application scenarios of the online document processing method, device and electronic device according to the embodiments of the present disclosure are schematically shown. It should be noted that the online document processing method, device and electronic device provided by the embodiments of the present disclosure can be used in cloud computing in document management related aspects, and can also be used in various fields other than the field of cloud computing. The application fields of the online document processing method, device and electronic device provided by the embodiments of the present disclosure are not limited.

[0036] like Figure 2 As shown, after user 1 (such as a research and development staff) initiates an online document, user 2 (such as a tester), user 3 (such as an operation and maintenance staff), etc. can perform operations such as viewing, editing, and approving the document online according to their own processing permissions without downloading the document. Among them, different users have different editing and approval processing permissions at different stages, and the processing permissions are determined according to the user's attributes and the current stage of the online document (such as any stage in stage 1 or stage 2). When a document stage is approved, the online document enters the next stage, and the user's processing permissions for the online document will change. In the above manner, the risk of accidents caused by irrelevant personnel editing online documents is reduced, which helps to improve the various problems encountered in the above-mentioned related technologies.

[0037] Embodiments of the present disclosure provide an online document processing method, device, and electronic device. The online document processing method includes an information determination process and a processing authority determination process. In the information determination process, first, a document processing request is received, the document processing request includes a user identifier and a document identifier, and then, in response to the document processing request, a user attribute corresponding to the user identifier is determined, and the current document stage of the online document identified by the document identifier is determined. After the information determination process is completed, the processing authority determination process is entered, and the processing authority of the user identifier for the online document is determined based on the first mapping relationship, the user attribute, and the current document stage, so as to assign the processing authority to the user corresponding to the user identifier.

[0038] The online document processing method, device and electronic device provided by the embodiments of the present disclosure achieve control over the final accuracy of version documents, such as version documents, through a pipelined, multi-party visible, multi-party participating document processing method, and achieve flexibility and efficiency in the release and production of version documents by verifying and confirming version documents.

[0039] Figure 3 The exemplary system architecture to which the online document processing method, apparatus and electronic device according to the embodiments of the present disclosure can be applied is schematically shown. It should be noted that: Figure 3 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0040] like Figure 3 As shown, the system architecture 300 according to this embodiment may include terminal devices 301, 302, 303, a network 304 and a server 305. The network 304 may include multiple routers, network cables, etc., which are used to provide a medium for communication links between the terminal devices 301, 302, 303 and the server 305. The network 304 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0041] The user can use the terminal devices 301, 302, 303 to interact with other terminal devices and the server 305 through the network 304 to receive or send information, such as sending a document creation request, a user role entry request, a document related information query request, editing an online document, approving an online document, and receiving processing results, etc. The terminal devices 301, 302, 303 can be installed with various communication client applications, such as banking applications, operation and maintenance applications, web browser applications, office applications, search applications, instant messaging tools, email client, social platform software, etc. (only for example).

[0042] Terminal devices 301 , 302 , and 303 include, but are not limited to, smart phones, virtual reality devices, augmented reality devices, tablet computers, laptop computers, and the like.

[0043] The server 305 can receive the request and process the request. For example, the server 305 can be a background management server, a server cluster, etc. The background management server can analyze and process the received document creation request, user role entry request, document related information query request, etc., and feed back the processing result (such as document creation success prompt, role entry success, etc.) to the terminal device.

[0044] It should be noted that the online document processing method provided in the embodiment of the present disclosure can generally be executed by the server 305. Accordingly, the online document processing device provided in the embodiment of the present disclosure can generally be set in the server 305. The online document processing method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 305 and can communicate with the terminal devices 301, 302, 303 and / or the server 305.

[0045] It should be understood that the number of terminal devices, networks and servers is only illustrative. Depending on the implementation requirements, there can be any number of terminal devices, networks and servers.

[0046] Figure 4 The flowchart of the online document processing method according to the embodiment of the present disclosure is schematically shown.

[0047] like Figure 4 As shown, the method may include operations S401 to S405.

[0048] In operation S401, a document processing request is received, where the document processing request includes a user identifier and a document identifier.

[0049] In this embodiment, the online document may include at least one document stage, such as the online document may include the research and development stage, the testing stage and the operation and maintenance stage, and each stage may correspond to each product stage in the life cycle of the product corresponding to the online document. For example, when a research and development personnel is developing a new product, they create a technical document for the product, then the document stage may be in the research and development stage, and when the product is subsequently delivered to the testing department for testing, the document stage may be in the testing stage. It should be noted that, in order to achieve refined management, each document stage can also be subdivided into multiple sub-document stages, and a user's processing permissions for multiple sub-document stages within a document stage can be the same or different.

[0050] When a user logs into a document processing system through a user ID, the user ID can be obtained. In addition, the user ID can also be input by the user in the document processing system. The user ID is used to uniquely identify a user, and it can be assigned to the user by the system or applied for by the user to the system, which is not limited here.

[0051] The document identifier can be an identifier automatically generated when an online document is created to uniquely identify a document. In addition, in order to facilitate intuitive determination of the product corresponding to a document, the document identifier can be generated based on certain rules using information such as product name and version. The document identifier can be modified or prohibited from being modified. In addition, when a document needs to be recreated, document version information can be added to the document identifier for differentiation.

[0052] In operation S403, in response to the document processing request, a user attribute corresponding to the user identifier is determined, and a current document stage of the online document identified by the document identifier is determined.

[0053] In this embodiment, different processing permissions can be set for different users for online documents in different document stages. For example, R&D personnel can perform processing such as editing and approving on documents in the R&D stage, but cannot edit or approve documents in the testing stage. Testers can perform processing such as editing and approving on documents in the testing stage, but cannot edit or approve documents in the R&D stage. It should be noted that users with user attributes that do not correspond to the current document stage can also have certain processing permissions, such as viewing permissions, so that product-related staff corresponding to the online document (such as R&D, testing, and operation and maintenance personnel, etc.) can view the document, which makes it easier for relevant staff to timely understand the product progress and the preparations required to undertake the product.

[0054] Specifically, the user attributes corresponding to the user ID can be determined in a human resources database, such as whether the user represented by the user ID is employed, what his position is, what department he belongs to, whether the department belongs to R&D, testing or operation and maintenance, etc., the user's position in the company, etc. The current document stage of the online document can be obtained by querying the database.

[0055] In operation S405, the processing authority of the user identifier for the online document is determined based on the first mapping relationship, the user attribute and the current document stage, so as to allocate the processing authority to the user corresponding to the user identifier.

[0056] In this embodiment, the processing authority of the current user for the online document may be determined by matching, querying, and the like.

[0057] Figure 5 A schematic diagram schematically shows a first mapping relationship according to an embodiment of the present disclosure.

[0058] like Figure 5 As shown, there is a mapping relationship between the combination of user attributes and document stages and processing permissions. For example, R&D personnel have the processing permissions of viewing, editing, and approving documents in the R&D stage, and testers have the processing permissions of viewing documents in the operation and maintenance stage. This allows the current user's processing permissions to be determined by query or matching. Figure 5 The first mapping relationship shown is only an example. In addition to the combination of user attributes and document stages, multiple other combinations can be used, such as a combination of employee rank and document stage, a combination of at least one of the user's department, user age group, user rank, user gender, user's product group, etc. and document stage, etc. This makes it easy to pre-set the mapping relationship between each combination and processing authority according to user needs.

[0059] In one embodiment, determining the processing authority of the user identifier for the online document based on the first mapping relationship, the user attribute and the current document stage may include the following operations: determining the processing authority corresponding to the user attribute and the current document stage by querying the authority table, wherein the variables of the authority table include the user attribute, the document stage and the processing authority.

[0060] For example, taking the DevOps continuous delivery pipeline scenario as an example, the version document pipeline of an application can set up three roles: R&D personnel, testers, and operation and maintenance personnel (roles can be a type of user attribute). In each document stage of a version of the online document, all roles are given the right to view the document, and the document content is visible throughout the process. The R&D role is given the document editing and development stage document approval authority. The tester role is given the document approval authority during the testing process. The operation and maintenance role is given the document approval authority during the production process. Table 1 is a table of the permissions of each role at each stage of the version document.

[0061] It should be noted that the permission table shown in Table 1 is only an example. In addition to the combination of user attributes and document stages, many other combinations can be used. In addition, permissions can include other permissions besides viewing, editing and approving, such as sharing, printing, returning to the previous document stage, etc.

[0062] Table 1

[0063]

[0064] The online document processing method provided by the disclosed embodiment realizes the full sharing and visibility of the version document from development creation and editing to operation and maintenance implementation and production throughout the entire life cycle. The accuracy of permissions is ensured through online conversion of document status and permission setting for relevant personnel, and the maintenance of a unique document for the same product (such as an application) is realized to ensure the accuracy of the version document. Users can edit and display documents through a unified global wide area network (World Wide Web, referred to as WEB) interface to make the documents more standardized. After development and delivery, the testing process is continuously improved, and production can intervene in document quality control in advance, and finally hand over and approve, directly forming a production document, without the need to edit documents offline and then transmit them online, avoiding manual integration of documents, and realizing the standardization of document writing and document operation processes.

[0065] In one embodiment, the method may further include the following operations.

[0066] First, a document creation request is received. The document processing request includes a document identification. The document identification includes at least one of a product name, product version information, product-related date information, and document version information. The product name may be an application name, an application abbreviation, an application code, etc. The product-related date may include: the project establishment date of the product, the product development start time, the product production date and its code, etc. The document version information may be included in the document creation request, or may be generated by the system by default. For example, the version of the document generated for the product for the first time may be 0, 1, a, etc., and the version of the document generated for the product for the second time may be 1, 2, b, etc., which will not be described in detail here.

[0067] Then, in response to the document creation request, the document template is called to generate an online document, wherein at least one document stage corresponds to each product stage in the product life cycle. The document template may be in a unified format, such as including: document title, subtitle, directory, section, etc. In addition, the document template may include multiple versions, such as a unified template for financial applications, a unified template for government applications, etc., so that users can select the required template from the template library according to their own needs.

[0068] For example, a unified version of a document template is entered into the system database. After the document name is generated, click on the document name displayed on the page (which can be a document ID or have a mapping relationship with the document ID) to trigger the call of the document template, display the document chapters for R&D personnel to fill in, obtain the written document content and save it to the server, initiating subsequent processes.

[0069] Figure 6 A schematic diagram of document identification according to an embodiment of the present disclosure is schematically shown.

[0070] like Figure 6As shown, the document identifier may include: product name partial information (XXXX), product version partial information (YYYY), associated date partial information (ZZZZ) and document version partial information (PPPP). It should be noted that the various parts and their digits, characters, etc. in the document identifier are only examples and cannot be understood as limitations of the present disclosure.

[0071] In one embodiment, at least one document stage is arranged in sequence according to the order of arrangement of each product stage in the product life cycle to form a document pipeline.

[0072] Figure 7 A schematic diagram of a document pipeline according to an embodiment of the present disclosure is schematically shown.

[0073] like Figure 7 As shown in the figure, the document pipeline may include: creation and editing stage, internal testing stage, delivery stage, testing stage, handover stage, production and commissioning stage, and end stage. After each previous document stage is approved, it will automatically enter the next document stage. The same user has different processing permissions for each document stage in the document pipeline. In addition, different users have different processing permissions for the same document stage in the document pipeline.

[0074] For example, when R&D personnel create a version document pipeline, they determine that the document name consists of three elements: application name, version number, and production date. A version document is determined by these three elements, forming a document pipeline. The system provides an entry to create a document. After obtaining the three elements entered on the page, the system generates a document name based on the rules and writes it into the database. At the same time, the page displays the document name.

[0075] In one embodiment, the processing authority includes the review authority. Accordingly, the following operations may also be included.

[0076] First, a review pass instruction is received, where the review pass instruction indicates that the review result for the online document is passed. Then, in response to the review pass instruction, the current document stage is updated to the next document stage in the document pipeline.

[0077] For example, an online document approved by a developer enters the testing phase, and a tester approves the online document. If the tester approves the online document, the document enters the next document phase, such as the operation and maintenance phase.

[0078] In one embodiment, the processing authority includes the review authority. Accordingly, the following operations may also be included.

[0079] First, an audit failure instruction is received, which indicates that the audit result for the online document is rejection. Then, in response to the audit failure instruction, the current document stage is updated to the first document stage of the document pipeline, and the document version information is updated.

[0080] For example, after the R&D personnel have approved the online document, it enters the testing phase, and the tester approves the online document. If the tester's approval result for the online document is that it fails, it will enter the document creation phase so that the R&D personnel can create the document again. It should be noted that the re-created online document is still for the same product (same product version), so the main body of the document identifier may not change, and only the document version information in the document identifier of the online document needs to be updated.

[0081] In addition, the authority of the user who created the document can be higher than that of other users with approval authority. For example, after the tester approves the online document, he only has the viewing function and cannot change the document stage to the first document stage (such as the document creation stage). However, if the tester finds that a certain online document has defects after approving it and needs to be re-approved or edited, the user who created the document, such as the R&D personnel, can be notified to change the document stage of the online document to the document creation stage. In addition, the user with approval authority for the current document stage can also be notified to change the document stage to the document creation stage.

[0082] The following is an example of how to apply for user attributes.

[0083] In one embodiment, the following operations may also be included.

[0084] First, a user attribute application request is received, which includes a user role and at least one of the following: user ID, organization, product name, and application reason. On the one hand, if the user role and organization match, the variable-related information in the user attribute application request and the permission table is entered into the permission table. On the other hand, if the user role and organization do not match, at least the application reason is sent to the client of the reviewing user, so that the reviewing user can process the permission review based on the application reason displayed by the client.

[0085] For example, the system provides an entry for users to apply for roles, and the system obtains the information entered by the user in the application page through an interactive interface (such as an interactive component in the interactive interface). Among them, the entered information includes but is not limited to at least one of: "affiliated unit department", "application name", "role", and "application reason". The R&D personnel of the R&D department apply for the R&D personnel role, the tester of the testing department applies for the tester role, and the operation and maintenance personnel of the production department applies for the operation and maintenance personnel role. If the applied role matches the unit department to which they belong, the system authorizes the user's role application and saves the obtained input information into the permission table of the database (see Table 1). The information in the permission table determines the processing rights of each user for online documents at each document stage. If the role applied by the user does not match the department to which he belongs, in one embodiment, if the application reason is not sufficient, the application is rejected first and the rejection reason is fed back, and the applicant is notified by email that the application is unsuccessful. The input information is not written into the permission table. Regardless of whether the permission application is successful, the application record is entered into the permission application record table (including information: personnel ID, application name, role, application reason, whether it is authorized, and rejection reason). Among them, whether the application reason is sufficient can be reviewed manually or automatically based on certain rules. For example, the reason is filled in as follows: XXX was seconded from R&D to the testing department on AA / BB / YY, and the role he applied for is a testing role. If "XXX was seconded from R&D to the testing department on AA / BB / YY" is consistent with the information recorded in the human resources database, the role application can be automatically approved.

[0086] In another embodiment, if the application reason is not sufficient, the application reason is sent to the terminal of the approver of the department to which the application is applied, so that the approver of the department to which the application is applied can approve the application.

[0087] In one embodiment, in order to facilitate the user to determine whether the current application is successful, the above method may also include the following operations. If the user role matches the organization, the user ID is used to match in the authentication system to determine the communication address corresponding to the user ID, so as to output a prompt message indicating that the permission application is successful based on the communication address. For example, the permission table may record the person ID (ID, as a key value, such as a login user name) obtained when the person first logs into the system, and the person name and email information obtained from the unified authentication system through the person ID, and write the corresponding information through the "personnel ID" attribute in the matching table, and notify the applicant of the success of the permission application by email.

[0088] In one embodiment, the method may also provide a query interface for the user to query relevant information such as the document stage. For example, the method may also include the following operations. First, a document stage information request is received. Then, document stage associated information corresponding to the document stage information request is output, wherein the document stage associated information includes status information of the document stage and color information corresponding to the status information.

[0089] For example, the version document is displayed through a WEB page, and each pipeline provides a pipeline link diagram to show the current status of the document. The passed links are displayed as the first status (such as green or the first fill), the current link is displayed as the second status (such as blue or the second fill), and the unreached link is the third status (such as gray or the third fill). The version document display page provides "Approval" and "Approval Rejection" buttons. Personnel with authority in each link can approve the corresponding link by clicking the page display. By converting the document status, the pipeline transmission of the version document is realized.

[0090] Figure 8 A schematic diagram schematically shows document stage association information according to an embodiment of the present disclosure.

[0091] like Figure 8 As shown, the document pipeline may include seven stages: creation and editing stage, internal testing stage, delivery stage, testing stage, handover stage, production commissioning stage and end stage. Among them, the creation and editing stage, internal testing stage and delivery stage are completed stages, and a grid fill pattern can be displayed. The testing stage is the current document stage, and a vertical bar fill pattern can be displayed. The handover stage, production commissioning stage and end stage are document stages that have not yet been carried out, and pattern filling may not be performed. In this way, users related to the product can directly view the current document stage of the online document related to the product.

[0092] The document processing flow of the application version document is exemplarily described below with a specific embodiment.

[0093] The version document of the application can be created by the R&D personnel. After the document content is uploaded to the server database, the document status is set to "internal test", and the internal test node of the page pipeline is set to blue. At this time, according to the personnel authority configuration, the R&D personnel have the approval authority. During the internal test phase, the approval operation is performed to obtain the approval result of the page writeback. If the approval is passed, the document status is set to "delivery", the internal test node of the page pipeline is set to green, and the delivery node is set to blue. During the delivery phase, the approval operation is performed to obtain the approval result of the page writeback. If the approval is passed, the document status is set to "testing", the delivery node of the page pipeline is set to green, and the test node is set to blue. At this time, according to the personnel authority configuration, the tester begins to have the approval authority. During the test phase, the approval operation is performed to obtain the approval result of the page writeback. If the approval is passed, the document status is set to "handover", the test node is set to green, and the handover node is set to blue. During the handover phase, the approval operation is performed to obtain the approval result of the page writeback. If the approval is passed, the document status is set to "production and production", the handover node of the page pipeline is set to green, and the production and production node is set to blue. At this time, according to the personnel authority configuration, the operation and maintenance personnel begin to have approval authority and perform approval operations in the production commissioning stage. If the approval is passed, the document status is set to ended, the page pipeline production commissioning node is set to green, the end node is set to green, and the pipeline ends.

[0094] When the version document reaches any document stage, an email is sent to notify the corresponding processing personnel of the application in this link according to the corresponding email information in the permission table to handle it in time. If the approval result obtained at each stage is not passed, the document is set to the "Create Edit" state, and the reason for the entered approval failure is obtained and saved in the database. The R&D personnel are notified to re-edit it, the node that fails the approval is set to red, the pipeline stops, and the pipeline is re-initiated for the newly edited document.

[0095] Users can trigger the document to be displayed on the page by clicking on the blue document stage on the WEB page. The red links that have been approved and rejected will also display the reasons for the rejection.

[0096] The document processing method disclosed herein is a version document maintenance method based on an assembly line form. On the one hand, through the online assembly line management of version documents, a unified online template is provided to improve the standardization of version document writing and the quality of version documents. From document creation and editing to completion of production implementation, all operations are performed through a unified system, replacing the online and offline alternating document maintenance method. Version document problems no longer require feedback from other system processes, thereby reducing manual operations and lowering the cost of version document maintenance.

[0097] On the other hand, the present invention controls the permissions of personnel with each user attribute and loosens the version document viewing permissions for users with all user attributes, so that the version document can be viewed by all personnel throughout its life cycle, and the document maintenance process is transparent, which facilitates relevant users to prepare the environment required for the product in advance and improves the efficiency of testing and production.

[0098] On the other hand, the disclosure enables the development, testing and operation and maintenance parties to perform their respective duties in the assembly line process to ensure the accuracy of permissions, and to jointly maintain and confirm the same document to ensure the accuracy of version documents, and to achieve production of version documents as soon as they are confirmed, breaking down the working barriers between the three parties, so that version document issues can be responded to quickly, improving the assistance from development to operation and maintenance, and ensuring the safety of version production.

[0099] One aspect of the present disclosure provides an online document processing apparatus.

[0100] Fig. 9 The block diagram of an online document processing apparatus according to an embodiment of the present disclosure is schematically shown.

[0101] like Fig. 9 As shown, the online document processing device 900 includes: a processing request receiving module 910, a processing request responding module 920 and a processing authority determining module 930.

[0102] The processing request receiving module 910 is used to receive a document processing request, where the document processing request includes a user identifier and a document identifier.

[0103] The processing request response module 920 is used to respond to the document processing request, determine the user attribute corresponding to the user identifier, and determine the current document stage of the online document identified by the document identifier, and the online document includes at least one document stage.

[0104] The processing authority determination module 930 is used to determine the processing authority of the user identifier for the online document based on the first mapping relationship, the user attribute and the current document stage, so as to allocate the processing authority to the user corresponding to the user identifier.

[0105] It should be noted that the implementation methods, technical problems solved, functions realized, and technical effects achieved of each module / unit in the device part embodiment are the same or similar to the implementation methods, technical problems solved, functions realized, and technical effects achieved of each corresponding step in the method part embodiment, and they will not be repeated here one by one.

[0106] According to the modules and units of the embodiments of the present disclosure, any multiple or at least part of the functions of any multiple thereof can be implemented in one module. According to the modules and units of the embodiments of the present disclosure, any one or more can be split into multiple modules for implementation. According to the modules and units of the embodiments of the present disclosure, any one or more can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware of any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, according to the modules and units of the embodiments of the present disclosure, one or more can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0107] For example, any of the processing request receiving module 910, the processing request response module 920, and the processing authority determination module 930 can be combined in one module for implementation, or any of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the processing request receiving module 910, the processing request response module 920, and the processing authority determination module 930 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation modes of software, hardware, and firmware or in any appropriate combination of any of them. Alternatively, at least one of the processing request receiving module 910, the processing request response module 920, and the processing authority determination module 930 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0108] One aspect of the present disclosure provides an electronic device. Fig.10 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown. Fig.10 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0109] like Fig.10As shown, the electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 into a random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include an onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0110] In RAM 1003, various programs and data required for the operation of electronic device 1000 are stored. Processor 1001, ROM 1002 and RAM 1003 are connected to each other through bus 1004. Processor 1001 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1002 and / or RAM 1003. It should be noted that the program can also be stored in one or more memories other than ROM 1002 and RAM 1003. Processor 1001 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.

[0111] According to an embodiment of the present disclosure, the electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to the bus 1004. The electronic device 1000 may further include one or more of the following components connected to the I / O interface 1005: an input portion 1006 including a keyboard, a mouse, etc.; an output portion 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1008 including a hard disk, etc.; and a communication portion 1009 including a network interface card such as a LAN card, a modem, etc. The communication portion 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage portion 1008 as needed.

[0112] According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1009, and / or installed from the removable medium 1011. When the computer program is executed by the processor 1001, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

[0113] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0114] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1002 and / or RAM 1003 described above and / or one or more memories other than ROM 1002 and RAM 1003.

[0115] Those skilled in the art will appreciate that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present disclosure. These embodiments are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the various embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, all of which should fall within the scope of the present disclosure.

Claims

1. A DevOps-based online version delivery document processing method, wherein the online document includes at least one document stage, and the method includes: receiving a document processing request, wherein the document processing request includes a user identifier and a document identifier; In response to the document processing request, determining a user attribute corresponding to the user identifier, and determining a current document stage of the online document identified by the document identifier; as well as Determining the processing authority of the user identifier for the online document based on the first mapping relationship, the user attribute and the current document stage, so as to allocate the processing authority to the user corresponding to the user identifier; The method further comprises: Receiving a document creation request, the document processing request including a document identifier, the document identifier including at least one of a product name, product version information, product associated date information, and document version information; In response to the document creation request, calling a document template to generate the online document, wherein at least one of the document stages corresponds to each product stage in the product life cycle; wherein at least one document stage is arranged in sequence according to the order of arrangement of the product stages in the product life cycle to form a document pipeline; Wherein, the processing authority includes review authority, and the method further comprises: Receiving a review pass instruction, which indicates that the review result for the online document is passed, and updating the current document stage of the review pass to the next document stage in the document pipeline until the document is put into production; Receive an audit failure instruction, wherein the audit failure instruction indicates that the audit result for the online document is rejection; and in response to the audit failure instruction, update the current document stage to the first document stage of the document pipeline, and update the document version information.

2. The method according to claim 1, wherein: The determining the processing authority of the user identifier for the online document based on the first mapping relationship, the user attribute and the current document stage includes: The processing authority corresponding to the user attribute and the current document stage is determined by querying an authority table, wherein variables of the authority table include user attributes, document stage and processing authority.

3. The method according to claim 2, further comprising: receiving a user attribute application request, wherein the user attribute application request includes a user role and at least one of the following: a user ID, an organization, a product name, and an application reason; If the user role matches the organization, then entering the information related to the variables in the permission table in the user attribute application request into the permission table; as well as If the user role and the organization do not match, at least the application reason is sent to the client of the reviewing user, so that the reviewing user can conduct processing authority review based on the application reason displayed by the client.

4. The method according to claim 3, further comprising: If the user role matches the organization, the user identification is used to perform a match in the authentication system to determine a communication address corresponding to the user identification, so as to send a prompt message indicating successful permission application based on the communication address.

5. The method according to any one of claims 1 to 4, further comprising: Receive document phase information requests; Output document stage associated information corresponding to the document stage information request, wherein the document stage associated information includes status information of the document stage and color information corresponding to the status information.

6. A DevOps-based online version delivery document processing device, comprising: A processing request receiving module, used to receive a document processing request and a document creation request, wherein the document processing request includes a user identifier and a document identifier, and the document identifier includes at least one of a product name, product version information, product associated date information, and document version information; a processing request response module, configured to, in response to the document processing request, determine a user attribute corresponding to the user identifier, and determine a current document stage of an online document identified by the document identifier, wherein the online document includes at least one document stage; in response to the document creation request, call a document template to generate the online document, wherein at least one of the document stages corresponds to each product stage in a product life cycle; wherein at least one of the document stages is arranged in sequence according to the arrangement order of each product stage in the product life cycle to form a document pipeline; and A processing authority determination module is used to determine the processing authority of the user identifier for the online document based on the first mapping relationship, the user attribute and the current document stage, so as to allocate the processing authority to the user corresponding to the user identifier; wherein the processing authority includes an audit authority, and the method further comprises: receiving an audit pass instruction, the audit pass instruction indicating that the audit result for the online document is passed, and updating the current document stage of the audit pass to the next document stage in the document pipeline until the document is put into production; receiving an audit failure instruction, the audit failure instruction indicating that the audit result for the online document is rejected; and in response to the audit failure instruction, updating the current document stage to the first document stage of the document pipeline, and updating the document version information; Wherein, the DevOps-based online version delivery document processing device is used to implement the method according to any one of claims 1 to 5.

7. An electronic device comprising: one or more processors; A storage device for storing executable instructions, wherein when the executable instructions are executed by the processor, the method according to any one of claims 1 to 5 is implemented.

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

Images