Data driven dynamic workflow

A non-transitory computer-readable medium containing a program for an application server and that, when executed performs operations to improve reconfigurability and uptime of the application server when managing workflow instances having variable runtime dependencies between workflow operations, by managing the workflow instances without requiring any application server maintenance for removing, redefining, and redeploying any workflow based on static workflow templates, the operations comprising:

• instantiating, by the application server, a parent process comprising an instance of a workflow, based on a parent process template, the workflow having variable runtime dependencies between workflow operations;
• commencing, by the parent process, execution of a number of workflow operations according to an active workflow configuration of the parent process, the active workflow configuration comprising a first workflow configuration;
• instantiating, by the parent process and based on a child process template distinct from the parent process template, one or more child processes each configured to execute a one or more workflow operations specified in the active workflow configuration;
• subsequent to instantiating the instance of the workflow according to the first workflow configuration, receiving, by the application server and from a requesting entity, a change request specifying a second workflow configuration distinct from the first workflow configuration in terms of runtime dependencies between the workflow operations;
• upon determining, by the application server, that the second workflow configuration is a valid workflow configuration, changing the execution of the workflow operations mid-execution by the application server, based on the second workflow configuration and by operation of one or more computer processors when executing the program, including replacing the first workflow configuration with the second workflow configuration as the active workflow configuration for the parent process, and without requiring any application server maintenance for removing, redefining, and redeploying the workflow based on static workflow templates, thereby improving the reconfigurability and uptime of the application server;
• and
• outputting, to the requesting entity, an indication that the execution of the workflow operations has been changed mid-execution based on the second workflow configuration.

A system to improve reconfigurability and uptime of an application server when managing workflow instances having variable runtime dependencies between workflow operations, by managing the workflow instances without requiring any application server maintenance for removing, redefining, and redeploying any workflow based on static workflow templates, the system comprising:

• one or more computer processors;
• a plurality of distinct templates including a parent process template and a child process template;
• and
• a workflow environment provided by program code when executed by the one or more computer processors, the program code configured to:
• instantiate, by the application server, a parent process comprising an instance of a workflow, based on the parent process template, the workflow having variable runtime dependencies between workflow operations;
• commencing, by the parent process, execution of a number of workflow operations according to an active workflow configuration of the parent process, the active workflow configuration comprising a first workflow configuration;
• instantiating, by the parent process and based on the child process template, one or more child processes each configured to execute a respective one or more workflow operations specified in the active workflow configuration;
• subsequent to instantiating the instance of the workflow according to the first workflow configuration, receive, by the application server and from a requesting entity, a change request specifying a second workflow configuration distinct from the first workflow configuration in terms of runtime dependencies between the workflow operations;
• upon determining, by the application server, that the second workflow configuration is a valid workflow configuration, change the execution of the workflow operations mid-execution, by the application server and based on the second workflow configuration, including replacing the first workflow configuration with the second workflow configuration as the active workflow configuration for the parent process, and without requiring any application server maintenance for removing, redefining, and redeploying the workflow based on static workflow templates, thereby improving the reconfigurability and uptime of the application server;
• and
• output, to the requesting entity, an indication that the execution of the workflow operations has been changed mid-execution based on the second workflow configuration.

A system for managing execution of workflow instances, comprising:

• one or more computer processors;
• a parent process template;
• and
• a workflow environment configured to:
• instantiate an instance of a workflow on the basis of the parent process template and according to a first workflow configuration, wherein instantiating comprises executing a number of workflow operations according to the first workflow configuration;
• receive a change request specifying a second workflow configuration;
• and
• change the execution of the workflow operations, based on the second workflow configuration and by operation of the one or more computer processors, including replacing the first workflow configuration with the second workflow configuration, wherein at least one workflow operation, selected from a currently executing workflow operation and a workflow operation scheduled to be executed, is replaced on the basis of the second workflow configuration.

A computer-implemented method to improve reconfigurability and uptime of an application server when managing workflow instances having variable runtime dependencies between workflow operations, by managing the workflow instances without requiring any application server maintenance for removing, redefining, and redeploying any workflow based on static workflow templates, the computer-implemented method comprising:

• instantiating, by the application server, a parent process comprising an instance of a workflow, based on a parent process template, the workflow having variable runtime dependencies between workflow operations;
• commencing, by the parent process, execution of a number of workflow operations according to an active workflow configuration of the parent process, the active workflow configuration comprising a first workflow configuration;
• instantiating, by the parent process and based on a child process template distinct from the parent process template, one or more child processes each configured to execute a respective one or more workflow operations specified in the active workflow configuration;
• subsequent to instantiating the instance of the workflow according to the first workflow configuration, receiving, by the application server and from a requesting entity, a change request specifying a second workflow configuration distinct from the first workflow configuration in terms of runtime dependencies between the workflow operations;
• determining, by the application server, that the second workflow configuration is a valid workflow configuration, comprising identifying all completed and executing workflow operations of the first workflow configuration, wherein the second workflow configuration is a valid workflow configuration only if the second workflow configuration is not requesting a change to one or more of the completed or executing workflow operations;
• upon determining that the second workflow configuration is a valid workflow configuration, changing the execution of the workflow operations mid-execution by the application server, based on the second workflow configuration and by operation of one or more computer processors, including replacing the first workflow configuration with the second workflow configuration as the active workflow configuration for the parent process, and without requiring any application server maintenance for removing, redefining, and redeploying the workflow based on static workflow templates, thereby improving the reconfigurability and uptime of the application server;
• and
• outputting, to the requesting entity, an indication that the execution of the workflow operations has been changed mid-execution based on the second workflow configuration.

A non-transitory computer-readable medium containing a program for an application server and that, when executed, performs operations to improve reconfigurability and uptime of the application server when managing workflow instances having variable runtime dependencies between workflow operations, by managing the workflow instances without requiring any application server maintenance for removing, redefining, and redeploying any workflow based on static workflow templates, the operations comprising:

• instantiating, by the application server, a parent process comprising an instance of a workflow, based on a parent process template, the workflow having variable runtime dependencies between workflow operations;
• commencing, by the parent process, execution of a number of workflow operations according to an active workflow configuration of the parent process, the active workflow configuration comprising a first workflow configuration;
• instantiating, by the parent process and based on a child process template distinct from the parent process template, one or more child processes each configured to execute a respective one or more workflow operations specified in the active workflow configuration;
• subsequent to instantiating the instance of the workflow according to the first workflow configuration, receiving, by the application server and from a requesting entity, a change request specifying a second workflow configuration distinct from the first workflow configuration in terms of runtime dependencies between the workflow operations;
• determining, by the application server, that the second workflow configuration is a valid workflow configuration, comprising identifying all completed and executing workflow operations of the first workflow configuration, wherein the second workflow configuration is a valid workflow configuration only if the second workflow configuration is not requesting a change to one or more of the completed or executing workflow operations;
• upon determining that the second workflow configuration is a valid workflow configuration, changing the execution of the workflow operations mid-execution by the application server, based on the second workflow configuration and by operation of one or more computer processors when executing the program, including replacing the first workflow configuration with the second workflow configuration as the active workflow configuration for the parent process, and without requiring any application server maintenance for removing, redefining, and redeploying the workflow based on static workflow templates, thereby improving the reconfigurability and uptime of the application server;
• and
• outputting, to the requesting entity, an indication that the execution of the workflow operations has been changed mid-execution based on the second workflow configuration.

A system to improve reconfigurability and uptime of an application server when managing workflow instances having variable runtime dependencies between workflow operations, by managing the workflow instances without requiring any application server maintenance for removing, redefining, and redeploying any workflow based on static workflow templates, the system comprising:

• one or more computer processors;
• a plurality of distinct templates including a parent process template and a child process template;
• and
• a workflow environment provided by program code when executed by the one or more computer processors, the program code configured to:
• instantiate, by the application server, a parent process comprising an instance of a workflow, based on a parent process template, the workflow having variable runtime dependencies between workflow operations;
• commence, by the parent process, execution of a number of workflow operations according to an active workflow configuration of the parent process, the active workflow configuration comprising a first workflow configuration;
• instantiate, by the parent process and based on a child process template distinct from the parent process template, one or more child processes each configured to execute a respective one or more workflow operations specified in the active workflow configuration;
• subsequent to instantiating the instance of the workflow according to the first workflow configuration, receive, by the application server and from a requesting entity, a change request specifying a second workflow configuration distinct from the first workflow configuration in terms of runtime dependencies between the workflow operations;
• determine, by the application server, that the second workflow configuration is a valid workflow configuration, comprising identifying all completed and executing workflow operations of the first workflow configuration, wherein the second workflow configuration is a valid workflow configuration only if the second workflow configuration is not requesting a change to one or more of the completed or executing workflow operations;
• upon determining that the second workflow configuration is a valid workflow configuration, change the execution of the workflow operations mid-execution, by the application server and based on the second workflow configuration, including replacing the first workflow configuration with the second workflow configuration as the active workflow configuration for the parent process, and without requiring any application server maintenance for removing, redefining, and redeploying the workflow based on static workflow templates, thereby improving the reconfigurability and uptime of the application server;
• and
• output, to the requesting entity, an indication that the execution of the workflow operations has been changed mid-execution based on the second workflow configuration.