Framework for ad-hoc process flexibility

• US 9,348,609 B2
• Filed: 08/02/2010
• Issued: 05/24/2016
• Est. Priority Date: 08/02/2010
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Balko, Soeren, Jann, Annette, Holz, Sabine, Moeller, Martin
• Primary Examiner(s): Ng, Amy
• Assistant Examiner(s): STITT, ERIK V
• Application Number:
  US12/848,679
• Publication Number:
  US 20120030573A1
• Time in Patent Office: 2,122 Days
• Field of Search: 715/810, 715/764, 715/735
• US Class Current: 1/1
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 9/4486 Formation of subprogram jump address

Abstract

The present disclosure involves systems, software, and computer implemented methods for providing a unified runtime framework and graphical, process-centric user interface for ad-hoc business process flexibility. One process includes operations for providing process instances of one or more business processes in a process visualization user interface. A request to initiate an ad-hoc change of a selected process instance is received from the client, and client user interaction options for implementing the ad-hoc change are provided to the client. A selection of a particular user interaction option for implementing the ad-hoc change is received from the client, and the ad-hoc change is implemented.

Claims

1. A computer implemented method performed by one or more processors for providing user interaction options for making ad-hoc changes of process instances at runtime, the method comprising the following operations:

providing process instances of one or more business processes to a client across a network in a process visualization user interface;

receiving a request from the client to initiate an ad-hoc change of a selected process instance associated with an original process model;

providing user interaction options for implementing the ad-hoc change to the client, the user interaction options provided in the process visualization user interface;

receiving a selection of a particular user interaction option for implementing the ad-hoc change from the client; and

implementing the ad-hoc change of the selected process instance at runtime for the original process model associated with the selected process instance, wherein implementing the ad-hoc change of the selected process instance at runtime comprises;

generating a revised process model based on the original process model, the revised process model further including at least one change associated with the selected user interaction option, wherein the original process model is maintained separate from the revised process model;

automatically migrating the selected process instance from the original process model to the revised process model at runtime by moving at least a portion of a process instance state associated with the selected process instance to the revised process model, wherein the process instance state is distinct from the original process model and the revised process model;

executing, after completing the migration, the revised process model using the moved process instance state; and

cancelling, while the revised process model is executing, the execution of the original process model.

2. The method of claim 1, wherein the process instances are associated with a particular Business Process Management Suite (BPMS) system.

3. The method of claim 1, wherein providing the user interaction options for implementing the ad-hoc change comprises aggregating pre-existing options available from runtime frameworks associated with an underlying Business Process Management Suite (BPMS) system and presenting the pre-existing options in the process visualization user interface.

4. The method of claim 1, wherein providing the user interaction options for implementing the ad-hoc change further comprises applying a set of constraints to the user interaction options provided to the client, the set of constraints prohibiting an ad-hoc change contrary to a business intent of the selected process instance.

5. The method of claim 4, wherein the set of constraints applied to the user interaction options provided to the client include compatibility rules to avoid at least one of:

incompatible process changes or process deadlocks.

6. The method of claim 5, wherein the compatibility rules are applied based on the process instance state of the selected process instance.

7. The method of claim 1, wherein the client user interaction options are selected based at least in part on a business context associated with the selected process instance.

8. The method of claim 1, wherein the process instance state copied during migrating the selected process instance from the original process model to the revised process model at runtime includes a container component.

9. The method of claim 8, wherein the container component includes at least one of the following:

at least one status variable or at least of stack data instance.

10. The method of claim 1, wherein migrating the selected process instance from the original process model to the revised process model includes compiling the revised process model after generating the revised process model.

11. The method of claim 1, wherein migrating the selected process instance from the original process model to the revised process model further comprises:

suspending the selected process instance; and

resuming the selected process instance using the revised process model.

12. The method of claim 1, further comprising, after migration, executing the selected process instance based on the revised process model.

13. The method of claim 4, wherein the set of constraints applied to the user interaction options provided to the client are determined based on a user role associated with the client.

14. A computer program product encoded on a non-transitory tangible storage medium, the product comprising computer readable instructions for causing one or more processors to perform operations comprising:

providing process instances of one or more business processes to a client across a network in a process visualization user interface;

receiving a request from the client to initiate an ad-hoc change of a selected process instance associated with an original process model;

providing user interaction options for implementing the ad-hoc change to the client, the user interaction options provided in the process visualization user interface;

receiving a selection of a particular user interaction option for implementing the ad-hoc change from the client; and

implementing the ad-hoc change of the selected process instance at runtime for the original process model associated with the selected process instance, wherein implementing the ad-hoc change of the selected process instance at runtime comprises;

generating a revised process model based on the original process model, the revised process model further including at least one change associated with the selected user interaction option, wherein the original process model is maintained separate from the revised process model;

automatically migrating the selected process instance from the original process model to the revised process model at runtime by moving at least a portion of a process instance state associated with the selected process instance to the revised process model, wherein the process instance state is distinct from the original process model and the revised process model;

executing, after completing the migration, the revised process model using the moved process instance state; and

cancelling, while the revised process model is executing, the execution of the original process model.

15. The computer program product of claim 14, wherein providing the user interaction options for implementing the ad-hoc change comprises aggregating pre-existing options available from runtime frameworks associated with an underlying Business Process Management Suite (BPMS) system and presenting the pre-existing options in the process visualization user interface.

16. The computer program product of claim 14, wherein providing the user interaction options for implementing the ad-hoc change further comprises applying a set of constraints to the user interaction options provided to the client, the set of constraints prohibiting an ad-hoc change contrary to a business intent of the selected process instance.

17. The computer program product of claim 14, wherein the client user interaction options are selected based at least in part on a business context associated with the selected process instance.

18. A system, comprising:

memory operable to store information associated with process instances of one or more business processes; and

one or more processors operable to;

provide process instances of one or more business processes to a client across a network in a process visualization user interface;

receive a request from the client to initiate an ad-hoc change of a selected process instance associated with an original process model;

provide user interaction options for implementing the ad-hoc change to the client, the user interaction options provided in the process visualization user interface;

receive a selection of a particular user interaction option for implementing the ad-hoc change from the client; and

implement the ad-hoc change of the selected process instance at runtime for the original process model associated with the selected process instance, wherein implementing the ad-hoc change of the selected process instance at runtime comprises;

generating a revised process model based on the original process model, the revised process model further including at least one change associated with the selected user interaction option, wherein the original process model is maintained separate from the revised process model;

automatically migrating the selected process instance from the original process model to the revised process model at runtime by moving at least a portion of a process instance state associated with the selected process instance to the revised process model, wherein the process instance state is distinct from the original process model and the revised process model;

executing, after completing the migration, the revised process model using the moved process instance state; and

cancelling, while the revised process model is executing, the execution of the original process model.

19. The system of claim 18, wherein providing the user interaction options for implementing the ad-hoc change comprises aggregating pre-existing options available from runtime frameworks associated with an underlying Business Process Management Suite (BPMS) system and presenting the pre-existing options in the process visualization user interface.