Methods and apparatuses to provide composite applications

• US 20070011334A1
• Filed: 03/22/2006
• Published: 01/11/2007
• Est. Priority Date: 11/03/2003
• Status: Abandoned Application

• Current Assignee: Apacheta (ResMed Incorporated)
• Original Assignee: Apacheta (ResMed Incorporated)
• Inventors: Collins, Jim, Skomra, Stewart, Clare, Peter, Higgins, Steven
• Application Number:
  US11/387,245
• Publication Number:
  US 20070011334A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 11/3604 Software analysis for verifying properties of programs byte-code verification G06F9/44589
• CPC Class Codes: G06F 8/34 Graphical or visual programming

Abstract

Methods and apparatuses to enable the development, deployment and update of composite applications on mobile devices. In one embodiment, a method processor in a mobile device may include a workflow engine and a cache manager which looks ahead of the current execution of a workflow to preload modules. The method processor may present modal user interfaces in a non-modal way to eliminate flicker, and use a logger to stamp the workflow related data with real time measurements, such as time, location, and vehicle bus information. The logger may capture screen images and global data of the workflow during the execution. The log data stream may be collected and sent from the mobile device in real time, or in a batch mode, for monitoring, debugging, diagnosing or tuning the execution of a workflow, for providing hot update, help and guidance against deviation during the execution, and for other features.

Claims

1. A method on a mobile device, comprising:

receiving a representation of a workflow over a wireless connection at the mobile device to specify information including;

locations of codes of a plurality of tasks;

mappings between local variables of the tasks and global variables maintained by the mobile device; and

relations between outcomes of the tasks and corresponding ones of the tasks that are scheduled to be execute when corresponding outcomes are generated; and

loading and executing the codes on the mobile device according to the representation of the workflow.

2. The method of claim 1, wherein the representation of the workflow is in an Extensible Markup Language (XML).

3. The method of claim 2, wherein a code of one of the tasks is in a shared library on the mobile device.

4. A method, comprising:

executing a workflow interpreter in a process running on a virtual machine for a programming language, the interpreter to parse a workflow defining execution flow among multiple modules, at least one module of the modules being in the programming language; and

loading the module in the programming language into the process for execution according to the workflow.

5. The method of claim 4, wherein the workflow is defined in an extensible markup language (XML).

6. The method of claim 5, wherein the programming language is Java byte code or Microsoft Intermediate Language.

7. The method of claim 5, wherein the module in the programming language is compiled from code in one or more programming languages including one or more of:

C, C++, C#, and Java.

8. The method of claim 4, wherein one of the modules generates a graphical user interface.

9. The method of claim 8, wherein one of the modules does not generate a graphical user interface.

10. The method of claim 4, wherein one of the modules specifies a workflow.

11. A method, comprising:

executing a workflow engine in a first thread of a process, the workflow engine to parse a workflow defining execution flow among multiple modules; and

executing a cache manager in a second thread of the process, the cache manager to manage caching of one or more modules of the multiple modules of the workflow.

12. The method of claim 11, wherein the cache manager is configurable to adjust a usage of computation resource used by the cache manager.

13. The method of claim 12, wherein the cache manage is dynamically configurable to adjust a limit on a number of modules to be cached.

14. The method of claim 12, wherein the cache manage is dynamically configurable to adjust a limit on an amount of cache memory.

15. The method of claim 11, wherein the cache manager pre-loads the one or more modules into cache based on likelihood modules to be executed after execution of a current module.

16. A method, comprising:

processing a first version of a workflow which defines first execution flow among first multiple modules;

during an execution of the workflow according to the first version of the workflow, receiving a second version of the workflow which defines second execution flow among second multiple modules, the first multiple modules and the second multiple modules having at least one common module; and

continuing the execution according to the second version of the workflow without restarting.

17. The method of claim 16, wherein said continuing the execution comprises:

executing the workflow up to the common module according to the first version of the workflow; and

executing the workflow according to second version of the workflow after an execution of the common module.

18. The method of claim 16, wherein the first execution flow is different from the second execution flow.

19. The method of claim 18, wherein the first multiple modules correspond to the second multiple modules.

20. The method of claim 18, wherein the second multiple modules include a module that is not in the first version of the workflow.

21. The method of claim 18, wherein the first multiple modules include a module that is not in the second version of the workflow.

22. A method, comprising:

processing a workflow described in a file which defines execution flow among multiple modules;

during execution of the workflow, determining a version of one module of the multiple modules; and

loading the version of the module for execution of the workflow.

23. The method of claim 22, wherein the version is a latest version of multiple versions of the module.

24. The method of claim 23, wherein the version is determined according to version number.

25. The method of claim 23, wherein the version is determined according to time of arrival of the versions at a mobile device on which the method is performed.

26. The method of claim 23, wherein the module comprises a file which defines execution flow among multiple modules;

and the latest version is loaded in a cache to replace a previous version of the module during the execution of the workflow.

27. The method of claim 23, wherein the module comprises a shared library which is in a same programming language as a workflow engine which processes the workflow;

and the method further comprising;

unloading a previous version of the module during execution of the workflow.

28. The method of claim 23, further comprising:

receiving the latest version of the module during execution of the workflow.

29. The method of claim 22, wherein the module is not available on a mobile device on which the method is performed when execution of the workflow is initiated.

30. A method, comprising:

executing a workflow engine to process a queue of workflows, each of the workflows defining execution flow among one or more modules;

waiting for reception of one or more workflows to be added to the queue when the queue is empty; and

receiving a user selection to start one of workflows in the queue.

31. The method of claim 30, further comprising:

automatically selecting a workflow from the queue for execution using a user request based on a priority indicator of the workflow.

32. The method of claim 30, further comprising:

removing a workflow from the queue after an execution of the workflow.

33. The method of claim 30, further comprising:

adding a workflow back to the queue after an execution of the workflow.

34. The method of claim 30, further comprising:

presenting a graphical user interface to manipulate the queue;

wherein the workflow engine processes the queue according to a workflow.

35. A method, comprising:

loading a first task module from a first vendor to execute a workflow application on a mobile device; and

loading a second task module from a second vendor to execute the workflow application on the mobile device.

36. The method of claim 35, further comprising:

generating a workflow application including the first task module from a first vendor and the second task module from the second vendor.

37. The method of claim 36, wherein the workflow application is generate without source coded access to at least one of the first task module from a first vendor and the second task module from the second vendor.

38. A method, comprising:

receiving a request to access a device of a type from a module of a workflow running on a mobile device;

determining a first device of the type currently available to the mobile device;

selecting one routine from a plurality of routines capable of operating a plurality of different devices of the type; and

executing the routine according to the request.

39. The method of claim 38, wherein the method is performed on the mobile device running a workflow engine which executes the workflow.

40. The method of claim 39, wherein said selecting is performed by a library code installed on the mobile device.

41. A method, comprising:

executing a first module by a workflow engine in a first thread; and

executing a second module by the workflow engine in a second thread concurrently with the first thread.

42. The method of claim 41, wherein the first module comprises a first workflow;

and the second module comprises a second workflow.

43. The method of claim 42, wherein the first module and the second module are in a third workflow executed in the workflow engine.

44. The method of claim 43, wherein a same outcome of a module in the third workflow leads to both the first module and the second module.

45. The method of claim 43, wherein the second module follows the first module in the third workflow.

46. A method, comprising:

receiving a request to close a first form of a first module of a workflow, the workflow specifying a flow from the first module to the second module;

determining a second form of the second module of the workflow; and

rendering the second form before closing the first form.

47. The method of claim 46, further comprising:

intercepting by a workflow engine an event to close the first form;

wherein the workflow engine loads the second form before closing the first form.

48. The method of claim 47, wherein the workflow engine loads the second form in a non-modal way.

49. The method of claim 48, wherein the second form is painted before the first form is closed.

50. The method of claim 49, wherein the second form is painted above the first form before the first form is closed.

51. The method of claim 49, wherein the second form is painted under the first form before the first form is closed.

