Contextual workflow modeling

• US 20050043982A1
• Filed: 07/29/2004
• Published: 02/24/2005
• Est. Priority Date: 08/22/2003
• Status: Abandoned Application

• Current Assignee: Vinh Dinh Nguyen
• Original Assignee: Vinh Dinh Nguyen
• Inventors: Nguyen, Vinh Dinh
• Application Number:
  US10/901,159
• Publication Number:
  US 20050043982A1
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A workflow modeling technique is proposed wherein a workflow is modeled as a modified finite-state machine executing strictly in the context of a data environment. The data environment isolates the state machine such that the only way to effect a change in the running status of the state machine is through modifications to the data environment. Each state in the state machine has a well-defined lifecycle. The progression of each state through its lifecycle and the transitions to other states are governed by user-defined business rules which operate on data drawn from the data environment. Business rules can also be defined to determine the executability of a particular task. Injection of data into the data environment can be accomplished either by programmatically setting values for user-defined variables or by users filling out forms interactively. User access to forms and individual data fields on a form is determined dynamically from the user'"'"'s role and the current workflow status. Form layouts are handled automatically to accommodate for the visibility of individual data fields at any particular time. The task list for each user is extracted dynamically from the form access information and the current workflow data contents.

Claims

1. A workflow modeling technique based on a finite state machine executing in a data environment wherein

a) Modifications to the data environment can lead to a change in the running status of the state machine.

b) Each state in the finite state machine follows a well-defined lifecycle including but not limited to the following lifecycle stages:

Instantiated, Activated, Aborted, and Completed.

c) Business rules operating on data drawn from the data environment govern the progression of each state through its lifecycle and the transitions from one state to one or more subsequent states.

d) Business rules operating on data drawn from the data environment govern the ability to start a workflow instance.

e) A business rule executes and returns a value that indicates the success or failure of rule execution.

2. The workflow modeling technique in claim 1, wherein each state can take on a single lifecycle stage at any one time.

3. The workflow modeling technique in claim 1, wherein the transitions out of a state are allowed only during specific stages in a state'"'"'s lifecycle.

4. The workflow modeling technique in claim 3, wherein the transitions out of a state can occur at any time, as long as the state is currently in a lifecycle stage permitting outward transitions.

5. The workflow modeling technique in claim 4, wherein the transitions out of a state are allowed only when the state is in Activated lifecycle state.

6. The workflow modeling technique in claim 1, wherein a state without an outward transition is considered an end state without requiring further special designations.

7. The workflow modeling technique in claim 6, wherein an end state cannot be aborted.

8. The workflow modeling technique in claim 1, wherein a workflow is considered completed when all currently active states are end states.

9. The workflow modeling technique in claim 1, wherein one or more states can be designated as initial states that are automatically instantiated upon creation of a workflow instance.

10. The workflow modeling technique in claim 9, wherein a workflow can be restarted by removing all currently active states and instantiating one or more initial states.

11. The workflow modeling technique in claim 1, wherein the workflow status is updated whenever there is a change in the data environment.

12. The workflow modeling technique in claim 1, wherein the workflow status is updated on a regular basis, according to a predefined schedule.

13. The workflow modeling technique in claim 1, wherein changes in the workflow status including but not limited to state instantiation, state activation, state abortion, state completion and all the corresponding times are captured in an audit log.

14. The workflow modeling technique in claim 1, wherein triggers are associated with any change in the workflow status and invoked when these changes occur.

15. The workflow modeling technique in claim 14, wherein a trigger is a piece of scripting code interpreted at runtime and the scripting code can be parameterized with system parameters and user variables.

16. The workflow modeling technique in claim 14, wherein a trigger is a compiled function or method and the complied function or method can be parameterized with system parameters and user variables.

17. The workflow modeling technique in claim 14, wherein a trigger is an SQL query and the SQL query can be parameterized with system parameters and user variables.

18. The workflow modeling technique in claim 14, wherein a trigger is an email message and the email message can be parameterized with system parameters and user variables.

19. The workflow modeling technique in claim 14, wherein a trigger is a message, such as one that can be sent to a message queue, and the message can be parameterized with system parameters and user variables.

20. The workflow modeling technique in claim 14, wherein a trigger is an XML-based message and the XML-based message can be parameterized with system parameters and user variables.

21. The workflow modeling technique in claim 14, wherein a trigger is a web service invocation and the web service invocation can be parameterized with system parameters and user variables.

22. The workflow modeling technique in claim 1, wherein the data environment consists of system parameters and workflow variables.

23. The workflow modeling technique in claim 22, wherein workflow variables comprise of global variables and local variables.

24. The workflow modeling technique in claim 23, wherein local variables can have the same names as global variables and override the global variables with the same names.

25. The workflow modeling technique in claim 22, wherein system parameters and workflow variables can be scalar-valued or array-valued.

26. The workflow modeling technique in claim 25, wherein automatic conversion is performed between scalar-valued and array-valued variables. Scalar values are converted to arrays with a single entry. Array values are converted to scalar values by selecting a single entry from the array.

27. The workflow modeling technique in claim 26, wherein array values are converted to scalar values by selecting the first entry in the array.

28. The workflow modeling technique in claim 22, wherein automatic type conversion is performed on workflow variables.

29. The workflow modeling technique in claim 22, wherein one or more variables can be designated as primary variables.

30. The workflow modeling technique in claim 29, wherein primary variables are used to differentiate different instances of the same workflow.

31. The workflow modeling technique in claim 30, wherein the ordering of primary variables are used in the differentiation of different instances of the same workflow.

32. The workflow modeling technique in claim 22, wherein a workflow variable can be bound to a data field on a form.

33. The workflow modeling technique in claim 22, wherein a workflow variable can be bound to scripting code that is interpreted at runtime and the scripting code can be parameterized with system parameters and other workflow variables.

34. The workflow modeling technique in claim 22, wherein a workflow variable can be bound to compiled functions or methods and the compiled functions or methods can be parameterized with system parameters and other workflow variables.

35. The workflow modeling technique in claim 22, wherein a workflow variable can be bound to SQL queries and the SQL queries can be parameterized with system parameters and other workflow variables.

36. The workflow modeling technique in claim 22, wherein a workflow variable can be bound to a web service invocation and the web service invocation can be parameterized with system parameters and other workflow variables.

37. The workflow modeling technique in claim 22, wherein a workflow variable can be bound to a constant value or an array of constant values.

38. The workflow modeling technique in claim 22, wherein workflow variables are automatically checked for circular dependencies.

39. The workflow modeling technique in claim 22, wherein the values of workflow variables can be set either programmatically or via a user interface.

40. The workflow modeling technique in claim 1, wherein

a) Users interact with the workflow through one or more forms in a form stack.

b) One or more forms in the form stack can be shared among all workflow participants such that all participant work with a single copy of the form.

c) One or more forms in the form stack can be user-specific such that each workflow participant has his own copy of the form.

d) A form comprises of data fields that can be organized in a hierarchical structure with groups containing subgroups and data fields.

41. The workflow modeling technique in claim 40, wherein a user'"'"'s access to a form is determined by a combination of the user'"'"'s role and the current status of the workflow.

42. The workflow modeling technique in claim 41, wherein a user'"'"'s access to a form is specified as a list of ACLs corresponding to the states in the workflow, with the list of currently active states determining the ACLs to use in a cumulative fashion.

43. The workflow modeling technique in claim 42, wherein a default ACL is used in case a state is not associated with an ACL.

44. The workflow modeling technique in claim 43, wherein a user'"'"'s access to data fields or groups of data fields on a form is determined by a combination of the user'"'"'s role and the current status of the workflow.

45. The workflow modeling technique in claim 44, wherein a user'"'"'s access to data fields or groups of data fields on a form is specified as a list of ACLs corresponding to the states in the workflow, with the list of currently active states determining the ACLs to use in a cumulative fashion.

46. The workflow modeling technique in claim 45, wherein a default ACL is used in case a state is not associated with an ACL.

47. The workflow modeling technique in claim 46, wherein user access propagates down the form'"'"'s hierarchical structure.

48. The workflow modeling technique in claim 47, wherein the propagated user access can be overridden on a subgroup or data field.

49. The workflow modeling technique in claim 46, wherein a form is dynamically rendered for each user based on the user'"'"'s current access to the data fields on the form.

50. The workflow modeling technique in claim 49, wherein visible data fields on a form are rearranged to take up space that otherwise would be occupied by invisible fields.

51. The workflow modeling technique in claim 46, wherein each data field on a form can be designated as required and the form can be optionally flagged to force users to fill in all required fields before submitting the form.

52. The workflow modeling technique in claim 51, wherein the presence of one or more required, writable, and unfilled data fields on a form indicates that a user is required to take an action to provide data for these fields and that the form is required.

53. The workflow modeling technique in claim 52, where in a task list for each user is dynamically generated by inspecting the form stack to see if at least one form is required.

54. The workflow modeling technique in claim 51, where in a form with no writable data fields is considered a read-only form and users cannot modify any data field on the form.

55. The workflow modeling technique in claim 51, where in a form with at least one writable data field but no required, writable, unfilled data fields is considered a completed form and users can optionally modify the writable data fields.

56. The workflow modeling technique in claim 40, wherein different data fields in the same form or different forms can be given the same binding name so that these data fields always share the same data value.

57. The workflow modeling technique in claim 40, wherein a particular form in the form stack is designated as the workflow initiation form, i.e., the form that is shown when a user initiates a workflow.

58. The workflow modeling technique in claim 57, wherein the form at the top of the form stack is designated as the workflow initiation form.

59. The workflow modeling technique in claim 40, wherein each data field on a form can be bound to scripting code that is interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

60. The workflow modeling technique in claim 40, wherein each data field on a form can be bound to compiled functions or methods and the complied functions or methods can be parameterized with system parameters and workflow variables.

61. The workflow modeling technique in claim 40, wherein each data field on a form can be bound to SQL queries and the SQL queries can be parameterized with system parameters and workflow variables.

62. The workflow modeling technique in claim 40, wherein each data field on a form can be bound to an object attribute store that can store data attributes of different types for a given object.

63. The workflow modeling technique in claim 40, wherein data fields on a form are automatically checked for circular dependencies.

64. The workflow modeling technique in claim 40, wherein the data values entered for each data field are captured in an audit log.

65. The workflow modeling technique in claim 1, wherein users can be assigned automatically or manually to a workflow instance as participants in one or more roles associated with the workflow.

66. The workflow modeling technique in claim 65, wherein the number of participants in each role can be defined as a range of values, with the upper limit being the desired number of participants and the lower limit being the required number of participants.

67. The workflow modeling technique in claim 66, wherein the upper and/or lower limits can be specified as a fixed value.

68. The workflow modeling technique in claim 66, wherein the upper and/or lower limits are bound to scripting code that is interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

69. The workflow modeling technique in claim 66, wherein the upper and/or lower limits are bound to compiled functions or methods and the complied functions or methods can be parameterized with system parameters and workflow variables.

70. The workflow modeling technique in claim 66, wherein the upper and/or lower limits are bound to SQL queries and the SQL queries can be parameterized with system parameters and workflow variables.

71. The workflow modeling technique in claim 65, wherein a role can be flagged so that assignments to the role can be made either incrementally or in an all- or-nothing fashion.

72. The workflow modeling technique in claim 65, wherein each role is associated with one or more assignment rules, each of which in turn is associated with one or more resource pools, i.e., groups of users and other resources that can be assigned to the workflow. If an assignment rule executes successfully, resources are drawn from the associated resource pools and assigned to the workflow in the given role.

73. The workflow modeling technique in claim 72, wherein one or more states can be selected as the points where automatic assignments to a particular role are to commence.

74. The workflow modeling technique in claim 73, wherein if no commencement points are specified for a role, automatic assignments are made upon the initiation of the workflow instance.

