Class: Ruote::Exp::ListenExpression

Inherits:
FlowExpression show all
Defined in:
lib/ruote/exp/fe_listen.rb

Overview

Listens for activity (incoming or outgoing workitems) on a (set of) participant(s).

This expression is an advanced one. It allows for cross process instance communication or at least cross branch communication within the same process instance.

DO NOT confuse the listen expression with the ‘listener’ concept. They are not directly related. The listen expression listens to workitem activity inside of the engine, while a listener listens for workitems or launchitems from sources external to the ruote workflow engine.

It can be used in two ways : ‘blocking’ or ‘triggering’. In both cases the listen expression ‘reacts’ upon activity (incoming or outgoing workitem) happening on a channel (a participant name or a tag name).

blocking

A blocking example :

sequence do
  participant 'alice'
  listen :to => 'bob'
  participant 'charly'
end

Once the listen expression got applied, this process will block until a workitem (in any other process instance in the same engine) is dispatched to participant ‘bob’. It then proceeds to charly.

triggering

This way of using ‘listen’ is useful for launching processes that “stalk” other processes :

Ruote.process_definition :name => 'stalker' do
  listen :to => 'bob' do
    participant :ref => 'charly'
  end
end

This small process will never exits and will send a workitem to charly each time the ruote engine sends a workitem to bob.

The workitems passed to charly will be copies of the workitem initially applied to the ‘listen’ expression, but with a copy of the fields of the workitem passed to bob, merged in.

Note : for now, the triggered segments of processes are ‘forgotten’. The ‘listen’ expression doesn’t keep track of them. This also means that in case of cancel, the triggered segments will not get cancelled.

:merge

By default, :merge is set to true, the listened for workitems see their values merged into a copy of the workitem held in the listen expression and this copy is delivered to the expressions that are client to the ‘listen’.

:upon

There are two kinds of main events in ruote, apply and reply. Thus, a listen expression may listen to ‘apply’ and to ‘reply’ and this is defined by the :upon attribute.

By default, listens upon ‘apply’ (engine handing workitem to participant).

Can be set to ‘reply’, to react on workitems being handed back to the engine by the participant.

Setting :upon to ‘entering’ or ‘leaving’ tells the listen to focus on tag events.

sequence do
  sequence :tag => 'phase_one' do
    alpha
  end
  sequence :tag => 'phase_two' do
    bravo
  end
end

In this dummy process definition, there are four tag events :

  • ‘entering’ ‘phase_one’

  • ‘leaving’ ‘phase_one’

  • ‘entering’ ‘phase_two’

  • ‘leaving’ ‘phase_two’

:to and :on

The :to attribute has already been seen, it can be replaced by the :on one.

listen :to => 'alpha'

is equivalent to

listen :on => 'alpha'

:to (:on) and regular expressions

It’s OK to write things like :

listen :to => "/^user\_.+/"

or

listen :to => /^user\_.+/

To listen for workitems for all the participant whose name start with “user_”.

:wfid

By default, a listen expression listens for any workitem/participant event in the engine. Setting the :wfid attribute to ‘true’ or ‘same’ or ‘current’ will make the listen expression only care for events belonging to the same process instance (same wfid).

:where

The :wfid can be considered a ‘guard’. Another tool for guarding listen is to use the :where attribute.

listen :to => 'alpha', :where => '${customer.state} == CA'

The listen will trigger only if the workitem has a customer field with a subfield state containing the value “CA”.

The documentation about the dollar notation and the one about common attributes :if and :unless applies for the :where attribute.

listen :to => :errors

The listen expression can be made to listen to errors.

listen :to => errors do
  participant 'supervisor_sms', :task => 'verify system'
end

Whenever an error happens in the process with this listen stance, the listen will trigger.

“listen :to => :errors” only works with errors in the same process instance (same wfid).

“listen :to => :errors” doesn’t trigger when the error is caught (via :on_error).

listen :to => :errors, :class => ‘ArgumentError’

One can restrict the listen to certain classes of errors. Passing a list of error classes separated by a comma is OK.

listen :to => :errors, :message => /x/

One can restrict the error listening to errors matching a certain regex or equal to a certain string. The attribute is :message or :msg. The value is a String (strict equality) or a Regex (matching).

Constant Summary collapse

UPONS = 
{
  'apply' => 'dispatch', 'reply' => 'receive',
  'entering' => 'entered_tag', 'leaving' => 'left_tag'
}

Constants inherited from FlowExpression

FlowExpression::COMMON_ATT_KEYS

Instance Attribute Summary

Attributes inherited from FlowExpression

#context, #error, #h

Instance Method Summary collapse

Methods inherited from FlowExpression

#ancestor?, #att, #attribute, #attribute_text, #attributes, #cancel, #compile_atts, #compile_variables, do_action, #do_apply, #do_cancel, #do_fail, #do_pause, #do_persist, #do_reply, #do_resume, #do_unpersist, #expand_atts, #fei, fetch, from_h, #handle_on_error, #has_attribute, #initial_persist, #initialize, #iterative_var_lookup, #launch_sub, #lookup_on_error, #lookup_val, #lookup_val_prefix, #lookup_variable, #name, names, #parent, #parent_id, #persist_or_raise, #set_variable, #to_h, #tree, #tree_children, #try_persist, #try_unpersist, #unpersist_or_raise, #unset_variable, #update_tree, #variables

Methods included from WithMeta

#class_def, included

Methods included from WithH

included

Constructor Details

This class inherits a constructor from Ruote::Exp::FlowExpression

Instance Method Details

#apply ⇒ Object 



206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
 
# File 'lib/ruote/exp/fe_listen.rb', line 206

def apply

  # gathering info

  h.to = attribute(:to) || attribute(:on)

  h.upon = UPONS[attribute(:upon) || 'apply']
  h.upon = 'error_intercepted' if h.to == 'errors'

  h.lmerge = attribute(:merge).to_s
  h.lmerge = 'true' if h.lmerge == ''

  h.lwfid = attribute(:wfid).to_s
  h.lwfid = %w[ same current true ].include?(h.lwfid)

  h.lwfid = true if h.to == 'errors'
    # can only listen to errors in the same process instance

  persist_or_raise

  # adding a new tracker

  @context.tracker.add_tracker(
    h.lwfid ? h.fei['wfid'] : nil,
    h.upon,
    Ruote.to_storage_id(h.fei),
    determine_condition,
    { 'action' => 'reply',
      'fei' => h.fei,
      'workitem' => 'replace',
      'flavour' => 'listen' })
end

#reply(workitem) ⇒ Object 



239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
 
# File 'lib/ruote/exp/fe_listen.rb', line 239

def reply(workitem)

  #
  # :where guard

  where = attribute(:where, workitem)
  return if where && ( ! Condition.true?(where))

  #
  # green for trigger

  wi = h.applied_workitem.dup

  if h.lmerge == 'true'
    wi['fields'].merge!(workitem['fields'])
  elsif h.lmerge == 'override'
    wi['fields'] = workitem['fields']
  #else don't touch
  end

  if tree_children.size > 0

    launch_sub(
      "#{h.fei['expid']}_0", tree[2][0], :forget => true, :workitem => wi)
  else

    reply_to_parent(wi)
  end
end