52. The method of claim 49, wherein the workflow engine loads the second form for rendering after the event to close the first form is intercepted in the workflow engine.

53. A method, comprising:

displaying help information relative to a current portion of user interface of a workflow during a first execution of the workflow; and

running a second execution of the workflow in a training mode in response to a user request during the first execution of the workflow.

54. The method of claim 53, wherein the first execution of the workflow is maintained in a first thread while the second execution of the workflow is executed in the training mode in second thread.

55. The method of claim 54, further comprising:

comparing log data of the second execution of the workflow with log data of a third execution of the workflow to determine a deviation in real time.

56. A method, comprising:

logging information related to a workflow as being processed, the workflow defining execution flow among multiple modules; and

associating the information related to the workflow with measurement information.

57. The method of claim 56, wherein the workflow is provided as input to a workflow execution engine which collects the information related to the workflow as being processed for a logger to log the information related to the workflow in association with the measurement information.

58. The method of claim 57, wherein the logger collects the measurement information from one or more peripheral devices.

59. The method of claim 56, wherein the measurement information includes time obtained from a clock.

60. The method of claim 59, wherein the measurement information further includes a space location.

61. The method of claim 60, wherein the space location is obtained from a position determination device co-located with a mobile device which performs the method.

62. The method of claim 60, wherein the measurement information further includes vehicle bus information.

63. The method of claim 60, wherein the measurement information further includes a strength of a wireless communication signal.

64. The method of claim 60, wherein the information related to the workflow and the measurement information include an indication of availability of a network resource.

65. The method of claim 64, further comprising:

estimating future availability of the network resource based at least partially on the information related to the workflow and the measurement information.

66. The method of claim 56, wherein the information related to the workflow is logged when an execution of the workflow enters or exits one module of the multiple modules.

67. The method of claim 66, wherein the information related to the workflow comprises one or more of:

a state of a memory;

a state of a microprocessor;

a value of a variable to be provided to or obtained from the module;

a name of the module;

a resource location of the module; and

a provider of the module.

68. The method of claim 56, further comprising:

transmitting the information related to the workflow with the measurement information in real time to a remote location over a network connection.

69. The method of claim 56, further comprising:

storing the information related to the workflow with the measurement information for transmission to a remote location over a network connection in a batch mode.

70. The method of claim 56, further comprising:

loading one module of the multiple modules for execution;

capturing a screen image of a graphical user interface rendered by the module;

wherein the information related to the workflow comprises the screen image.

71. A method on a mobile device, comprising:

receiving a representation of a workflow over a wireless connection at the mobile device to specify a plurality of tasks;

loading and executing the executable codes on the mobile device according to the representation of the workflow; and

during execution of the workflow, generating log data when entering or exiting individual ones of the tasks according to the workflow.

72. The method of claim 71, wherein a first one of the tasks generates a graphical user interface for user interaction.

73. The method of claim 72, further comprising:

capturing a screen image of the graphical user interface as part of the log data when the first one of the tasks is executed.

74. The method of claim 73, further comprising:

transmitting the log data in real time over a network connection to an integrated development environment not running on the mobile device.

75. A method, comprising:

receiving a threshold level indicator;

determining a level identifier of a module of a workflow, the workflow defining execution flow among multiple modules;

determining whether or not to log information related to execution of the module based on a comparison between the threshold level indicator and the level identifier of the module.

76. The method of claim 75, further comprising:

determining a set of data items to be logged for the module according to a configuration file.

77. The method of claim 75, wherein the threshold level indicator specifies a set of level identifiers which when associated with a module causes the module to be logged.

78. The method of claim 75, wherein the workflow is specified in an extensible markup language (XML);

and the level identifier is specified as an attribute or an element designed to specify the module.

79. The method of claim 78, wherein the threshold level indicator is specified in one of:

a configuration file for a mobile device on which the method is performed;

a configuration file specific for the workflow;

a definition of the workflow in extensible markup language (XML).

80. A method, comprising:

receiving a stream of log data of an execution of a workflow from a mobile device, the workflow defining execution flow among multiple modules; and

re-producing the execution of the workflow on a system different from the mobile device according to the stream of log data.

81. The method of claim 80, wherein the stream of log data is received by the system from the mobile device in real time;

and the execution of the workflow is re-produced on the system in real time.

82. The method of claim 81, further comprising:

indicating portions of the workflow that has not been executed on a graphical representation of the workflow.

83. The method of claim 81, further comprising:

indicating portions of the workflow that has been executed on a graphical representation of the workflow; and

providing access to the stream of log data from the graphical representation of the workflow.

84. The method of claim 80, wherein said re-producing comprises:

extracting input to the multiple modules from the stream of log data;

following an execution path of the workflow according to the stream of log data; and

providing input to the multiple modules according to the input extracted from the stream of log data.

85. A method in a computing device, comprising:

receiving a first stream of log data of a first execution of a workflow, the workflow defining execution flow among multiple modules;

comparing the first stream of log data of the first execution of the workflow with log data of a second execution of the workflow during the execution of the second execution; and

determining a deviation between the first execution of the workflow and the second execution of the workflow.

86. The method of claim 85, further comprising:

generating an alert in response to a detection of a deviation in execution path between the first execution of the workflow and the second execution of the workflow.

87. The method of claim 86, further comprising:

correcting an execution path of the second execution of the workflow in accordance with an execution path of the first execution of the workflow.

88. The method of claim 87, wherein the second execution of the workflow is in a workflow engine;

and the workflow engine determines the deviation and corrects the execution path of the second execution of the workflow in accordance with the execution path of the first execution of the workflow.

89. The method of claim 87, further comprising:

receiving the second stream of log data of the second execution of the workflow in real time from a mobile device during the execution of the second execution on the mobile device; and

transmitting the alert to the mobile device to correct the execution path of the second execution of the workflow in accordance with an execution path of the first execution of the workflow.

90. The method of claim 85, further comprising:

generating an alert in response to a detection of a deviation in data between the first execution of the workflow and the second execution of the workflow; and

correcting data of the second execution of the workflow in accordance with data of the first execution of the workflow.

91. The method of claim 85, further comprising:

counting a number of times that the second execution fails to to be consistent with the first stream of log data; and

automatically correcting the second execution in accordance with the first stream of log data in response to the number of times reaching a threshold value.

92. The method of claim 85, further comprising:

searching the first stream of log data to find an execution point in the first execution of the workflow matching to a current execution point in the second execution of the workflow.

93. The method of claim 92, wherein a criterion to find an execution point in the first execution of the workflow matching to the current execution point in the second execution of the workflow includes one or more of:

a value of a variable and a path of one or more modules leading to a module currently being executed in the second execution of the workflow.

94. The method of claim 85, further comprising:

providing help to a user of the device to interactive with a user interface of the workflow.

95. The method of claim 85, wherein said providing help comprises:

executing a help module in response to the deviation.

96. The method of claim 95, further comprising:

logging information indicating the deviation between the first execution of the workflow and the second execution of the workflow

97. A method, comprising:

executing a workflow in a workflow engine, the workflow defining execution flow among multiple modules including at least one user interface module which when executed presents a graphical user interface;

loading the user interface module by the workflow engine for execution to generate the graphical user interface; and

capturing a screen image of the graphical user interface by the workflow engine to document the user interface module.

98. The method of claim 97, further comprising:

transmitting the screen image of the graphical user interface in real time to a location away from a mobile device on which the method is performed.

99. The method of claim 97, further comprising:

storing the screen image of the graphical user interface with log data of an execution of the workflow on a mobile device on which the method is performed;

transmitting the screen image and the log data in a batch mode from the mobile device.

100. The method of claim 97, further comprising:

the workflow engine running through the workflow without user interaction with the graphical user interface.

101. The method of claim 100, further comprising:

the workflow engine executing the workflow engine automatically to capture screen images of user interface modules of the workflow.

102. A method, comprising:

displaying a graphical representation of a workflow; and

displaying a version of a screen image of a graphical user interface generated by a module of the workflow in the graphical representation of the workflow.

