Document workflow versioning style governance
By specifying document styles as linear or branching workflows in the document management system, the problem that traditional systems cannot support both linear and branching workflows simultaneously is solved, enabling flexible editing and version control of documents within the same application.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- GOOGLE LLC
- Filing Date
- 2021-02-03
- Publication Date
- 2026-07-14
AI Technical Summary
Traditional document management systems cannot support both linear and branching workflows simultaneously, forcing end users to adapt to different document management applications to handle different types of documents.
A workflow style governance method is provided, which allows version control of the entire document or different parts of the document by specifying the document style as linear or branching workflow in the document management system, and allows editing in the document editor or component editor according to the style.
It enables the same document management application to handle documents with different workflow styles, improving the flexibility and efficiency of document management and supporting diverse document editing needs.
Smart Images
Figure CN115053227B_ABST
Abstract
Description
Technical Field
[0001] This disclosure pertains to the field of document management, and more specifically to document editing. Background Technology
[0002] Document management refers to the organized and recorded retrieval and storage of documents in a repository, enabling reliably retrieved documents from different end users on demand without fear of data loss. Modern document management computer programs incorporate version control, allowing the creation, retention, and retrieval of different versions of documents. Version control not only provides individual end users with a convenient way to track changes to a document throughout its lifecycle from initial creation to deletion, but it also enables collaborative document editing among different end users. This allows edits made by one end user to be visible to other users sequentially, and allows for the separate management of multiple concurrent edits by different end users.
[0003] Traditionally, documents are managed sequentially as part of a linear workflow, where each different version of a document is a separate file that can be loaded into a document editor such as a word processor or text editor. However, not all documents are single files. Instead, some documents are combinations of components that are presented as a document when they are dynamically assembled. Examples of component-driven documents include portal pages dynamically assembled from different portlet components, or document components assembled from different files, each corresponding to a different part of the document, and each being editable and reproducible separately from the other components in the assembly. In the latter instance, document assembly is edited according to a branching workflow style, where each component has a different version, but any document can be assembled from any version of each of the components that are combined to form the document.
[0004] It can be seen that both linear workflow and branching workflow styles can serve as ideal foundations for document management. However, in practice, traditional document management systems only support one type—either linear or branching workflow. Therefore, end users must adapt to two different document management applications to accommodate linear workflow styles for some documents and branching workflow styles for others. Summary of the Invention
[0005] The embodiments of this disclosure address deficiencies in document editing and version control in the art and provide a novel and non-obvious method, system, and computer program product for workflow style governance. In embodiments of this disclosure, the workflow style governance method includes: creating a document in the memory of a host computing system comprising one or more computers, each computer having memory and at least one processor; and specifying a document style for a document selected from a group consisting of linear workflow styles and branching workflow styles, wherein the linear workflow styles allow for linear sequential version control of the document as a whole, and the branching workflow styles allow for individual and independent version control of different parts of the document, as well as the synthesis of different parts to produce a version of the document. The method further includes: saving the document along with the specified document style to fixed storage of the host computing system.
[0006] Subsequently, in response to a subsequent request to load the document into the memory of one of the computers, a specified document style of the document can be retrieved, and if the specified document style is a linear workflow style, a specified version of the document can be retrieved into the document editor for editing as a new version of the document; otherwise, if the specified document style is a branching workflow style, the different components of the document are retrieved as a combination of components, each combination of components having an independent version, and one of the components of the combination of components constituting the document is loaded into the component editor for editing as a new version.
[0007] In one aspect of the embodiment, the method further includes: deferring the recombination of a document with a designated branch workflow after a component of the document has been edited, and instead saving the edited component in a pre-committed state in fixed storage. In another aspect of the embodiment, the method further includes: allowing editing of a document with a designated linear workflow style only if the end user requesting access to the document for editing has access rights to the location where the document is stored in fixed storage. In yet another aspect of the embodiment, the method further includes: allowing editing of one selected component of a document with a designated branch workflow only if the end user requesting access to the document for editing has access rights to one of the selected components, regardless of other access rights the end user has to other components of the document that differ from the access rights to the selected component.
[0008] Other aspects of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Aspects of this disclosure will be realized and obtained by means of the elements and combinations particularly pointed out in the appended claims. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and not intended to limit the claimed disclosure. Attached Figure Description
[0009] The accompanying drawings, which are included in and form part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. The embodiments shown herein are currently preferred; however, it should be understood that the present disclosure is not limited to the precise arrangements and means shown, wherein:
[0010] Figure 1 It is a diagrammatic explanation of the workflow style governance process used for document management;
[0011] Figure 2 This is a schematic diagram of a document management and data processing system suitable for workflow style governance; and,
[0012] Figure 3 This is a flowchart illustrating the process of workflow style governance in document management. Detailed Implementation
[0013] Embodiments of this disclosure provide workflow style governance in document management. According to embodiments of this disclosure, a document is created for editing, and a document style is specified for the created document. In this regard, the document style can be a linear workflow style or a branching workflow style, wherein a linear workflow style allows for linear sequential version control of the entire document, while a branching workflow style allows for individual and independent version control of different parts of the document and the merging of different parts to produce a version of the document. The document, along with the specified document style, is then saved to fixed storage. Subsequently, in response to a subsequent request to load the document into the memory of one of the computers, the specified document style of the document is retrieved, and if the specified document style is a linear workflow style, the specified version of the document is provided to the document editor for editing as a new version of the document; otherwise, if the specified document style is a branching workflow style, the different components of the document are retrieved as combinations of components, each combination of components having an independent version, and one of the components is provided to the component editor for editing as a new version. In this way, a single document management application can process different documents according to different workflow styles, regardless of the underlying workflow style of any single document.
[0014] In further illustrations, Figure 1 This is a diagrammatic illustration of the workflow style governance process used for document management. For example... Figure 1As shown, document 100 can be retained as a single version among multiple versions 130 of a linear workflow style or model 110A, or document 100 can be retained as a combination of versioned components 140 in a branch workflow model 110B or style. Along with the retention of document 100, a style selection 120 is also included to determine, based on the re-invoked style selection 120, whether to provide document 100 to a text editor 150 where all content 170 of document 100 can be edited, or to a component editor 160 where components 180 selected from the combination of components 190 can be edited.
[0015] Combination Figure 1 The described process can be implemented in a document management data processing system. In a further illustration, Figure 2 A document management data processing system suitable for workflow style governance is schematically illustrated. The system includes a host computing platform 210 comprising one or more computers, each having memory and at least one processor. The host computing platform is coupled to a document repository 230 (i.e., fixed storage), in which different document repositories are combined as both individual files and components to form virtual files. Similarly, the host computing platform 210 supports the execution of a document management application 220, which is configured to manage access to documents in the document repository 230 by requesting computing devices 260 on a computer communication network 250, including version control of documents when they are edited on those computing devices 260, and managing access to documents in the document repository 230 regarding access permissions stored in a permissions table 240.
[0016] It is worth noting that the workflow governance module 300 is coupled to the document management application 220. Module 300 includes computer program instructions enabled during execution in the host computing platform 210 to assign linear or branching workflow style selections to each document stored in the document repository 230. When a document is loaded from the document repository 230, program instructions are also enabled to identify the corresponding assigned workflow style selection and provide the document for editing in the text editor 270A if the workflow style selection is linear, or for editing in the component editor 270B if the workflow style selection is branching.
[0017] Optionally, in response to a request to retain an edited document associated with a linear workflow selection, the request is rejected if the program instruction determines that the requester lacks permissions to a location in the document repository 230. Alternatively, in response to a request to retain an edited document associated with a branch workflow selection, the request is rejected only if the requester has access to one of the selected components, regardless of any other access permissions the requester has to other components of the document that differ from access to that selected component. As yet another option, the program instruction can be enabled to postpone recombining the document with the selected components, instead saving the edited form of the selected components in a pre-committed state in the document repository 230 and allowing recombining the document only when an instruction is received in the document management application to commit the edits to that selected component.
[0018] In a further illustration of the operation of the workflow management module 300, Figure 3 This is a flowchart illustrating the workflow style governance process in document management. Starting at box 310, a document stored in the document repository is selected for retrieval and editing. At box 320, the workflow style selection associated with the document is retrieved. In decision box 330, it is determined whether the workflow style selection is linear or branching. If linear, a text editor is invoked at box 340 to edit the document, and at box 350, the edits to the document are received and stored in the repository. Subsequently, at box 360, the edited document undergoes version control and is stored in the repository, and the process ends at box 400. Conversely, if branching, a component editor is invoked at box 370 to edit the document, and at box 380, one of the components in the combination forming the document is selected for editing, and at box 390, the edited component undergoes version control and is stored in the repository. Finally, the process ends at box 400.
[0019] This disclosure may be embodied in systems, methods, computer program products, or any combination thereof. A computer program product may include one or more computer-readable storage media having computer-readable program instructions thereon for causing a processor to perform aspects of this disclosure. A computer-readable storage medium may be a tangible device capable of retaining and storing instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof.
[0020] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a suitable computing / processing device, or downloaded via a network to an external computer or external storage device. The computer-readable program instructions can be executed entirely on a user's computer, partially on a user's computer, as a standalone software package, partially on a user's computer and partially on a remote computer, or entirely on a remote computer or server. Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.
[0021] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks of a flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium that can instruct a computer, programmable data processing apparatus, and / or other device to operate in a particular manner, such that the computer-readable storage medium in which the instructions are stored includes an article of writing comprising instructions for implementing aspects of the functions / actions specified in one or more blocks of a flowchart and / or block diagram.
[0022] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the instructions, which execute on the computer, other programmable apparatus or other device, implement the functions / actions specified in one or more boxes of a flowchart and / or block diagram.
[0023] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a portion of a module, segment, or instruction, which includes one or more executable instructions for implementing one or more specified logical functions. In some alternative implementations, the functions marked in the blocks may not appear in the order indicated in the figures. For example, depending on the functions involved, two consecutively shown blocks may actually be executed substantially simultaneously, or sometimes these blocks may be executed in reverse order. It should also be noted that each block in the block diagrams and / or flowcharts, as well as combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified function or action or executes a combination of dedicated hardware and computer instructions.
[0024] Finally, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to also include the plural forms. It will be further understood that the terms “comprising” and / or “including” as used in this specification specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0025] All means or steps in the appended claims, plus corresponding structures, materials, actions, and equivalents of the functional elements, are intended to include any structure, material, or action for performing a function in combination with other claimed elements as specifically claimed. The description of this disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limiting to the disclosure in its form. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of this disclosure. Embodiments have been chosen and described in order to best explain the principles and practical application of this disclosure, and to enable others skilled in the art to understand the disclosure of various embodiments with various modifications suitable for the particular intended use.
[0026] Having described the disclosure of this application in such detail and by referring to its embodiments, it will be apparent that modifications and variations may be made without departing from the scope of this disclosure as defined by the appended claims.
Claims
1. A workflow style management method, comprising: Create a document in the memory of a host computing system comprising one or more computers, each computer having memory and at least one processor; Specify a document style for the document selected from a group consisting of linear workflow styles and branch workflow styles. The linear workflow style allows for linear sequential version control of the document as a whole, while the branch workflow style allows for individual and independent version control of each of the multiple components of the document, as well as composing the multiple components to produce a version of the document. The document, along with the specified document style, is saved to the fixed storage of the host computing system; as well as In response to a subsequent request to load the document into a memory of one of the computers, the document is retrieved using a document editor or component editor based on the specified document style by: In response to the specified document style of the document specifying the linear workflow style, the specified version of the entire document is retrieved into the document editor for editing as a new version of the document; and The branch workflow style is specified in response to the specified document style of the document: Retrieve a component from the plurality of components of the document; as well as The component is loaded into the component editor for editing as a new component version, the component being less than the entire document, and the document editor being different from the component editor.
2. The method according to claim 1, further comprising: After the components of the document have been edited, the recombination of the document, which has already been assigned the branch workflow style, is postponed. Instead, the edited components are saved in the fixed storage in a pre-commit state.
3. The method according to claim 1, further comprising: Editing of a document that has been assigned the linear workflow style is permitted only if the end user requesting access to the document for editing has access to the location in the fixed storage where the document is stored.
4. The method according to claim 1, further comprising: Editing of a component of a document that has been assigned the branch workflow style is permitted only if the end user requesting access to the document for editing has access to the component, regardless of any other access permissions the end user has to other components of the document that differ from the access permissions to the component.
5. A document management data processing system suitable for workflow style governance, the system comprising: A host computing platform, the host computing platform comprising one or more computers, each computer having memory and at least one processor; A document repository for storing documents; A document management computer program, which executes in the memory of the host computing platform and is configured to retain the documents stored in the document repository and retrieve the documents from the document repository; as well as A workflow style governance module, coupled to the document management computer program, and including computer program instructions enabled during execution on the host computing platform to perform: The document management computer program specifies a document style for a document, which is selected from a group of linear workflow styles and branch workflow styles. The linear workflow style allows for linear sequential version control of the entire document, while the branch workflow style allows for individual and independent version control of each of the multiple components of the document, as well as the combination of the multiple components to produce a version of the document. Save the document along with the specified document style to the document repository; as well as In response to a subsequent request to load the document, the document is retrieved from the document repository using a document editor or component editor based on the specified document style as follows: In response to the specified document style of the document specifying the linear workflow style, the document management computer program retrieves a specified version of the entire document and provides the specified version of the entire document to the document editor for editing as a new version of the document; and The branch workflow style is specified in response to the specified document style of the document: Retrieve each of the plurality of components of the document; and The component is provided to the component editor for editing as a new component version of the component, the component being less than the entire document, and the document editor being different from the component editor.
6. The system according to claim 5, wherein, The program instructions also include: postponing the recombination of the document, which has already been assigned the branch workflow style, after components of the document have been edited, and instead saving the edited components in a pre-commit state in the document repository.
7. The system according to claim 5, wherein, The program instructions further include: allowing editing of a document that has been assigned the linear workflow style only if the end user requesting access to the document for editing has access rights to the location in the document repository where the document is stored.
8. The system according to claim 5, wherein, The program instructions further include: allowing editing of a component of a document that has been assigned the branch workflow style only when the end user requesting access to the document for editing has access to the component, regardless of other access permissions the end user has to other components of the document that are different from the access permissions to the component.
9. A non-volatile computer-readable storage medium storing program instructions, said program instructions causing the device to perform a method when executed by a device, said method comprising: Create a document in the memory of a host computing system comprising one or more computers, each computer having memory and at least one processor; Specify a document style for the document selected from a group consisting of linear workflow styles and branch workflow styles. The linear workflow style allows for linear sequential version control of the document as a whole, while the branch workflow style allows for individual and independent version control of each of the multiple components of the document, as well as composing the multiple components to produce a version of the document. The document, along with the specified document style, is saved to the fixed storage of the host computing system; as well as In response to a subsequent request to load the document into a memory of one of the computers, the document is retrieved using a document editor or component editor based on the specified document style by: In response to the specified document style of the document specifying the linear workflow style, the specified version of the entire document is retrieved into the document editor for editing as a new version of the document; and The branch workflow style is specified in response to the specified document style of the document: Retrieve a component from the plurality of components of the document; as well as The component is loaded into the component editor for editing as a new component version, the component being less than the entire document, and the document editor being different from the component editor.
10. The non-volatile computer-readable storage medium according to claim 9, wherein, The method further includes: postponing the recombination of the document, which has already been assigned the branch workflow style, after the components of the document have been edited, and instead saving the edited components in the fixed storage in a pre-commit state.
11. The non-volatile computer-readable storage medium according to claim 9, wherein, The method further includes allowing editing of a document that has been assigned the linear workflow style only if the end user requesting access to the document for editing has access rights to a location in the fixed storage where the document is stored.
12. The non-volatile computer-readable storage medium according to any one of claims 9 to 11, wherein, The method further includes allowing editing of the component of the document, which has been assigned the branch workflow style, only when the end user requesting access to the document for editing has access to the component, regardless of other access permissions the end user has to other components of the document that are different from the access permissions to the component.