Similar to Member Attribute, but tracks a relationship to a specific Member Role rather than to a specific Member.

Introduced in 10.6.0.

1 Overview
2 Usage and Appearance
- 2.1 Configuration
- 2.2 Input mode
- 2.3 Read-only mode
3 Advanced use cases
4 Technical details
- 4.1 Data Storage

Overview

It is often useful to associate a Workflow with a person. For instance, consider the following business rules:

Each approved Course must be affiliated with an approved Instructor
An accredited Waste Management facility must have a licensed Building Manager on staff
A real estate agency must designate a primary broker

In all of these cases, a need exists to link a Workflow (such as a Course or Application) not just to a specific person, but to a specific role held by that person. For instance, a course cannot be taught by just anyone, it must be taught by someone that holds an active “Instructor” role.

This attribute provides that link, associating a Workflow Instance to a specific Member Role.

This is very similar to Member Attribute, except that the “Member” associates a Workflow Instance to a Member, rather than a specific Member Role owned by that Member.

In fact, many legacy use cases implemented using “Member” could probably be implemented using “Member Role” instead. See the “Member Attribute” docs for more information.

Usage and Appearance

Configuration

The “Member Role” Attribute accepts these configuration settings:

Setting	Purpose / Notes

Setting	Purpose / Notes
Member Role / Role Status	Only `Member Roles` matching the specified Roles and Statuses can be selected for this attribute. (The Status option is only presented for those Roles where it is relevant) Multiple Roles can be selected only if they share the same Grant Role Workflow and Status list. Changing this setting after data has been collected will trigger the “When designated Member Role becomes ineligible” setting for any existing attributes where the target `Member Role` does not match the new criteria.
Filter By	By default, users will be able to select any `Member Role` that matches the specified Role and Status. In some advanced cases, it is necessary to further restrict the list of selectable `Member Roles` by some custom logic. This can be implemented by selecting a Custom Database Object (a custom stored procedure) in this field. See “Filtering Member Role Attribute by a custom procedure” for more details.
Execute an Action when relationship is created/broken	Executes an Action against the selected Member Role’s Grant Role Workflow, when a new `Member Role` is selected in the Attribute. See “Triggering Workflow Actions when a Member Role Attribute is modified” for more details
When designated Member Role becomes ineligible	Executes a Data Import Action when the `Member Role` selected in an existing Attribute loses the required Role and/or Status, thereby becoming ineligible for the designation. The specified Action is triggered against this `Workflow Instance` (the one that contains the “Member Role” attribute). This Action can perform notifications, or even clear the designation if desired.
When designated Member Role becomes eligible	Executes a Data Import Action when the `Member Role` selected in an existing Attribute was previously ineligible for the designation, but regains the required Role and/or Status, thereby becoming eligible again. The specified Action is triggered against this `Workflow Instance` (the one that contains the “Member Role” attribute). This Action can perform notifications, or even clear the designation if desired.

Input mode

In input mode, this renders a textbox with autocomplete functionality. Only those Member Roles matching the specified configuration settings are selectable.

Read-only mode

In readonly mode, the selected Member Role (member name, Role name, and Unique Id) are displayed as readonly text.

Advanced use cases

Technical details

Data Storage

The MemberRoleId of the selected Member Role is stored in the ITEM_ATTRIBUTE_VALUE table.