103. The method of claim 102, further comprising:

reducing a size of the screen image to generate the version of the screen image.

104. The method of claim 102, wherein the version of the screen image is displayed near an iconic representation of the module in the graphical representation of the workflow.

105. The method of claim 104, further comprising:

in response to a user selection of the version of the screen image, displaying a full version of the screen image.

106. The method of claim 102, wherein the version of the screen image displayed as an iconic representation of the module in the graphical representation of the workflow.

107. The method of claim 106, further comprising:

in response to a user selection of the version of the screen image, displaying a graphical user interface to edit the module.

108. The method of claim 106, further comprising:

in response to a user selection of an icon representation of a further module of the workflow, displaying a graphical user interface to edit the further module which when executed does not display a graphical user interface.

109. The method of claim 102, further comprising:

receiving the screen image in real time from a remote mobile device which executes the workflow.

110. The method of claim 109, further comprising:

receiving an update version of the screen image of the graphical user interface when a screen image of the graphical user interface on the remote mobile device is changed.

111. The method of claim 110, further comprising:

receiving a stream of log data of execution of the workflow on the mobile device;

presenting the log data in an integrated environment in which the graphical representation of the workflow is displayed.

112. The method of claim 111, wherein the stream of log data is received in the integrated environment in real time.

113. A method, comprising:

receiving a stream of log data of execution of a workflow; and

identifying an occurrence of a predefined pattern in the stream of log data.

114. The method of claim 113, wherein said identifying is performed during the execution of the workflow.

115. The method of claim 114, further comprising:

logging the occurrence of the predefined pattern.

116. The method of claim 115, further comprising:

generating an alerting in response to a detection of the occurrence of the predefined pattern.

117. The method of claim 116, wherein the predefined pattern comprises a combination of a plurality of log data items.

118. The method of claim 116, further comprising:

logging the occurrence of the predefined pattern.

119. The method of claim 116, further comprising:

executing a workflow in response to the occurrence of the predefined pattern.

120. A method, comprising:

determining a reference execution flow of a workflow;

comparing a first execution flow of the workflow to the reference execution flow based on log data generated for the first execution flow;

predicting an indication of a performance goal based on a result of the comparison.

121. The method of claim 120, wherein the performance goal comprises day sales outstanding (DSO).

122. The method of claim 120, further comprising:

modifying an execution of the workflow to improve a prediction of performance goal.

123. The method of claim 122, wherein said modifying comprises:

modifying the workflow to guide an execution flow of the workflow towards a preferred execution flow.

124. The method of claim 120, wherein said modifying comprises:

modifying business logic of the workflow to improve a prediction of the day sales outstanding (DSO).

125. The method of claim 120, wherein said comparing and predicting are performed in real time on a mobile device on which the first execution flow is generated.

126. A method, comprising:

generating a network connectivity map from log data of execution of one or more workflows on one or more mobile devices; and

updating a workflow according to the network connectivity map.

127. The method of claim 126, further comprising:

predicting availability of network connectivity based at least partially on the network connectivity map; and

wherein said updating is at least partially based on the availability predicated.

128. The method of claim 127, wherein the availability is predicted based further on a measurement of a location and a speed of movement of a mobile device on which the method is performed.

129. The method of claim 128, wherein the availability is predicted based further on history of execution of the workflow on the mobile device.

130. The method of claim 126, further comprising:

increasing a priority of a communication operation when outage of network connection is predicted.

131. A method on a mobile device, comprising:

determining a first cost to transmit first data over a first network connection;

determining a second cost to transmit the first data over a second network connection;

determining a third cost to transmit second data over the first network connection;

determining a fourth cost to transmit the second data over the second network connection; and

scheduling transmission of the first and second data based on the first, second, third and fourth costs.

132. The method of claim 131, wherein one of the first and second network connection comprises:

a connection in accordance with IEEE 802.15;

a connection in accordance with IEEE 802.11; and

a connection in accordance with IEEE 802.16.

133. A machine readable media embodying instructions, the instructions causing a mobile device to perform a method, the method comprising:

receiving a representation of a workflow over a wireless connection at the mobile device to specify information including;

locations of codes of a plurality of tasks;

mappings between local variables of the tasks and global variables maintained by the mobile device; and

relations between outcomes of the tasks and corresponding ones of the tasks that are scheduled to be execute when corresponding outcomes are generated; and

loading and executing the codes on the mobile device according to the representation of the workflow.

134. The media of claim 133, wherein the method further comprises:

executing a workflow interpreter in a process running on a virtual machine for a programming language, the interpreter to parse the workflow defining execution flow among multiple modules, at least one module of the modules being in the programming language; and

loading the module in the programming language into the process for execution according to the workflow.

135. The media of claim 133, wherein the method further comprises:

executing a workflow engine in a first thread of a process, the workflow engine to parse a workflow defining execution flow among multiple modules; and

executing a cache manager in a second thread of the process, the cache manager to manage caching of one or more modules of the multiple modules of the workflow.

136. The media of claim 133, wherein the method further comprises:

processing a first version of the workflow which defines first execution flow among first multiple modules;

during an execution of the workflow according to the first version of the workflow, receiving a second version of the workflow which defines second execution flow among second multiple modules, the first multiple modules and the second multiple modules having at least one common module; and

continuing the execution according to the second version of the workflow without restarting.

137. The media of claim 133, wherein the method further comprises:

processing a workflow described in a file which defines execution flow among multiple modules;

during execution of the workflow, determining a version of one module of the multiple modules; and

loading the version of the module for execution of the workflow.

138. The media of claim 133, wherein the method further comprises:

executing a workflow engine to process a queue of workflows, each of the workflows defining execution flow among one or more modules;

waiting for reception of one or more workflows to be added to the queue when the queue is empty; and

receiving a user selection to start one of workflows in the queue.

139. The media of claim 133, wherein the method further comprises:

loading a first task module from a first vendor to execute a workflow application on a mobile device; and

loading a second task module from a second vendor to execute the workflow application on the mobile device.

140. The media of claim 133, wherein the method further comprises:

receiving a stream of log data of an execution of the workflow from a mobile device; and

re-producing the execution of the workflow according to the stream of log data.

141. The media of claim 133, wherein the method further comprises:

displaying help information relative to a current portion of user interface of the workflow during a first execution of the workflow; and

running a second execution of the workflow in a training mode in response to a user request during the first execution of the workflow.

142. A machine readable media embodying instructions, the instructions causing a mobile device to perform a method, the method comprising:

receiving a request to close a first form of a first module of a workflow, the workflow specifying a flow from the first module to the second module;

determining a second form of the second module of the workflow; and

rendering the second form before closing the first form.

143. A machine readable media embodying instructions, the instructions causing a mobile device to perform a method, the method comprising:

logging information related to a workflow as being processed, the workflow defining execution flow among multiple modules; and

associating the information related to the workflow with measurement information.

144. The media of claim 143, wherein said logging comprises generating log data when entering or exiting individual ones of tasks of the workflow.

145. The media of claim 143, wherein the method further comprises:

receiving a threshold level indicator;

determining a level identifier of a module of the workflow;

determining whether or not to log information related to execution of the module based on a comparison between the threshold level indicator and the level identifier of the module.

146. The media of claim 143, wherein the method further comprises:

receiving a first stream of log data of a first execution of the workflow;

comparing the first stream of log data of the first execution of the workflow with log data of a second execution of the workflow during the execution of the second execution; and

determining a deviation between the first execution of the workflow and the second execution of the workflow.

147. The media of claim 143, wherein the method further comprises:

identifying an occurrence of a predefined pattern, during the execution of the workflow, using the information related to the workflow and the measurement information.

148. A mobile handheld device, comprising:

a wireless communication unit to receive a representation of a workflow over a wireless connection at the mobile device to specify information including;

locations of codes of a plurality of tasks;

mappings between local variables of the tasks and global variables maintained by the mobile device; and

relations between outcomes of the tasks and corresponding ones of the tasks that are scheduled to be execute when corresponding outcomes are generated; and

