Jump to: navigation, search

Difference between revisions of "Activity:PushCriterionSequential (Activity)"


(Created page with "Creates a push criterion to publish a push action only once instead of permanently (default). <!-- DO NOT REMOVE THIS -->{{Template:Activity/Begin}}<!-- DO NOT REMOVE THIS --...")
 
 
Line 22: Line 22:
  
 
=Example=
 
=Example=
When using a [[Activity:PushContent (Activity)|PushContent]] Activity, the clients will be notified about an update of each property value of the {{UBIK}} object. With this activity as a criterion, the notification only happens once and can therefore be influenced by the author of the workflow.
+
When using a [[Activity:PushContent (Activity)|PushContent]] Activity, the clients will be notified about every update of each property value of the {{UBIK}} object. With this activity as a criterion, the notification only happens once and the point in time when the push is cast can therefore be influenced exclusively by the author of the workflow.
  
 
<!-- DO NOT REMOVE THIS -->{{Template:Activity/End}}<!-- DO NOT REMOVE THIS -->
 
<!-- DO NOT REMOVE THIS -->{{Template:Activity/End}}<!-- DO NOT REMOVE THIS -->

Latest revision as of 10:18, 30 March 2015

Creates a push criterion to publish a push action only once instead of permanently (default).


[edit]

Description

PushCriterionSequential
Name PushCriterionSequential
Purpose Execute push action only once
Category UBIK Push
Returns true if successful
Version 2.4.2+

Arguments

This activity doesn't have any arguments.

Usage

Use this activity as criterion for your push action if you want to cast the push update only once per execution run. If this criterion is not added, the push receiver will be notified every time about updates.

Example

When using a PushContent Activity, the clients will be notified about every update of each property value of the UBIK® object. With this activity as a criterion, the notification only happens once and the point in time when the push is cast can therefore be influenced exclusively by the author of the workflow.


See also