I haven't yet come across a way to annotate or comment on logic added within the logic canvas so perhaps somebody else has an ideal answer to this question or perhaps I haven't understood it correctly.
However to answer your second question: There are a few ways to tell if a page or app variable has been used. If a variable is assigned to a property or layout, The first indication on weather or not its a page or app variable is the icon.
Lastly if you select a property that is bound to a variable and switch it to binding type: formula, You can identify a key difference which is that app variables will always start with appVars.example while page variables will be labeled as pageVars.example within the formula binding type. To clear any doubts over any variable you have, you could simply type the name of the variable in formula binding and see if it begins with appVars or pageVars. Below are some examples of an app variable named DeviceToken
and page variable named DailyTemp within formula binding
Hopefully this answers your second question and all the best with your project!
- SAP Managed Tags:
Well for this I have not yet found a proper solution. There is one workaround, but that still won't help you find the variable in the UI. What I do sometimes is copy the page (or just an element) and paste it into an empty component.json file inside visual studio code. It will show you something like this:
Inside here you can easily use the ctrl+F again, to find a specific pagevariable. This method doesn't really help if you also need to identify where it is as you would be lost in thousands of lines of json on a more complicated page. So I would only use this if you want to check if there is any use of a variable before deleting it.
Of course this copying of an element allows things like this happen:
Mevi's selectable calendar component
- SAP Managed Tags:
Hey there, All pretty amazing suggestions above!
I would also like to add my few thoughts on this.
First suggestion that saves me enourmous amounts of time is to acutally use the browsers built in text search, so use the 'ctrl+F' or 'cmd+F' keyboard combination. Then search for the specific variable, component name or similar. This is why the change (that happened a few months ago) that renaming components is pretty easy helped a lot. This method works pretty well, if you need to find styles (and you happen to have many) or if you are in the variable settings screen.
As for how to document. I tend to just use a 'javascript' custom node which doesn't have an output and the content of it is a comment. I then name it either 'comment' or with some more descriptive name. This way you could in fact position your comments pretty close to where the actual logic happens. See image below:
And then on the inside I have something like this:
Hope this also gives some useful suggestions.
Best wishes
- SAP Managed Tags:
