Changes

m
Line 5: Line 5:  
It is also possible to use the [[Constraint: Geofence|Geofence (Location)]] constraint to limit when functionality can run based on your current location.
 
It is also possible to use the [[Constraint: Geofence|Geofence (Location)]] constraint to limit when functionality can run based on your current location.
   −
=== Defining Geofences ===
+
<span style="color: #548687; font-size: 24px; display: inline-block; margin-top: 15px; margin-bottom: 0px;"><strong>Defining Geofences</strong></span>
   −
<pre style="background-color: #ACC8E5; color: #112A46; border-radius: 10px; padding: 10px;">
   
You can access the list of current Geofences from the Geofence tile on the application home screen. From  the list you can add a new Geofence or edit an existing one. This will take you to the Geofence configuration screen.
 
You can access the list of current Geofences from the Geofence tile on the application home screen. From  the list you can add a new Geofence or edit an existing one. This will take you to the Geofence configuration screen.
   Line 13: Line 12:     
Each Geofence area should be given an identifying name (e.g. home, work, school etc.). This is then used to easily identify which area is being referenced in any trigger/constraint that uses Geofences.
 
Each Geofence area should be given an identifying name (e.g. home, work, school etc.). This is then used to easily identify which area is being referenced in any trigger/constraint that uses Geofences.
</pre><br>
      
=== Location Trigger ===
 
=== Location Trigger ===
editors
1,590

edits