Recording Area CIDs (flows in German)
Posted: 24 May 2015 16:19
UPDATE 29.05.2015
Hello everybody,
for those of you who came from Llama you know a function to record CID and connect them to profiles. Martin built something similar but I needed it mor powerful, so I created a group of flows that record CIDs and write them in global_vars so that you can use them later as trigger, or conditions or whatever you want without maintain them in every trigger or condition you are using this list.
The Widget is connected to the flow "Areazelle aufnehmen". The flow will ask you first to which subarea CIDs should be recorded, you also can say that you want to record a new subarea (Every subarea must have a diffrent name, no matter to which mainarea it belongs). Each subarea belongs to one mainarea (the profile you want to select); if you want to add a mainarea you have to edit the global var "global_subarea2area" and add a entry with the new mainarea as key.
How to use the result in triggers an conditions: You have a few global_vars that you can use. For example you want to use the trigger for a the mainarea "work" you use the "GSM-Trigger" (I don't know the wording for it in the english version) and put the following expression into the Cell ID list field
or fot the subarea "branch":
Installation:
- Just import the flows an run the "Init RecAreaCIDs" after you did you can deactivate (and/or delete) the flow "Init RecAreaCIDs".
- Put the widget wherever you want
http://automagic4android.com/flow.php?i ... 1f2f84ebc1
UPDATE:
In the main flow there is an action in the end that calls the flow "Area prüfen". I added it in my flow because when you record new CIDs in Cell ID lists it can be that the GSM-trigger wouldn't be triggered as long as you are in the newly recorded CID. It can be that it starts the next time you enter (or leave) the recorded CID, so I added an action in the end that starts my area checking flow manually. You can delete this action or replace it with an action that will call your area checking flow.
Hello everybody,
for those of you who came from Llama you know a function to record CID and connect them to profiles. Martin built something similar but I needed it mor powerful, so I created a group of flows that record CIDs and write them in global_vars so that you can use them later as trigger, or conditions or whatever you want without maintain them in every trigger or condition you are using this list.
The Widget is connected to the flow "Areazelle aufnehmen". The flow will ask you first to which subarea CIDs should be recorded, you also can say that you want to record a new subarea (Every subarea must have a diffrent name, no matter to which mainarea it belongs). Each subarea belongs to one mainarea (the profile you want to select); if you want to add a mainarea you have to edit the global var "global_subarea2area" and add a entry with the new mainarea as key.
How to use the result in triggers an conditions: You have a few global_vars that you can use. For example you want to use the trigger for a the mainarea "work" you use the "GSM-Trigger" (I don't know the wording for it in the english version) and put the following expression into the Cell ID list field
Code: Select all
{getMapValue(global_arr_cid_main, "work"), listformat, comma}
Code: Select all
{getMapValue(global_arr_cid, "branch"), listformat, comma}
- Just import the flows an run the "Init RecAreaCIDs" after you did you can deactivate (and/or delete) the flow "Init RecAreaCIDs".
- Put the widget wherever you want
http://automagic4android.com/flow.php?i ... 1f2f84ebc1
UPDATE:
In the main flow there is an action in the end that calls the flow "Area prüfen". I added it in my flow because when you record new CIDs in Cell ID lists it can be that the GSM-trigger wouldn't be triggered as long as you are in the newly recorded CID. It can be that it starts the next time you enter (or leave) the recorded CID, so I added an action in the end that starts my area checking flow manually. You can delete this action or replace it with an action that will call your area checking flow.