a processor coupled to the wireless communication unit to load and execute the codes on the mobile device according to the representation of the workflow;

wherein the processor is to execute the workflow in one thread of a process and executes a cache manager in a second thread of the process to manage caching of one or more modules of the workflow;

wherein the processor is to log information related to the workflow as being processed and associate the information related to the workflow with measurement information.

149. The mobile device of claim 148, wherein the processor is further to:

trap a request to close a first form of a first module of the workflow;

determine a second form of the second module of the workflow; and

rendering the second form before closing the first form.

wherein the workflow specifies a flow from the first module to the second module.

150. A system, comprising:

a dispatch station to generate and customize a workflow, the workflow to defining execution flow among multiple modules;

a population of mobile devices;

an integration server coupled to the dispatch station, the integration server to transmit a version of the workflow to one of the mobile devices via a wireless connection;

wherein the workflow specifies;

locations of codes of a plurality of tasks;

mappings between local variables of the tasks and global variables maintained by the mobile device; and

relations between outcomes of the tasks and corresponding ones of the tasks that are scheduled to be execute when corresponding outcomes are generated.

151. A machine readable media embodying instructions, the instructions causing a mobile device to perform a method, the method comprising:

defining a set of global variables maintained by the mobile device;

locating of codes of a plurality of tasks;

mapping between local variables of the tasks and the global variables; and

loading and executing the codes on the mobile device according to relations between outcomes of the tasks and corresponding ones of the tasks that are scheduled to be execute when corresponding outcomes are generated.

152. A machine readable media embodying instructions, the instructions causing a mobile device to perform a method, the method comprising:

processing log data comprising;

information related to a workflow generated during execution of the workflow, and measurement information associated with the information related to the workflow;

wherein the measurement information is obtained while the information related to a workflow is generated.

153. The media of claim 152, wherein said processing log data comprises:

determining a time duration of an event.

154. The media of claim 152, wherein said processing log data comprises:

determining location information of an event.

155. A machine readable media embodying data generated from execution instructions, the instructions causing a mobile device to perform a method, the method comprising:

logging information related to a workflow as being processed, the workflow defining execution flow among multiple modules; and

associating the information related to the workflow with measurement information.

156. A method of providing training to users of mobile devices, the method comprising:

recording a first execution path of a workflow;

receiving log data streams generated from the users of the mobile devices running the workflow;

monitoring executions of the workflow by the users on the mobile devices based on the log data streams; and

providing help to one user of the users based on said monitoring.

157. The method of claim 156, wherein said providing comprises:

providing a new version of the workflow with a help module to the user to replace a current version of the workflow being executed on a mobile device of the user.

158. The method of claim 157, further comprising:

dynamically generating the new version of the workflow based on said monitoring.

159. A method of incentivizing an operator of a mobile device, the method comprising:

providing one or more rules to the mobile device for an incentive program;

monitoring actual performance of the operator of the mobile device during execution of a workflow;

providing to the user of the mobile device with real-time status based on said monitoring to determine performance according to the one or more rules.

160. The method of claim 159, further comprising:

allowing the mobile operator to customize a goal of the mobile operator;

tracking performance of the mobile operator in relation with the goal.

161. The method of claim 160, further comprising:

hot swapping at least one component of the one or more rules applying to the incentive program for the mobile operator.

162. A method to provide services to vendors, the method comprising:

providing the vendors with means to develop customization of workflows; and

loading the customization of workflows into mobile devices of mobile device operators when the mobile device operators visit sites of the vendors.

163. The method of claim 162, wherein the customization of workflows comprises customization of user interfaces.

164. The method of claim 162, wherein the customization of workflows comprises customized flow paths.

165. The method of claim 162, further comprising:

receiving the customization of workflows when the mobile device operators visit sites of the vendors.

166. The method of claim 162, further comprising:

providing log data from the mobile devices to the vendors when the mobile device operators visit sites of the vendors.

167. The method of claim 166, further comprising:

retrieving data from the vendors as part of log data related to execution of the workflow.