| Info |
|---|
See also: Member Role Attribute (DRAFT) |
...
| Table of Contents |
|---|
Overview
“Member Role” attributes can be used to represent “designation” relationships between two different Member Roles. For instance, a business rule for a licensing system might state that a real estate agency must have a licensed broker on staff. In this example, the Agency must designate a “responsible broker” in order to legally practice real estate.
In such an implementation, if the designated “responsible broker” were to lose their license, or leave the agency, then the system would probably need to send a notification or change the Agency’s role status to indicate that they no longer have a valid broker designation.
Configuration
To implement these rules, use the “When designated Member Role becomes…” triggers on the “Member Role” attribute configuration.
...
These triggers specify Data Import Actions on the referencing Workflow (e.g. the one that contains the “Member Role” Attribute) that are triggered when that workflow references a Member Role that is modified and no longer meets the required Role/Status for the Attribute.
For example, these Actions could be used to:
Clear out the “Member Role” Attribute
Send a notification to the designating agency
etc
| Note |
|---|
The Data Import Actions selected for these triggers must not expect there to be any required input attributes on the Import Step. None of the |
...
Workflow data from the |
...
designating Workflow is provided to the Action. In other words, these Actions should only be used to trigger Behaviors or other state changes; they should not expect or require any incoming attribute data. |