Relationship Between Tasks and Features
If no features within a particular functional area task are granted for a role, then even if that task is specifically granted to the role, it will not be visible (and directly accessible) to the users in that role. At least one feature applicable to the functional area must be granted for that task to appear in the functional area for a user assigned to the role.
Note: Events, Membership, and Prospects are built as pages, not functional areas. While you cannot assign tasks to pages, pages can have actions. For more information about adding actions to pages, see the Page Designer Guide.
Additionally, when you grant certain tasks, it grants the minimum underlying features necessary for a user to actually complete the task. The rules governing this behavior are:
Task Type |
Feature Granted |
Go to page Ex. Search for constituents |
Page expression form for that page (if any) Ex. Constituent Page Expression Data View Form |
Show Form Ex. Add an Individual |
That form + post action Go to page expression Ex. Individual Add Form + Constituent Page Expression Data View Form |
Launch Business Process |
The business process |
Record operation Ex. A custom task could be implemented to “Delete Constituent.” |
The record operation The feature associated with a Delete Constituent task is Delete Constituent (the Record operation). |
Task Type |
Feature Granted |
Go To page |
Page expression form for that page (if any) |
Show Form |
That form + post action Go To page expression |
Launch Business Process |
The business process |
Record operation |
The record operation |