Method, medium, program product and system for implementing workflow using finite state machine

By integrating a finite state machine into the data processing system, directly accessing data objects and metadata, and dynamically identifying authorized actors, the system solves the synchronization difficulties and frequent errors caused by the separation of traditional workflow management systems and data processing systems, thus achieving efficient and accurate workflow management.

CN113454662BActive Publication Date: 2024-11-26AB INITIO TECHNOLOGY LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080010482.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-01-22
Filing Date
2020-01-22
Publication Date
2024-11-26
Estimated Expiration
2040-01-22

AI Technical Summary

Technical Problem

The existing workflow management system is separated from the data processing system, which leads to difficulties in synchronization, frequent errors, complex deployment and high costs, and cannot effectively manage the workflow of data objects.

Method used

By integrating a finite state machine (FSM) with the data processing system, it can directly access data objects and metadata, dynamically identify authorized actors, and generate a graphical user interface to execute workflow tasks.

Benefits of technology

It improves the efficiency and accuracy of workflow management in the data processing system, simplifies the configuration process, reduces errors, and enhances the system's reliability and synchronization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113454662B_ABST
    Figure CN113454662B_ABST
Patent Text Reader

Abstract

The present invention provides a method, medium, program product and system for implementing a workflow using a finite state machine (FSM) in a data processing system, the data processing system including at least one data storage device storing data objects, and a workflow management system (WMS). The WMS is configured to perform the following operations: determine the current value of an attribute of a first data object by accessing the current value in the at least one data storage device; use the current value and metadata specifying the relationship between at least some of the data objects to identify an actor authorized to perform a workflow task for the first data object; generate a GUI through which the actor can provide input to perform the workflow task; and in response to receiving input from the actor and through the GUI specifying that the workflow task is to be performed: perform the workflow task; and update the current workflow state of the first FSM to a second workflow state.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 62 / 795,443, filed on January 22, 2019, entitled “FINITESTATE MACHINES FOR IMPLEMENTING WORKFLOWS FOR DATA OBJECTS MANAGED BY A DATAPROCESSING SYSTEM,” the entire contents of which are incorporated herein by reference. Background Art

[0003] A finite state machine (FSM) is a computational model that can be implemented in hardware or software. As the name implies, a finite state machine includes a finite set of states, and the finite state machine can be in exactly one of these states at any given time. A finite state machine also includes one or more transitions between states in the set of states. A finite state machine can be switched from one state to another in a variety of ways and, for example, in response to satisfying a condition and / or in response to an external input. A finite state machine can be represented in a memory using one or more data structures that store data specifying a list of states, transitions between states, and / or an indication of the current state. Finite state machines are used in many different fields, including reactive system modeling, hardware digital system design, applied behavior modeling, software engineering, network protocols, natural language processing, and compilers. Summary of the invention

[0004] Some embodiments relate to a method for managing a workflow in a data processing system, the data processing system comprising: (i) at least one data storage device, the at least one data storage device storing: a plurality of data objects and their attribute values, the plurality of data objects including a first data object, the first data object having a plurality of attributes, the plurality of attributes including a first attribute that can have any one of a plurality of values; and metadata specifying relationships between at least some of the plurality of data objects; and (ii) a workflow management system, the workflow management system comprising: a workflow execution engine for managing the execution of finite state machines (FSMs), the finite state machines including a first FSM associated with the first data object and for managing a first workflow of the first data object. The method includes: when the current workflow state of the first FSM is the first workflow state, using the workflow management system to perform the following operations: determine the current value of the first attribute of the first data object by accessing the current value of the first attribute in the at least one data storage device; use the current value of the first attribute and metadata specifying the relationship between at least some of the multiple data objects to identify a first actor who is authorized to perform a first workflow task for the first data object; generate a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and in response to receiving input specifying that the first workflow task is to be performed from the first actor and through the GUI: perform the first workflow task for the first data object; and update the current workflow state of the first FSM to a second workflow state.

[0005] Some embodiments relate to at least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by a data processing system, cause the data processing system to perform a method for managing a workflow in the data processing system, the data processing system comprising: (i) at least one data storage device storing: a plurality of data objects and attribute values ​​thereof, the plurality of data objects including a first data object having a plurality of attributes including a first attribute that can have any one of a plurality of values; and metadata specifying relationships between at least some of the plurality of data objects; and (ii) a workflow management system comprising: a workflow execution engine for managing the execution of finite state machines (FSMs), the finite state machines including a first state machine associated with the first data object and for managing the first data object A first FSM for a workflow, the method comprising: when the current workflow state of the first FSM is the first workflow state, using the workflow management system to perform the following operations: determine the current value of the first attribute of the first data object by accessing the current value of the first attribute in the at least one data storage device; use the current value of the first attribute and metadata specifying the relationship between at least some of the multiple data objects to identify a first actor who is authorized to perform a first workflow task for the first data object; generate a graphical user interface (GUI), through which the first actor can provide input to perform the first workflow task; and in response to receiving input specifying that the first workflow task is to be performed from the first actor and through the GUI: perform the first workflow task for the first data object; and update the current workflow state of the first FSM to a second workflow state.

[0006] Some embodiments relate to a data processing system comprising: at least one computer hardware processor; at least one data storage device storing: a plurality of data objects and attribute values ​​thereof, the plurality of data objects comprising a first data object having a plurality of attributes, the plurality of attributes comprising a first attribute that can have any one of a plurality of values; and metadata specifying relationships between at least some of the plurality of data objects; and a workflow management system comprising: a workflow execution engine for managing execution of finite state machines (FSMs), the finite state machines comprising a first FSM associated with the first data object and for managing a first workflow of the first data object, wherein the workflow management system is configured to execute using the at least one computer hardware processor A method, the method comprising: when the current workflow state of the first FSM is the first workflow state: determining the current value of the first attribute of the first data object by accessing the current value of the first attribute in the at least one data storage device; identifying a first actor who is authorized to perform a first workflow task for the first data object using the current value of the first attribute and metadata specifying the relationship between at least some of the multiple data objects; generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and in response to receiving input specifying that the first workflow task is to be performed from the first actor and through the GUI: performing the first workflow task for the first data object; and updating the current workflow state of the first FSM to a second workflow state.

[0007] Some embodiments relate to a system for managing a workflow of a first data object among multiple data objects using a first finite state machine (FSM), the first FSM having a first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first state and the second state, the first transition representing a first workflow task in the first workflow. The system includes: at least one computer hardware processor; and at least one non-transitory computer-readable storage medium storing processor-executable instructions, which, when executed by the at least one computer hardware processor, cause the at least one computer hardware processor to perform the following operations: identify a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object; and when the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receive input from the first actor specifying that the first workflow task is to be performed; perform the first workflow task for the first data object; and update the first FSM to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

[0008] Some embodiments relate to a method for managing a workflow of a first data object of a plurality of data objects using a first finite state machine (FSM), the first FSM having a first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first state and the second state, the first transition representing a first workflow task in the first workflow. The method includes performing the following operations using at least one computer hardware processor: identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object; and when the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input from the first actor specifying that the first workflow task is to be performed; performing the first workflow task for the first data object; and updating the first FSM to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

[0009] Some embodiments relate to at least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by at least one computer hardware processor, cause the at least one computer hardware processor to perform a method for managing a workflow of a first data object among a plurality of data objects using a first finite state machine (FSM), the first FSM having a first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first state and the second state, the first transition representing a first workflow task in the first workflow. The method includes: identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object; and when the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input from the first actor specifying that the first workflow task is to be performed; performing the first workflow task for the first data object; and updating the first FSM to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

[0010] Some embodiments provide a method for managing a workflow of multiple data objects including a first data object, the method comprising performing the following operations using at least one computer hardware processor: generating a first finite state machine (FSM) for managing a first workflow of a first group of data objects using a first specification of the FSM, the first specification indicating: a first group of workflow states including a first workflow state and a second workflow state; and a first group of transitions between the first group of workflow states, the first group of transitions representing tasks in the first workflow and including a first transition between the first state and the second state, the first transition representing a first task in the first workflow; and when the first FSM indicates that the current workflow state of the first workflow of the first group of data objects is the first workflow state, receiving input specifying that the first workflow task is to be performed from a first actor authorized to perform a first workflow task corresponding to the first transition between the first workflow and the second workflow state; performing the first workflow task for the first data object; and updating the first FSM to indicate that the current workflow state of the first workflow of the first group of data objects is the second workflow state.

[0011] Some embodiments provide at least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by the at least one computer hardware processor, cause the at least one computer hardware processor to perform the following operations: generate a first finite state machine (FSM) for a first workflow of a first data object among a plurality of data objects; use at least one value of at least one attribute of the first data object to identify a first actor authorized to perform a first workflow task associated with a first transition from the first workflow state to a second workflow state; when the first FSM indicates that a current workflow state of the first workflow is the first workflow state: generate a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and present the GUI to the first actor.

[0012] Some embodiments provide a method comprising performing the following operations using at least one computer hardware processor: generating a first finite state machine (FSM) for a first workflow of a first data object among a plurality of data objects; using at least one value of at least one attribute of the first data object to identify a first actor who is authorized to perform a first workflow task associated with a first transition from the first workflow state to a second workflow state; when the first FSM indicates that a current workflow state of the first workflow is the first workflow state: generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and presenting the GUI to the first actor.

[0013] Some embodiments provide a system comprising: at least one computer hardware processor; and at least one non-transitory computer-readable storage medium storing processor-executable instructions, which, when executed by the at least one computer hardware processor, cause the at least one computer hardware processor to perform the following operations: generate a first finite state machine (FSM) for a first workflow of a first data object among a plurality of data objects; use at least one value of at least one attribute of the first data object to identify a first actor authorized to perform a first workflow task associated with a first transition from the first workflow state to a second workflow state; when the first FSM indicates that a current workflow state of the first workflow is the first workflow state: generate a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and present the GUI to the first actor.

[0014] Some embodiments provide at least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by at least one computer hardware processor, cause the at least one computer hardware processor to perform the following operations: generate a first FSM for managing a first workflow, the first workflow for changing a value of an attribute of a first data object in a plurality of data objects, the generating being performed using a specification indicating a first set of workflow states, the first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing a first workflow state in the first workflow. task and includes a first transition between the first state and the second state, the first transition representing the first task in the first workflow; and when the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input specifying that the first workflow task is to be executed from a first actor who is authorized to execute the first workflow task corresponding to the first transition between the first workflow and the second workflow state; executing the first workflow task for the first data object; and updating the first FSM to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

[0015] Some embodiments provide a system comprising: at least one computer hardware processor; and at least one non-transitory computer-readable storage medium storing processor-executable instructions, which, when executed by the at least one computer hardware processor, cause the at least one computer hardware processor to perform the following operations: generate a first FSM for managing a first workflow, the first workflow for changing a value of an attribute of a first data object in a plurality of data objects, the generating being performed using a specification indicating a first set of workflow states, the first set of workflow states comprising a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the ... A set of transitions represents tasks in the first workflow and includes a first transition between the first state and the second state, the first transition representing a first task in the first workflow; and when the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input specifying that the first workflow task is to be executed from a first actor authorized to execute the first workflow task corresponding to the first transition between the first workflow and the second workflow state; executing the first workflow task for the first data object; and updating the first FSM to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

[0016] Some embodiments provide a method that includes performing the following operations using at least one computer hardware processor: generating a first FSM for managing a first workflow, the first workflow being used to change a value of an attribute of a first data object among a plurality of data objects, the generating being performed using a specification indicating a first set of workflow states, the first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first state and the second state, the first transition representing a first task in the first workflow; and when the first FSM indicates that a current workflow state of the first workflow of the first data object is the first workflow state, receiving input specifying that the first workflow task is to be performed from a first actor authorized to perform a first workflow task corresponding to the first transition between the first workflow and the second workflow state; performing the first workflow task for the first data object; and updating the first FSM to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

[0017] The foregoing is a non-limiting summary of the present invention, which is defined by the appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Various aspects and embodiments will be described with reference to the following drawings. It should be understood that the drawings are not necessarily drawn to scale. Items appearing in multiple drawings are indicated by the same or similar reference numerals in all drawings in which they appear.

[0019] Figure 1A It is a block diagram of a traditional workflow management system.

[0020] Figure 1B is a block diagram of an illustrative data processing system 120 and a workflow management system 130 integrated with the data processing system 120 in accordance with some embodiments of the techniques described herein.

[0021] Figure 1C According to some embodiments of the technology described herein Figure 1B A block diagram of an illustrative embodiment of data processing system 120 is shown.

[0022] Figure 1D to Figure 1E An example is shown of using information about a data object hierarchy to which a data object belongs to identify an actor authorized to perform a workflow task for the data object according to some embodiments of the technology described herein.

[0023] Figure 1F to Figure 1GAn example is shown of using information about a data object hierarchy to which a data object belongs to identify an actor authorized to perform a workflow task for the data object according to some embodiments of the technology described herein.

[0024] Figures 1H to 1I An example is presented of using information about a data object group to which a data object belongs to identify an actor authorized to perform a workflow task for the data object according to some embodiments of the technology described herein.

[0025] Figure 2 is a flow chart of an illustrative process 200 for managing a workflow of data objects using a finite state machine in accordance with some embodiments of the techniques described herein.

[0026] Figure 3A is a diagram of states and transitions of an illustrative finite state machine 300 showing a workflow for managing changes to data objects in accordance with some embodiments of the techniques described herein.

[0027] Figure 3B is a diagram showing states and transitions of an illustrative finite state machine 350 for an issue management workflow in accordance with some embodiments of the techniques described herein.

[0028] Figure 3C is a diagram of an illustrative graphical user interface (GUI) 380 through which an actor may view and / or perform one or more workflow tasks, according to some embodiments of the techniques described herein.

[0029] Figure 3D is an illustration of another GUI 390 through which an actor may view and / or perform one or more workflow tasks for a data object, according to some embodiments of the techniques described herein.

[0030] Figure 4A is a diagram of an illustrative finite state machine 400 for creating and managing business terminology data objects in accordance with some embodiments of the techniques described herein.

[0031] Figures 4B to 4D is a demonstration of some embodiments of the technology described herein Figure 4A A diagram of a portion of a finite state machine 400 is shown.

[0032] Figure 5A is a diagram of an illustrative finite state machine 500 for managing changes to business term data objects, in which one of the states of FSM 500 is associated with an auxiliary finite state machine, in accordance with some embodiments of the techniques described herein.

[0033] Figure 5Bis a diagram of an illustrative GUI 510 showing the state of a primary FSM for managing changes to a business glossary data object and the state of a secondary FSM for managing changes to attributes of the business glossary data object in accordance with some embodiments of the techniques described herein.

[0034] Figure 5C An auxiliary FSM 550 for making changes to a business term data object is shown in accordance with some embodiments of the techniques described herein.

[0035] Fig. 6A A finite state machine 600 is shown for importing additions, modifications and / or deletions of multiple data objects in accordance with some embodiments of the techniques described herein.

[0036] Figure 6B A finite state machine 650 is shown for conditionally importing additions, modifications, and / or deletions of multiple data objects in accordance with some embodiments of the techniques described herein.

[0037] Fig. 7A is a diagram 700 showing identification of one or more workflow actors for a data object using information specified for at least one other data object in at least one data object hierarchy containing the data object, according to some embodiments of the techniques described herein.

[0038] Figure 7B is a diagram 705 illustrating identifying one or more workflow actors for a data object based on the value of a classification attribute of the data object according to some embodiments of the techniques described herein.

[0039] Figure 7C is another diagram 710 illustrating identifying one or more workflow actors for a data object based on a value of a classification attribute of the data object in accordance with some embodiments of the techniques described herein.

[0040] Fig.7D is a diagram 715 showing identification of a workflow actor for a data object using information specified for other data objects in a plurality of data object hierarchies containing the data object, according to some embodiments of the techniques described herein.

[0041] Fig. 7E is a diagram 720 showing a "single" decision-making configuration for a pending change, in which only a single party needs to approve the pending change, according to some embodiments of the techniques described herein.

[0042] Figure 7F is a diagram 725 showing a "majority" decision-making configuration for a pending change, where a majority of identified workflow actors are required to approve the pending change, according to some embodiments of the techniques described herein.

[0043] Figure 7G is a diagram 730 showing a "consistent" decision-making configuration for a pending change, where all identified workflow actors are required to approve the pending change, according to some embodiments of the techniques described herein.

[0044] Figures 7H to 7M Decision-making configurations for pending changes to data objects belonging to multiple object hierarchies are presented according to some embodiments of the techniques described herein, where each of the configurations is specified relative to each of the multiple object hierarchies.

[0045] Fig. 8A is a diagram of a GUI 800 showing multiple business term data objects according to some embodiments of the techniques described herein.

[0046] Figure 8B is a diagram of a GUI 810 showing information of a business term data object, including values ​​of data object attributes and related parties, according to some embodiments of the techniques described herein.

[0047] Figure 8C is a view of a GUI 820 showing information of a business term data object including a current workflow state of a finite state machine of the business term data object according to some embodiments of the techniques described herein.

[0048] Fig.8D is a view of a GUI 825 showing how a change by an actor to the value of a first property of a data object causes, according to some embodiments of the techniques described herein,: (1) a change to the current state of a finite state machine for managing a workflow for a business term data object; and (2) the instantiation of a secondary finite state machine for managing an approval process for changes to the value of the first property.

[0049] Fig. 8E is a view of a GUI 830 illustrating how a change by an actor to the value of a second property of a data object triggers an instantiation of another auxiliary finite state machine for managing an approval process for changes to the property value in accordance with some embodiments of the techniques described herein.

[0050] Figure 8F is a view of a GUI 835 showing an actor's view after the actor has submitted a change to the value of a property of a data object, according to some embodiments of the techniques described herein.

[0051] Figure 8G is a view of a GUI 837 showing a list of reviewers for approving submitted changes to the value of a data object property in accordance with some embodiments of the techniques described herein.

[0052] Figure 8H is a view of a GUI 840 showing a reviewer logging in, checking his work queue, and approving changes submitted by an actor, according to some embodiments of the techniques described herein.

[0053] Figure 8I is a view of a GUI 845 showing another reviewer logging in, checking his work queue, and approving changes submitted by the actor, according to some embodiments of the techniques described herein.

[0054] Figure 8J Shown is a diagram of a GUI 850 through which a reviewer may access his or her work queue, according to some embodiments of the techniques described herein.

[0055] Figure 8K Shown is a view of a GUI 855 through which an actor can see whether her changes have been approved, according to some embodiments of the techniques described herein.

[0056] Figure 8L is a view of a GUI 860 showing another reviewer logging in, checking his work queue, and approving changes submitted by the actor, according to some embodiments of the techniques described herein.

[0057] Figure 8M is a view of a GUI 865 showing that a change to one property value of a data object has been approved, but approval of a change to another property value of the data object is still pending, according to some embodiments of the techniques described herein.

[0058] Figure 8N is a view of GUI 870 showing that the current state of the finite state machine of a data object has been updated to a “Published” state according to some embodiments of the techniques described herein.

[0059] Fig. 9A is a diagram of a GUI 910 showing a list of finite state machine specifications according to some embodiments of the techniques described herein.

[0060] Fig. 9B is an illustration of some embodiments of the technology described herein for managing FIG. 8A to FIG. 8N 920 is a view of a master finite state machine GUI showing changes to an example data object.

[0061] Fig. 9C is an illustration of some embodiments of the technology described herein Fig. 9B A view of GUI 930 of a state table for a main state machine and a state transition for one of the states is shown.

[0062] Fig.9D is an illustration of some embodiments of the technology described herein Fig. 9B A view of GUI 940 of a state table of a main state machine and state transitions from one state to another is shown.

[0063] Fig.10 is an illustration of some embodiments of the technology described herein for managing FIG. 8A to FIG. 8N 1000 is a view of a GUI 1000 assisting in the modification of properties of a data object in an example and an associated state table.

[0064] Fig.11 is a block diagram of an illustrative computing system environment that can be used to implement some embodiments of the techniques described herein. DETAILED DESCRIPTION

[0065] Various aspects of the technology described herein relate to improving the speed, throughput and accuracy of a data processing system by improving conventional techniques for implementing workflows of data objects managed by the data processing system. A data processing system may manage thousands, millions or billions of data objects. The technology described herein can efficiently implement workflows of such data objects in a manner that reduces errors that occur in data processing systems that use conventional workflow implementation techniques to implement workflows and the computing resources used by these data processing systems. The technology developed by the inventor provides data processing system users with precise and concise control over who can edit data, who can access data and when to access data, who can see pending changes, who can approve the dissemination of data to a wider audience, who gets notified of changes (e.g., people and systems), and who can advance the workflow state of data objects.

[0066] In some embodiments, a workflow for a data object may include a set of workflow tasks associated with the data object, each of which is performed by a data processing system automatically or in response to input provided by one or more actors. For example, a workflow for a data object may be a workflow for changing the value of a property of the data object. Tasks in such a workflow may include making a proposed change to a property value, submitting the proposed change for review, reviewing the proposed change, and approving or rejecting the proposed change. Examples of such workflows are provided herein, including references to Figure 3A and FIG. 4A to FIG. 4D As another example, a workflow for a data object may be a workflow for resolving a problem (e.g., a data error) represented by the data object. Tasks in such a workflow may include editing a data object representing a problem, submitting the problem, indicating that the problem has been resolved, and verifying that the problem has been resolved. Illustrative examples of such workflows are provided herein, including references to Figure 3B .

[0067] In some embodiments, one or more workflow tasks in a workflow may be performed by one or more actors. An actor may perform one or more actions to advance the execution (e.g., start execution, begin and complete execution) of a workflow task in a workflow. For example, one actor may perform a workflow task of editing a data object and submitting the changes for review, while another one or more actors may review the changes and determine whether to approve or reject the changes. An actor may be a user of a data processing system that is authorized to perform one or more actions on one or more data objects managed by the data processing system.

[0068] The inventors recognize that the traditional methods for implementing workflows in data processing systems can be improved. For example, one traditional method for specifying a workflow is to use a graphical representation called Business Process Model and Notation (BPMN). However, the workflow specified in BPMN is just a specification - BPMN does not include executable code that a data processing system can use to execute the BPMN workflow. Further, BPMN does not provide any ability to control the visibility or editability of data objects stored in a relational database. Although there are software tools for implementing BPMN workflows (e.g., CAMUNDA BPMN), such software tools require writing low-level code for implementing BPMN workflows, which is time-consuming, error-prone, and ultimately impractical, especially when multiple workflows need to be specified for a large number of data objects managed by a data processing system.

[0069] In addition, traditional software tools for implementing workflows do not provide a way to customize which actors are authorized to perform which workflow tasks at the data object level. Instead, traditional approaches involve identifying actors at the workflow task level. For example, unlike the techniques described herein, BPMN does not provide a mechanism to identify and change actors based on data object attributes and / or relationships.

[0070] The inventors have also recognized that, although conventional workflow management systems are sometimes used to manage workflows of data objects in data processing systems, such conventional workflow management systems are not integrated with the data processing systems. As described below, such deployments have many disadvantages, including lack of synchronization and complexity of implementation and maintenance. In addition, such deployments generally do not provide the rich workflows or information that can be presented to business users that integrated approaches can provide.

[0071] exist Figure 1AAn illustrative scenario that may be contemplated is illustrated in a potential computing environment 100 of FIG. 1 , which shows a conventional workflow management system 102 communicatively coupled to a data processing system 104 via a network 106 (e.g., the Internet). The data processing system 104 includes: a data storage device 106 storing a plurality of data objects; and business rules 108 that specify information for implementing any workflow of the data objects in the data storage device 106. For example, the business rules 108 may specify actor permissions by specifying which actors (e.g., actors from actors 115) have create, read, update, and / or delete permissions to various data objects in the data storage device 106 and which actors are authorized to review updates to data objects by other actors. The business rules 108 are typically specified by a business user (e.g., business user 107).

[0072] The workflow management system 102 includes workflow rules 103 that specify how workflows involving data objects are to be implemented by the external workflow management system 102. For example, the workflow rules 103 may specify a sequence of tasks in a workflow and which actor(s) of the workflow actors 115 are authorized to perform these tasks. The workflow rules 103 are implemented by one or more software developers (such as developer 105) using low-level software code (e.g., using Camunda BPMN).

[0073] Since conventional workflow management systems 102 are not integrated with data processing systems 104, these two separate systems need to be synchronized. One conceivable synchronization method is a "data pull" method, in which WMS 102 repeatedly polls data processing system 104 via data pull requests 109a to obtain updates to its data. Another conceivable synchronization method is a "data push" method, in which data processing system 104 pushes data updates 109b to WMS 102. However, both of these conceivable methods have significant disadvantages and not only fail to provide an acceptable level of synchronization, but can also lead to workflow errors.

[0074] For example, in a data pull approach, there is latency in receiving data updates because the data processing system may manage a large number of data objects (e.g., thousands / millions) whose values ​​need to be updated and time is required to collect and transmit such updates over the network to the WMS 102. Furthermore, if the workflow rules 103 depend on the values ​​of data objects, any delay in updating these values ​​means that the WMS 102 is not implementing the workflow correctly (e.g., by allowing an actor to perform a workflow task that she is not authorized to perform), which is unacceptable in many applications (e.g., data governance).

[0075] On the other hand, in the data push approach, the data processing system 104 will not know what information the workflow rules 103 use to implement the workflow, and will not know what data to provide to the WMS 102, or when to provide this data (and it is impractical to provide all possible data changes, as this would mean sending a copy of each update). Since the workflow rules 103 are managed by the workflow management system 102, the data processing system 104 cannot access the workflow rules 103, does not have any ability or mechanism to reason about the workflow rules 103, and cannot be used to drive push updates. For example, if one of the data objects in the data storage device 106 is updated, the data processing system 104 cannot know whether the change to the data object may trigger a specific workflow rule 103 (or affect how it is executed), and therefore, the data processing system cannot decide whether to "push" notification of the change to the workflow management system 102. Therefore, the WMS 102 may not receive the information it needs to accurately implement the workflow from the data processing system 104, or may be overwhelmed by all possible data changes, most of which may be irrelevant to workflow management.

[0076] In addition to the lack of synchronization, Figure 1A Another disadvantage of the conceivable system shown in is the amount of time and effort required to deploy, maintain and update such a system. For example, if the business rules 108 change, the workflow rules 103 may need to be updated, which will require the time of the software developer 107. As another example, if the workflow rules 103 change, the data processing system 104 will need to be updated (may require the participation of one or more software developers) to ensure that the data processing system 104 pushes any data required by the WMS 102 to implement the workflow now to the WMS 102 (as a result of the workflow rules 103 update). This is not only costly, but also introduces unacceptable time delays, especially when the time between changes to the workflow rules 103 and / or business rules 108 is much shorter than the time it takes to write, test and deploy code to implement such changes. Any inconsistency in the workflow logic in the WMS 102 and the data "push" logic in the data processing system 104 will immediately lead to incorrect workflow management. This system vulnerability is obviously unacceptable in practice.

[0077] In order to address the above shortcomings of conventional techniques for implementing workflows, the inventors have developed a novel approach for a workflow management system for formally managing rich workflows of data objects stored in a data processing system. Unlike conventional approaches where a workflow management system is separated from a data processing system (e.g., as described above with reference to Figure 1AThe workflow management system developed by the inventors is integrated with a data processing system, which avoids many of the disadvantages of the above-mentioned traditional methods. The workflow management system developed by the inventors can directly access not only the data objects managed by the data processing system (which avoids the synchronization and waiting time problems mentioned above), but also the metadata specifying the relationships between the data objects, which metadata can be used to efficiently identify the authorized actors of the data objects using inheritance and / or group membership relationships, as described herein.

[0078] The workflow management system developed by the inventor uses a finite state machine to implement the workflow of data objects managed by a data processing system. In some embodiments, the workflow of a data object can be represented by a finite state machine, the state of the finite state machine corresponds to the workflow state of the data object in the workflow, and the transition of the finite state machine corresponds to the workflow task. In some embodiments, in order to implement the workflow of a specific data object, an instance of a finite state machine can be created for the data object. As the workflow tasks are executed, the state of the FSM instance is updated to indicate the current state of the data object. After the workflow of the data object is completed, the instance of the FSM used to manage the workflow can be deleted and / or a workflow for subsequent modification can be initiated (for example, a workflow for creating and publishing a document can be completed by initiating a new workflow to give one or more actors permission to revise the published document).

[0079] The inventors have recognized that the use of finite state machines to implement workflows at the data object level eliminates the need for actors to write low-level code, as is the case with other traditional workflow implementation techniques. Instead, actors only need to configure the finite state machine by specifying its states, transitions, and related parameters, as described herein. Although the finite state machine approach is more constrained than an approach in which actors can write any suitable program code to implement a workflow (notably, an FSM is in one state at any given time, while BPMN and related solutions allow a workflow to be in multiple states simultaneously), the structure and constraints imposed by the FSM approach reduce the amount of time required to specify a new workflow and the number of errors therein, which in turn improves the accuracy and reliability of the data processing system that manages the execution of data objects and workflows of data objects.

[0080] The techniques described herein and developed by the inventors provide a variety of other benefits relative to traditional workflow modeling approaches such as BPMN. For example, the techniques described herein provide concise configurations / controls to express the editability, visibility, notifications, and lifecycle of data objects. As another example, the techniques described herein provide mechanisms for identifying and changing actors based on data object attributes and / or relationships between multiple data objects (including, for example, direct relationships, associative relationships, and / or recursive relationships). As another example, BPMN does not employ any kind of user interface (or even a single application), and the techniques described herein improve BPMN by allowing workflows to express what should happen in the user interface presented to the workflow actors. These improvements make the implementation of workflows more concise, less error-prone, faster to market, and more efficient than BPMN.

[0081] In some embodiments, a data processing system can use the state of an FSM instance for managing a workflow for a data object to enable one or more actors of the data processing system to perform a workflow task on the data object. For example, the data processing system can use the state of the FSM to determine which action(s) can be performed with respect to the data object (e.g., based on a transition from a current workflow state) and allow one or more actors to perform such action(s). For example, the data processing system can notify an actor that he or she can perform a workflow action and / or present an interface (e.g., a graphical user interface) to the actor through which the actor can provide input indicating that the workflow action is to be performed.

[0082] In some embodiments, a data processing system may use multiple finite state machines to manage a workflow for a single data object. For example, when the workflow involves making multiple different changes to the data object, a dedicated finite state machine may be instantiated to manage the approval process for each respective change. Using multiple finite state machines to manage different changes to a single data object allows the workflow for making such changes and the workflow for approving such changes to proceed in parallel and independently of each other. This parallelization further increases the efficiency of the data processing system. This is described in more detail herein, including with reference to FIG. 5A to FIG. 5C In addition, such parallelization makes it easier for an administrator or other actor interacting with the data processing system to make / process multiple changes in parallel, since each change can be managed by a corresponding finite state machine. Thus, one or more parallel workflows can be instantiated for one or more corresponding attributes of a data object. The state of the (multiple) parallel workflows may affect the main workflow (e.g., the state of the main workflow may change in response to a parallel workflow completing after all attribute changes have been completed).

[0083] The inventors have further recognized that using a finite state machine to manage workflows at a per-data object level allows a data processing system to identify actors authorized to perform various workflow tasks at a per-data object level. Thus, in some embodiments, a data processing system may identify actors authorized to perform workflow tasks on a data object based on information associated with the data object. For example, in some embodiments, a data processing system may identify one or more actors authorized to perform workflow tasks on a data object based on one or more values ​​of one or more attributes of the data object.

[0084] In some embodiments, one or more finite state machines can be used to manage one or more workflows associated with one or more life cycle phases of a particular data object. For example, the life cycle of a data object can involve phases such as creating the data object, revising the data object, publishing the data object, approving the data object, approving changes to the data object, and collaborating on changes to the data object. According to some embodiments of the technology described herein, each of the life cycle phases can be associated with a workflow managed by using a finite state machine.

[0085] Some embodiments described herein address all of the above-discussed problems that the inventors have recognized with conventional techniques for implementing workflows of data objects managed by a data processing system. However, not every embodiment described herein addresses every one of these problems, and some embodiments may not address any of them. Therefore, it should be understood that embodiments of the technology described herein are not limited to addressing all or any of the above-discussed problems of conventional techniques for implementing workflows of data objects managed by a data processing system.

[0086] In some embodiments, the data object managed by the data processing system may include data and one or more attributes, each of which may be single-valued or multi-valued. The data in the data object may include content, such as, for example, text, data records, and / or one or more alphanumeric values. As an example, a data object may represent a data record (e.g., a transaction), and the data in the data object may be stored in a field of the data record. As another example, a data object may represent a file. As another example, a data object may represent a document. In this example, the data in the data object may include text in the document. As another example, a data object may represent a business term in an organization's business vocabulary (e.g., "credit risk", "accounting exposure", etc.). In this example, the data in the data object may include text that specifies the definition of the business term. As another example, a data object may represent a problem to be solved (e.g., a data error, a request to reset a password, a problem with a purchase order, an invoice, or other document). In this example, the data in the data object may include text that describes the problem.

[0087] In some embodiments, a data object may have one or more attributes. The values ​​of these attributes may provide information about the data object. For this reason, these attribute values ​​may be considered metadata. As an example, a data object may have attributes indicating its name and / or other identifiers. As another example, a data object may have a definition attribute that specifies the semantic meaning of the data object. As another example, the data object may be part of one or more hierarchies of data objects and may have an attribute indicating one or more hierarchies to which the data object belongs. As another example, a data object may have one or more classification attributes, including (by way of example and not limitation) a governance group classification attribute that may specify a list of one or more governance groups to which the data object belongs, a sensitivity classification attribute that may indicate the sensitivity level of the data in the data object (e.g., "internal", "public", "confidential", "highly confidential"), and a personally identifiable information ("PII") classification attribute that indicates the level of harm (e.g., "level 1", "level 2", etc.) that may result from improper use, access and / or modification of the data in the data object. As another example, a data object may have an attribute that specifies one or more actors that are authorized to perform one or more actions (e.g., create, read, access, update, delete) on the data object. As another example, a data object may have an attribute that indicates valid values ​​(via a range, a list) of another value associated with the data object. These examples of attributes are illustrative and non-limiting, and additional examples of attributes are provided herein.

[0088] Some embodiments provide a method for managing a workflow in a data processing system, the data processing system comprising: (i) at least one data storage device, the at least one data storage device storing: a plurality of data objects and their attribute values, the plurality of data objects including a first data object, the first data object having a plurality of attributes, the plurality of attributes including a first attribute that can have any one of a plurality of values; and metadata specifying relationships between at least some of the plurality of data objects; and (ii) a workflow management system, the workflow management system comprising: a workflow execution engine for managing the execution of finite state machines (FSMs), the finite state machines including a first FSM associated with the first data object and for managing a first workflow of the first data object. The method may include, when a current workflow state of the first FSM is a first workflow state (e.g., Figure 3A ), using a workflow management system to perform the following operations: (A) determining a current value of a first attribute of a first data object by accessing a current value of the first attribute in at least one data storage device (in such a manner that the current value is used rather than a previously cached, possibly stale value); (B) identifying a first actor who is authorized to perform a first workflow task for the first data object using the current value of the first attribute and metadata specifying relationships between at least some of the plurality of data objects; (C) generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and (D) in response to receiving input from the first actor and through the GUI specifying that the first workflow task is to be performed: (1) performing the first workflow task for the first data object (e.g., rejecting the change); and (2) updating the current workflow state of the first FSM to a second workflow state (e.g., changing the current workflow state to Figure 3A "Draft" status 304).

[0089] In some embodiments, the data objects in the plurality of data objects are organized into one or more hierarchies, wherein the metadata specifies the one or more hierarchies, and wherein the current value of the first attribute indicates a first hierarchy of the one or more hierarchies to which the first data object belongs. Thus, in some embodiments, identifying the first actor includes identifying the first actor as an actor authorized to perform the first workflow task for a second data object in the plurality of data objects, wherein the second data object is related to the first data object according to the first hierarchy (e.g., it is an ancestor, descendant, or sibling of the first data object).

[0090] Some embodiments provide a data processing system for managing a workflow of a first data object among a plurality of data objects using a first FSM, the first FSM having a first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first state and the second state, the first transition representing a first workflow task in the first workflow. In some embodiments, the system is programmed to: (1) identify a first actor authorized to perform a first workflow task for the first data object from among a plurality of actors and using a value of an attribute of the first data object; and (2) when the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state (e.g., Figure 3A , (a) receiving input from a first actor specifying that a first workflow task is to be performed (e.g., receiving input from a reviewer rejecting a change); (b) performing the first workflow task for the first data object (e.g., rejecting the change); and (c) updating the first FSM to indicate that the current workflow state of the first workflow is the second workflow state (e.g., changing the current workflow state to Figure 3A "Draft" status 304).

[0091] The data processing system may use (multiple) values ​​of any of a variety of types of data object attributes to identify actors who are authorized to perform a workflow task. For example, in some embodiments, the attribute may be a classification attribute whose value indicates a classification of the data object, and the actor may be identified based on the value of the classification attribute. Examples of classification attributes include, but are not limited to, governance group classifications, sensitivity classifications, and personally identifiable information classifications. For example, in some embodiments, when a data object has a sensitivity classification of "public", an actor may be identified as being authorized to perform a workflow task on the data object, and when another data object has a sensitivity classification of "confidential", another actor may be identified as being authorized to perform the same workflow task on the other data object.

[0092] As another example, in some embodiments, the data objects in the plurality of data objects may be organized into one or more hierarchies, and the attributes may indicate one or more of these hierarchies to which the data object belongs. In some such embodiments, the data processing system may identify an actor authorized to perform workflow task "T" for data object "A" as an actor designated for at least one other data object "B" related to data object "A" in the same hierarchy (e.g., data object "B" may be a sibling, parent, grandparent, or other ancestor of data object "A" in the hierarchy). In some embodiments, the actor designated for data object "B" may be an actor authorized to perform workflow task "T" on data object "B", or may be any other suitable actor, as the various aspects of the technology described herein are not limited in this respect. This is described herein, including with reference to the accompanying drawings. Figure 1D to Figure 1G .

[0093] In some embodiments, a data processing system may use the value of a property to identify an actor with create, read, update, and / or delete (CRUD) permissions for a data object. Once such an actor is identified, the data processing system may provide the actor with access to an interface (e.g., a graphical user interface) through which the actor may provide input related to a first workflow task of a workflow for a first data object. The data processing system may generate such a GUI and present it to the actor. In turn, the actor may use the GUI to provide input to the data processing system specifying that the first workflow task is to be performed (e.g., indicating that changes to the data object are to be submitted for review, provide a decision, etc.). The data processing system may receive the input through the GUI, perform the workflow task for the first data object; and update a finite state machine for managing the workflow of the first data object to indicate that a current workflow state of the first data object has changed.

[0094] In some embodiments, the data processing system is configured to generate a finite state machine for managing a workflow of data objects according to a specification of the finite state machine. The specification may indicate states and transitions of the FSM and may be stored in any suitable format and / or any suitable (multiple) data structures, as aspects of the technology described herein are not limited in this respect.

[0095] In some embodiments, a data processing system can: (1) use an instance of a finite state machine for a workflow of a data object to implement the workflow; and (2) use another instance of the finite state machine to implement the same workflow for a different data object.

[0096] In some embodiments, a data processing system may use one FSM to manage the workflow for a data object, and another FSM to manage the workflow for approving changes to the values ​​of attributes of the object. In this case, the FSM for managing the workflow for the data object may be referred to as the "primary" FSM, and the FSM for managing the workflow for approving changes to attribute values ​​may be referred to as the "secondary" FSM. The primary finite state machine and the secondary finite state machine are described herein, including references to FIG. 5A to FIG. 5C .

[0097] In some embodiments, the data processing system can generate one or more graphical user interfaces indicating the current workflow state of the finite state machine of the data object. Examples of this are described herein, including reference to FIG. 8A to FIG. 8N .

[0098] In some embodiments, a workflow task may involve a decision made by one or more actors. For example, one or more reviewers may decide whether to approve or reject a pending change to a data object. As another example, one or more reviewers may decide whether to delete a data object. As yet another example, one or more reviewers may decide whether a pending issue is resolved. In some embodiments, a data processing system may utilize a voting scheme to determine the decision based on input provided by multiple actors. For example, the data processing system may determine that a pending change is approved if any one of the multiple actors provides such approval. As another example, the data processing system may determine that a pending change is approved only if a majority or all of the multiple actors provide such approval.

[0099] It should be understood that the techniques described above and discussed in more detail below can be implemented in any of a variety of ways, as these techniques are not limited to any particular implementation. Examples of implementation details are provided herein for illustrative purposes only. In addition, the techniques disclosed herein can be used alone or in any suitable combination, as aspects of the techniques described herein are not limited to use with any particular technique or combination of techniques.

[0100] Illustrative Data Processing System

[0101] Figure 1B is a block diagram of an illustrative data processing system 120 and a workflow management system 130 integrated with the data processing system 120 according to some embodiments of the techniques described herein. Figure 1B As shown, data processing system 120 includes workflow management system (WMS) 130. In turn, workflow management system 130 includes, among other components: (1) configuration module 131; (2) workflow execution engine 133; and (3) data layer 140 storing data objects 142.

[0102] The workflow management system 130 is configured to perform various functions related to instantiating and managing workflows for making changes to the data objects 142. In some embodiments, the WMS 130 is configured to simultaneously manage multiple workflows for making changes to corresponding data objects in the data objects 142. To this end, the WMS 130 can be configured to instantiate, for any one data object, a corresponding finite state machine for managing a workflow for making changes to the data object. In this way, when the WMS 130 manages a workflow for making changes to N different data objects (in the data objects 142), the WMS 130 uses N corresponding finite state machine instances to do so (where N is an integer greater than one). Therefore, the WMS 130 can be configured to save information about the N finite state machines in the memory of the data processing system 120.

[0103] In some embodiments, data processing system 120 may be configured to manage thousands, tens of thousands, hundreds of thousands, millions, tens of millions, or even hundreds of millions of data objects. In turn, WMS 130 may be configured to instantiate and store finite state machines as appropriate for any suitable number of these data objects. For example, WMS 130 may be configured to store hundreds, thousands, tens of thousands, hundreds of thousands, millions, tens of millions, or even hundreds of millions of finite state machine instances to manage change workflows for corresponding data objects.

[0104] In some embodiments, in order to avoid synchronization problems that occur in traditional workflow management systems, WMS130 can be the only system through which changes can be made to data objects 142. Therefore, in some embodiments, changes to at least some of the data objects 142 can be made only through actions allowed by the FSM used to manage the change workflow for these objects. In addition, these actions can be performed only by those actors who are authorized by WMS130 to perform these actions. In this way, in some embodiments, WMS130 can provide a unique interface through which changes to at least some of the data objects 142 can be implemented. To this end, WMS130 can generate GUIs for performing only those actions allowed by the workflow, and can present these GUIs only to those actors who are authorized to perform those actions; WMS130 may block other mechanisms for accessing data objects (e.g., through integrated web services).

[0105] exist Figure 1B In the illustrated embodiment, the WMS 130 can access any data stored in the data layer 140. For example, the WMS 130 can access (eg, directly access) one or more memories storing data in the data layer 140.

[0106] For example, the WMS 130 can access data objects 142 stored in the data layer 140. For example, the workflow management system 130 can access any data stored within any of the data objects 142, including, by way of example, the current value of any attribute of any of the data objects 142. Examples of data object attributes are provided herein, and include, but are not limited to, attributes whose values, for a particular data object, identify one or more groups (e.g., a hierarchy of data objects, a group of objects having the same classification, or any other suitable group of data objects) to which the particular data object belongs.

[0107] As another example, WMS130 may access metadata about data objects 142. In some embodiments, WMS130 may access metadata specifying relationships between at least some of data objects 142. For example, in some embodiments, at least some of data objects 142 may be organized into one or more hierarchies, and WMS130 may access metadata specifying the one or more hierarchies. In this manner, WMS130 may identify, for a particular data object, one or more other data objects that are related to the particular data object according to the hierarchy. For example, WMS130 may identify, for a particular data object, one or more of its ancestors (e.g., parent data object(s), grandparent data object(s), etc.), one or more of its descendants (e.g., one or more child or grandchild data objects), and / or one or more of its sibling data objects (e.g., data objects that share at least one common ancestor with the particular data object) in the hierarchy.

[0108] As part of managing a workflow for a particular data object using a finite state machine, WMS 130 may be configured to identify actors that are allowed to perform various tasks in the workflow. In some embodiments, WMS 130 may be configured to dynamically identify these actors based on the current values ​​of the attributes of the particular data object. For example, when the FSM for a first data object (whose workflow is managed) is in a first state of the FSM (e.g., Figure 3A 306 of the FSM 300 shown), the WMS 130 can dynamically identify (multiple) actors authorized to perform the workflow task (e.g., approve or reject the proposed change to the first data object) based on the (multiple) current values ​​of the (multiple) attributes of the first object and from the potential workflow actors 139.

[0109] For example, to identify one or more actors authorized to perform a workflow task for a first data object, WMS 130 may: (1) determine a current value of an attribute of the first data object indicating one or more hierarchies to which the first data object belongs; (2) identify a second data object in a hierarchy related to the first data object (e.g., the second object may be an ancestor, descendant, or sibling of the first data object); (3) identify one or more actors authorized to perform the same workflow task for the second data object; and (4) identify the actor(s) as also authorized to perform the same workflow task for the first data object. In this example, WMS 130 identifies an actor to perform a workflow task for the first data object based on: (1) the current value of an attribute of the first data object indicating the hierarchy to which the data object belongs; and (2) metadata specifying the hierarchy of the data object so that the second data object (and the actor of its associated workflow task) can be identified. Integrating WMS 130 into data processing system 120 enables WMS 130 to access the latest values ​​of these data and use them to authorize actors to perform various workflow tasks at each data object level. Various aspects of this example are further described herein, including reference Figure 1D to Figure 1G .

[0110] As another example, to identify one or more actors authorized to perform a workflow task for a first data object, WMS 130 may: (1) determine a current value of an attribute of the first data object indicating a classification of the first data object; (2) identify a data object group to which the first data object belongs (e.g., a group of data objects having the same classification) based on the current value; (3) identify one or more actors authorized to perform the same workflow task for the identified group; and (4) identify the actor(s) as actors that are also authorized to perform the same workflow task for the first data object. Also in this example, WMS 130 identifies the actors that perform the workflow task for the first data object based on: (1) the current value of the attribute of the first data object indicating the object group to which the data object belongs; and (2) metadata that specifies relationships between data objects by specifying assignments of actors to a set of data objects in data objects 142. As in the previous example, integrating WMS 130 into data processing system 120 enables WMS 130 to access the latest values ​​of these data and use these values ​​to authorize actors to perform various workflow tasks at a per-data object level. Various aspects of this example are further described herein, including reference Figure 1H and Fig. 1I .

[0111] As can be understood from the previous examples, the workflow management system 130 is tightly coupled to the data objects 142 in the data processing system 120. On the one hand, this enables the WMS 130 to manage workflows for making changes to data objects. On the other hand, since the WMS dynamically accesses the current values ​​of the data objects, any changes to the data objects can change the workflows being managed by the WMS. For example, as explained in the previous examples, changes to data objects can change the state of the corresponding FSM and can affect which actors are allowed to perform workflow tasks.

[0112] By developing a workflow management system that manages workflows through a finite state machine, the inventors have enabled a wide range of users to configure the workflow management system. In fact, configuring a finite state machine (e.g., by specifying its states and transitions) does not require writing low-level software and does not require software developers (such as Figure 1A The situation is different from the conventional method shown in Figure 1B In the example of , business user 138 may specify the finite state machine and its parameters through configuration module 131, which may be configured to present one or more interfaces (e.g., graphical user interfaces) to business user 138, through which the business user may specify the finite state machine and any related information. Non-limiting examples of information that business user 138 may input through configuration module 131 are shown in 9A to 9D and Fig.10 Shown in.

[0113] like Figure 1B As shown, the workflow management system 130 includes a workflow execution engine 133, which can be configured to instantiate and manage finite state machine instances for managing workflows for corresponding data objects in the data objects 142. For example, the workflow execution engine 133 can be configured to use one or more FSM specifications (e.g., stored in Figure 1C The workflow execution engine 133 may be configured to generate one or more FSM instances using the FSM specification module 132 shown in the figure. As another example, the workflow execution engine 133 may be configured to update information associated with the FSM instance, for example, by updating the current state of the FSM (e.g., the current workflow state of the workflow represented by the FSM instance). As another example, the workflow execution engine 133 may be configured to delete the FSM instance after the workflow represented by the FSM instance is completed (e.g., when the current state of the FSM is a terminal state). The workflow execution engine 133 may manage the FSM instances in the memory of the data processing system 120 in any suitable manner using any suitable (multiple) data structures, as aspects of the technology described herein are not limited in this respect.

[0114] like Figure 1BAs shown, the data layer 140 stores data objects 142. The data layer can store any data of the data object 142, including but not limited to the attribute values ​​of the data object 142. The data layer 140 may include one or more data storage devices to store the data objects 142. Each data storage device may include one or more storage devices that store data in one or more formats of any suitable type. For example, the (multiple) storage device portion of the data storage device may use one or more database tables, spreadsheet files, plain text files, and / or files in any other suitable format (e.g., the native format of a mainframe) to store data. The (multiple) storage devices may be of any suitable type and may include one or more servers, one or more database systems, one or more portable storage devices, one or more non-volatile storage devices, one or more volatile storage devices, and / or any other (multiple) devices configured to electronically store data. In an embodiment where the data storage device includes multiple storage devices, these storage devices may be co-located in one physical location (e.g., in one building) or distributed in multiple physical locations (e.g., in multiple buildings, in different cities, states, or countries). These storage devices may be configured to communicate with each other using one or more networks of any suitable type, because the various aspects of the technology described herein are not limited in this regard.

[0115] In some embodiments, data layer 140 may store additional types of data, including but not limited to metadata specifying relationships between data objects 142 and information used to facilitate searches between data objects 142 (e.g., search indexes maintained for data objects 142), as well as information stored in conjunction with Figure 1C as described.

[0116] Figure 1C According to some embodiments of the technology described herein Figure 1B A block diagram of an illustrative embodiment of data processing system 120 is shown. Figure 1C An embodiment of a data processing system 120 is shown, which includes Figure 1B Some of the same components are shown (e.g., workflow management system 130, configuration module 131, workflow execution engine 133, data layer 140, and data objects 142), but also shown Figure 1B It should be understood that Figure 1C The embodiments are illustrative, and in other embodiments, data processing system 120 may include one or more other components as Figure 1C In addition to or as a replacement for the components shown in .

[0117] like Figure 1CAs shown, the data processing system 120 includes one or more computer programs 124 configured to operate on the data in the data layer 140. The computer program 124 can be of any suitable type and can be written in any suitable (multiple) programming languages. For example, in some embodiments, the computer program 124 may include one or more computer programs written at least in part using structured query language (SQL) and configured to access data in one or more data storage device portions of the data layer 140. As another example, in some embodiments, the data processing system 120 is configured to execute programs in the form of a graph, and the computer program 124 may include one or more computer programs developed as a data flow graph. The data flow graph may include components (called "nodes" or "vertices") representing data processing operations to be performed on input data, and links between components representing data flows. The technology for executing calculations encoded by data flow graphs is described in U.S. Patent No. 5,966,072, entitled "Executing Computations Expressed as Graphs," the entire contents of which are incorporated herein by reference.

[0118] exist Figure 1C In the illustrated embodiment of , the data processing system 120 further includes a development environment 122 that can be used by a person (e.g., software developer 121) to develop one or more of the computer programs 124 for operating on the data in the data layer 140. An environment for developing computer programs as data flow graphs is described in U.S. Patent Publication No. 2007 / 0011668, entitled “Managing Parameters for Graph-Based Applications,” the entire contents of which are incorporated herein by reference.

[0119] In some embodiments, one or more of computer programs 124 may be configured to perform any suitable operations on the data in data layer 140. For example, one or more of computer programs 124 may be configured to access data from one or more sources, transform the accessed data (e.g., by changing data values, filtering data records, changing the format of the data, sorting the data, combining data from multiple sources, dividing the data into multiple parts, and / or in any other suitable manner), calculate one or more new values ​​based on the accessed data, and / or write the data to one or more destinations.

[0120] exist Figure 1CIn the illustrated embodiment of the data layer 140, the data layer 140 further includes metadata 144 specifying the relationship between the data objects 142 and information 146 for facilitating searching between the data objects 142. In some embodiments, the metadata 144 may specify one or more hierarchies of data objects (in the data objects 142). The hierarchies may be specified in any suitable manner and using any suitable (multiple) data structures (e.g., using one or more tree data structures, pointers, or in any other suitable manner), as the various aspects of the technology described herein are not limited in this regard. In some embodiments, the metadata 144 may explicitly or implicitly specify one or more groups of objects. For example, in some embodiments, the metadata 144 may implicitly specify a group of objects by specifying a commonly authorized actor for performing a workflow task for the data objects in the group. For example, the metadata 144 may indicate that a particular actor is authorized to perform a particular workflow task for all data objects having the same value of a classification attribute. This assignment of actors is an implicit grouping of objects having the same value of the classification attribute.

[0121] In some embodiments, information 146 for facilitating searching between data objects 142 may include one or more search indexes. The search index may be implemented as a suffix tree, an inverted index, a citation index, an N-gram index, a document-term matrix, or any other suitable manner, as aspects of the technology described herein are not limited in this respect.

[0122] exist Figure 1C In the illustrated embodiment, the workflow management system 130 further includes the following components: a finite state machine specification 132 , a GUI generation module 134 , a permission module 135 , a data object module 136 , and a search module 137 .

[0123] In some embodiments, the finite state machine specification 132 may include one or more FSM specifications. In some embodiments, the FSM specification 132 may be stored in the data layer 140, or in any other component of the data processing system 120, because the various aspects of the technology described herein are not limited in this regard. In some embodiments, the FSM specification may specify a set of states and a set of state transitions of the FSM. The FSM specification may be stored in any suitable format and using any suitable (multiple) data structures, because the various aspects of the technology described herein are not limited in this regard. As described herein, the workflow execution engine may be configured to generate one or more FSM instances using one or more FSM specifications stored in the FSM specification module 132.

[0124] In some embodiments, the GUI generation module 134 can be configured to generate a graphical user interface through which an actor can provide input to advance the execution of one or more workflow tasks. For example, the GUI generation module 134 can be configured to generate a GUI through which an actor authorized to make a decision (e.g., whether to reject or approve a pending change) can provide input indicating his or her decision. Additionally or alternatively, the GUI generation module can be configured to generate a GUI indicating the current workflow state of the workflow of the object. Examples of such GUIs are provided herein.

[0125] It should be understood that the GUI generated by the GUI generation module 134 adheres to and enforces the editability rules defined by the workflow. For example, if there is no edit transition from a workflow state, meaning that a data object is not editable, the GUI generation module 134 will not generate an interface for any actor through which the data object can be edited. In addition, the WMS 130 will prevent the editing of the data object through any other mechanism, such as integrated web services. (The concept of editability driven by workflow, as implemented in the system described herein, does not exist in traditional workflow systems, such as those based on BPMN).

[0126] In some embodiments, permission module 135 may be configured to identify one or more actors authorized to perform one or more workflow tasks in one or more workflows. Permission module 135 may use any of the techniques described herein to identify such actors. For example, permission module 135 may: (1) determine one or more current property values ​​of data objects in data storage device 140 by accessing (multiple) current property values ​​in data layer 140; (2) access metadata 144 that specifies relationships between data objects (e.g., specifies a hierarchy of objects, specifies a set of objects that share a common classification, etc.); and (3) use these two types of information to identify one or more actors authorized to perform workflow tasks.

[0127] In some embodiments, data object module 136 may be configured to manage data objects 142. For example, data object module 136 may be configured to access, modify, and / or store data objects 142 and any associated information. For example, data object module 136 may be configured to access property values ​​of data objects stored in data layer 140. As another example, data object module 136 may be configured to access metadata 144 that specifies relationships between data objects (e.g., information that specifies a data object hierarchy).

[0128] In some embodiments, data objects can be versioned. For example, after a data object is modified, the modified data object can be associated with a new version number, and a previous version of the data object can be stored. In some embodiments, the data object module 136 can be configured to manage versions of data objects and can be configured to provide access to one or more old versions of the data object and information about changes to a specified data object version and / or differences between data object versions. As described herein, versioning of data objects is achieved by managing workflows on a per-data object basis (e.g., by using corresponding finite state machine instances to manage the workflows for each data object). In fact, achieving management of data object versioning is a key advantage of managing workflows on a per-data object basis.

[0129] In some embodiments, a finite state machine for managing a workflow of a data object may be "versioned" in that when a workflow results in a change being made to a data object, the modified data object is stored as a new version of the data object, and the previous version of the data object is saved. In some embodiments, a finite state machine for managing a workflow of a data object may be "unversioned" in that when a workflow results in a change being made to a data object, the modified data object is stored and the previous version of the data object is not saved.

[0130] In some embodiments, search module 137 may provide a programming interface (e.g., API) and / or a user interface (e.g., GUI) for searching for data objects among data objects 142 in data layer 140. In some embodiments, search module 137 may utilize a search index to perform searches. In some embodiments, search module 137 may update and / or recalculate the search index to optimize future searches (e.g., in response to the addition of new data objects, deletion of data objects, and / or modification of data objects in data layer 140).

[0131] Figure 1D to Figure 1E An example is shown of using information about a data object hierarchy to which a data object belongs to identify an actor authorized to perform a workflow task for the data object according to some embodiments of the technology described herein. Figure 1DA hierarchy of data objects 150 is shown, where data object 152 is a descendant of data object 154. In this example, assume that the finite state machine for managing the change workflow for data object 152 enters a state in which the workflow management system 130 must identify any actor(s) who are authorized to edit data object 152. (This may occur, for example, when FSM 300 enters state 304 or when FSM 400 enters state 402.) In this example, to identify the authorized actor(s), WMS 130 uses hierarchy 150 to identify an ancestor of object 152 for which an authorized editor exists. Figure 1D As shown, authorized editors 156 (Rob and Diane) are authorized to edit data object 154 , which is an ancestor of data object 152 .

[0132] like Figure 1E As shown, WMS 130 traverses hierarchy 150 via links 161, 162, and 163 to search for ancestors of data object 152 that are associated with authorized editors. WMS 130 then identifies actors authorized to edit ancestor data objects as actors that are also authorized to edit data object 152. In this example, the first such object is data object 154, and as shown in FIG. Figure 1E As shown, WMS 130 assigns actor 156 as an actor authorized to edit data object 152. In this manner, hierarchy 150 enables the authorized actors for data object 152 to be inherited from one of its ancestors.

[0133] Thus, in some embodiments, one or more actors authorized to perform a particular workflow task for a data object may be inherited from an ancestor of the data object in a hierarchy to which the data object belongs. In some embodiments, the ancestor object may be selected as the ancestor object closest to the data object in the hierarchy that also has one or more actors authorized to perform the same workflow task. Thus, if a parent object and a grandparent object of a particular data object each have an associated actor, the actor of the parent object may be identified as an actor authorized to perform the same workflow task for the particular data object.

[0134] Figure 1F to Figure 1G Another example of using information about a data object hierarchy to which a data object belongs to identify actors authorized to perform workflow tasks for the data object according to some embodiments of the technology described herein is shown. This example shows how inheritance can be used to assign different actors to different workflow tasks (in the same workflow) by inheriting from different ancestor objects of the same data object 152. Figure 1FAs shown, data object 152 has ancestor data object 153 and ancestor object 154 in hierarchy 150. As in the previous example, data object 154 is associated with actors 156 (Rob and Diane) who are authorized to edit data object 154. Data object 153 is associated with actor 158 (David) who is authorized to review (and approve or reject) any changes made to data object 153. Figure 1F As shown, data object 152 has not yet been associated with any actors who are authorized to edit the object ("authorized editors") or to review any such edits ("authorized reviewers").

[0135] like Figure 1G As shown, WMS 130 can traverse hierarchy 150 via links 161, 162, and 163 to identify both authorized editors and authorized reviewers of data object 152. In this example, WMS 130 identifies actor 156 as an actor authorized to edit data object 152 (e.g., by identifying data object 154 as the data object closest to data object 152 (in terms of the number of links in hierarchy 150) that is also associated with the authorized actor). WMS 130 also identifies actor 158 as an actor authorized to review (e.g., accept or reject) any changes made to data object 152 (e.g., by one of actors 156). In this manner, the workflow for making changes to data object 152 is defined in part by the authorized actors of data objects (153 and 154) in hierarchy 150 that are related to data object 152. As can be appreciated from this example, actors for different tasks in the same workflow for a data object can inherit from different ancestors of the data object.

[0136] Figure 1D , Figure 1E , Figure 1F as well as Figure 1G The inheritance concept shown in is powerful because a data processing system may manage thousands or millions of data objects, and it is impossible to manually specify authorized actors at each data object level. On the other hand, the data objects managed by the data processing system are hierarchically related in many practical applications (e.g., deploying business term vocabularies, data governance applications for financial services companies, etc.). The workflow management system developed by the inventor can utilize such hierarchical relationships to efficiently and dynamically identify actors who are authorized to perform various workflow tasks.

[0137] It should also be understood that it would be impossible to implement this type of functionality using a conventional workflow management system that is not integrated with a data processing system (which manages the workflow of data objects of the data processing system). Such a conventional workflow management system would not be able to access metadata specifying relationships between data objects, or even if such access was provided in some way, it would not be possible to keep such information synchronized between the conventional workflow management system and the data processing system.

[0138] As described herein, other types of relationships between data objects may be utilized to identify actors who are authorized to perform various workflow tasks. Figures 1H to 1I An example is presented of using information about a data object group to which a data object belongs to identify an actor authorized to perform a workflow task for the data object according to some embodiments of the technology described herein.

[0139] Figure 1H It is shown that a data processing system may include multiple data objects, including data object 172, that share a common value for a sensitivity classification attribute (in this example, "confidential"). The data objects having the common value for the specified attribute form a group 170, and a group of actors 176 (Rob and Diane) are associated with the group. In this example, actors 176 may be authorized to review changes made to any data object in group 170. To identify an authorized reviewer of a proposed change to data object 172, a workflow management system (e.g., WMS 130) may: (1) determine the current value of its sensitivity classification attribute by accessing the current value in data storage device 140; (2) identify group 170 as the group to which data object 172 belongs; and (3) as authorized reviewers of the proposed change to data object 172. Fig. 1I As shown, actors 176 are identified as actors authorized to audit changes to data object 172 because they are authorized to audit changes to data objects in group 170 .

[0140] Illustrative methods

[0141] Figure 2 is a flow chart of an illustrative process 200 for managing a workflow of a data object using a finite state machine according to some embodiments of the technology described herein. Process 200 may be performed by any suitable data processing system and may be performed by reference to, for example, Figure 1B and Figure 1C The data processing system 120 described herein performs.

[0142] Process 200 begins at act 202, where a finite state machine for managing a workflow of a first data object is instantiated. In some embodiments, the FSM may be instantiated by: (1) accessing a specification of the FSM; (2) generating an instance of the FSM using the accessed specification; and (3) associating the generated FSM instance with the first data object.

[0143] In some embodiments, the specification of the FSM may be one of the FSM specifications 132 and may be stored in the data layer 140 or any other computer-readable storage medium (e.g., memory) accessible to the workflow management system 130. The FSM specification may be in any suitable format (e.g., a table, a configuration file, a text file, a structured data file, an XML file, etc.), as aspects of the techniques described herein are not limited in this respect.

[0144] In some embodiments, the specification may specify states of the FSM and transitions of the FSM. In some embodiments, the specification may specify one or more properties for each state (e.g., whether the state is a start state, a quiescent state, a final state; information specifying how to present a graphical representation of the state, etc.) and / or transitions of the FSM (e.g., the type of transition, information identifying one or more actors that are allowed to take actions in the workflow represented by the transition, etc.).

[0145] A finite state machine instance can be generated from the FSM specification in any suitable manner, as aspects of the technology described herein are not limited in this regard. For example, one or more variables and / or objects representing a finite state machine can be instantiated using information in the accessed specification. The FSM instance can be associated with the first data object in any suitable manner, as aspects of the technology described herein are not limited in this regard.

[0146] Next, at action 204, the current state of the FSM is determined. This can be done in any suitable manner, such as by checking the value of a variable indicating the current state. Upon instantiation, the finite state machine enters a start state. That is, the current state of the finite state machine can be its start state (or the state to which the FSM automatically transitions from its start state without user input, which may be the case during import). After taking one or more actions, the state of the finite state machine can be updated to reflect the new state, for example, as described below with reference to action 214.

[0147] Next, at act 206, an actor authorized to perform a workflow task for the first data object is identified. In some embodiments, the workflow task may be associated with an action that may be taken based on the current workflow task identified at act 204. In some embodiments, the actor may be identified using the current value of a property of the first data object. For example, Figure 2 In the illustrated embodiment, an actor is identified by: (1) at action 206a, determining a current value of an attribute of a data object by accessing the current value of the attribute in the data processing system 120 (e.g., in the data layer 140); (2) at action 206b, accessing metadata (e.g., metadata 144) that specifies the relationship between data objects in the data processing system 120; and (3) at action 206c, identifying an actor that performs a workflow task using both: (a) the current value of the attribute of the data object determined at action 206a (rather than some previously cached version); and (b) the metadata accessed at action 206b.

[0148] As an example, a current value of a property of a first data object may indicate a particular data object hierarchy to which the first data object belongs. The metadata may specify one or more other data objects in the hierarchy, and an actor authorized to perform a workflow task may be identified as an actor that has been authorized to perform the same workflow task for a second data object related to the first data object in the hierarchy (e.g., identified as an ancestor, descendant, or sibling of the first data object).

[0149] As another example, the current value of the attribute of the first data object may indicate the group of objects to which the first data object belongs (e.g., a group of objects that share a common value of a particular attribute). The metadata may specify an actor that is authorized to perform a workflow task for any data object within the group, and the actor that is authorized to perform the workflow task for the first data object may be identified as the actor that is authorized to perform the workflow task for the group. Examples of such attributes include, but are not limited to, classification attributes whose values ​​indicate a classification of the data object (e.g., a governance group classification, a sensitivity classification, a personally identifiable information classification, etc.), and the actor may be identified based on the value of the classification attribute.

[0150] Next, process 200 proceeds to act 208, where a graphical user interface is generated so that the actor identified at act 206 can provide input through the GUI specifying that a first workflow task is to be performed. Figure 3A, when the current workflow state of the data object is the draft state 304, action 208 may involve generating a GUI through which the actor identified at action 206 may provide input indicating that the changes to the first data object are to be submitted. After the actor logs into the data processing system 120, the generated GUI may be presented to the actor.

[0151] Next, at act 210, the actor may provide input specifying that the first workflow task is to be performed via the GUI generated at act 208. For example, the actor may provide input to submit changes to the data object by clicking a "Submit" button in the GUI presented to the actor by the data processing system.

[0152] In response to receiving input specifying that a first workflow task is to be performed, at act 212, the data processing system performs the first workflow task for the first data object, and at act 214, updates the current workflow state of the FSM of the first data object to a second workflow state. For example, in response to receiving input indicating that changes to the first data object are to be submitted at act 210, the data processing system may update the current state of the FSM from a "draft" state 304 to a "pending approval" state 306. After performing act 214, process 200 returns to act 204.

[0153] It should be understood that process 200 is illustrative and variations exist. For example, an actor authorized to perform an action corresponding to one or more workflow tasks may be identified before process 200 begins, and thus one or more attributes of one or more data objects may be known. On the other hand, if one or more data object attribute values ​​change during the execution of process 200, an actor authorized to perform an action on a data object may be identified during the execution of process 200.

[0154] Managing Workflows Using Finite State Machines

[0155] Figure 3A 300 is a diagram showing states and transitions of an illustrative finite state machine 300 for a workflow for managing changes to data objects according to some embodiments of the technology described herein. For example, FSM 300 can be used to manage changes to business term data objects, examples of which are provided herein. As another example, FSM 300 can be used to manage changes to documents (e.g., articles, text files, blog posts, etc.). In some embodiments, the specification of FSM 300 can be one of FSM specifications 132 and FSM 300 can be instantiated using workflow execution engine 133.

[0156] like Figure 3AAs shown, the finite state machine 300 includes five workflow states: a start state 302, a draft state 304, a pending approval state 306, a published state 308, and an abandoned state 310. The FSM 300 includes state transitions that control how a workflow governed by the FSM 300 moves from one workflow state to another and the actions that occur as a result (e.g., submit, abandon, approve, etc.). Figure 3A In the illustrative embodiment of , there are two edit transitions (edit transition 312 from start state 302 to draft state 304, and edit transition 314 from draft state 304 to itself), two actor action transitions (submit transition 316 from state 304 to state 306, and discard transition 320 from state 304 to state 310), and two decision transitions (approve transition 318 from state 306 to state 308, and reject transition 322 from state 306 to state 304).

[0157] For example, when an actor creates a document, an instance of a finite state machine 300 may be generated for a workflow for managing changes to the document. The current state of the FSM 300 may be initialized to a start state 302. After the actor completes the changes to the document, the current workflow state may be updated from the start state 302 to a draft workflow state 304. When the current workflow state is state 304 and the actor edits the document, the current workflow state may remain in the draft state 304. When the current workflow state is state 304, the actor may: submit the document for approval, in which case the current workflow state is updated to the pending approval state 306; or discard the document, in which case the current workflow state is updated to the abandoned state 310. When the current state of the FSM for the document is the Pending Approval state 306, the approver (or a set of approvers operating according to a voting scheme, an example of which is described herein) can: (1) reject the changes to the document submitted by the actor, in which case the current state of the FSM is updated to the Draft state 304; or (2) approve the changes to the document submitted by the actor, in which case the current state of the FSM is updated to the Published state 308.

[0158] As can be appreciated from the foregoing description, different actors may be authorized to perform different types of actions on a data object. For example, with respect to FSM 300, an actor may be authorized to create a data object, edit the data object, discard edits to the data object, and / or submit the edits for approval. On the other hand, one or more different actors may be authorized to approve or reject the edits to the data object.

[0159] Thus, in some embodiments, a first group of one or more actors may be authorized to perform one or more workflow tasks corresponding to one workflow state (e.g., when the current workflow state is the draft state 304, person A may be authorized to edit the document, submit edits to the document, or discard edits to the document), and a second group of one or more actors may be authorized to perform one or more workflow tasks corresponding to another workflow state (e.g., when the current workflow state is the pending approval state 306, person B may be authorized to approve or reject edits to the document).

[0160] In some embodiments, more fine-grained permissions are possible. For example, in some embodiments, each transition from an FSM state can be associated with one or more corresponding authorized actors. For example, approve and reject transitions can be associated with the same authorized actor (e.g., a single reviewer can approve or reject a change) or different authorized actors (e.g., a reviewer can be authorized to unilaterally reject but not approve a change because approval by multiple approvers may be required). Techniques for identifying actors associated with one or more state transitions are described herein.

[0161] In some embodiments, the current workflow state of the finite state machine 300 can be used to generate a user interface through which an actor can perform one or more workflow tasks. The user interface can be generated in response to the FSM entering a workflow state according to which tasks can be performed, or after the FSM enters a workflow state and one or more other events occur (such as, for example, an actor logs into the system and requests to view any pending workflow tasks).

[0162] For example, when the current workflow state of the document is in the edit state 304, an actor (e.g., "Abby A. Williams") may be authorized to submit changes for approval or to discard those changes. Thus, in this example, the actor is authorized to take actions associated with transitions 316 and 320 of FSM 300, and this information may be used by the data processing system (e.g., by GUI generation module 134 of data processing system 120) to generate a graphical user interface through which the actor may perform these authorized actions. An illustrative example of such a user interface is shown in FIG. Figure 3C , which shows a graphical user interface 380 generated and presented to an actor 382 (Abby A. Williams in this example).

[0163] like Figure 3CAs shown, GUI 380 shows a list of tasks 384 that actors 382 can perform for various data objects. For example, GUI 380 shows that actor 382 can commit or discard changes to the "Book Balance" data object 386, and enables actor 382 to do so using button 387. The details of the changes to be committed or discarded are shown in panel 388. Other actions taken by actors on this object or related objects are shown in panel 389.

[0164] Another example is Figure 3D , which shows an illustrative graphical user interface 390 generated for an actor 392 (in this example, "Lisa D. Cadotte") when the FSM 300 is in the pending approval state 306 shown using GUI elements 396. The GUI 390 allows the actor 392 to approve or reject the changes using voting buttons 394.

[0165] It should be understood that in some embodiments, an instance of FSM 300 will be generated for use in managing the workflow for each data object. Rather than a single instance of FSM 300 being used to track changes to multiple data objects (e.g., multiple documents), multiple instances of FSM 300 will be used to do so, and a data processing system (e.g., system 120) will manage such instances (e.g., using workflow execution engine 133). However, in some embodiments, a FSM may be used to manage the workflow for multiple data objects, such as in the case of managing a process for importing multiple data objects into a data processing system, as described herein by reference. Fig. 6A and Figure 6B as described.

[0166] Another example of a finite state machine for managing the workflow of data objects is in Figure 3B , which shows a diagram of states and transitions of a finite state machine 350 for a problem management workflow according to some embodiments of the technology described herein. The FSM 350 can be used to manage workflow tasks related to a problem, which can be represented by a problem data object, examples of which are provided herein. In some embodiments, the specification of the FSM 350 can be stored in the FSM specification storage device 132 and the FSM 350 can be instantiated using the workflow execution engine 133.

[0167] like Figure 3BAs shown, the finite state machine 350 includes six workflow states: a start state 352, an open state 354, an ongoing state 356, a waiting for verification state 358, a resolved state 360, and a deleted state 362. The FSM 350 includes state transitions that control how the problem-solving workflow governed by the FSM 350 moves from one workflow state to another and the actions that occur as a result (e.g., submit, delete). Figure 3B In the illustrative embodiment of , FSM 350 includes a transition 364 from state 352 to state 354, a transition 365 from state 354 to itself, a transition 366 from state 354 to state 356, a transition 367 from state 356 to itself, a transition 368 from state 356 to state 358, a transition 370 from state 358 to state 360, a transition 372 from state 358 to state 356, and a transition 374 from state 356 to state 362.

[0168] exist Figure 3B In the illustrated example of , for a state transition labeled with the title "Submit And Approve," changes (e.g., edits, deletions) associated with such a transition are made automatically without further approval. For example, edits made to the problem data object while FSM 350 is in state 354 are made automatically, and the data processing system can implement these changes immediately.

[0169] As an illustrative example of how FSM 350 may be used, an instance of the FSM may be generated for a problem data object when it is created, and the current workflow state moves from start state 352 to state 354. For example, the problem data object may indicate that there is an error in the content of another data object (e.g., a document, a business term data object, an actor's account number, an address, etc.). When the actor assigned to handle the problem clicks "In Progress" through an appropriate user interface (thereby instructing the actor to begin resolving the problem), the current workflow state moves from open state 354 to in progress state 356, at which time the actor may perform various actions, such as editing the problem data object (the current workflow state will not change), deleting the problem data object (the current workflow state will transition to state 362, and the instance of the workflow will end), or submitting the problem data object for verification (the current workflow will transition to state 358 and will remain in that state until a decision is made). One or more other actors may review the problem data object and determine whether the problem has been resolved (e.g., by determining that the error in the content of the other data object has been resolved). In this case, the approval decision is based on whether the underlying issue has been resolved, not whether edits have been made to the actual issue data object. If the issue is rejected (e.g., because additional steps are required to resolve the issue, such as by making further edits to the document), the current workflow state transitions to state 356, where the issue data object can be edited, resubmitted, or deleted. If the issue is approved, the current workflow state transitions to state 360, and the current workflow instance ends.

[0170] exist FIG. 4A to FIG. 4D Another example of a finite state machine 400 for managing a workflow for making changes to a business terminology data object (BTDO) is provided in FIG. Figure 4A It is shown in FIG. 4B to FIG. 4D In some embodiments, the specification of FSM 400 may be one of FSM specifications 132 and workflow execution engine 133 may be used to instantiate FSM 400 .

[0171] like Figure 4A As shown, state machine 400 includes ten workflow states: start state 401, draft state 402, draft pending approval state 404, published state 406, pending deletion state 408, deletion pending approval state 410, deleted state 412, imported state 414, pending approval state 416, and pending change state 418.

[0172] As an illustrative example of how FSM 400 may be used, an instance of FSM 400 may be generated for a business term data object when it is created to capture a new business term being proposed, and the current workflow state moves from start state 401 to draft state 402 .

[0173] like Figure 4B As shown, when the current workflow state is state 402, the authorized actor can: (1) delete the BTDO (the deletion will be automatically performed without approval), in which case the workflow will transition to the deleted state 412 and the workflow ends (for example, this may involve deleting the FSM 400 instance used to manage the workflow); (2) edit the BTDO, in which case the current workflow state remains state 402. 1 ; or (3) submit the BTDO for review, in which case the workflow will transition to the Draft Pending Approval state 404.

[0174] In some embodiments, when the current workflow state is state 404, the current workflow state can transition back to state 402 when the proposed business term data object is rejected (e.g., by an authorized reviewer) or the proposed BTDO is revoked by the actor who submitted the proposed BTDO for review. On the other hand, when the current workflow state is state 404, the current workflow state can transition to published state 406 when the proposed BTDO is approved (e.g., by an authorized reviewer).

[0175] It should be noted that FSM 400 includes two different system-defined workflow states - Start state 401 and Imported state 414. When a new business term is created, Start state 401 is used. On the other hand, when the data processing system imports one or more objects from one or more external sources (e.g., one or more external systems, databases, data storage devices, etc.), the initial state is Import state 414, and when the import is complete, the current workflow state of FSM 400 moves to Published state 406. In some embodiments, multiple objects can be imported in batches, and the overall import can be referred to as "batch processing."

[0176] 1 Since there is a transition from the draft state 402 to itself, the BTDO remains editable as long as the FSM 400 is in the draft state 402. Without this transition, the BTDO would not be open to additional changes after its initial creation.

[0177] like Figure 4CAs shown, when the current workflow state is the published state 406 and an authorized actor edits the BTDO, a new version of the BTDO is created and the current workflow state transitions to the pending changes state 418. When the current workflow state is state 418, if the authorized actor who submitted the edit for approval discards the edit, the current workflow state transitions back to the published state 406. When the current workflow state is state 418, the current workflow state transitions to the pending approval state 416 when the authorized actor submits the change for approval.

[0178] In some embodiments, when the current workflow state is the pending approval state 416, the authorized actor (or actors) can: approve the proposed edit, in which case the current workflow state transitions to the published state 406; or reject the proposed edit, in which case the current workflow state transitions back to the pending change state 418.

[0179] like Figure 4D As shown, when the current workflow state is the published state 406 and the authorized actor deletes the business term data object, the current workflow state transitions to the pending deletion state 408. When the current workflow state is state 408, if the authorized actor who deletes the BTDO discards the deletion, the current workflow state transitions back to the published state. On the other hand, when the actor submits the deletion request for approval, the current workflow state becomes the deletion pending approval state 410.

[0180] In some embodiments, when the current workflow state is the deletion pending approval state 410, the authorized reviewer can reject the deletion of the BTDO, in which case the current workflow transitions to the waiting for deletion state 408; or can approve the deletion, in which case the BTDO is deleted and the current workflow state moves to the deleted state 412.

[0181] Reference above FIG. 4A to FIG. 4D In the illustrative example described, any changes to the business term data objects are bundled together so that when any edits are made to the BTDO, the entire BTDO is locked. No additional changes are allowed until the workflow state of the BTDO returns from the pending approval state 416 (upon approval) or the pending change state 418 (upon discarding the edits) to the published state 406.

[0182] Main finite state machine and auxiliary finite state machine

[0183] Any embodiment of the present invention can implement two or more tasks in parallel to a common data object. Therefore, one or more auxiliary, further finite state machines can be instantiated to manage one or more corresponding workflows for performing corresponding different tasks. This allows different actors to perform different processes on the same data object at the same time. For example, in some embodiments, a data object can have two or more attributes, and one FSM can be instantiated to manage a workflow for performing changes to one attribute of the data object, while another FSM can be instantiated to manage a workflow for performing changes to another attribute of the data object. This allows different attributes of a given data object to be changed or edited simultaneously without locking the data object for editing by other actors when a given actor edits the data object. This reduces the amount of time required for the data processing system to manage changes, thereby making the data processing system more efficient, while also avoiding the need to lock data objects for other actors during changes or edits to data objects.

[0184] Simultaneous modification or editing of different attributes of a given data object may be accomplished by instantiating each auxiliary finite state machine using a separate execution thread within the workflow execution engine 133. In addition, tasks associated with each of the respective workflows may also be executed simultaneously in parallel, such as by using one or more separate execution threads for each respective workflow.

[0185] As an example, and as discussed herein, the inventors have recognized that it is valuable to allow finer-grained control over the approval process for edits. Thus, in some embodiments, one or more auxiliary finite state machines may be instantiated for managing one or more corresponding workflows for making different edits to a data object. For example, in some embodiments, a data object may have multiple attributes, and one FSM may be instantiated to manage a workflow for managing changes to one attribute of the data object, while another FSM may be instantiated to manage a workflow for managing changes to another attribute of the data object. This allows different actors to edit different attributes of a data object simultaneously without the data object being locked. This reduces the amount of time required for a data processing system to manage changes, thereby making the data processing system more efficient.

[0186] FIG. 5A to FIG. 5C An example of this approach is shown in . Figure 5Ais a diagram of an illustrative finite state machine 500 for managing changes to business terminology data objects according to some embodiments of the techniques described herein, wherein one of the states of FSM 500 is associated with a "child" or "auxiliary" finite state machine. In some embodiments, the specification of FSM 500 may be one of FSM specifications 132 and FSM 500 may be instantiated using workflow execution engine 133.

[0187] from Figure 4A and Figure 5A As can be appreciated in the examples above, the structure of finite state machine 500 is similar to that of finite state machine 400. However, when the current workflow state is in the published state 501 and an edit is made, FSM 500 transitions to the pending changes state 502, and another finite state machine (e.g., FSM "A") is instantiated to manage the workflow for approving that particular edit. In this case, the business term data object is not locked, and other edits can be made. When other edits are made to the BTDO, the workflow for approving these other edits is managed by other finite state machines (e.g., FSM "B", "C", "D"). When the workflows for all edits (e.g., the workflows for four different edits managed by four different FSMs (A, B, C, D)) are completed, the current workflow state returns to the published state 501. In this example, finite state machine 500 may be referred to as a "primary" or "parent" finite state machine, and the finite state machines generated to manage the workflows for edits to the business term data object may be referred to as "auxiliary" or "child" finite state machines.

[0188] In some embodiments, the auxiliary finite state machine allows simultaneous changes to be processed independently of each other - the workflows for approving or rejecting proposed changes can be executed in parallel independently of each other. Figure 5B As shown in GUI 510 of FIG. 5 , changes to different attributes of a data object may be managed by different auxiliary finite state machines, which may be in different states. Figure 5B, the current workflow state of the main finite state machine 500 for managing BTDO 511 (named "Government Identification Number") is the pending change state 502. In this example, changes to the definition attributes of the BTDO are managed by one auxiliary finite state machine, whose workflow state is in the "submitted" state, as shown in GUI element 514, while changes to the "sensitivity" attribute are managed by another finite state machine, whose workflow state is in the "open" state, as shown in GUI element 516. In this example, there are three finite state machines for managing changes to the base data object - one main state machine and two auxiliary state machines, the states of which are shown by GUI elements 512, 514 and 516 respectively. The two auxiliary finite state machines can be instances of the same FSM specified by the same FSM specification, or instances of different finite state machines specified by different FSM specifications.

[0189] Figure 5C An example of an illustrative auxiliary finite state machine 550 for making changes to a business term data object according to some embodiments of the techniques described herein is shown. A portion of the main finite state machine 500 includes Figure 5C In some embodiments, the specification of FSM 550 may be one of FSM specifications 132 and workflow execution engine 133 may be used to instantiate FSM 550 .

[0190] like Figure 5C As shown, the auxiliary FSM 550 has five states: a start state 552, an open state 554, a submitted state 556, an approved state 558, and an abandoned state 560. When the attribute of a published data object is modified, the current state of the workflow managed by the main FSM moves from state 501 to state 502, thereby triggering the generation of an instance of the auxiliary FSM 550 for managing the life cycle of the modification. The current state of the workflow managed by the auxiliary FSM 550 moves from the start state 552 to the open state 554. Since there is an edit transition from open to open (from state 554 to itself), when the current workflow state is in state 554, the attribute remains editable. When the current workflow state is in the open state 554 and the authorized actor discards the change, the current workflow state moves to the abandoned state 560. On the other hand, when the authorized actor submits the proposed change for approval, the current workflow state moves from the open state 554 to the submitted state 556.

[0191] In some embodiments, when the current workflow state is in the submitted state 556, the current workflow state can transition back to state 554 when the actor who submitted the edit undoes the edit or when the reviewer rejects the edit. On the other hand, if the change is approved, the current workflow state transitions to the approved state 558 and the edit is implemented by the data processing system.

[0192] In some embodiments, when all auxiliary finite state machines associated with the pending change state 502 have reached a terminal state (abandoned state 560 or approved state 558), the instances of the auxiliary finite state machines are deleted and the current workflow state of the workflow managed by the main FSM 500 returns to the published state 501.

[0193] Automatically triggered actions

[0194] In some embodiments, the data processing system can automatically perform one or more actions in response to one or more triggering events. These events can be defined in the data processing system (e.g., by programming, configuration settings, rules, etc.) and can be used to trigger the execution of (multiple) actions. Examples of such actions include, but are not limited to, generating and sending notifications (e.g., email notifications, SMS messages, MMS messages, phone calls, or any other suitable type of communication) to one or more actors and / or systems (e.g., downstream systems, external systems, and / or any other systems), triggering the execution of another computer program (e.g., a script), and causing state transitions in the workflow of a data object.

[0195] As a specific example, an administrator of a data processing system may set up a notification trigger that causes an email to be sent to interested parties whenever someone submits a change to a business term. As another specific example, an administrator of a data processing system may set up a trigger that causes a script to automatically add classifications to business terms when those business terms enter a specific workflow state. As another specific example, an administrator of a data processing system may set up a trigger that causes a script to automatically check for the existence of certain classifications (e.g., a "Governance Group" classification) before those classifications enter a specific workflow state (e.g., a "Draft Pending Approval" state), and display an error message if such classifications are not specified.

[0196] Thus, in some embodiments, an administrator of a data processing system can define events that will trigger actions such as notifications (e.g., emails), scripts (e.g., Apache Groovy scripting language), or state transitions. In some embodiments, events (and thus actions) can be raised in response to workflow activities or in response to receiving remote requests (e.g., HTTP requests received via REST web services).

[0197] Non-limiting examples of events that can trigger actions include: (1) when a data object's finite state machine enters a particular workflow state (e.g., when a business term enters a particular workflow state, it can trigger the execution of a script used to validate the classification of the business term); (2) when a data object's FSM leaves a particular workflow state; (3) before a workflow FSM transition occurs; (4) after a workflow FSM transition occurs (e.g., initiating a new version of a data object can trigger notification to one or more approvers); (5) when a workflow decision is initiated; (6) when a workflow decision is resolved; and (7) when a decision participant selects a voting option.

[0198] In the context of notifications, for example, the following list of events is a non-limiting list of examples of events that can trigger notifications: (1) when a change is approved by a designated approver; (2) when a change is approved by an actor with override authority; (3) when an actor commits a change to a data object and an approval decision is initiated; (4) after all approvals for the change have been received and the change has been implemented to the data storage device; (5) when a data object in a "draft" state is deleted; (6) when a data object in a "published" state is marked for deletion; (7) when a data object in a "pending approval" state is discarded; (8) when a pending change is discarded; (9) when a pending change is discarded by an actor with override authority; (10) when a designated approver rejects the change; (11) when a change is submitted; (12) when a user undoes a pending change; and (13) when a user with override authority undoes a change.

[0199] Finite state machine for managing imports

[0200] Some embodiments provide a finite state machine for managing the batch import of multiple data objects, which can be advantageous because many (e.g., thousands, millions) of data objects may go through the same approval process during the import. In some embodiments, rather than instantiating a different finite state machine for importing each individual data object, a single finite state machine can be utilized for this purpose.

[0201] Fig. 6A Finite state machine 600 is shown for importing additions, modifications and / or deletions of multiple data objects according to some embodiments of the techniques described herein. In some embodiments, the specification of FSM 600 may be one of FSM specifications 132 and FSM 600 may be instantiated using workflow execution engine 133.

[0202] like Fig. 6AAs shown, FSM 600 includes six workflow states: Start state 602, Ready state 604, Open state 606, Submitted state 608, Approved state 610, and Abandoned state 612. When an actor initiates the import of a data object using a data processing system, an instance of FSM 600 is generated and the current workflow state moves to Ready state 604. When the current workflow state is state 604 and the import fails to complete, the actor can abandon it (e.g., by clicking a "discard" button on a GUI presented to the actor) and the current workflow state transitions to Abandoned state 612 and the workflow is completed. Otherwise, when the import is completed, the current workflow state transitions to Open state 606.

[0203] In some embodiments, when the current workflow state is the open state 606, the authorized actor can: discard the imported data object, in which case the current workflow state moves to the abandoned state 612 and the workflow is completed; or submit the imported data object for approval, in which case the current workflow state moves to the submitted state 608.

[0204] In some embodiments, when the current workflow state is in the Submitted state 608, if the import is rejected (e.g., by one or more authorized reviewers), the current workflow state transitions back to the Open state 606. On the other hand, when the import is approved, the current workflow state transitions to the Approved state 610, and the workflow is completed. In some embodiments, when the import of objects is to be managed through the user interface, the data objects are automatically assigned the "Imported" state and will continue their respective main workflows after the batch import is approved.

[0205] Figure 6B A finite state machine 650 for conditionally importing additions, modifications, and / or deletions of multiple data objects according to some embodiments of the techniques described herein is shown. The FSM 650 includes conditional transitions that allow requesting approval for the import only if predefined conditions are met (e.g., one or a threshold number of errors occur, one or more imported records are rejected). In some embodiments, the specification of the FSM 650 can be one of the FSM specifications 132 and the FSM 650 can be instantiated using the workflow execution engine 133. It should be understood that according to embodiments of the techniques described herein, the ability to branch in a finite state machine is not limited to processing import workflows, as is the case in this example, but can be used in any finite state machine for managing workflows of data objects.

[0206] like Figure 6BAs shown, FSM 650 includes 7 workflow states: Start state 652, Ready state 654, Open state 656, Review required state 658, Submitted state 660, Approved state 662, and Abandoned state 664. When an actor initiates the import of a data object using the data processing system, an instance of FSM 650 is generated and the current workflow state moves to Ready state 654. When the current workflow state is state 654 and the import fails to complete, the actor can abandon it (e.g., by clicking a "discard" button on a GUI presented to the actor) and the current workflow state transitions to Abandoned state 664 and the workflow is completed. Otherwise, when the import is completed, the current workflow state transitions to Open state 656.

[0207] In some embodiments, when the current workflow state is the open state 656 and the review conditions are not met (e.g., no errors in the import, no rejected records in the import, etc.), the current workflow state transitions to the approved state 662 and the workflow is completed. On the other hand, when the review conditions are met, the current workflow transitions to the review required state 658.

[0208] In some embodiments, when the current workflow state is the Review Required state 658, the authorized actor can: discard the imported data object, in which case the current workflow state moves to the Abandoned state 664 and the workflow is completed; or submit the imported data object for approval, in which case the current workflow state moves to the Submitted state 660.

[0209] In some embodiments, when the current workflow state is in the submitted state 660, if the import is rejected (e.g., rejected by one or more authorized reviewers), the current workflow state transitions back to the review required state 658. On the other hand, when the import is approved, the current workflow state transitions to the approved state 662, and the workflow is completed.

[0210] Identify the actors that perform workflow tasks

[0211] As described herein, a data processing system can authorize different actors to perform different workflow tasks in a workflow of a data object. For example, different actors can be authorized to make changes to a data object and review (e.g., approve or reject) those changes. Typically, a set of one or more actors can be identified as actors authorized to perform workflow tasks for each workflow task in a workflow. Two different tasks can be associated with the same set of one or more actors or with different actors.

[0212] In some embodiments, a data processing system (e.g., data processing system 120 using permission module 135) may identify one or more actors as authorized to perform a workflow task for each of one or more workflow tasks in a workflow for a data object. For example, in some embodiments, one or more actors may be identified as authorized to perform a workflow task for each of one or more (e.g., all) transitions in a FSM used to manage a workflow. For example, one or more actors may be identified as authorized to perform a workflow task represented by a state transition that requires actor input (e.g., is not an automatic transition) - such as edit or approve.

[0213] In some embodiments, the identification of the authorized actor can be stored by the data processing system and used to perform one or more functions to advance the management workflow. For example, in some embodiments, the data processing system can provide an actor authorized to perform a workflow task (e.g., an auditor authorized to approve changes to a data object) with a graphical user interface that enables the actor to perform the workflow task (e.g., a graphical user interface through which the auditor can approve or reject the proposed changes to the data object). As another example, in some embodiments, the data processing system can notify the actor (e.g., via email, text message, through an application and / or any other suitable type of communication) that he or she has one or more workflow tasks to be performed on one or more workflows. As another example, in some embodiments, the data processing system can notify one or more actors (e.g., regulatory actors who do not perform workflow tasks themselves) about the identity of one or more actors identified as being authorized to perform one or more workflow tasks (e.g., so that these regulatory actors know who is authorized to perform the (multiple) workflow tasks). As yet another example, in some embodiments, a data processing system may provide a notification to one or more other systems (e.g., downstream systems) indicating that one or more tasks are to be performed and / or information identifying one or more actors authorized to perform the task(s).

[0214] The inventors have developed a variety of techniques for identifying one or more actors authorized to perform workflow tasks for a workflow data object. In some embodiments, workflow actors can be directly selected. For example, one or more actors can be designated (e.g., by the actor through a graphical user interface) as being authorized to perform one or more specific actions for a particular data object. For example, an actor authorized to make changes to a particular business term data object can be entered. However, the inventors have realized that it is impractical to assign actors to each workflow and workflow action for each data object, particularly given that a data processing system can support multiple workflows for multiple (e.g., hundreds, thousands, millions) of data objects. For large-scale operations, the inventors have developed rules for automatically and dynamically identifying actors for a target group of objects (e.g., a hierarchy) based on data object attributes, relationships to other objects, and the like.

[0215] Therefore, some embodiments provide automated techniques for identifying actors authorized to perform workflow tasks. In some embodiments, a data processing system may use information associated with a data object to identify one or more actors authorized to perform workflow tasks for the data object. For example, in some embodiments, a data processing system may identify one or more actors authorized to perform workflow tasks for the data object based on the values ​​of one or more attributes of the data object.

[0216] As an example, a data processing system may manage multiple data objects by organizing them into one or more hierarchies, and the data objects may include one or more attributes, the (multiple) values ​​of the one or more attributes indicating the one or more hierarchies to which the data object belongs. The data processing system may use the (multiple) values ​​of the one or more attributes to identify one or more actors authorized to perform workflow tasks for the object. For example, data object "A" may be related to (e.g., may be a descendant of) data object B in the data object hierarchy. In some embodiments, the data processing system may use the hierarchy to identify a specific set of one or more actors authorized to perform specific workflow tasks for data object B, and may authorize the set of actors to perform the same specific workflow tasks for data object A. In some embodiments, data object B may be a parent or ancestor of data object A.

[0217] An example of this method is Fig. 7A In an illustrative embodiment of FIG. 700 , a diagram is shown illustrating identifying one or more workflow actors for a data object using information specified for at least one other data object in at least one data object hierarchy that contains the data object. Fig. 7AAs shown, data object 701 is a child of data object 702, which in turn is a child of data object 703. Actors 704 ("Adam" and "Greg" in this example) are assigned to data object 703 as "responsible parties" and are therefore authorized to perform any workflow tasks that the "responsible parties" are authorized to perform. The data processing system can identify actor 704 as the "responsible party" for data object 701. In this way, authorized actors can be identified by inheritance. The authority to perform workflow tasks for a particular data object can be inherited from one or more related data objects in the object hierarchy.

[0218] Another example of this approach is Fig.7D , which shows a diagram 715 demonstrating the use of information specified for multiple data object hierarchies containing a data object 716 to identify workflow actors for the data object. In this example, data object 716 (which is a business term data object representing the business term "credit score") is part of two hierarchies - a "mortgage loan" data object hierarchy 717 and a "car loan" data object hierarchy 718. Each of these hierarchies is associated with a corresponding set of "reviewers" who are authorized to perform any workflow tasks that the "reviewers" are authorized to perform. In fact, in some embodiments, workflow tasks can be specified so that the authorized actors of the workflow task are members of the "reviewers". Therefore, identifying the set of "reviewers" for a data object is equivalent to identifying which actors are authorized to perform the "reviewer" workflow task for a workflow involving the data object.

[0219] In this example, the "Mortgage" hierarchy 717 is associated with reviewers 719a (Ian, Will, and Lisa in this example) and the "Auto Loan" hierarchy 718 is associated with reviewers 719b (Joan and Dana in this example). In this example, two groups of reviewers (i.e., reviewers 719a and 719b) can be identified as authorized "reviewers" for the primary object 716, so that the review workflow task can involve all of them according to appropriate voting rules (e.g., majority vote, unanimous vote, at least one reviewer per group, etc.). For example, if a change is made to the data object 716, the review process for the change may require votes from all five reviewers, and approval may be granted if a majority of reviewers approve the change. Voting rules are described in more detail below, but this example illustrates that a data object (e.g., data object 716) can have an attribute that specifies multiple data object hierarchies (e.g., hierarchies 717 and 718) to which the data object belongs and that actors authorized to perform workflow tasks (e.g., approve changes to data object 716) can be identified based on the value of the attribute by identifying actors associated with the specified hierarchies. Other examples are described herein, including references to Figure 1D , Figure 1E , Figure 1F as well as Figure 1G .

[0220] As another example of a technique for automatically identifying one or more actors authorized to perform a workflow task for a data object based on the values ​​of one or more attributes of the data object, in some embodiments, a data processing system may identify one or more actors authorized to perform a workflow task for a data object having one or more classification attributes based on the value(s) of the classification attribute(s). For example, the system may use the value of a governance group classification attribute of a data object, the value of a sensitivity classification attribute of a data object, the value of a personally identifiable information (PII) classification attribute of a data object, and / or the value of any other suitable classification attribute(s) of a data object to identify one or more actors to perform a workflow task for a data object, examples of which are provided herein.

[0221] An example of this method is Figure 7B In the illustrative embodiment of FIG. 700 , a diagram 705 is shown showing identification of one or more workflow actors for a data object based on the value of a classification attribute of the data object. Figure 7BAs shown, data object 706 has a sensitivity classification attribute 707 and the data processing system can identify authorized actors based on the value of the attribute (e.g., to perform "reviewer" tasks such as approving changes to the data object). In this example, the value of sensitivity classification attribute 707 is "Highly Confidential", which causes the data processing system to identify actors 708 based on the value - the actors identified in this example are Carl, Jon, and security officers 709 (Renee and Ethan). In contrast, Figure 7C As shown, the value of classification attribute 712 of data object 711 is "public", which causes the data processing system to identify different actors (actors 713 - Sara and Jess in this example) as actors authorized to perform the "reviewer" task.

[0222] In some embodiments, when actors authorized to perform workflow tasks are identified based on the value of a data object attribute, the authorized actors may change when the value of the data object attribute changes. Such changes may occur even during workflow execution. For example, when a change to a data object involves a change in the value of its sensitivity classification attribute (e.g., from "confidential" to "highly confidential"), a different (e.g., larger) set of reviewers may be identified to review that change and / or other changes. Other examples of this are described herein, including with reference to Figure 1H and Fig. 1I .

[0223] Voting Scheme

[0224] As described herein, some workflow tasks are decisions made by one or more parties. For example, one or more reviewers may decide whether to approve or reject a pending change to a data object (e.g., as described with reference to state 416 of FSM 400). As another example, one or more reviewers may decide whether to delete a data object (e.g., as described with reference to state 408 of FSM 400). As yet another example, one or more reviewers may decide whether a pending issue is resolved (e.g., as described with reference to state 358 of FSM 350).

[0225] When only one actor is assigned to make a decision, then the input of that single actor completely determines the decision. However, in some embodiments, multiple actors may be assigned to vote on a decision, and a voting scheme may be utilized to determine the overall decision based on their individual votes. For example, in some embodiments, only a single one of the assigned decision makers is required to approve a pending change. In some such embodiments, once one of the assigned decision makers approves the pending change, the change is approved, and when all decision makers reject the pending change, the change is rejected. For example, if Fig. 7E As shown in diagram 720 of , the "Security Approver" group is defined to include three reviewers (Security Officer, Carl, and John) and can be assigned as the "reviewer" of any data object whose sensitivity classification attribute has a value of "Highly Confidential". The group is configured with a voting scheme parameter of "Single" which indicates that once any one of the three reviewers approves a pending change, the change is approved. For example, if Carl approves a pending change, the change will be approved and other reviewers will not be presented with voting buttons in their work queues when they log in to see the pending actions.

[0226] exist Fig. 7E In the example of , where two of the reviewers are individuals and one of the reviewers (the "security officer") is a group of multiple reviewers (Rennie and Ethan), any of the multiple reviewers can vote on behalf of the "security officer" group as a whole. Therefore, either Rennie or Ethan can approve the pending change.

[0227] In some embodiments, a majority of the assigned decision makers are required to approve pending changes. For example, as shown in diagram 725 of 7F, once both Rainey and Jon reject pending changes, the pending changes are rejected because the majority of decision makers no longer have the means to approve the changes.

[0228] In some embodiments, the vote must be unanimous and all assigned decision makers need to approve the pending change in order for the change to be approved. Figure 7G As shown in diagram 730, when Ethan and Carl and Jon all vote to approve, the pending changes are approved.

[0229] In some embodiments, there may be a decision maker that is authorized to override the voting scheme and the votes of other decision makers. For example, such a decision maker may review the votes provided by other decision makers and consider them, but ultimately make his or her own final decision as to whether to approve or reject a pending change.

[0230] In some embodiments, a data object may belong to multiple data object hierarchies and a decision workflow task may involve a decision maker associated with each of the multiple hierarchies. In some such embodiments, a hierarchy voting scheme may be employed, wherein the voting scheme of each individual hierarchy must be satisfied before a pending change is approved.

[0231] For example, Figure 7H As shown in diagram 735, a "LOB Approver" will approve a pending change to a data object if: (1) a single decision maker from the decision makers associated with the mortgage business hierarchy approves the change; and (2) a single decision maker from the decision makers associated with the auto loan business hierarchy approves the change. For example, if Will (a decision maker in the mortgage hierarchy) is the first person to vote and approve a pending change, the "Approve" and "Reject" buttons will be removed from Ian and Lisa's work queues, but the vote will remain open to Joan and Dina (decision makers in the auto loan hierarchy). If Joan approves the pending change, the pending change will be approved, but if Joan rejects the change, Figure 7H , the pending changes will be rejected.

[0232] As another example, Fig.7I As shown in diagram 740 of , each of the multiple hierarchies requires majority approval. Thus, a "LOB Approver" will approve a pending change to a data object when: (1) a majority of the decision makers associated with the mortgage loan business hierarchy approve the change; and (2) a majority of the decision makers associated with the auto loan business hierarchy approve the change. For example, in Fig.7I , the change is approved when Ian and Lisa, and June and Dinah approve the change.

[0233] As another example, if each of multiple hierarchies requires unanimous approval, a "LOB Approver" would approve a pending change to a data object if: (1) all decision makers associated with the mortgage business hierarchy approve the change; and (2) all decision makers associated with the auto loan business hierarchy approve the change.

[0234] In some embodiments, multiple groups of decision makers may be assigned to a decision. Figures 7J to 7M As shown, three groups of reviewers ("Security Approver", "Steward Approver", and "LOB Approver") may be assigned to a decision. Approval from a single group, a majority of the group, or each of the groups may be required. For example, Figure 7JAs shown in diagram 745, when approval from a single group is required, if Anne approves the pending change on behalf of the "Manager Approver" group, the pending change will be approved and implemented - the Approve and Reject buttons will be removed from the work queues of others.

[0235] As another example, Figure 7K As shown in the diagram 750 of , when approval of a majority of groups is required, assume that Carl and Jon approve the change, thereby satisfying the majority requirement of the "Security Approver" group, but Anne rejects the change on behalf of the "Manager Approver" group. In this case, the vote will remain open because it is still possible to obtain a majority vote. If Will approves the change for the mortgage hierarchy and Joan approves the change for the auto loan hierarchy, the pending changes will be approved as a whole and implemented.

[0236] As another example, Figure 7L As shown in diagram 755 of , when approval from all groups is required, the pending change will be approved, for example, if: (1) Carl and John approve the pending change, thereby satisfying the majority requirement of the "Security Approver" group; (2) Anne approves the pending change on behalf of the "Manager Approver" group; and (3) Will and Joan approve the change on behalf of the Mortgage Hierarchy and the Auto Loan Hierarchy. On the other hand, if Figure 7M As shown in diagram 760 of , if Anne rejects the pending change on behalf of the “Manager Approver” group, a unanimous decision is no longer possible and the pending change will be rejected.

[0237] Example of workflow management using primary and secondary finite state machines

[0238] As described herein, in some embodiments, one or more finite state machines may be used to manage a workflow for a data object. For example, a primary finite state machine and one or more auxiliary finite state machines may be used to manage a workflow for making changes to a data object (e.g., managing fine-grained changes to the attributes of a data object). Additionally, as described herein, in some embodiments, a graphical user interface may be generated and presented to various actors to perform workflow tasks in a workflow for a data object. Aspects of these embodiments will be discussed below with reference to a graphical user interface for managing a workflow for a data object. FIG. 8A to FIG. 8N The example workflow for changing a business term data object is shown in further detail.

[0239] Fig. 8Ais a view of a graphical user interface 800 showing a plurality of business terminology data objects according to some embodiments of the techniques described herein. The GUI 800 provides information about business terminology data objects for a business term in a business vocabulary containing 260 business terminology data objects. The GUI 800 includes a "Search Results" pane 801 that shows a list of the first few of the 260 business terminology data objects in alphabetical order, including: "Account Type" data object 802, "Accounting Risk" data object 803, "Accounting Unit" data object 804, "Address" data object 805, and "Address Line 1" data object 806.

[0240] In response to an actor selecting a business term data object through GUI 800, the data processing system may provide the actor with information about the selected business term data object. For example, in response to an actor selecting the "Accounting Risk" data object 803, the data processing system may generate a GUI (such as, for example, Figure 8B GUI 810 is shown to provide information about data object 803 to the actor.

[0241] like Figure 8BAs shown, GUI 810 displays information about the properties of data object 803, etc. For example, GUI 810 indicates property values, including values ​​of the following properties: (1) dictionary property 811, whose value (in this example, "Enterprise Business Dictionary") indicates the dictionary to which the business term represented by BTDO belongs; (2) name property 812, whose value (in this example, "Accounting Risk") indicates the identifier or name of BTDO; (3) definition property 813, whose value (in this example, "The risk that the value of a company's equity, assets, liabilities, or revenue will change due to changes in exchange rates. This occurs when a company denominates part of its equity, assets, liabilities, or revenue in a foreign currency") provides the definition of BTDO; (4) parent term property 814, whose value indicates the parent data object of BTDO in at least one hierarchy; (5) hierarchy property 815, which can be one or more hierarchical structures to which BTDO belongs. (6) various classification attributes 816, including: a governance group classification attribute 816a, which can be a list of one or more governance groups to which the BTDO belongs (in this example, "Risk", "Liquidity", and "Financial"); a sensitivity classification attribute 816b, which indicates the sensitivity level of the BTDO (e.g., "Internal", "Public", "Confidential", and "Highly Confidential"); and a personally identifiable information ("PII") classification attribute 816c (e.g., "Level 1", "Level 2", etc.); (7) various responsible party attributes 817, including a business owner attribute 817a (in this example, "Wade L. Register"); L. Register)”), manager attribute 817b (in this example, “Abby A. Williams”), and subject matter expert attribute 817c (in this example, “Rosa S. Todd” and “Donald D. Mace”).

[0242] Various actors may be authorized to perform different actions for a business term data object. In this example, "Abby A. Williams" or "Abby" is the manager of the "Accounting Risk" business term data object 803 and is authorized to make changes to that data object. Abby is able to make these changes through the graphical user interface, for example, like Figure 8C 820, which Abby sees when she logs into the data processing system. 9A to 9D as well as Fig.10 The main finite state machine and auxiliary finite state machine shown are used to manage changes to the data object "Accounting Risk" as described below. Alternatively, the reference FIG. 4A to FIG. 4D as well as FIG. 5A to FIG. 5CThe finite state machine described in this paper manages these changes. Figure 8C As shown in GUI element 821 in , the current state of the main finite state machine for managing changes to data object 803 is the "published" state.

[0243] In this example, Abby changes the value of definition attribute 813 via GUI 820. Thus, Fig.8D As shown in GUI element 826 of GUI 825 of FIG, the state of the primary finite state machine changes from the "Published" state to the "Pending Approval" state. In addition, as a result of this change, an auxiliary finite state machine is instantiated for managing the workflow of approving changes to the value of definition attribute 813. As shown in GUI element 827, the state of the auxiliary finite state machine is "Open". When the current workflow state of the auxiliary FSM is the "Open" state, Abby is authorized to submit changes to definition attribute 813 for review or to discard the changes, and to this end, the data processing system generates a GUI portion 828 with buttons 828a and 828b to allow her to perform one of these actions.

[0244] Next, if Fig. 8E As shown in GUI 830 of FIG. 8A , Abby makes another change to data object 803 by changing the value of PII classification attribute 816 c. As a result of this change, another auxiliary finite state machine is instantiated for managing the workflow of approving changes to the value of PII classification attribute 816 c. As shown in GUI element 831 , the state of this auxiliary FSM is the “open” state. When the current workflow state of the auxiliary FSM is the “open” state, Abby is authorized to submit the change to PII classification attribute 816 c for review or to discard the change, and to this end, the data processing system generates a GUI portion 832 having buttons 832 a and 832 b to allow her to perform one of these actions.

[0245] Next, Abby submits the changes to the definition attribute 813 for review using button 828a. As a result, the state of the auxiliary finite state machine used to manage the changes is converted to the "Submitted" state, as shown in FIG. Figure 8F As shown in GUI element 827 in GUI 835 of FIG. Figure 8G As shown in pane 838 of GUI 837, this submitted change is subject to approval by three reviewers - a risk reviewer, a liquidity reviewer, and a financial reviewer.

[0246] Next, in this example, the risk reviewer logs in and is presented with a GUI 840 such as Figure 8H As shown, through the GUI she can approve or reject the submitted changes to the value of the definition attribute 813. The risk reviewer can take this action through the Approve button 841a and the Reject button 841b respectively.

[0247] Next, in this example, the financial auditor logs in and is presented with a GUI 845 such as Figure 8I As shown, through the GUI he can approve or reject the submitted change to the value of the definition attribute 813. The financial reviewer can take this action through the approval button 846a and the rejection button 846b respectively. Before taking this action, the financial reviewer can see through the GUI portion 847 that one other reviewer has approved the change, but two reviewers (i.e., the financial reviewer and the liquidity reviewer) have not yet submitted their decisions, which are still pending.

[0248] After approving the submitted changes to the values ​​of definition attributes 813, the financial reviewer can Figure 8J GUI 850 is shown viewing his job queue.

[0249] Next, in this example, Abby logs in to see whether the changes she submitted to definition attribute 813 have been approved. Figure 8K 855, Abby can see in GUI portion 856 that two of the three reviewers have approved the changes, but one approval (from the liquidity reviewer) is still pending.

[0250] Next, in this example, the liquidity auditor logs in and is presented with a GUI 860 such as Figure 8L As shown, through the GUI she can approve or reject the submitted changes to the values ​​of the definition attributes 813. The liquidity reviewer can take this action through the approve button 861a and reject button 861b shown in the pane 861, respectively.

[0251] As a result of all three reviewers approving the submitted change, the change is approved and the instance of the auxiliary finite state machine used to manage the approval process for the change is completed and deleted. Next, when Abby logs in to check the status of her submission, she is presented with Figure 8L GUI 865 shown in , indicates that the change she submitted to the value of definition attribute 813 has been approved.

[0252] Nonetheless, Abby must decide what action to take with respect to her proposed change to PII classification attribute 816c. In this example, Abby discards the change by using button 831b. With the first change approved and the second change discarded, there are no further pending changes, and the current workflow state of the master finite state machine transitions from the "pending approval" state to the "published" state, as shown in FIG. Figure 8N GUI element 871 of GUI 870 is shown.

[0253] As can be appreciated from the previous examples, using an auxiliary finite state machine allows workflows for making changes to different properties to proceed independently of each other.

[0254] Fig. 9A 9 is an illustration of a graphical user interface 910 showing a list of finite state machine specifications according to some embodiments of the techniques described herein. Graphical user interface 910 may be generated by a data processing system (e.g., by GUI generation module 134) to provide an actor with a GUI through which to view, edit, add, and / or delete finite state machine specifications. Fig. 9A In the illustrative example of , GUI 910 shows a list of multiple different finite state machine specifications, including reference Fig. 6A and Figure 6B The import state machine described and used to implement FIG. 8A to FIG. 8N Specifications of the primary and secondary state machines for the workflow shown.

[0255] Fig. 9B is an illustration of some embodiments of the technology described herein for managing FIG. 8A to FIG. 8N 920 is a view of a graphical user interface 920 of a master finite state machine of changes to a data object in an example of FIG. GUI 920 may be presented to an actor in response to the actor selecting to view a state diagram of the state machine through GUI 910.

[0256] Fig. 9C is a view of a graphical user interface 930 through which Fig. 9B The states of the FSM shown in FIG. 9 can be viewed, added, deleted, and / or edited. For example, user interface 930 can be used to edit the properties of a state (e.g., by specifying which state (if any) is static, associated with an auxiliary finite state machine, etc.). Fig. 9C As shown, actors can select a state and edit the transitions associated with that state. Fig. 9C As shown, in response to an actor selecting the "start" state in the state table, a transition table associated with the start state may be presented to the actor. As another example, Fig.9D As shown in GUI 940 of , in response to an actor selecting a “pending change” state in the state table, a transition table associated with the “pending change” state may be presented to the actor.

[0257] Fig.10 is an illustration of some embodiments of the technology described herein for managing FIG. 8A to FIG. 8N1000 is a view of a graphical user interface 1000 of an auxiliary finite state machine for modifying the properties of a data object in an example. GUI 1000 also shows a state table of the auxiliary finite state machine and the corresponding properties of these states. States (and their associated transitions) can be edited, deleted, added and / or viewed through GUI 1000.

[0258] Additional implementation details

[0259] Fig.11 An example of a suitable computing system environment 1100 on which the techniques described herein may be implemented is shown. The computing system environment 1100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the techniques described herein. Neither should the computing environment 1100 be interpreted as having any dependency or requirement relating to any one or combination of components shown in the exemplary operating environment 1100.

[0260] The technology described herein operates with many other general or special computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations that may be suitable for use with the technology described herein include, but are not limited to, personal computers, server computers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like.

[0261] A computing environment can execute computer executable instructions, such as program modules. Typically, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The techniques described herein can also be practiced in a distributed computing environment, where tasks are performed by remote processing devices linked through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including memory storage devices.

[0262] refer to Fig.11, an exemplary system for implementing the techniques described herein includes a general purpose computing device in the form of a computer 1110. Components of the computer 1110 may include, but are not limited to, a processing unit 1120, a system memory 1130, and a system bus 1121 that couples various system components including the system memory to the processing unit 1120. The system bus 1121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example and not limitation, such architectures include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus (also known as a Mezzanine bus).

[0263] Computer 1110 typically includes various computer-readable media. Computer-readable media can be any available media that can be accessed by computer 1110, and includes volatile and non-volatile, removable and non-removable media. By way of example and not limitation, computer-readable media can include computer storage media and communication media. Computer storage media include volatile and non-volatile media, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage devices, cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by computer 1010. Communication media typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and include any information delivery medium. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in such a way as to encode the information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.

[0264] The system memory 1130 includes computer storage media in the form of volatile and / or nonvolatile memory, such as read-only memory (ROM) 1131 and random access memory (RAM) 1132. A basic input / output system 1133 (BIOS), containing the basic routines that help transfer information between elements within the computer 1110, such as during startup, is typically stored in ROM 1131. RAM 1132 typically contains data and / or program modules that are immediately accessible to and / or currently being operated on by the processing unit 1120. By way of example and not limitation, Fig.11 Operating system 1134 , application programs 1135 , other program modules 1136 , and program data 1137 are shown.

[0265] The computer 1110 may also include other removable / non-removable, volatile / non-volatile computer storage media. By way of example only, Fig.11 A hard disk drive 1141 is shown that reads from or writes to a non-removable non-volatile magnetic medium, a flash drive 1151 that reads from or writes to a removable non-volatile memory 1152 (such as flash memory), and an optical drive 1155 that reads from or writes to a removable non-volatile optical disk 1156 (such as a CD ROM or other optical media). Other removable / non-removable, volatile / non-volatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tapes, solid-state RAM, solid-state ROM, etc. The hard disk drive 1141 is typically connected to the system bus 1121 via a non-removable memory interface such as interface 1140, and the magnetic disk drive 1151 and optical drive 1155 are typically connected to the system bus 1121 by a removable memory interface such as interface 1150.

[0266] The above discussion and Fig.11 The drives and their associated computer storage media shown in FIG. 1 provide storage for computer readable instructions, data structures, program modules and other data for the computer 1110. Fig.11In the figure, for example, hard disk drive 1141 is shown as storing operating system 1144, application programs 1145, other program modules 1146, and program data 1147. Note that these components can be the same or different from operating system 1134, application programs 1135, other program modules 1136, and program data 1137. Different reference numerals are given to operating system 1144, application programs 1145, other program modules 1146, and program data 1147 to show that at least they are different copies. An actor can enter commands and information into computer 1110 through input devices such as keyboard 1162 and pointing device 1161 (commonly called a mouse, trackball, or touch pad). Other input devices (not shown) may include microphones, joysticks, game controllers, satellite dishes, scanners, etc. These and other input devices are typically connected to processing unit 1120 through user input interface 1160 coupled to the system bus, but can be connected by other interfaces and bus structures such as parallel ports, game ports, or universal serial bus (USB). A monitor 1191 or other type of display device is also connected to the system bus 1121 via an interface, such as a video interface 1190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 1197 and printer 1196, which may be connected through an output peripheral interface 1195.

[0267] Computer 1110 can operate in a networked environment using logical connections to one or more remote computers, such as remote computer 1180. Remote computer 1180 can be a personal computer, server, router, network PC, peer device, or other common network node, and typically includes many or all of the elements described above with respect to computer 1110, although in the example of FIG. Fig.11 Only the memory storage device 1181 is shown. Fig.11 The logical connections depicted in the diagram include a local area network (LAN) 1171 and a wide area network (WAN) 1173, but may also include other networks. Such networking environments are common in offices, enterprise-wide computer networks, intranets and the Internet.

[0268] When used in a LAN networking environment, the computer 1110 is connected to the LAN 1171 through a network interface or adapter 1170. When used in a WAN networking environment, the computer 1110 typically includes a modem 1172 or other means for establishing communications over the WAN 1173, such as the Internet. The modem 1172 may be internal or external and may be connected to the system bus 1121 via the actor input interface 1160 or other appropriate mechanism. In a networking environment, program modules depicted relative to the computer 1110, or portions thereof, may be stored in the remote memory storage device. By way of example and not limitation, Fig.11 Remote application programs 1185 are shown residing on memory device 1181. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

[0269] Having thus described several aspects of at least one embodiment of this invention, it is to be appreciated various alterations, modifications, and improvements will readily occur to those skilled in the art.

[0270] Such changes, modifications and improvements are intended to be part of the present disclosure and are intended to fall within the spirit and scope of the present invention. In addition, although the advantages of the present invention are indicated, it should be understood that not every embodiment of the technology described herein will include each described advantage. Some embodiments may not implement any feature described as advantageous herein, and in some cases, one or more of the described features may be implemented to achieve further embodiments. Therefore, the foregoing description and accompanying drawings are by way of example only.

[0271] The above-mentioned embodiments of the technology described herein can be implemented in any of a variety of ways. For example, hardware, software or a combination thereof can be used to implement these embodiments. When implemented in software, the software code can be executed on any suitable processor or processor set, whether the processor or processor set is set in a single computer or distributed in multiple computers. Such processors can be implemented as integrated circuits (wherein the integrated circuit component has one or more processors), including commercially available integrated circuit components known in the art such as CPU chips, GPU chips, microprocessors, microcontrollers or coprocessors. Alternatively, the processor can be implemented with a custom circuit system (such as ASIC) or a semi-custom circuit system generated by configuring a programmable logic device. As another alternative, the processor can be part of a larger circuit or semiconductor device, whether commercially available, semi-custom or customized. As a specific example, some commercially available microprocessors have multiple cores, so that one or a subset of these cores can constitute a processor. However, the processor can be implemented using any suitable form of circuit system.

[0272] Further, it should be understood that the computer may be embodied in any of a variety of forms, such as a rack-mounted computer, a desktop computer, a laptop computer, or a tablet computer. In addition, the computer may be embedded in a device that is not generally considered a computer but has suitable processing capabilities, including a personal digital assistant (PDA), a smart phone, or any other suitable portable or fixed electronic device.

[0273] Moreover, the computer may have one or more input devices and output devices. These devices may be used in particular for presenting a user interface. Examples of output devices that may be used to provide a user interface include a printer or display screen for visually presenting the output, and a speaker or other sound generating device for auditorily presenting the output. Examples of input devices that may be used for a user interface include a keyboard and a pointing device, such as a mouse, a touch pad, and a digitizing tablet. As another example, a computer may receive input information by speech recognition or in other auditory formats.

[0274] Such computers may be interconnected by one or more networks of any suitable form, including a local area network or a wide area network, such as an enterprise network or the Internet. Such a network may be based on any suitable technology and may operate according to any suitable protocol, and may include a wireless network, a wired network, or a fiber optic network.

[0275] In addition, the various methods or processes summarized herein can be encoded as software executable on one or more processors using any of a variety of operating systems or platforms. In addition, such software can be written using any of a variety of suitable programming languages ​​and / or programming or scripting tools, and can also be compiled into executable machine language code or intermediate code executed on a framework or virtual machine.

[0276] In this regard, the present invention may be embodied as a computer-readable storage medium (or multiple computer-readable media) encoded with one or more programs (e.g., computer memory, one or more floppy disks, compact discs (CDs), optical disks, digital video discs (DVDs), magnetic tapes, flash memory, circuit configurations in field programmable gate arrays or other semiconductor devices, or other tangible computer storage media), which, when executed on one or more computers or other processors, perform methods for implementing the various embodiments of the present invention discussed above. As will be clear from the foregoing examples, a computer-readable storage medium may retain information for a sufficient time to provide computer-executable instructions in a non-transient form. Such a computer-readable storage medium may be transportable so that one or more programs stored thereon may be loaded onto one or more different computers or other processors to implement various aspects of the present invention as discussed above. As used herein, the term "computer-readable storage medium" covers only non-transient computer-readable media that can be considered to be an article of manufacture (i.e., an article of manufacture) or a machine. Alternatively or in addition, the present invention may be embodied as a computer-readable medium other than a computer-readable storage medium, such as a propagating signal.

[0277] The term "program" or "software" is used in a general sense herein to refer to any type of computer code or computer executable instruction set that can be used to program a computer or other processor to implement various aspects of the present invention as discussed above. In addition, it should be understood that according to one aspect of this embodiment, one or more computer programs that perform the methods of the present invention when executed do not necessarily reside on a single computer or processor, but can be distributed in a modular manner among multiple different computers or processors to implement various aspects of the present invention.

[0278] Computer executable instructions may be in many forms, such as program modules, that are executed by one or more computers or other devices. Typically, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. Typically, the functionality of program modules may be combined or distributed as desired in various embodiments.

[0279] In addition, the data structure can be stored in a computer-readable medium in any suitable form. To simplify the description, the data structure can be shown as having fields that are related by position in the data structure. Such a relationship can also be achieved by assigning a location in a computer-readable medium that conveys the relationship between the fields for storage of the fields. However, any suitable mechanism can be used to establish the relationship between the information in the fields of the data structure, including by using pointers, tags, or other mechanisms that establish the relationship between data elements.

[0280] The various aspects of the present invention can be used alone, in combination, or in various arrangements not specifically discussed in the embodiments described above, and therefore its application is not limited to the details and arrangements of the components set forth in the foregoing description or shown in the accompanying drawings. For example, the aspects described in one embodiment can be combined in any manner with the aspects described in other embodiments.

[0281] Furthermore, the present invention may be embodied as a method for which examples have been provided. The actions performed as part of the method may be ordered in any suitable manner. Thus, embodiments may be constructed in which the actions are performed in an order different from the order shown, which may include performing some actions simultaneously, even though the actions are shown as sequential actions in the illustrative embodiments.

[0282] Further, some actions are described as being performed by an “actor.” It should be understood that an “actor” need not be a single individual, and in some embodiments, actions attributable to an “actor” may be performed by a team of individuals and / or a combination of individuals and computer-aided tools or other mechanisms.

[0283] The use of ordinal terms such as "first", "second", "third", etc. to modify claim elements in the claims does not itself imply any priority, superiority or order of one claim element over another claim element, or the temporal order of performance of the actions of the method, but is merely used as a label to distinguish one claim element with a specific name from another element with the same name (but using ordinal terms) to distinguish the claim elements.

[0284] In addition, the words and terms used in this article are for descriptive purposes and should not be regarded as limiting. The words "including", "comprising" or "having", "containing", "involving" and their variations used in this article are intended to cover the items listed thereafter and their equivalents, as well as other items.

Claims

1. A method for managing a workflow in a data processing system, the data processing system comprising: (i) at least one data storage device storing: a plurality of data objects and attribute values ​​thereof, the plurality of data objects including a first data object having a plurality of attributes including a first attribute; and metadata specifying relationships between at least some of the plurality of data objects by specifying one or more hierarchies of data objects including a first hierarchical structure; and (ii) a workflow management system, the workflow management system comprising: a workflow execution engine for managing execution of finite state machines (FSMs), the finite state machines comprising a first FSM associated with the first data object and for managing a first workflow of the first data object, the first FSM comprising a plurality of workflow states and a plurality of transitions corresponding to a first workflow task, the method comprising: Using the workflow management system and the first FSM associated with the first data object to manage a first workflow of the first data object by: accessing a current value of the first attribute in the at least one data storage device; identifying a first actor authorized to perform a first workflow task for the first data object using the current value of the first attribute and metadata specifying relationships between at least some of the plurality of data objects, the first workflow task corresponding to a first transition of the plurality of transitions of the first FSM, the first transition transitioning the first FSM from a first workflow state of the plurality of workflow states to a second workflow state of the plurality of workflow states, the identifying comprising: using the current value of the first attribute to determine that the first data object belongs to the first hierarchy of data objects specified by the metadata; and identifying the first actor as an actor authorized to perform the first workflow task on a second data object, the second data object being related to the first data object hierarchy in the first hierarchy; generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and In response to receiving input from the first actor through the GUI specifying that the first workflow task is to be performed: executing the first workflow task for the first data object; and By converting the first FSM from the first workflow state to the second workflow state, the current workflow state of the first FSM is updated to another workflow state.

2. The method of claim 1, wherein: The second data object is an ancestor of the first data object in the first hierarchy.

3. The method of claim 2, wherein: The second data object is a parent of the first data object in the first hierarchy.

4. The method of claim 1, further comprising: accessing a first specification of a first FSM for managing the first workflow, the first specification indicating workflow states and transitions between states in the workflow states; generating a first FSM for managing a first workflow of the first data object using the first specification; as well as The first FSM is associated with the first data object.

5. The method of claim 4, wherein: The plurality of data objects includes a second data object different from the first data object, the method further comprising: generating a second FSM for managing a first workflow of the second data object using the first specification, wherein the first FSM is different from the second FSM; and The second FSM is associated with the second data object.

6. The method of claim 1, wherein: The first data object includes a second attribute, the method comprising: generating a second FSM for managing a second workflow for changing a value of a second attribute of the first data object; and Concurrently with managing a first workflow of the first data object using the first FSM, managing a second workflow of a second attribute of the first data object using the second FSM.

7. The method of claim 1, wherein: The first workflow of the first data object is a workflow for managing changes to the first data object.

8. The method of claim 1, further comprising: When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving an input from each of a plurality of actors including the first actor, the input indicating whether the first workflow task is to be performed; as well as The first workflow task is performed for the first data object only when a majority of the plurality of actors provide input indicating that the first workflow task is to be performed.

9. At least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by a data processing system, cause the data processing system to perform a method for managing a workflow in the data processing system, the data processing system comprising: (i) at least one data storage device storing: a plurality of data objects and attribute values ​​thereof, the plurality of data objects including a first data object having a plurality of attributes including a first attribute; and metadata specifying relationships between at least some of the plurality of data objects by specifying one or more hierarchies of data objects including a first hierarchical structure; and (ii) a workflow management system, the workflow management system comprising: a workflow execution engine for managing execution of finite state machines (FSMs), the finite state machines comprising a first FSM associated with the first data object and for managing a first workflow of the first data object, the first FSM comprising a plurality of workflow states and a plurality of transitions corresponding to a first workflow task, the method comprising: Using the workflow management system and the first FSM associated with the first data object to manage the first workflow of the first data object by: accessing a current value of the first attribute in the at least one data storage device; identifying a first actor authorized to perform a first workflow task for the first data object using the current value of the first attribute and metadata specifying relationships between at least some of the plurality of data objects, the first workflow task corresponding to a first transition of the plurality of transitions of the first FSM, the first transition transitioning the first FSM from a first workflow state of the plurality of workflow states to a second workflow state of the plurality of workflow states, the identifying comprising: using the current value of the first attribute to determine that the first data object belongs to the first hierarchy of data objects specified by the metadata; and identifying the first actor as an actor authorized to perform the first workflow task on a second data object, the second data object being related to the first data object hierarchy in the first hierarchy; generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and In response to receiving input from the first actor through the GUI specifying that the first workflow task is to be performed: executing the first workflow task for the first data object; and By converting the first FSM from the first workflow state to the second workflow state, the current workflow state of the first FSM is updated to another workflow state.

10. The non-transitory computer-readable storage medium of claim 9, wherein: The second data object is an ancestor of the first data object in the first hierarchy.

11. The non-transitory computer-readable storage medium of claim 9 or 10, wherein: The second data object is a parent of the first data object in the first hierarchy.

12. The non-transitory computer-readable storage medium of claim 9, wherein: The method further comprises: accessing a first specification of a first FSM for managing the first workflow, the first specification indicating workflow states and transitions between states in the workflow states; generating a first FSM for managing a first workflow of the first data object using the first specification; and The first FSM is associated with the first data object.

13. The non-transitory computer-readable storage medium of claim 12, wherein: The plurality of data objects includes a second data object different from the first data object, wherein the method further comprises: generating a second FSM for managing a first workflow of the second data object using the first specification, wherein the first FSM is different from the second FSM; and The second FSM is associated with the second data object.

14. The non-transitory computer-readable storage medium of claim 9, wherein: The first data object includes a second attribute, wherein the method further comprises: generating a second FSM for managing a second workflow for changing a value of a second attribute of the first data object; and Concurrently with managing a first workflow of the first data object using the first FSM, managing a second workflow of a second attribute of the first data object using the second FSM.

15. The non-transitory computer-readable storage medium of claim 9, wherein: The first workflow of the first data object is a workflow for managing changes to the first data object.

16. The non-transitory computer-readable storage medium of claim 9, wherein: The method further comprises: When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input from each of a plurality of actors including the first actor, the input indicating whether the first workflow task is to be performed; and The first workflow task is performed for the first data object only when a majority of the plurality of actors provide input indicating that the first workflow task is to be performed.

17. A data processing system comprising: at least one computer hardware processor; at least one data storage device storing: a plurality of data objects and attribute values ​​thereof, the plurality of data objects including a first data object having a plurality of attributes including a first attribute; and metadata specifying relationships between at least some of the plurality of data objects by specifying one or more hierarchies of data objects including a first hierarchy; as well as A workflow management system, the workflow management system comprising: a workflow execution engine for managing the execution of finite state machines (FSMs), the finite state machines comprising a first FSM associated with the first data object and for managing a first workflow of the first data object, the first FSM comprising a plurality of workflow states and a plurality of transitions corresponding to a first workflow task, wherein the workflow management system is configured to use the at least one computer hardware processor to perform a method comprising: Using the workflow management system and the first FSM associated with the first data object to manage a first workflow of the first data object by: accessing a current value of the first attribute in the at least one data storage device; identifying a first actor authorized to perform a first workflow task for the first data object using the current value of the first attribute and metadata specifying relationships between at least some of the plurality of data objects, the first workflow task corresponding to a first transition of the plurality of transitions of the first FSM, the first transition transitioning the first FSM from a first workflow state of the plurality of workflow states to a second workflow state of the plurality of workflow states, the identifying comprising: using the current value of the first attribute to determine that the first data object belongs to the first hierarchy of data objects specified by the metadata; and identifying the first actor as an actor authorized to perform the first workflow task on a second data object, the second data object being related to the first data object hierarchy in the first hierarchy; generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task; and In response to receiving input from the first actor through the GUI specifying that the first workflow task is to be performed: executing the first workflow task for the first data object; and By converting the first FSM from the first workflow state to the second workflow state, the current workflow state of the first FSM is updated to another workflow state.

18. The data processing system of claim 17, wherein: The second data object is an ancestor of the first data object in the first hierarchy.

19. The data processing system according to claim 17 or 18, wherein: The second data object is a parent of the first data object in the first hierarchy.

20. The data processing system of claim 17, wherein: The method further comprises: accessing a first specification of a first FSM for managing the first workflow, the first specification indicating workflow states and transitions between states in the workflow states; generating a first FSM for managing a first workflow of the first data object using the first specification; and The first FSM is associated with the first data object.

21. The data processing system of claim 20, wherein: The plurality of data objects includes a second data object different from the first data object, wherein the method further comprises: generating a second FSM for managing a first workflow of the second data object using the first specification, wherein the first FSM is different from the second FSM; and The second FSM is associated with the second data object.

22. The data processing system of claim 17, wherein: The first data object includes a second attribute, wherein the method further comprises: generating a second FSM for managing a second workflow for changing a value of a second attribute of the first data object; and Concurrently with managing a first workflow of the first data object using the first FSM, managing a second workflow of a second attribute of the first data object using the second FSM.

23. The data processing system of claim 17, wherein: The first workflow of the first data object is a workflow for managing changes to the first data object.

24. The data processing system of claim 17, wherein: The method further comprises: When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input from each of a plurality of actors including the first actor, the input indicating whether the first workflow task is to be performed; and The first workflow task is performed for the first data object only when a majority of the plurality of actors provide input indicating that the first workflow task is to be performed.

25. A system for managing a workflow of a first data object of a plurality of data objects using a first finite state machine (FSM), the first FSM having a first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first workflow state and the second workflow state, the first transition representing a first workflow task in the first workflow, the system comprising: at least one computer hardware processor; as well as At least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by the at least one computer hardware processor, cause the at least one computer hardware processor to: identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; as well as When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input from the first actor specifying that the first workflow task is to be performed; Executing the first workflow task for the first data object; as well as The first FSM is updated to indicate that the current workflow state of the first workflow is the second workflow state.

26. The system of claim 25, wherein: Objects of the plurality of data objects are organized into one or more hierarchies, and wherein the at least one attribute indicates at least one hierarchy of the one or more hierarchies to which the first data object belongs.

27. The system of claim 26, wherein: Identifying the first actor includes: The first actor is identified using information specified for at least one other data object related to the first data object in the at least one hierarchy.

28. The system of claim 26, wherein: Identifying the first actor includes: The first actor is identified as an actor authorized to perform the first workflow task for at least one other data object in the at least one hierarchy that is related to the first data object.

29. The system of claim 28, wherein: The first data object has an ancestor data object in the at least one hierarchy, and wherein identifying the first actor comprises: The first actor is identified as an actor authorized to perform the first workflow task for the ancestor data object.

30. The system of claim 29, wherein: The ancestor data object is a parent of the first data object in the at least one hierarchical structure.

31. The system of claim 25, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: accessing a first specification of a finite state machine for managing the first workflow, the first specification indicating the first set of workflow states and a first set of transitions between states in the first set of workflow states; as well as A first FSM for managing a first workflow of the first data object is generated using the first specification.

32. The system of claim 31, wherein: The plurality of data objects includes a second data object different from the first data object, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: A second FSM for managing a first workflow of the second data object is generated using the first specification, wherein the first FSM is different from the second FSM.

33. The system of claim 32, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: A second actor authorized to perform the first workflow task for the second data object is identified from the plurality of actors and using at least one value of at least one attribute of the second data object, wherein the second actor is different from the first actor.

34. The system of claim 33, wherein: The first data object is in a first object hierarchy and the second data object is in a second object hierarchy different from the first object hierarchy, and wherein identifying the second actor comprises identifying the second actor from actors associated with one or more data objects in the second object hierarchy.

35. The system of claim 33, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: receiving input from the second actor specifying that the first workflow task is to be performed; executing the first workflow task for the second data object; as well as The second FSM is updated to indicate that the current workflow state of the first workflow of the second data object is the second workflow state.

36. The system of claim 25, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: A graphical user interface (GUI) is generated through which the first actor can provide input specifying that the first workflow task is to be performed.

37. The system of claim 25, wherein: The first data object has a first attribute, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: generating a second FSM', ie, an auxiliary FSM, for a second workflow for managing the first attribute of the first data object; and Concurrently with managing the first workflow of the first data object using the first FSM, the second workflow of the first attribute of the first data object is managed using the second FSM', ie, the auxiliary FSM.

38. The system of claim 37, wherein: The first data object has a second attribute, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: generating a third FSM for a third workflow for managing a second attribute of the first data object; and Simultaneously with the first workflow using the first FSM to manage the first data object and the second workflow using the second FSM', ie the auxiliary FSM, to manage the first attribute of the first data object, the third workflow using the third FSM to manage the second attribute of the first data object.

39. The system of claim 25, wherein: The first data object has a first attribute, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: generating a second FSM', ie, an auxiliary FSM, for managing a second workflow for changing the value of the first attribute of the first data object; and Concurrently with managing the first workflow of the first data object using the first FSM, the second FSM', ie the auxiliary FSM, is used to manage the workflow for changing the value of the first attribute of the first data object.

40. The system of claim 25, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: A graphical user interface is generated indicating a current state of the first FSM of the first data object and a current state of a second FSM', ie, an auxiliary FSM, for managing a workflow for changing a value of a first attribute of the first data object.

41. The system of claim 37, wherein: The first data object represents a business term, and wherein the first attribute is selected from the group consisting of: a hierarchy of the business term, a classification of the business term, a value of the business term, an indication of valid values ​​of the business term, and an actor associated with the business term.

42. The system of claim 25, wherein: The first workflow of the first data object is a workflow for managing changes to the first data object.

43. The system of claim 25, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving an input from each of a plurality of actors including the first actor, the input indicating whether the first workflow task is to be performed; as well as The first workflow task is performed for the first data object only when a majority of the plurality of actors provide input indicating that the first workflow task is to be performed.

44. The system of claim 25, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving an input from each of a plurality of actors including the first actor, the input indicating whether the first workflow task is to be performed; as well as The first workflow task is performed for the first data object only when each of the plurality of actors provides input indicating that the first workflow task is to be performed.

45. The system of claim 25, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state and before receiving the input from the first actor, receiving input from a plurality of actors excluding the first actor, the input indicating whether the first workflow task is to be performed; as well as Input received from the plurality of actors is provided to the first actor via a graphical user interface.

46. ​​A method for managing a workflow of a first data object of a plurality of data objects using a first finite state machine (FSM), the first FSM having a first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first workflow state and the second workflow state, the first transition representing a first workflow task in the first workflow, the method comprising: Use at least one computer hardware processor to do the following: identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; as well as When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input from the first actor specifying that the first workflow task is to be performed; Executing the first workflow task for the first data object; as well as The first FSM is updated to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

47. At least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by at least one computer hardware processor, cause the at least one computer hardware processor to perform a method for managing a workflow of a first data object of a plurality of data objects using a first finite state machine (FSM), the first FSM having a first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first workflow state and the second workflow state, the first transition representing a first workflow task in the first workflow, the method comprising: identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; as well as When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, receiving input from the first actor specifying that the first workflow task is to be performed; Executing the first workflow task for the first data object; as well as The first FSM is updated to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

48. A method for managing a workflow of a plurality of data objects including a first data object, the method comprising: Use at least one computer hardware processor to do the following: A first finite state machine (FSM) is generated using a first specification of the FSM for a first workflow for managing a first set of data objects, the first specification indicating: A first set of workflow states including a first workflow state and a second workflow state; and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first workflow state and the second workflow state, the first transition representing a first workflow task in the first workflow; as well as When the first FSM indicates that the current workflow state of the first workflow of the first group of data objects is the first workflow state, identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; receiving, from the first actor authorized to perform a first workflow task corresponding to a first transition between the first workflow state and the second workflow state, input specifying that the first workflow task is to be performed; Executing the first workflow task for the first data object; as well as The first FSM is updated to indicate that a current workflow state of the first workflow of the first set of data objects is the second workflow state.

49. At least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by at least one computer hardware processor, cause the at least one computer hardware processor to: generating a first finite state machine (FSM) for a first workflow of a first data object of the plurality of data objects; identifying a first actor authorized to perform a first workflow task associated with a first transition from the first workflow state to a second workflow state using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; When the first FSM indicates that the current workflow state of the first workflow is the first workflow state, generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task, and The GUI is presented to the first actor.

50. The non-transitory computer readable storage medium of claim 49, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: receiving, through the generated GUI, input provided by the first actor, the input specifying that the first workflow task is to be performed; Executing the first workflow task for the first data object; as well as The first FSM is updated to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

51. The non-transitory computer readable storage medium of claim 49 or 50, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: In response to updating the first FSM to indicate that the current workflow state of the first data object is the second workflow state, identifying a second actor authorized to perform a second workflow task associated with a second transition from the second workflow state to a third workflow state; as well as The second actor and / or the third actor are notified that there is a workflow task for the second actor to perform.

52. The non-transitory computer readable storage medium of claim 51, wherein: Notifying the second actor includes sending an email notification to the actor and / or providing a visual notification to the actor through a graphical user interface.

53. The non-transitory computer readable storage medium of claim 49, wherein: Objects of the plurality of data objects are organized into one or more hierarchies, and wherein the at least one attribute indicates at least one hierarchy of the one or more hierarchies to which the first data object belongs.

54. The non-transitory computer readable storage medium of claim 53, wherein: Identifying the first actor includes: The first actor is identified as an actor authorized to perform the first workflow task for at least one other data object in the at least one hierarchy.

55. The non-transitory computer readable storage medium of claim 53 or 54, wherein: The first data object has a parent data object in the at least one hierarchy, and wherein identifying the first actor comprises: The first actor is identified as an actor authorized to perform the first workflow task for the parent data object.

56. The non-transitory computer readable storage medium of claim 49 or 50, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: accessing a first specification of a finite state machine for managing the first workflow, the specification indicating a set of workflow states and a set of transitions between states in the set of workflow states; and A first FSM for managing a first workflow of the first data object is generated using the accessed first specification.

57. The non-transitory computer readable storage medium of claim 49 or 50, wherein: The first data object has a first attribute, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: generating a second FSM for a second workflow for managing the first attribute of the first data object; and Concurrently with managing a first workflow of the first data object using the first FSM, managing a second workflow of the first attribute of the first data object using the second FSM.

58. The non-transitory computer readable storage medium of claim 57, wherein: The first data object has a second attribute, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: generating a third FSM for a third workflow for managing a second attribute of the first data object; and Concurrently with the first workflow using the first FSM to manage the first data object and the second workflow using the second FSM to manage the first attribute of the first data object, the third workflow using the third FSM to manage the second attribute of the first data object.

59. The non-transitory computer readable storage medium of claim 49 or 50, wherein: Generating the GUI involves: A graphical user interface is generated that indicates a current state of a first FSM for the first data object and a current state of a second FSM for managing a workflow for changing a value of a first attribute of the first data object.

60. The non-transitory computer readable storage medium of claim 57, wherein: The first data object represents a business term, and wherein the first attribute is selected from the group consisting of: a hierarchy of the business term, a classification of the business term, a value of the business term, an indication of valid values ​​of the business term, and an actor associated with the business term.

61. A method for workflow, comprising: Use at least one computer hardware processor to do the following: generating a first finite state machine (FSM) for a first workflow of a first data object of the plurality of data objects; identifying a first actor authorized to perform a first workflow task associated with a first transition from the first workflow state to a second workflow state using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; When the first FSM indicates that the current workflow state of the first workflow is the first workflow state, generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task, and The GUI is presented to the first actor.

62. A system for workflow, comprising: at least one computer hardware processor; as well as At least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by the at least one computer hardware processor, cause the at least one computer hardware processor to: generating a first finite state machine (FSM) for a first workflow of a first data object of the plurality of data objects; identifying a first actor authorized to perform a first workflow task associated with a first transition from the first workflow state to a second workflow state using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; When the first FSM indicates that the current workflow state of the first workflow is the first workflow state, generating a graphical user interface (GUI) through which the first actor can provide input to perform the first workflow task, and The GUI is presented to the first actor.

63. At least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by at least one computer hardware processor, cause the at least one computer hardware processor to: generating a first FSM for managing a first workflow for changing a value of an attribute of a first data object in a plurality of data objects, the generating being performed using a specification indicating a first set of workflow states, the first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first workflow state and the second workflow state, the first transition representing a first workflow task in the first workflow; as well as When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; receiving, from a first actor authorized to perform a first workflow task corresponding to a first transition between the first workflow state and the second workflow state, an input specifying that the first workflow task is to be performed; Executing the first workflow task for the first data object; as well as The first FSM is updated to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

64. The non-transitory computer readable storage medium of claim 63, wherein: The plurality of data objects includes a second data object different from the first data object, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: A second FSM for managing the first workflow of the second data object is generated using the specification, wherein the first FSM is different from the second FSM.

65. The non-transitory computer readable storage medium of claim 64, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: When the second FSM indicates that the current workflow state of the first workflow of the second data object is the first workflow state, receiving, from a second actor authorized to perform a first workflow task corresponding to a first transition between the first workflow state and the second workflow state, an input specifying that the first workflow task is to be performed; executing the first workflow task for the second data object; as well as The second FSM is updated to indicate that the current workflow state of the first workflow of the second data object is the second workflow state.

66. The non-transitory computer readable storage medium of claim 63 or 64, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: A plurality of FSMs are generated for managing a plurality of corresponding workflows for a plurality of corresponding data objects among the plurality of data objects.

67. The non-transitory computer readable storage medium of claim 63 or 64, wherein: The processor-executable instructions further cause the at least one computer hardware processor to: When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, identifying the first actor from a plurality of actors as an actor authorized to perform the first workflow task for the first data object using at least one value of at least one attribute of the first data object, generating a graphical user interface (GUI) through which the first actor can provide input to execute the first workflow, and An input specifying that the first workflow task is to be executed is received through the generated GUI.

68. The non-transitory computer readable storage medium of claim 63 or 64, wherein: The first data object has a first attribute, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: generating a second FSM', ie, an auxiliary FSM, for a second workflow for managing the first attribute of the first data object; and Concurrently with managing the first workflow of the first data object using the first FSM, the second workflow of the first attribute of the first data object is managed using the second FSM', ie, the auxiliary FSM.

69. The non-transitory computer readable storage medium of claim 68, wherein: The first data object has a second attribute, and wherein the processor-executable instructions further cause the at least one computer hardware processor to: generating a third FSM for a third workflow for managing a second attribute of the first data object; and Simultaneously with the first workflow using the first FSM to manage the first data object and the second workflow using the second FSM', ie the auxiliary FSM, to manage the first attribute of the first data object, the third workflow using the third FSM to manage the second attribute of the first data object.

70. A data processing system comprising: at least one computer hardware processor; as well as At least one non-transitory computer-readable storage medium storing processor-executable instructions that, when executed by the at least one computer hardware processor, cause the at least one computer hardware processor to: generating a first FSM for managing a first workflow for changing a value of an attribute of a first data object in a plurality of data objects, the generating being performed using a specification indicating a first set of workflow states, the first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first workflow state and the second workflow state, the first transition representing a first workflow task in the first workflow; as well as When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; receiving, from a first actor authorized to perform a first workflow task corresponding to a first transition between the first workflow state and the second workflow state, an input specifying that the first workflow task is to be performed; Executing the first workflow task for the first data object; as well as The first FSM is updated to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

71. A method for workflow, comprising: Use at least one computer hardware processor to do the following: generating a first FSM for managing a first workflow for changing a value of an attribute of a first data object in a plurality of data objects, the generating being performed using a specification indicating a first set of workflow states, the first set of workflow states including a first workflow state and a second workflow state and a first set of transitions between the first set of workflow states, the first set of transitions representing tasks in the first workflow and including a first transition between the first workflow state and the second workflow state, the first transition representing a first workflow task in the first workflow; as well as When the first FSM indicates that the current workflow state of the first workflow of the first data object is the first workflow state, identifying a first actor authorized to perform the first workflow task for the first data object from among a plurality of actors and using at least one value of at least one attribute of the first data object and metadata specifying relationships between at least some of the plurality of data objects; receiving, from a first actor authorized to perform a first workflow task corresponding to a first transition between the first workflow state and the second workflow state, an input specifying that the first workflow task is to be performed; Executing the first workflow task for the first data object; as well as The first FSM is updated to indicate that the current workflow state of the first workflow of the first data object is the second workflow state.

72. A computer program product comprising a computer program which, when executed by a processor, performs the method according to any one of claims 1-8, 46, 48, 61, 71.