Adding A New Action Type

Objective: To better understand when creating a new Action Type.

Category: The Category is where the Action Type will appear on the Settings>Action Types screen. It's not only where it appears but the Category determines what Rules will be available (For a better understanding of Rule's, Click Here). The Category can also affect where the Action Type can be used. 

• Collections: Not all associations use the same collections process. When multiple collection models are needed, we need to create additional Collections Action Types. Picking this Category allows for this Action Type to be selected under the Association>Settings screen per association.
• Homeowner Request: This Category will allow for these Action Types to appear on the homeowners portal. A common additional Action Type we see here is an Action Type that will let a homeowner put in a request for a Clubhouse Reservation.

• Violations: Just like the Collections processes, not all associations use the same Violation process. We need to create a new Action Type with the Category of Violation so we can select this model under the Association>Settings screen.

Action Type: The Action Type field is used to create the name of the new Action Type.

Send To (Default Followers): The Send To field, also known as the Default Followers, allows the roles that are included in this field to view, create, and step this Action Type. If a role is not inserted in this field, a user with that role will not be able to view, create, or step this Action Type.

Administrator Role: Whichever role is input in this field will have permission to step this Action Type to any step, at any time.

Action Type Requirement: This field sets the requirements for what needs to be select to create this Action Type. For example, if the Action Type Requirement is set to Require Association and/or Owner means this Action Type can not be created without the Association selected and/or the homeowner being selected.

Block Creation: If Block Creation is checked then it will not allow any user to create this Action Type. This feature is mainly used for Action Type's that a client doesn't want to delete but doesn't want anyone to use or if a Generation Action Type kicks off this Action Type automatically then there is no use for manual creation.

Enable No Email Alerts: Select to reduce unnecessary Failed To Send - No Email notifications. Previously, these notifications were sent automatically whenever email delivery failed due to missing recipient email addresses (for example, when a role has no associated email address). These notifications are now disabled by default for all action types and you can enable them on a per-action-type basis by selecting this option.