JP7508690B2 - Multi-Process Workflow Designer - Google Patents

Description

Digitizing a workflow process can often increase the efficiency of completing the process. For example, converting a series of tasks into a digitized, automated process can save significant time and a significant amount of resources. This can be especially true when the tasks are complex, repetitive, and/or involve many individual steps. Typically, workflows are digitized by a programmer and/or a person with intrinsic knowledge of the digital tools used to execute the digitized workflow. Transformation can be applied to a variety of different tasks, such as business processes, structured activities that require a specific sequence, process-oriented goals, and the like. In many instances, digitizing and automating a task can result in a more robust user experience.

Various embodiments of the present invention are disclosed in the following detailed description and accompanying drawings.

FIG. 1 is a block diagram illustrating an example network environment for creating and utilizing a multi-process workflow solver.

1 is a flow diagram illustrating an embodiment of a process for creating a digital multi-process workflow solution.

1 is a flow diagram illustrating an embodiment of a workflow design tool process.

1 is a flow diagram illustrating an embodiment of a process for modifying execution conditions of processes of a multi-process workflow solver using a workflow design tool.

1 is a flow diagram illustrating an embodiment of a process for adding a new activity to a process of a multi-process workflow solver using a workflow design tool.

1 is a flow diagram illustrating an embodiment of a process for adding a new multi-process workflow solver using a workflow design tool.

FIG. 13 is a diagram illustrating an example of a user interface of a workflow design tool. FIG. 13 is a diagram illustrating an example of a user interface of a workflow design tool.

FIG. 13 is a diagram illustrating an example of a user interface of a workflow design tool.

FIG. 1 illustrates an example of a user interface of a workflow design tool for advanced configuration of a process.

FIG. 2 illustrates an example of a user interface of a workflow design tool for adding a new activity to a process.

FIG. 13 is a diagram illustrating an example of a user interface of a workflow design tool for creating an activity definition.

FIG. 2 illustrates an example of a user interface of a workflow design tool for displaying process execution.

FIG. 2 illustrates an example of a user interface of a workflow design tool for displaying process execution.

FIG. 13 is a diagram illustrating an example of a user interface of a workflow design tool for selecting reference data.

FIG. 13 illustrates an example of a user interface of a workflow design tool for selecting an activity.

The present invention can be implemented in numerous ways, including as a process, an apparatus, a system, a composition, a computer program product embodied in a computer-readable storage medium, and/or as a processor, such as a processor configured to execute instructions stored and/or provided by a memory coupled to the processor. These implementations, or any other form the present invention may take, may be referred to herein as techniques. In general, the order of steps of the disclosed processes may be varied within the scope of the present invention. Unless otherwise specified, components such as a processor or memory described as being configured to perform a task may be implemented as general components that are temporarily configured to perform the task at a given time, or as specific components manufactured to perform the task. As used herein, the term "processor" refers to one or more devices, circuits, and/or processing cores that are configured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the present invention is provided below along with accompanying figures illustrating the principles of the present invention. Although the present invention will be described in connection with such embodiments, the present invention is not limited to any embodiment. The scope of the present invention is limited only by the claims, and the present invention encompasses numerous alternatives, modifications, and equivalents. In order to provide a thorough understanding of the present invention, numerous specific details are set forth in the following description. These details are provided for illustrative purposes, and the present invention may be practiced according to the claims without some or all of these specific details. For purposes of clarity, technical material that is known in the art related to the present invention has not been described in detail so as not to unnecessarily obscure the present invention.

Techniques are disclosed for digitizing and automating workflow processes. For example, multi-process workflows can be digitized and automated to run on software-as-a-service (SaaS) platforms. Examples of multi-process workflows that can be digitized and automated include workflows related to onboarding new employees, prioritizing customer incidents, and sourcing new products, among others. Multi-process workflows are particularly complex in part because they may span different departments and divisions and require coordination of all involved parties. As described herein, the disclosed techniques include the ability to easily create and visualize multi-process workflows without requiring programming knowledge that is typically required to build software applications. The techniques enable a person with limited knowledge of digital platforms to create automated versions of digital workflows, including enabling the combination of processes that interact with different parties.

In various embodiments, the disclosed techniques address the technical challenges of digitizing and automating multi-process workflows. Non-savvy users can easily create and visualize multi-process workflows that include many activities that make up each process. Little programming ability is required to create a corresponding application that can be hosted as a SaaS application, such as a web service, and accessed by users via a web browser. In some embodiments, a user interface for a multi-process workflow design tool includes different lanes or workflow item grouping containers that group containers for each process of the multi-process workflow. For example, the steps of a first process of the multi-process workflow are contained within a first workflow item grouping container. The steps of a second process of the multi-process workflow are contained within a second workflow item grouping container. The steps of a third process of the multi-process workflow are contained within a third workflow item grouping container, and so on. Users can add or remove workflow item grouping containers as needed to add or remove processes from the workflow. Complex multi-process workflows can contain four, five, or more workflow item grouping containers. In various embodiments, the workflow item grouping containers and their corresponding workflow items can also be reordered, for example, by dragging and dropping the containers using a visual user interface. Similarly, the individual workflow items within each container can be reordered by dragging and dropping the items using a visual user interface. The workflow item grouping containers can also be configured by manipulating the user interface components that represent each workflow item grouping container. In various embodiments, the workflow items in each workflow item grouping container are the different activities (e.g., steps or tasks) that make up the process represented by the workflow item grouping container.

In some embodiments, each workflow item grouping container has its own execution conditions. The configured execution conditions control the execution of the workflow item grouping container, such as when and under what conditions the workflow item grouping container should be executed. For example, by configuring the execution conditions, different workflow item grouping containers can be executed sequentially or in parallel, allowing different processes in a multi-process workflow to proceed sequentially or in parallel. Other settings can be configured as well. For example, the workflow items of a workflow item grouping container can be configured to be executed only when certain conditions are met, such as only after a certain start delay has passed and/or only after dependencies or conditions have been met. In some embodiments, the execution conditions include one or more action plans. The action plans can be created to comprise start plans, end plans, and restart plans. In some embodiments, each plan can have different start conditions. The operation of the different configurations is modifiable via the provided user interface.

In some embodiments, the user interface includes a user interface component that displays the workflow items of each workflow item grouping container. For example, each workflow item corresponds to a different activity of the process and is displayed as its own user interface component with its own configurable specifications. As an example of an activity of a single process of a multi-process workflow, a first workflow item of the workflow item grouping container may correspond to sending an initial email communication, a second workflow item of the workflow item grouping container may correspond to creating a shared online chat channel, and a third workflow item of the workflow item grouping container may correspond to initiating a conference call. Other examples of workflow items may include performing different tasks, such as running scripts, sending notifications, and requesting approvals, among others. Each workflow item belongs to a workflow item grouping container and is also individually configurable. For example, in some embodiments, each workflow item has an execution condition that is individually configurable. A workflow item can be configured to run immediately, after a preceding activity, together with a preceding activity, or using another appropriate configuration option. In various embodiments, the configuration settings are visually represented using user interface components of the workflow item and can be modified through the provided user interface. The provided user interface allows workflow configuration not only at the workflow item level granularity but also at the workflow item grouping container level granularity. In various embodiments, modifications of the workflow item grouping container apply to the set of workflow items belonging to that container, while modifications of each workflow item apply only to the workflow item itself.

In some embodiments, the workflow design tool includes a user interface for easily visualizing and modifying the creation of the multi-process workflow solver. Each process of the multi-process workflow can be represented as a group of workflow items and can correspond to a different workflow item grouping container (or lane). In some embodiments, an identification of a first workflow item grouping container is received. The first workflow item grouping container is part of a collection of workflow item grouping containers that organize the end-to-end multi-process workflow solver. The first workflow item grouping container corresponds to a single process of the multi-process workflow and is displayed as a user interface component as part of the workflow design tool. The first workflow item grouping container can contain activities related to the first process of the multi-process workflow solver. In some embodiments, an identification of a second workflow item grouping container is received, the second workflow item grouping container is part of a collection of workflow item grouping containers of the end-to-end multi-process workflow solver. For example, the second workflow item grouping container corresponds to another single process of the multi-process workflow and is also displayed as a user interface component as part of the workflow design tool. The second workflow item grouping container can contain activities related to a second process of the multi-process workflow.

In some embodiments, receive execution conditions for a first workflow item grouping container and receive execution conditions for a second workflow item grouping container. For example, each workflow item grouping container has its own execution conditions. The execution conditions can specify the conditions for executing the workflow items of the workflow item grouping container. For example, the execution conditions can include start condition settings such as specifying that the workflow item grouping container should start immediately, with a preceding workflow item grouping container, after a preceding workflow item grouping container, with a dependency condition, and after a dependency condition, among other reasonable configurations. For example, a workflow item group can be configured to start when a preceding workflow item in another workflow item group starts or when a preceding workflow item in another workflow item group ends. With respect to the dependency condition, the workflow item group can be configured to start when a dependent task starts or when a dependent task ends. In some embodiments, the start can be configured with a delay and/or based on a certain condition. For example, a fixed time delay can be configured as part of the execution conditions. As another example, the workflow item group can be configured to start only after a certain condition is met. The condition may be based on a trigger record, the output of another preceding activity, or another configured condition.

