[brooklyn-docs] 07/14: document the `entity.effector` syntax for workflow, to check if effector exists

[he...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git

commit 555a4937126b988964b7f527bd14740831acd9e6
Author: Alex Heneveld <al...@cloudsoft.io>
AuthorDate: Mon May 22 15:34:35 2023 +0100

    document the `entity.effector` syntax for workflow, to check if effector exists
---
 guide/blueprints/workflow/variables.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/guide/blueprints/workflow/variables.md b/guide/blueprints/workflow/variables.md
index 868bca50..5dcf862f 100644
--- a/guide/blueprints/workflow/variables.md
+++ b/guide/blueprints/workflow/variables.md
@@ -81,6 +81,7 @@ workflow is running, where `<KEY>` can be:
 * `config.<KEY>` - returns the value of the config key `<KEY>` 
 * `sensor.<KEY>` - returns the value of the sensor key `<KEY>` 
 * `attributeWhenReady.<KEY>` - returns the value of the sensor key `<KEY>` once it is ready (available and truthy), for use with the `wait` step
+* `effector.<KEY>` - returns the definition of the effector `<KEY>` (useful in conditions to invoke effectors only if they are defined on an entity)
 * `children` - returns the list of children; these can be further identified either by index or by ID using square-bracket notation
 * `members` - returns the list of members (for a group); these can be further identified either by index or by ID using square-bracket notation
 * `parent.<KEY>` - returns the value of `<KEY>` per any of the above in the context of the application