[bpel4people] ISSUE BP-19: Title: Using process variables in constellations 1 and 2

["Mark Ford" <mark.ford@activevos.com>]

The consensus from the face to face meeting was that the variables would be
live such that a change to a process variable that is used in an escalation
handler is visible to that escalation handler during its execution.

For example:

<ht:escalation ...>
   <ht:condition>ht:getActualOwner() = 'Bob' and $v1 = 100</ht:condition>
   ...
</ht:escalation>

If the value of v1 at the time of the people activity's execution is 100
then this condition may evaluate to true. If the process changes the value
of v1 to 101 prior to the deadline's alarm firing then this condition will
never be true.

My initial thought here was to add some text to Section 4.9.2 in the b4p
specification to clarify this. The current text reads as follows:

--- quote ---
4.9.2 Context Data
Tasks defined as part of a BPEL4People business not only have access to the
context data of the task, but also of the surrounding business process. The
process context includes
.	Process state like variables and ad-hoc attachments
.	Values for all generic human roles of the business process, i.e. the
process stakeholders, the business administrators of the process, and the
process initiator
.	Values for all generic human roles of human tasks running within the
same business process
--- end quote ---

However, there is some text in the HT specification which touches on this
area. Section