In some embodiments, a specification of one or more workflow items belonging to a first workflow item grouping container is received. Each workflow item belonging to the first workflow item grouping container has an individually configurable execution condition and corresponds to a different individual activity of the end-to-end multi-process workflow solver. Similarly, a specification of one or more workflow items belonging to a second workflow item grouping container is received. Each workflow item belonging to the second workflow item grouping container has an individually configurable execution condition and corresponds to a different individual activity of the end-to-end multi-process workflow solver. In various embodiments, each workflow item belonging to the workflow item grouping container has its own individually configurable execution condition. For example, an activity associated with a workflow item can be configured with an execution condition that specifies a start condition setting. Examples of different start condition settings can include, among others, a configuration to start an activity immediately, a configuration to start an activity with a preceding activity, a configuration to start an activity after a preceding activity, a configuration to start an activity based on a dependency, and a configuration to start an activity after a dependency is satisfied. In various embodiments, each workflow item is displayed as a user interface component associated with its workflow item grouping container. Once the workflow design tool has been used to illustrate the multi-process workflow, an application that implements the workflow can be generated. For example, a web service application can be generated and hosted as a SaaS application. In various embodiments, the user interface of the workflow design tool can be rendered to the user as part of a web service via a web browser or another suitable application. Similarly, the generated web service can be accessed via a web browser or another suitable application.

In some embodiments, a user-modifiable user interface representation of a first workflow item grouping container is provided. The first workflow item grouping container is part of a collection of workflow item grouping containers that organize the design of an end-to-end multi-process workflow solution. Similarly, a user-modifiable user interface representation of a second workflow item grouping container is provided. The second workflow item grouping container is part of a collection of workflow item grouping containers that organize the design of an end-to-end multi-process workflow solution. The user interface representations of the first workflow item grouping container and the second workflow item grouping container allow a user to modify the execution conditions, ordering, or other properties of the corresponding container and the corresponding workflow items of the corresponding container. Each workflow item of each workflow item grouping container is similarly modifiable via an interactive user interface representation. In various embodiments, an interactive user interface representation of the first workflow items belonging to the first workflow item grouping container is provided. The first workflow items correspond to different individual activities of the end-to-end multi-process workflow solver, and the user can interact with the interactive user interface representation of the first workflow items to modify the workflow characteristics of the first workflow items. For example, the user can modify the start conditions and/or execution conditions of each workflow item using the interactive user interface representation of the items. In various embodiments, an interactive user interface representation of a second workflow item belonging to a second workflow item grouping container is provided. The second workflow items correspond to different individual activities of the end-to-end multi-process workflow solver, and the user can interact with the interactive user interface representation of the second workflow items to modify the workflow characteristics of the second workflow items. For example, the user can modify the start conditions and/or execution conditions of the second workflow items using the interactive user interface representation of the second workflow items without modifying the characteristics of the first workflow items.

FIG. 1 is a block diagram illustrating an example of a network environment for creating and utilizing a multi-process workflow solver. In the illustrated example, clients 101, 103, and 105 access services on application server 121 via network 111. The services can include applications generated to implement the designed multi-process workflow solver as well as automation design tools for creating multi-process workflows. Network 111 can be a public or private network. In some embodiments, network 111 is a public network such as the Internet. In various embodiments, clients 101, 103, and 105 are network clients such as web browsers for accessing web services. Application server 121 provides web services including web applications. Application server 121 may utilize database 123 to provide certain services and/or to store data related to the automation design tools. For example, database 123 may be a configuration management database (CMDB) used by application server 121 to provide a CMDB related to the multi-process workflow solution. Among other information, database 123 may store configuration information related to managed assets, such as related hardware and/or software configurations. Database 123 may also be used to store information related to process configurations and process activities of the multi-process workflow.

In some embodiments, each of clients 101, 103, and 105 can access application server 121 to create custom workflows involving multiple processes. The application server provides interactive visual design tools to clients such as clients 101, 103, and 105. Using the visual design tools, a multi-process workflow can be designed by a user and a corresponding application is created. The visual design tools allow a user to create a digitized workflow without having to write any software or programming code. In some embodiments, the application generated from the visual design tools is a web service hosted on application server 121. A user can access the created application via a client such as clients 101, 103, and 105. In some embodiments, each of clients 101, 103, and 105 can be a network client running on one of many different computing devices including laptops, desktops, mobile devices, tablets, kiosks, smart TVs, etc.

Although single instances of some components have been shown to simplify the illustration, more instances of any of the components shown in FIG. 1 may be present. For example, application server 121 may include one or more servers. Similarly, database 123 may not be directly connected to application server 121 and/or may be replicated or distributed across multiple components. As another example, clients 101, 103, and 105 are only a few examples of possible clients leading to application server 121. Fewer or more clients may be connected to application server 121. In some embodiments, components not shown in FIG. 1 may also be present.

2 is a flow diagram illustrating an embodiment of a process for creating a digital multi-process workflow solution. In the illustrated example, the workflow is created using an interactive visual design tool. The created workflow is at least partially automated via a generated computer application that can be accessed via a digital device such as a web browser. Using the process of FIG. 2, multi-process workflows can be easily digitized and bridge processes that require coordination by multiple parties. In some embodiments, the process of FIG. 2 is executed on an application server, such as application server 121 of FIG. 1. The application server may utilize and/or store workflow data in a database, such as database 123 of FIG. 1. In some embodiments, the design tool is accessed by a client, such as clients 101, 103, and/or 105 of FIG. 1. Moreover, once the design is completed, a generated application that implements the workflow can be hosted on an application server, such as application server 121 of FIG. 1, and accessed by clients, such as clients 101, 103, and/or 105 of FIG. 1.

In various embodiments, the process of FIG. 2 is used to digitize a multi-process workflow. For example, onboarding a new employee can be implemented as a multi-process workflow solver. The workflow can include a first process for coordinating with a new manager, a second process for coordinating with HR, and a third process for coordinating with the Information Technology department. In some scenarios, additional, fewer, or different processes may be required. The process of FIG. 2 is used to create each process of the multi-process workflow solver and to add and configure the activities that make up each process. Using the previous example, a first process for coordinating with HR may require three different activities. The activities may include tasks such as sending an email to a human resources contact, registering the new employee for a HR orientation meeting, and completing a HR survey. Each activity is a workflow item and belongs to a workflow item grouping container that describes the first process. In various embodiments, each workflow item grouping container and the associated workflow item are visually displayed via a user interface. New processes can be added and existing processes can be modified (including removed). Similarly, new activities can be added to a process and existing activities can be modified (including removed). Multi-process workflows are created using visual design tools, and automated digital workflows can be generated as application services.

As another example, a user can create a digitized version of a multi-process manufacturing workflow. Using the process of FIG. 2 and the techniques disclosed herein, the workflow can be automated using a computer application generated by a workflow design tool. An example manufacturing workflow can include multiple processes such as welcome & setup, feasibility, provisioning, installation, and billing effectuation processes. Each of the processes can include multiple activities. For example, the welcome & setup process can include activities to send a welcome email to the primary customer contact, provide login instructions and setup guides, and set up the customer contact. The feasibility process can include activities to coordinate schedule with customer/vendor, dispatch on-site inspection, perform on-site inspection, complete inspection, coordinate schedule with customer/vendor, dispatch for on-site re-inspection, and perform on-site re-inspection. The provisioning process can include activities to obtain authorization and coordinate with vendor/supplier. The installation process can include activities to plan for installation, coordinate schedule with customer, dispatch installation personnel, and perform installation. The billing activation process may include activities to obtain customer signatures, renew warranties, and initiate claims. Each of the processes and/or activities may be assigned to different responsible parties. The workflow design tool allows the user to visually connect separate tasks into a common integrated multi-process workflow and generate digital automated computer application processes to implement the workflow solution.

At 201, the creation of a multi-process workflow begins. For example, a visual design tool is used to create a new multi-process workflow or load an existing multi-process workflow. In some embodiments, the created multi-process workflow is based on an existing workflow or workflow template. In various embodiments, each multi-process workflow corresponds to one or more database records. For example, a database record is created for each workflow to store information for that particular workflow. The records can be used to persist the workflow across user sessions and to generate application programs. In various embodiments, a workflow item grouping container is associated with each process of the multi-process workflow.

