| Table of Contents |
|---|
...
| Recipient Type | Description |
|---|---|
| The Case | The case which matches the rule will be a recipient. See Registering a Case Contact. |
| The Case's Owner | The owner of the case which matches the rule will be a recipient. If the owner is a user group, then all users in that group will be recipients. If the owner is an Organization, then all users assigned to that Organization will be recipients. |
| The Case's Parent Case | The parent of the case which matches the rule will be a recipient. Note: This only works for parent/child relationships and not host/extension or parent/extension. If this is used with host/extension relationships, the SMS or email will not send and the error in the Messaging History Report will display as "Error - No recipient". |
| User Specified via Case Property | A commcare user whose username is a case property of the matching case. The case property in which to look up the username is specified in a text box under the recipient choices. The user must be a mobile worker in the same project space. |
| Email Specified via Case Property | An email address found in a case property of the matching case. The case property in which to look up the email address is specified in a text box under the recipient choices. This option can only be used for email alerts, not SMS ones. |
...
| Reference | Meaning |
|---|---|
| case.name | the case's name |
| case.case_property | any dynamic case property (here case_property is just an example) |
| case.parent | a reference to the parent case; for example, you can reference {case.parent.name} |
| case.host | a reference to the host of the extension case; for example, you can reference {case.host.name} |
| case.owner | a reference to the case's owner; for example, you can reference {case.owner.name} |
| case.last_modified_by | a reference to the user who last modified the case; for example, you can reference {case.last_modified_by.name} |
...