75. The workflow modeling technique in claim 72, wherein the assignment rules are executed in a pre-defined order until the assignment requirement for the associated role is fulfilled.

76. The workflow modeling technique in claim 72, wherein each assignment rule can be associated with triggers that are automatically invoked upon successful execution of the assignment rule.

77. The workflow modeling technique in claim 76, wherein a trigger is a piece of scripting code interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

78. The workflow modeling technique in claim 76, wherein a trigger is a compiled function or method and the complied function or method can be parameterized with system parameters and workflow variables.

79. The workflow modeling technique in claim 76, wherein a trigger is an SQL query and the SQL query can be parameterized with system parameters and workflow variables.

80. The workflow modeling technique in claim 76, wherein a trigger is an email message and the email message can be parameterized with system parameters and workflow variables.

81. The workflow modeling technique in claim 76, wherein a trigger is a message, such as one that can be sent to a message queue, and the message can be parameterized with system parameters and user variables.

82. The workflow modeling technique in claim 76, wherein a trigger is an XML-based message and the XML-based message can be parameterized with system parameters and user variables.

83. The workflow modeling technique in claim 76, wherein a trigger is a web service invocation and the web service invocation can be parameterized with system parameters and user variables.

84. The workflow modeling technique in claim 65, wherein one or more roles can be flagged so that they are automatically assigned to the user who initiated the workflow instance.

85. The workflow modeling technique in claim 65, wherein a role can be flagged so that it will not be automatically assigned to the user who initiated the workflow instance.

86. The workflow modeling technique in claim 1, wherein a business rule can be a piece of scripting code interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

87. The workflow modeling technique in claim 1, wherein a business rule can be a compiled function or method and the function or method can be parameterized with system parameters and workflow variables.

88. The workflow modeling technique in claim 1, wherein a business rule can be a message, such as one that can be sent to a message queue, and the message can be parameterized with system parameters and workflow variables.

89. The workflow modeling technique in claim 1, wherein a business rule can be an XML-based message and the XML-based message can be parameterized with system parameters and workflow variables.

90. The workflow modeling technique in claim 1, wherein a business rule can be a web service invocation and the web service invocation can be parameterized with system parameters and workflow variables.

91. The workflow modeling technique in claim 1, wherein business rules can be chained together and executed in a predefined order.

92. The workflow modeling technique in claim 91, wherein the execution of a chain of business rules is terminated upon the first successful execution of a business rule in the chain.

93. The workflow modeling technique in claim 91, wherein a business rule can be flagged as fall-through so that the execution of a chain of business rules will continue despite the successful execution of this business rule.

94. The workflow modeling technique in claim 1, wherein a business rule can be associated with one or more triggers that are automatically invoked upon successful rule execution.

95. The workflow modeling technique in claim 94, wherein a trigger is a piece of scripting code interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

96. The workflow modeling technique in claim 94, wherein a trigger is a compiled function or method and the complied function or method can be parameterized with system parameters and workflow variables.

97. The workflow modeling technique in claim 94, wherein a trigger is an SQL query and the SQL query can be parameterized with system parameters and workflow variables.

98. The workflow modeling technique in claim 94, wherein a trigger is an email message and the email message can be parameterized with system parameters and workflow variables.

99. The workflow modeling technique in claim 94, wherein a trigger is a message, such as one that can be sent to a message queue, and the message can be parameterized with system parameters and workflow variables.

100. The workflow modeling technique in claim 94, wherein a trigger is an XML-based message and the XML-based message can be parameterized with system parameters and workflow variables.

101. The workflow modeling technique in claim 94, wherein a trigger is a web service invocation and the web service invocation can be parameterized with system parameters and workflow variables.

102. The workflow modeling technique in claim 1, wherein triggers can be associated with the entry into and the exit from each lifecycle stage.

103. The workflow modeling technique in claim 102, wherein a trigger is a piece of scripting code interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

104. The workflow modeling technique in claim 102, wherein a trigger is a compiled function or method and the complied function or method can be parameterized with system parameters and workflow variables.

105. The workflow modeling technique in claim 102, wherein a trigger is an SQL query and the SQL query can be parameterized with system parameters and workflow variables.

106. The workflow modeling technique in claim 102, wherein a trigger is an email message and the email message can be parameterized with system parameters and workflow variables.

107. The workflow modeling technique in claim 102, wherein a trigger is a message, such as one that can be sent to a message queue, and the message can be parameterized with system parameters and workflow variables.

108. The workflow modeling technique in claim 102, wherein a trigger is an XML-based message and the XML-based message can be parameterized with system parameters and workflow variables.

109. The workflow modeling technique in claim 102, wherein a trigger is a web service invocation and the web service invocation can be parameterized with system parameters and workflow variables.

110. The workflow modeling technique in claim 1, wherein a state can optionally have a due time.

111. The workflow modeling technique in claim 110, wherein the due time is computed once when the state is instantiated.

112. The workflow modeling technique in claim 110, wherein the due time is computed once when the state is activated.

113. The workflow modeling technique in claim 110, wherein the due time is recomputed once when an already active state is reactivated.

114. The workflow modeling technique in claim 110, wherein the due time is recomputed every time the workflow instance is updated.

115. The workflow modeling technique in claim 110, wherein the due time is recomputed every time it is accessed.

116. The workflow modeling technique in claim 110, wherein a state can be given a duration and the due time is computed as the start time plus the duration.

117. The workflow modeling technique in claim 116, wherein the start time is start of a state'"'"'s lifecycle state.

118. The workflow modeling technique in claim 116, wherein the start time is time the workflow instance was initiated.

119. The workflow modeling technique in claim 110, wherein the due time is computed by executing a piece of scripting code interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

120. The workflow modeling technique in claim 110, wherein the due time is computed by executing a compiled function or method and the complied function or method can be parameterized with system parameters and workflow variables.

121. The workflow modeling technique in claim 110, wherein the due time is computed by executing an SQL query and the SQL query can be parameterized with system parameters and workflow variables.

122. The workflow modeling technique in claim 110, wherein a state can be associated with escalation rules that are evaluated on a regular basis and upon successful execution, cause some action to be taken.

123. The workflow modeling technique in claim 122, wherein each escalation rule is can be evaluated successfully at most once.

124. The workflow modeling technique in claim 122, wherein the action associated with an escalation rule is a piece of scripting code that is interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

125. The workflow modeling technique in claim 122, wherein the action associated with an escalation rule is a compiled method or function and the compiled method or function can be parameterized with system parameters and workflow variables.

126. The workflow modeling technique in claim 122, wherein the action associated with an escalation rule is a SQL query and the SQL query can be parameterized with system parameters and workflow variables.

127. The workflow modeling technique in claim 122, wherein the action associated with an escalation rule is an email message and the email message can be parameterized with system parameters and workflow variables.

128. The workflow modeling technique in claim 122, wherein the action associated with an escalation rule is a message, such as one that can be sent to a message queue, and the message can be parameterized with system parameters and workflow variables.

129. The workflow modeling technique in claim 122, wherein the action associated with an escalation rule is an XML-based message and the XML-based message can be parameterized with system parameters and workflow variables.

130. The workflow modeling technique in claim 122, wherein the action associated with an escalation rule is a web service invocation and the web service invocation can be parameterized with system parameters and workflow variables.

131. The workflow modeling technique in claim 122, wherein the escalation rule can be specified as a relative time measured from the due time of the corresponding state.

132. The workflow modeling technique in claim 122, wherein the escalation rule is a piece of scripting code that is interpreted at runtime and the scripting code can be parameterized with system parameters and workflow variables.

133. The workflow modeling technique in claim 122, wherein the escalation rule is a compiled function or method and the compiled function or method can be parameterized with system parameters and workflow variables.

134. The workflow modeling technique in claim 122, wherein the escalation rule is a web service invocation and the web service invocation can be parameterized with system parameters and workflow variables.