At 203, create and/or modify one of the processes of the multi-process workflow. A visual design tool is used to add or modify a multi-process workflow process. The process can be one of many processes of the workflow. Each process is associated with a workflow item grouping container that is used to contain the related activities (or workflow items) of the process. In some embodiments, each workflow item grouping container is displayed as a visual process lane. In various embodiments, each process can have its own configurable execution conditions. At 203, one of the processes can be configured. For example, modify the execution conditions of the process. In some embodiments, configuring the execution conditions includes configuring a start condition. Examples of start conditions include starting the process immediately, starting the process with a preceding process, starting the process after a preceding process, starting the process with a configured dependency (such as when a dependent task starts), and starting the process after a configured dependency is satisfied (such as when a dependent task finishes). Other start conditions may be valid as well. In various embodiments, the visual user interface allows the user to easily configure the conditions. As another example, a delay can be configured so that the process starts only after the delay has elapsed. For example, a process can be delayed by a time value, such as 5 seconds, 5 minutes, 1 day, 1 week, or another reasonable amount of time. As another example, a process can be delayed to start only after dependencies are satisfied. In some embodiments, execution conditions can be configured that are independent of when a process starts. For example, conditions can be configured to control whether a process lane is enabled and whether a process lane should be omitted.

In some embodiments, action plans for the processes can also be configured at 203. For example, each process can have one or more action plans. Different action plans can be configured for starting a process, terminating a process, and restarting a process. In some embodiments, the start, end, and restart action plans can each be designed or modified for each process. Moreover, in some embodiments, the start conditions can be individually configured for each action plan. For example, a process can be configured such that upon restart, the associated action plan restarts immediately, with a preceding event, after a preceding event, with a dependent event, or after a dependent event.

In some embodiments, a process can be configured with compliance rules. For example, a process (or an activity of the process) can be configured with one or more verification rules. A verification rule can be a conditional rule that determines whether the process (or an activity of the process) passes or fails an audit verification condition. The output of the compliance rule can be directed to a compliance log or report, for example, when a workflow is executed. In some embodiments, the compliance rule is used to generate a compliance report.

At 205, one of the processes of the multi-process workflow is created and/or modified. For example, activities belonging to each process can be created and/or modified. New activities can be added to the process and existing activities can be modified. In various embodiments, each activity is a workflow item that belongs to a workflow item grouping container that represents that process. An activity can have its own individually configurable execution conditions. For example, an activity can be modified at 205 to configure the execution conditions of the activity. Similar to a process, the configuration can control different activity execution parameters. As an example, each workflow item can have a start condition that can be configured to control the start of the activity. Examples of start condition settings can include starting the activity immediately, starting the activity with a preceding activity, starting the activity after a preceding activity has finished, starting the activity with a dependency, starting the activity after a dependency has been completed, among others. Additional or fewer start conditions may be valid as well. For example, in some embodiments, the start condition can include a configurable delay or condition requirement. In some embodiments, execution conditions can be configured that are independent of when the activity starts. For example, conditions can be configured to control whether a process lane is enabled and/or visible, and whether a process lane should be omitted or displayed, respectively.

At 207, it is determined whether additional changes exist to the workflow. If additional changes exist, processing continues back to step 203 where a workflow process can be created and/or modified at 203. In some embodiments, processing continues back to step 205 (not shown) to modify one or more activities of the workflow instead of the workflow process. If there are no additional changes, processing continues to step 209.

At 209, the digital workflow is generated, e.g., a computer application corresponding to the configured workflow is generated. In some embodiments, the generated application is a web service hosted on an application server and offered to clients as SaaS. For example, a user can access the generated digital workflow via a web browser or similar client application. In some embodiments, as part of the generated computer application, the digital workflow generates reports and analysis results. For example, a reporting feature of the application can be used to output details of cases and activities along with other analysis results. The reports can take the form of a web page, email, log file, or another suitable format.

3 is a flow diagram illustrating an embodiment of a workflow design tool process. In the illustrated example, the workflow design tool provides a user with a visual representation of a multi-process workflow and allows the user to create and modify the workflow. In some embodiments, each process of the workflow is displayed as a process lane, with each lane including different activities associated with the process. Visual indicators display the configuration of different workflow components, and user interface components allow the different workflow components to be configured. In some embodiments, a user interface component may launch another user interface component for more advanced configuration options. In some embodiments, the process of FIG. 3 is performed as part of the process of FIG. 2. For example, the process of FIG. 3 can be performed at 203, 205, and/or 207 of FIG. 2. In some embodiments, the process of FIG. 3 is performed on an application server, such as application server 121 of FIG. 1, from a client, such as clients 101, 103, and/or 105 of FIG. 1.

At 301, a visual representation of the multi-process workflow is displayed, for example by rendering a user interface displaying the multi-process workflow via a web browser or similar application. Each process can be displayed as a group of workflow activities or items. In some embodiments, configuration settings for the workflow item group and associated workflow items are displayed along with the representation of the group and items. For example, start conditions can be displayed as part of the user interface components of the workflow item group. As another example, user interface instructions associated with the workflow item group can be displayed to identify whether the associated process should be executed in parallel with another process or sequentially.

In some embodiments, the displayed activities of each process can be independently controlled. For example, a user can scroll through each workflow item group independently. Similarly, if there are too many workflow item groups to display all, a subset is displayed and the user can scroll through the workflow item groups to determine which one to display. For example, a user can scroll from left to right to display a different set of workflow item groups.

At 303, a configuration modification is received. For example, a user modifies the configuration of one or more portions of the workflow. In various embodiments, the modification can be initiated via a user interface device, such as a mouse, trackpad, touch screen, keyboard, or another suitable device. In some embodiments, activities and groups of activities can be reordered, added, and/or removed. For example, an activity can be dragged and dropped before or after another activity to reorder corresponding activities, or an activity can be moved from one process to another. Similarly, groups or lanes of activities can be dragged and dropped to reorder corresponding processes. In some embodiments, execution conditions, such as start settings, are configured. As another example, advanced or excessive configuration settings can be modified by accessing an advanced configuration user interface component.

At 305, dependencies are updated. For example, some activities receive the output of another activity as an input. Similarly, the output of one activity can be used as an input for the next activity. At 305, workflow dependencies are updated. For example, a selection window for an input related to an activity can navigate available outputs of a preceding activity based on the updated dependencies. In various embodiments, dependencies are updated at least in part to allow different user interface components to dynamically display available reference data for an activity, such as available reference values that can be used as input. The updated dependencies also allow data to be properly passed from one activity to another.

At 307, visual indicators of the multi-process workflow are updated, e.g., the workflow is rendered to reflect the changes to the configuration by steps 303 and/or 305. In response to step 303, new activities or workflow items may be added or removed, new processes or workflow item groups may be modified or removed. Similarly, conditions such as execution conditions may be modified and the visual indicators updated. For example, two processes are changed from running sequentially to now being configured to run in parallel. Accordingly, the visual indicators corresponding to the operation of the two processes are updated with each other. In some embodiments, a chevron indicating that one process precedes the other may be changed and a boxed border is drawn to indicate that the two processes should be run in parallel.

4 is a flow diagram illustrating an embodiment of a process for modifying execution conditions of processes of a multi-process workflow solver using a workflow design tool. In the illustrated example, the workflow design tool updates a visual representation of the multi-process workflow solver in response to a configuration modification to one of the processes of the workflow. Each process of the multi-process workflow can have its own execution conditions. The rendered visual interface of the workflow reflects at least a portion of the execution condition settings. For example, a user can glance at the user interface to understand important settings regarding how the processes of the workflow are configured. In some embodiments, the process of FIG. 4 is performed as part of the process of FIG. 2 and/or as part of the process of FIG. 3. For example, the process of FIG. 4 can be performed at 303, 305, and/or 307 of FIG. 3. In some embodiments, the process of FIG. 4 is performed on an application server, such as application server 121 of FIG. 1, from a client, such as clients 101, 103, and/or 105 of FIG. 1. In various embodiments, the processes of a workflow are each represented as a workflow item grouping container, and the activities of each process are each represented as a workflow item.

At 401, an update of the execution conditions is received. For example, a user performs a user event to modify the execution condition configuration of the process. For example, the user can update the execution conditions so that the process runs in parallel with another process or sequentially with another process. The user can configure when the process starts, such as immediately, scheduled, or in another appropriate configuration. In some embodiments, the user configures the start settings with associated logic. For example, the process can be configured to start manually, immediately, after a preceding process, or together with a preceding process. As another example, the process can start after a condition is met and/or with specific logic, such as with a start delay.

In some embodiments, a user can configure one or more action plans, such as start, end, and/or restart action plans, for a process. With certain user interface embodiments, a user can also modify metadata for a process. For example, a user can modify the name, description, sequence, and/or active (or inactive) state of a process. In some embodiments, a user can modify visibility settings for a process to control whether the process and/or corresponding data for the process, such as inputs, are visible during execution. As another example, in some embodiments, each process has a runtime state, such as started, not started, completed, skipped, etc., as examples. The runtime state can be configured to be displayed with the process when the workflow is executed. For example, the runtime states can be color coded and different colors can be displayed with the process when the workflow is executed. A started process can be colored green and a not started process can be colored red.

At 403, dependencies are updated, e.g., the availability of data that can be passed between activities. In various embodiments, dependencies are updated based on relationships between activities and processes. For example, changing the order of execution of activities and/or processes may result in an output of one activity becoming available as an input to another activity. In various embodiments, the updated dependencies allow data to be properly passed from one activity to another.

At 405, for each process pair, it is determined whether the processes should be executed sequentially. If the pair is configured to be executed sequentially with respect to one another, processing proceeds to 407 where the execution of the corresponding visual indicator is updated to a chevron. If the pair is configured not to be executed sequentially with respect to one another, processing proceeds to 409 where the execution of the corresponding visual indicator is updated to a linear vertical edge. In various embodiments, the appropriate visual indicator affects the boundary of a user interface component between the process pair.

At 407, the visual indicator for the process pair is updated to include a chevron. For example, the visual indicator for a first running process of the process pair is modified to include a chevron. The orientation of the chevron points to the second running process of the process pair. In some embodiments, the visual indicator for the second running process is changed to indicate that it is the target of the chevron of the first running process. For example, the border of a user interface component of the second running process can be modified to have a recessed portion to match the chevron and become the target of the chevron.

At 409, the visual indicator for the process pair is updated to include a straight vertical edge. For example, the border of the user interface component of the process pair is updated to be a square or to have a straight vertical edge. Two parallel edges bordering each process indicate to the user that neither process precedes the other in the execution order. In some embodiments, a process can have one border that is a straight vertical edge and another border that is a chevron. This indicates that the process runs in parallel with one process, but also precedes the other.

5 is a flow diagram illustrating an embodiment of a process for adding a new activity to a process of a multi-process workflow solver using a workflow design tool. In the illustrated example, a workflow design tool is used to add a new activity or workflow item to a process or a group of workflow items. In some embodiments, the new activity is depicted as part of a process lane and is distinct from other activities in the process and from other activities in the process lane. In some embodiments, the process of FIG. 5 is performed as part of the process of FIG. 2 and/or as part of the process of FIG. 3. For example, at least a portion of the process of FIG. 5 can be performed at 205 of FIG. 2. In some embodiments, the process of FIG. 5 is performed on an application server, such as application server 121 of FIG. 1, from a client, such as clients 101, 103, and/or 105 of FIG. 1. In some embodiments, information related to the newly added activity is stored in a database, such as database 123 of FIG. 1.

At 501, an activity definition is created. For example, an activity creator creates an activity definition that specifies the nature of the activity, such as the type and flow of the activity. The activity definition can be stored in a database, such as database 123 of FIG. 1, and can be retrieved and used as a template for creating new activities. In various embodiments, the activity creator can be a different user than the user creating the multi-process workflow solver. In various embodiments, the activity definition is part of a catalog or list of predefined activities that can be used to quickly build a working multi-process workflow solver. For example, predefined activities can be created to correspond to, among others, fulfilling a request, notification, approval, request to create a catalog, creating or updating a parent case, creating or updating a child case, and running a script.

At 503, a new activity is added into a process of the multi-process workflow based on the activity definition. For example, in some embodiments, a user creating a workflow selects an activity definition from an activity selection user interface component to add a new activity to a particular process of the workflow. For example, a user adds a notification activity to a process for notifying a hiring manager that a new employee has completed onboarding training.

At 505, an input is associated with the newly added process activity. For example, a user may proceed to configure or customize the newly added activity. In some embodiments, the activity accepts inputs and the user associates data with the inputs of the newly added activity. The associated inputs may be outputs of a previous activity or from the record that started the process (the trigger record). For example, the input of a newly added email notification process activity may be the email address output of a previous new hire activity that was previously set up in the process.

At 507, an activity record is generated and saved. For example, a database record is generated to reflect the settings of the activity. In some embodiments, the activity record is stored in a database, such as database 123 of FIG. 1. For example, the generated activity record corresponding to the process activity is stored in an activity table of the database. The activity record can include the concatenated outputs of other activities as inputs.

At 509, outputs of the activity are determined to associate the multi-process workflow with other activities. For example, in some embodiments, the workflow dependencies are updated to make the output of the newly added activity available as an input to the next activity. In various embodiments, outputs of the newly added activity are determined and made available as input to other activities in the workflow that come after this activity. For example, an activity where the IT department creates a new email address makes the newly created email address available as an input to the other activity. Other activities can be associated with other departments, such as sending a calendar invite to the new employee's email address for a weekly scheduled internal team meeting.

FIG. 6 is a flow diagram illustrating an embodiment of a process for adding a new multi-process workflow solver using a workflow design tool. In the illustrated example, a workflow design tool is used to add a new multi-process workflow solver. In some embodiments, the process of FIG. 6 is performed as part of one or more of the processes of FIGS. 2-5. For example, the process of FIG. 6 is used to save a newly created workflow that has been modified using the processes of FIGS. 2-5. In some embodiments, the process of FIG. 6 is performed on an application server, such as application server 121 of FIG. 1, from a client, such as clients 101, 103, and/or 105 of FIG. 1. In some embodiments, information related to the newly added workflow is stored in a database, such as database 123 of FIG. 1.

At 601, a record corresponding to a multi-process workflow is retrieved. For example, a user opens a new or existing workflow, which results in retrieving a workflow record from the database. The workflow record can reference other records, such as activity records of related activities utilized in the workflow. At 601, the corresponding activity records can also be retrieved. For example, the corresponding activity records may be stored as references in the retrieved workflow record, and are also retrieved from the database. In various embodiments, the database used to maintain the workflow records is a database, such as database 123 of FIG. 1. In some embodiments, a user creates a new workflow at 601, which includes creating a new workflow record in the database and then effectively retrieving the newly created record. If the new workflow record is not stored in the database, it is not retrieved.

At 603, activities of the multi-process workflow are grouped into processes. For example, activities related to the workflow are grouped into individual process groups or workflow item groups. In various embodiments, a workflow record describes the different processes of the workflow and each activity of each process. Each activity can be represented as a workflow item and is associated with a workflow item grouping container for each process. In some embodiments, each process is a process lane that contains activities ordered as workflow items.

At 605, the processes of the multi-process workflow and the associated activities of the processes are rendered. For example, each activity is associated with a workflow item and belongs to the workflow item grouping container of the activity's process. The different workflow item grouping containers of the workflow and the associated workflow items are displayed to the user. In some embodiments, all the processes can be displayed. If there are too many to display, a subset of the workflow item grouping containers are displayed and the user can navigate the different processes of the workflow to determine which processes to display. For example, in some embodiments, the user can scroll from left to right to show the different process lanes. In some embodiments, the different processes and associated activities are rendered on the display device along with visual indications of at least some of the configuration settings. For example, the most important settings can be displayed as part of the rendered user interface components.

At 607, user input is addressed. For example, a user modifies a workflow by making changes such as changing the processes and activities of the workflow. New processes and activities can be added. Processes and/or activities can also be modified and/or deleted. Drag-and-drop user input operations on the process and activity user interface components can be addressed, for example, to reorder the appropriate processes or activities. In some embodiments, activity cards can be dragged within or across process lanes. An overflow user interface window can be displayed to allow the user to modify additional configuration settings that are not accessible in the main user interface. In some embodiments, the user can provide input to configure workflow parameters such as execution conditions. In various embodiments, in response to the user input, the visual representation of the displayed workflow is updated. For example, two process lanes can be reordered after addressing user input to reorder the processes. In various embodiments, the processes of FIGS. 2-5 are used to address the user input. For example, in steps 203 and 205 of FIG. 2, user input is addressed to create and/or modify processes and activities, respectively. As another example, step 303 of FIG. 3 accommodates user input that modifies the configuration.

In some embodiments, at 607, a user can launch a test procedure. For example, a user can launch a test procedure to test a process and/or an activity of the process. In some embodiments, a process of the workflow can be started in a test mode. The process starts from a specified starting point. This functionality is useful for testing a process (or activity) that is outside the context of the entire workflow. In some embodiments, a test process can be launched to start the process from a specified activity of the process. For example, instead of starting a test process at the first activity of the process, testing can start in the middle of the process or from another specified starting point. In various embodiments, the testing of the process can input data, such as using data from a previous step for testing.

At 609, a record corresponding to the multi-process workflow is saved. For example, a database workflow record for the workflow is saved to reflect changes to the workflow. In some embodiments, the workflow record is stored in a database, such as database 123 of FIG. 1. For example, a workflow record corresponding to the settings for the workflow is stored in a workflow table in the database. The workflow record can reference activity records related to activities in the workflow.

FIG. 7 illustrates an example of a user interface for a workflow design tool. In the illustrated example, user interface 700 is a user interface for the workflow design tool to visually create a digital multi-process workflow. Generate an automation application based on the created workflow. For example, the generated application can be hosted as a web service and used to automate a digital workflow. User interface 700 is rendered within a client application, such as a web browser. In some embodiments, the user interface of FIG. 7 is implemented at least in part by an application server, such as application server 121 of FIG. 1, via a client, such as clients 101, 103, and/or 105 of FIG. 1. In various embodiments, user interface 700 is created at least in part by utilizing the processes of FIGS. 2-6. In some embodiments, information related to user interface 700 is stored in a database, such as database 123 of FIG. 1. In some embodiments, the user interacts with the user interface 700 at 203 and/or 205 of FIG. 2, at 303 of FIG. 3, at 401 of FIG. 4, at 503 and/or 505 of FIG. 5, and/or at 607 of FIG. 6. The updates to the user interface 700 may correspond to at least steps 301 and/or 307 of FIG. 3, and/or steps 407 and/or 409 of FIG. 4.

In various embodiments, a user interface 700 is used to create a multi-process workflow. The user interface 700 includes a process visual user interface component 711. In the illustrated example, the process visual user interface component 711 includes visual indicators of five different processes, one for each of the five processes of a vendor employee onboarding workflow. The visual indicator for the first process corresponds to the identification process, the visual indicator for the second process corresponds to the pre-employment process, the visual indicator for the third process corresponds to the day 1 process, the visual indicator for the fourth process corresponds to the week 1 process, and the visual indicator for the fifth process corresponds to the day 30 process. Each of the visual indicators includes a description of their corresponding process, and all but the last, fifth indicator, includes a chevron indicating the sequential execution order of the five processes. Each of the five processes further includes a set of activities. The five processes shown in the user interface 700 are presented as process lanes 701, 703, 705, 707, and 709, which correspond to the identification, pre-employment, day 1, week 1, and day 30 processes, respectively. In some embodiments, each of process lanes 701, 703, 705, 707, and 709 includes workflow items for each activity in the process and visual user interface components for the corresponding process. In some embodiments, each process lane is a workflow item grouping container, and the activities are represented as workflow items belonging to that container. In the illustrated example, process lane 701 includes activity set 721. Activity set 721 includes activity cards 723, 725, and 727, which are three activity user interface components that represent three different activities or workflow items of the identification process. Each of activity cards 723, 725, and 727 corresponds to a workflow item and describes an activity of the identification process. For example, activity card 723 corresponds to and depicts a new employee paperwork task, activity card 725 corresponds to and depicts a drug screening request task, and activity card 727 corresponds to and depicts a background check request task. As with the identification process, each of the other four processes in the workflow includes their own activity cards that represent their own activities.

In various embodiments, activity cards describe activities that may belong to a process of the workflow. Activity cards can include configuration information such as execution condition settings and activity type as well as the displayed name and description of the corresponding activity. For example, an activity card can indicate that an activity is configured to start immediately or after a preceding activity. Examples of activity types include process activities and record operation activities. For each process, the activity cards in the process lane are displayed in order of execution and numbered according to the relative order of the activity cards in the workflow. For example, activity cards 723, 725, and 727 are displayed in order of execution and numbered accordingly. The activity cards of the second process are also numbered, with the numbering continuing from the numbering of activity card 727, the last activity card of the preceding process. For example, the activity cards of the first process are numbered 1-3, and the first activity card of the second process is numbered 4. In some embodiments, the numbering of activities for a particular process restarts at 1 rather than continuing from the numbering of the preceding process. In some embodiments, activities that are executed in parallel are each given a unique number.

In some embodiments, additional user interface components are depicted, but not labeled, as in the illustrated example. For example, an "Add Activity" button is included below the end of each activity in the process, allowing a user to add a new activity to the corresponding process. Similarly, an Add Process button, depicted as a large plus on the right side of the Process visual interface component 711, allows a user to add a new process. Using the user interface 700, a user can easily navigate and visualize a multi-process workflow. For example, a user can scroll within a process (e.g., up and down within a process lane) to view and modify the activities of a process. Similarly, a user can scroll within a workflow (e.g., left and right) to view the processes of the workflow.

FIG. 8 illustrates an example of a user interface of a workflow design tool. In the illustrated example, user interface 800 is a user interface of a workflow design tool for visually creating digital multi-process workflows. User interface 800 displays three process lanes 801, 803, and 805. There are no activities in process lanes 801, 803, and 805. In some embodiments, user interface 800 reflects a new workflow with three processes and with only minor modifications to the first process, such as naming the process and adding a description and setting an initiation. Additional processes can be added to the workflow and activities can be added to implement the corresponding process. In some embodiments, a multi-process workflow, such as the multi-process workflow displayed in user interface 700 of FIG. 7, is created from the workflow shown in user interface 800. In various embodiments, user interface 800 is created at least in part by utilizing the processes of FIGS. 2-6. In some embodiments, the user interface of FIG. 8 is implemented at least in part by an application server, such as application server 121 of FIG. 1, via a client, such as clients 101, 103, and/or 105 of FIG. 1. In some embodiments, a user interacts with user interface 800 at 203 of FIG. 2, at 303 of FIG. 3, at 401 of FIG. 4, at 503 of FIG. 5, and/or at 607 of FIG. 6. Updates to user interface 800 may correspond to at least steps 301 and/or 307 of FIG. 3, and/or 407 and/or 409 of FIG. 4.

In the illustrated example, user interface 800 includes a process visual user interface component 807. Process visual user interface component 807 includes visual indicators 811, 813, and 815 of individual processes. Process visual indicators 811, 813, and 815 correspond to process lanes 801, 803, and 805, respectively. For example, process visual indicator 811 is a visual indicator for process lane 801. In various embodiments, the process visual indicator displays information about the process, such as the name of the process, a description of the process, and important run configuration settings of the process, such as start settings. In some embodiments, the process visual indicator is highlighted when a process lane is selected. For example, process visual indicator 811 is highlighted after process lane 801 is selected. Process visual indicators 811 and 813 of user interface 800 are depicted as chevrons pointing to the next process lane. For example, process visual indicator 811 points to process visual indicator 813, which points to process visual indicator 815. A process lane with a chevron indicates to a user that the process precedes the target process. For example, the process in process lane 801 executes before the process in process lane 803. Similarly, the process in process lane 803 executes before the process in process lane 805. In various embodiments, the next process (or the process that is the target of the chevron) includes a visual indicator that fits the chevron of the preceding process. In FIG. 8, the visual indicator of the target process is a concave left border with respect to the process visual indicators 813 and 815. The concave left border indicates that the target process follows the preceding process. In contrast, in some embodiments, a process that does not depend on another process has a square or straight vertical border. For example, the process visual indicator 815 has a square or straight vertical edge right border. This indicates that there is no dependent process that follows the process in process lane 805. In various embodiments, the visual indicator of the process can include additional user interface components. For example, process visual indicators 811, 813, and 815 each include a "more" icon drawn as a vertical line of dots that allows a user to modify the associated process. In some embodiments, the more icon opens a lane configuration dialog, such as lane configuration dialog 833.

In various embodiments, the process lane can be configured via a lane configuration dialog, such as lane configuration dialog 833. In the illustrated example, process lane 801 is selected and lane configuration dialog 833 displays configuration settings for the selected process lane 801 and allows the user to modify them. As illustrated, the configuration settings include the ability to set the name, description, and start settings for the process. In various embodiments, the start settings allow for different start settings such as immediately, with preceding process, after preceding process, at dependent settings, and after dependent settings. Additional settings can be added or existing settings can be removed as appropriate. In the illustrated example, process lane 801 is configured to start immediately. Lane configuration dialog 833 also includes an advanced configuration selection 835, a cancel button to undo any changes made, and a save button to save the changes. The advanced configuration selection 835 can be selected to access additional configuration settings for the process. In some embodiments, the advanced configuration selection 835 exposes the advanced configuration user interface 941 of FIG. 9.

In the illustrated example, user interface 800 includes additional UI components such as an add activity button and an add process button 823. Every process lane in user interface 800 includes an individual add activity button. The add activity buttons, such as add activity button 821, are labeled with the description "Add an Activity" and allow a user to add an activity with an associated process lane. For example, add activity button 821 adds a new activity to process lane 801. To add a new process to the workflow, a user utilizes add process button 823. Add process button 823 is depicted as a large plus to the right of the process visual user interface component 807. Add process button 823 allows a user to add a new process to the included workflow as a new process lane.

FIG. 9 illustrates an example of a workflow design tool user interface for advanced configuration of a process. In the illustrated example, user interface 900 is a user interface of a workflow design tool for visually creating a digital multi-process workflow. User interface 900 displays three process lanes, including process lane 901. Process lane 901 includes a visual indicator 923 of a process that is highlighted to indicate that it is a selected process of the workflow. User interface 900 includes a lane configuration dialog 933 with advanced configuration selection 935, neither of which is focused. In various embodiments, lane configuration dialog 933 and advanced configuration selection 935 are lane configuration dialog 833 and advanced configuration selection 835 of FIG. 8. User interface 900 also includes advanced configuration user interface 941, which is the user interface component that is currently active and focused. User interface 900 is an example of a user interface presented to a user for modifying advanced configuration settings of a process. For example, in some embodiments, user interface 900, and in particular advanced configuration user interface 941, is provided to a user when an advanced configuration selection, such as advanced configuration selection 935 and/or advanced configuration selection 835 of FIG. 8, is activated. In various embodiments, user interface 900 is created at least in part by utilizing the processes of FIGS. 2-6. In some embodiments, the user interface of FIG. 9 is implemented at least in part by an application server, such as application server 121 of FIG. 1, via a client, such as clients 101, 103, and/or 105 of FIG. 1. In some embodiments, a user interacts with advanced configuration user interface 941 at 203 of FIG. 2, at 303 of FIG. 3, at 401 of FIG. 4, and/or at 607 of FIG. 6.

In the illustrated example, the advanced configuration user interface 941 displays the configuration settings of the process to the user and allows the user to modify the configuration settings of the process. For example, the user can modify the process description, set the process to be enabled (or disabled), and set the process to be visible (or invisible). Using the advanced configuration user interface 941, the user can configure action plans, such as start, end, and/or restart action plans for the process. In some embodiments, the inputs of the process can be configured. For example, data including the outputs of other processes and/or activities can be specified as inputs. In various embodiments, the user can also configure the input records, process type, and process approvers. In some embodiments, a data lookup dialog is made available to the user to present available reference data to the user and to link the reference data to the current configuration settings. For example, the data lookup dialog is used to link the outputs of an activity to the inputs of a process. In some embodiments, a bullseye icon 951 is used to launch the data lookup dialog.

FIG. 10 illustrates an example of a user interface of a workflow design tool for adding a new activity to a process. In the illustrated example, the user interface 1000 is a user interface of a workflow design tool for visually creating a digital multi-process workflow. The example user interface 1000 is used to illustrate the steps of adding a new activity to a process. The user interface 1000 displays a number of process lanes, including a process lane 1001. The process lane 1001 includes a visual indicator of a process 1003, an activity card 1005, and an add activity button 1007. In some embodiments, at different stages of workflow creation, the process lane 1001 corresponds to the process lane 701 of FIG. 7 and/or the process lane 801 of FIG. 8, the activity card 1005 corresponds to the activity card 723 of FIG. 7, and the add activity button 1007 corresponds to the add activity button 821 of FIG. 8. The user interface 1000 also includes an activity configuration dialog 1009. In some embodiments, a user interacts with the user interface 1000 at 205 in FIG. 2, at 303 in FIG. 3, at 503 and/or 505 in FIG. 5, and/or at 607 in FIG. 6.

In the illustrated example, activity card 1005 is added to a process in process lane 1001. Activity card 1005 is highlighted to indicate that it is selected. Activity card 1005 displays the corresponding activity's name (new employee document creation), description (shown as a placeholder description), activity type (process), and start setting (starts immediately). In some embodiments, an activity card such as activity card 1005 includes a "show more" icon drawn as a vertical line of dots that allows a user to modify the associated activity. For example, in some embodiments, the show more icon opens an activity configuration dialog such as activity configuration dialog 1009. Activity configuration dialog 1009 can be used to modify the activity corresponding to activity card 1005. For example, activity configuration dialog 1009 can be used to configure the name, description, start conditions, execution conditions, action plan, and inputs. Inputs can be specified as variables and selected using a data reference dialog such as data reference dialog 1400 of FIG. 14. Data references can be displayed in the corresponding fields using a bull's-eye icon. In some embodiments, more or fewer settings can be configured via the activity configuration dialog.

FIG. 11 illustrates an example of a workflow design tool user interface for creating an activity definition. In the illustrated example, activity definition dialog 1100 is a user interface dialog for creating an activity definition for a workflow process. In some embodiments, activity definitions can be reused across multiple processes and multiple workflows. Activity definition dialog 1100 may be accessed from a workflow design tool, such as the workflow design tool described by the process of FIGS. 2-6. For example, in some embodiments, activity definition dialog 1100 can be launched from activity card 1005 and/or activity definition dialog 1009, or via another suitable trigger. In various embodiments, activity definition dialog 1100 is created at least in part by utilizing the process of FIGS. 2-6. In some embodiments, the user interface of FIG. 11 is implemented at least in part by an application server, such as application server 121 of FIG. 1, via a client, such as clients 101, 103, and/or 105 of FIG. 1. In some embodiments, a user interacts with the user interface 1100 at 205 in FIG. 2, at 303 in FIG. 3, at 401 in FIG. 4, at 503 and/or 505 in FIG. 5, and/or at 607 in FIG. 6.

In various embodiments, the activity definition dialog 1100 can be useful for creating and/or modifying activity definitions, which may include steps for configuring advanced settings for the activity. For example, a new activity definition can be created to be used as a template for inserting an instance of the activity into a process workflow. The activity definition can include default configurations, such as default input fields and behaviors. The activity definition dialog 1100 can be used to configure an activity's plan of action for the activity. In some embodiments, the name, short description, long description, badges, active (or inactive) settings, settings wait for completion, visible (or invisible) settings, and inputs, among other settings, can be configured using the activity definition dialog 1100. For example, a badge icon can be configured for the activity. Badges can be used as visual indicators to associate an activity with a responsible person, a particular subject, or another reference. As an example, a HR badge is applied to an activity that references the HR department with HR activities. In some embodiments, the badge configuration can be inherited based on the configuration of the activity. In another example, settings wait for completion can be configured to have the activity wait for completion before starting the next step or starting and immediately moving to the next step. The wait for completion setting can be used to configure the activity to execute the action plan synchronously or asynchronously. As another example, settings accessible via the activity definition dialog 1100 allow the user to configure which inputs of the action plan are visible and, if applicable, which inputs are set to default. In some embodiments, the visibility setting configures whether to hide certain data associated with the activity, such as the action plan inputs. When an instance of the activity definition is added to a process, the activity definition's default values and behaviors are used.

In some embodiments, an administrator using the activity definition dialog 1100 can specify default values for the activity's inputs. The default values can be default lookup values that are later populated with valid lookup values when an instance of the activity is added into a process. The lookup/values entered are based on the context of the process/workflow to which the activity is added. For example, when an activity is added to a process, a data lookup dialog such as data lookup dialog 1400 of FIG. 14 allows the user to select from only valid lookup values that fit the configured default values. A user who includes the activity in a process does not need to create/recreate the inputs. The inputs are populated based on predefined default values. In some embodiments, the default values can be configured based on conditional rules, such as using trigger conditions and/or trigger records. The inputs of the activity instance can then be dynamically determined when the conditions are evaluated. A keyed input can be used to turn off a trigger record that is triggered, for example, by creating or updating a record for a particular database table.

12 illustrates an example of a user interface of a workflow design tool for displaying process execution. In the illustrated example, user interface 1200 is a simplified version of the workflow design tool. The details of the user interface are removed to focus on the visual indicators of process execution. Using the concepts depicted by user interface 1200 and user interface 1300 of FIG. 13, a user can quickly visually determine the process execution order and dependencies of different processes of a workflow. User interface 1200 includes three process lanes, namely process lanes 1201, 1211, and 1221 of a multi-process workflow. Each process lane includes a visual indicator of a process, such as visual indicator 1203 of a process for process lane 1201. Each process lane also includes a different activity card. For example, process lane 1201 includes activity cards 1205, 1207, and 1209. Process lane 1211 includes four activity cards, and process lane 1221 includes two activity cards.

In the illustrated example, the visual indicator for each process in user interface 1200 is a chevron. Process visual indicator 1203 points to process lane 1211 and its corresponding process visual indicator. Similarly, process lane 1211's visual indicator points to process lane 1221 and its corresponding process visual indicator. By utilizing the chevron user interface element as a visual indicator, user interface 1200 provides execution order information to the user. The execution order of the process lane with the chevron precedes the execution of the target process lane. In some embodiments, the target process lane has a visual indicator of the process that includes a visual target element portion that is the target of the chevron and matches the chevron. For example, the left side of the process visual indicator for process lanes 1211 and 1221 has a concave left border that is recessed to accommodate the chevron of the process lane that precedes the process for process lanes 1211 and 1221.

FIG. 13 illustrates an example of a workflow design tool user interface for displaying process execution. In the illustrated example, user interface 1300 is a simplified version of the workflow design tool user interface. Similar to user interface 1200 of FIG. 12, the user interface details of user interface 1300 have been removed to focus on the visual indicators of process execution. Using the concepts depicted by user interface 1200 and user interface 1300 of FIG. 12, a user can quickly determine the process execution order of different processes of a workflow. Similar to user interface 1200 of FIG. 12, user interface 1300 includes three process lanes, namely process lanes 1301, 1311, and 1321 of a multi-process workflow. Each process lane includes a visual indicator of a process, such as visual indicator 1303 of a process for process lane 1301. Each process lane also includes a different activity card. For example, process lane 1301 includes activity cards 1305, 1307, and 1309. Process lane 1311 contains four activity cards, and process lane 1321 contains two activity cards.

In the illustrated example, only the visual indicator 1303 of the process in the user interface 1300 is a chevron. The visual indicator 1303 of the process points to the process lane 1311 and its corresponding visual indicator of the process to indicate that the process in the process lane 1311 runs after the process in the process lane 1301. Unlike the user interface 1200 of FIG. 12, the visual indicators of the processes in the process lanes 1311 and 1321 have a shared or common border that includes a squared edge or a straight vertical edge. Instead of displaying a chevron and a matching, matching border, the border between the visual indicators of the processes in the process lanes 1311 and 1321 is a straight vertical edge. Using the straight vertical border, the user interface 1300 provides execution order information to the user. The squared user interface element portion along the common border indicates that the process lanes 1311 and 1321 run in parallel and that neither one precedes the other. In some embodiments, process lanes 1301, 1311, and 1321 are process lanes 1201, 1211, and 1221 of FIG. 12 after the execution conditions of process lane 1321 have been changed so that it runs in parallel with process lane 1311.

In various embodiments, user interface 1200 of FIG. 12 and user interface 1300 of FIG. 13 are created at least in part by utilizing the processes of FIGS. 2-6. In some embodiments, user interface 1200 of FIG. 12 and user interface 1300 of FIG. 13 are implemented at least in part by an application server, such as application server 121 of FIG. 1, via a client, such as clients 101, 103, and/or 105 of FIG. 1.

FIG. 14 illustrates an example of a workflow design tool user interface for selecting reference data. In the illustrated example, the data reference dialog 1400 is a user interface dialog for selecting and linking reference data, such as the output of a preceding activity. For example, the input of an activity can reference the output of a preceding activity. The data reference dialog 1400 can be implemented as a shared component library that can be made accessible whenever a configuration setting can reference a data value. In some embodiments, the data reference dialog 1400 is API driven. In various embodiments, the data reference dialog 1400 is launched via a bull's eye icon, such as bull's eye icon 951 of FIG. 9. In various embodiments, the data reference dialog 1400 is created at least in part by utilizing the processes of FIGS. 2-6. In some embodiments, the data reference dialog 1400 is implemented at least in part by an application server, such as application server 121 of FIG. 1, via a client, such as clients 101, 103, and/or 105 of FIG. 1. In some embodiments, the user interacts with the data reference dialog 1400 at 203 and/or 205 in FIG. 2, at 303 in FIG. 3, at 401 in FIG. 4, at 503 and/or 505 in FIG. 5, and/or at 607 in FIG. 6.

In the illustrated example, the data lookup dialog 1400 includes a selection or search component field and multiple columns. The multiple columns allow a navigation user interface component to continuously narrow the selection. The multiple columns allow the user to visually nudge the object data to select the appropriate reference field for the object. In some embodiments, the data lookup dialog 1400 is automatically populated with activity outputs from the action plan of the preceding activity. When a workflow is modified, the workflow dependencies can be dynamically updated and the selection options in the data lookup dialog 1400 can be updated accordingly. When configuring a workflow item corresponding to an activity, the user can view and select from the outputs of other workflow items that are configured to complete before the workflow item is executed. In some embodiments, the selection or search field automatically filters the current level based on whether the field name contains a specified string.

FIG. 15 illustrates an example of a workflow design tool user interface for selecting an activity. In the illustrated example, activity selection dialog 1500 is a user interface dialog for selecting an activity from among the activities created for adding to the workflow. In some embodiments, activity selection dialog 1500 is accessible from the workflow design tool and can be launched via an add activity button in a process lane, such as add activity button 821 in user interface 800 and/or add activity button 1007 in user interface 1000 in FIG. 10. In various embodiments, selected activities in activity selection dialog 1500 are added to the corresponding process lane of the workflow. In some embodiments, the activities included in activity selection dialog 1500 are created using activity definition dialog 1100 in FIG. 11. In some embodiments, activity selection dialog 1500 is created at least in part by utilizing the processes of FIGS. 2-6. In some embodiments, activity selection dialog 1500 is implemented at least in part by an application server, such as application server 121 in FIG. 1, via a client, such as clients 101, 103, and/or 105 in FIG. 1. In some embodiments, the user interacts with the activity selection dialog 1500 at 205 in FIG. 2, at 303 in FIG. 3, at 401 in FIG. 4, at 503 and/or 505 in FIG. 5, and/or at 607 in FIG. 6.

In the illustrated example, the activity selection dialog 1500 includes a search bar and a number of panels. The search bar allows a user to specify a search query for selecting an activity. The provided search query can be matched against the activity's name, description, installed categories (i.e., installed spokes), and/or another pertinent field. As the search query is typed, matching search results can be displayed and corresponding matching text can be highlighted. Similarly, non-matches can be filtered out as the search query is typed. In some embodiments, the list of available activities is based on user criteria defined in the activity definition. The left panel of the activity selection dialog 1500 shows categories (i.e., installed spokes), each of which may include a corresponding category icon. The category panel allows the available activities to be grouped by a scope of activity. The center panel of the activity selection dialog 1500 shows activity names, each of which may include a corresponding activity definition badge/icon. The right panel of the activity selection dialog 1500 displays the associated description.

Although the above embodiments have been described in some detail for clarity of understanding, the present invention is not limited to the details provided. There are many alternative ways to implement the present invention. The disclosed embodiments are illustrative and not restrictive.
[Application Example 1] A method, comprising:
receiving an identification of a first workflow item grouping container that is part of a collection of workflow item grouping containers that organize an end-to-end multi-process workflow solution;
receiving an execution condition for the first workflow item grouping container;
receiving an identification of a second workflow item grouping container that is part of the collection of workflow item grouping containers of the end-to-end multi-process workflow solver;
receiving an execution condition for the second workflow item grouping container;
receiving a specification of one or more workflow items belonging to said first workflow item grouping container, each of said one or more workflow items belonging to said first workflow item grouping container having individually configurable execution conditions and corresponding to different individual activities of said end-to-end multi-process workflow solver;
receiving a specification of one or more workflow items belonging to said second workflow item grouping container, each of said one or more workflow items belonging to said second workflow item grouping container having individually configurable execution conditions and corresponding to different individual activities of said end-to-end multi-process workflow solver.
[Application Example 2] A method as described in Application Example 1, wherein the execution condition of the first workflow item grouping container is associated with a start condition setting, and the start condition setting is associated with a start immediately setting, a start with predecessor setting, a start after predecessor setting, a start on dependency setting, and a start after dependency setting.
[Application Example 3] The method according to Application Example 2, wherein the start condition setting of the execution condition of the first workflow item grouping container is associated with a start with delay configuration and a start with condition configuration.
[Application Example 4] The method according to Application Example 1, wherein the execution condition of the first workflow item grouping container is associated with action plans including a start action plan, an end action plan, and a resume action plan.
[Application Example 5] The method according to Application Example 4, wherein the start action plan, the end action plan, and the resume action plan are each associated with a separate start condition setting.
[Application Example 6] The method described in Application Example 5, wherein each of the separate start condition settings is associated with a setting that starts immediately, a setting that starts with a predecessor, a setting that starts after a predecessor, a setting that starts on a dependency, and a setting that starts after a dependency.
[Application Example 7] A method as described in Application Example 1, wherein the individually configurable execution conditions of each of the one or more workflow items belonging to the first workflow item grouping container are associated with a start condition setting, and the start condition setting is associated with a start immediately setting, a start with predecessor setting, a start after predecessor setting, a start on dependency setting, and a start after dependency setting.
[Application Example 8] The method according to Application Example 7, wherein the start condition settings of the individually configurable execution conditions are associated with a start with delay configuration and a start with condition configuration.
[Application Example 9] The method according to Application Example 1, wherein each of the one or more workflow items belonging to the first workflow item grouping container includes a runtime state.
[Application Example 10] The method according to Application Example 9, wherein the execution state is one of an unstarted state, a started state, a completed state, or an omitted state.
[Application Example 11] The method described in Application Example 1, wherein one of the one or more workflow items belonging to the first workflow item grouping container corresponds to a request fulfillment activity, a notification activity, an approval activity, a catalog request activity, a case modification activity, or a script execution activity.
[Application Example 12] A method as described in Application Example 1, wherein one of the one or more workflow items belonging to the first workflow item grouping container provides data to a second one of the one or more workflow items belonging to the first workflow item grouping container.
[Application Example 13] A method as described in Application Example 1, wherein one of the one or more workflow items belonging to the first workflow item grouping container provides data to one of the one or more workflow items belonging to the second workflow item grouping container.
[Application Example 14] The method described in Application Example 13, wherein the data provided to the one of the one or more workflow items belonging to the second workflow item grouping container is an output of the one of the one or more workflow items belonging to the first workflow item grouping container.
[Application Example 15] The method according to Application Example 1, wherein the first workflow item grouping container and the second workflow item grouping container are configured to be executed in parallel.
[Application Example 16] The method according to Application Example 1, wherein one of the one or more workflow items belonging to the first workflow item grouping container is associated with a condition rule.
[Application Example 17] The method according to Application Example 1, further comprising:
receiving an identification of a third workflow item grouping container that is part of the collection of workflow item grouping containers of the end-to-end multi-process workflow solver;
receiving an execution condition for the third workflow item grouping container;
receiving a specification of one or more workflow items belonging to said third workflow item grouping container, each of said one or more workflow items belonging to said third workflow item grouping container having individually configurable execution conditions and corresponding to different individual activities of said end-to-end multi-process workflow solver.
[Application Example 18] A method according to Application Example 17, wherein the first workflow item grouping container and the second workflow item grouping container are configured to be executed in parallel, and the first workflow item grouping container and the third workflow item grouping container are configured to be executed sequentially.
[Application Example 19] A system,
A processor;
A memory coupled to the processor, the memory, when executed, causing the processor to:
receiving an identification of a first workflow item grouping container that is part of a collection of workflow item grouping containers that organize an end-to-end multi-process workflow solution;
receiving an execution condition for the first workflow item grouping container;
receiving an identification of a second workflow item grouping container that is part of the collection of workflow item grouping containers of the end-to-end multi-process workflow solver;
receiving an execution condition for the second workflow item grouping container;
receiving a specification of one or more workflow items belonging to said first workflow item grouping container, each of said workflow items having individually configurable execution conditions corresponding to a different individual activity of said end-to-end multi-process workflow solver;
receiving specifications of one or more workflow items belonging to said second workflow item grouping container, each of said workflow items having individually configurable execution conditions corresponding to a different individual activity of said end-to-end multi-process workflow solver;
a memory configured to provide instructions to the processor;
A system comprising:
[Application Example 20] A computer program product, embodied in a non-transitory computer-readable storage medium,
receiving an identification of a first workflow item grouping container that is part of a collection of workflow item grouping containers that organize an end-to-end multi-process workflow solution;
receiving an execution condition for the first workflow item grouping container;
receiving an identification of a second workflow item grouping container that is part of the collection of workflow item grouping containers of the end-to-end multi-process workflow solver;
receiving an execution condition for the second workflow item grouping container;
receiving a specification of one or more workflow items belonging to said first workflow item grouping container, each of said workflow items having individually configurable execution conditions corresponding to a different individual activity of said end-to-end multi-process workflow solver;
receiving a specification of one or more workflow items belonging to said second workflow item grouping container, each of said workflow items having individually configurable execution conditions and each of said workflow items corresponding to a different individual activity of said end-to-end multi-process workflow solver;
A computer program product comprising computer instructions for:

Claims (20)

1. A method comprising:
receiving an identification of a first workflow item grouping container that is part of a collection of workflow item grouping containers that organize an end-to-end multi-process workflow solution;
receiving an execution condition for the first workflow item grouping container;
receiving an identification of a second workflow item grouping container that is part of the collection of workflow item grouping containers of the end-to-end multi-process workflow solver;
receiving an execution condition for the second workflow item grouping container;
receiving a specification of one or more workflow items belonging to said first workflow item grouping container, each of said one or more workflow items belonging to said first workflow item grouping container having individually configurable execution conditions and corresponding to different individual activities of said end-to-end multi-process workflow solver;
receiving a specification of one or more workflow items belonging to said second workflow item grouping container, each of said one or more workflow items belonging to said second workflow item grouping container having individually configurable execution conditions and corresponding to different individual activities of said end-to-end multi-process workflow solver ;
11. A method according to claim 1, wherein the first workflow item grouping container is associated with a first process and the second workflow item grouping container is associated with a second process different from the first process, and the first process and the second process are associated with different responsible parties . The method of claim 1, wherein the execution conditions of the first workflow item grouping container are associated with start condition settings, and the start condition settings are associated with start immediately, start with predecessor, start after predecessor, start on dependency, and start after dependency settings. The method of claim 2, wherein the start condition settings of the execution conditions of the first workflow item grouping container are associated with a start with delay configuration and a start with condition configuration. The method of claim 1, wherein the execution conditions of the first workflow item grouping container are associated with action plans including a start action plan, an end action plan, and a resume action plan. The method of claim 4, wherein the start action plan, the end action plan, and the resume action plan are each associated with a separate start condition setting. The method of claim 5, wherein each of the separate start condition settings is associated with a setting that starts immediately, a setting that starts with a predecessor, a setting that starts after a predecessor, a setting that starts on a dependency, and a setting that starts after a dependency. The method of claim 1, wherein the individually configurable execution conditions of each of the one or more workflow items belonging to the first workflow item grouping container are associated with a start condition setting, the start condition setting being associated with a start immediately setting, a start with predecessor setting, a start after predecessor setting, a start on dependency setting, and a start after dependency setting. The method of claim 7, wherein the start condition settings of the individually configurable execution conditions are associated with a start with delay configuration and a start with condition configuration. The method of claim 1, wherein each of the one or more workflow items belonging to the first workflow item grouping container includes a runtime state. The method of claim 9, wherein the run-time state is one of an unstarted state, a started state, a completed state, or an omitted state. The method of claim 1, wherein one of the one or more workflow items belonging to the first workflow item grouping container corresponds to a request fulfillment activity, a notification activity, an approval activity, a catalog request activity, a case modification activity, or a script execution activity. The method of claim 1, wherein one of the one or more workflow items belonging to the first workflow item grouping container provides data to a second one of the one or more workflow items belonging to the first workflow item grouping container. The method of claim 1, wherein one of the one or more workflow items belonging to the first workflow item grouping container provides data to one of the one or more workflow items belonging to the second workflow item grouping container. 14. The method of claim 13, wherein the data provided to the one of the one or more workflow items belonging to the second workflow item grouping container is an output of one of the one or more workflow items belonging to the first workflow item grouping container. The method of claim 1, wherein the first workflow item grouping container and the second workflow item grouping container are configured to execute in parallel. The method of claim 1, wherein one of the one or more workflow items belonging to the first workflow item grouping container is associated with a condition rule. 10. The method of claim 1 further comprising:
receiving an identification of a third workflow item grouping container that is part of the collection of workflow item grouping containers of the end-to-end multi-process workflow solver;
receiving an execution condition for the third workflow item grouping container;
receiving a specification of one or more workflow items belonging to said third workflow item grouping container, each of said one or more workflow items belonging to said third workflow item grouping container having individually configurable execution conditions and corresponding to different individual activities of said end-to-end multi-process workflow solver. The method of claim 17, wherein the first workflow item grouping container and the second workflow item grouping container are configured to be executed in parallel, and the first workflow item grouping container and the third workflow item grouping container are configured to be executed sequentially. 1. A system comprising:
A processor;
A memory coupled to the processor, the memory, when executed, causing the processor to:
receiving an identification of a first workflow item grouping container that is part of a collection of workflow item grouping containers that organize an end-to-end multi-process workflow solution;
receiving an execution condition for the first workflow item grouping container;
receiving an identification of a second workflow item grouping container that is part of the collection of workflow item grouping containers of the end-to-end multi-process workflow solver;
receiving an execution condition for the second workflow item grouping container;
receiving a specification of one or more workflow items belonging to said first workflow item grouping container, each of said workflow items having individually configurable execution conditions corresponding to a different individual activity of said end-to-end multi-process workflow solver;
and a memory configured to provide instructions to the processor to receive specifications of one or more workflow items belonging to the second workflow item grouping container, the workflow items having individually configurable execution conditions and each corresponding to a different individual activity of the end-to-end multi-process workflow solver ,
The system, wherein the first workflow item grouping container is associated with a first process, the second workflow item grouping container is associated with a second process different from the first process, and the first process and the second process are associated with different responsible parties. A computer program product embodied in a non-transitory computer-readable storage medium,
receiving an identification of a first workflow item grouping container that is part of a collection of workflow item grouping containers that organize an end-to-end multi-process workflow solution;
receiving an execution condition for the first workflow item grouping container;
receiving an identification of a second workflow item grouping container that is part of the collection of workflow item grouping containers of the end-to-end multi-process workflow solver;
receiving an execution condition for the second workflow item grouping container;
receiving a specification of one or more workflow items belonging to said first workflow item grouping container, each of said workflow items having individually configurable execution conditions and each of said workflow items corresponding to a different individual activity of said end-to-end multi-process workflow solver;
receiving a specification of one or more workflow items belonging to said second workflow item grouping container, each of said workflow items having individually configurable execution conditions corresponding to a different individual activity of said end-to-end multi-process workflow solver ;
the first workflow item grouping container is associated with a first process, the second workflow item grouping container is associated with a second process different from the first process, and the first process and the second process are associated with different responsible parties.

Images