Module 21 - Other Rules in AccuCampus

Module 21 - Other Rules in AccuCampus

Module 21: Other Rules in AccuCampus

Topic: Other Rules

  1. Parts of Rules
  2. Prompt Ratings Rules
  3. Debut Information Rules
  4. Stop  Execution Rules

Rules

Within AccuCampus, you are able to create rules that tell the system to complete tasks automatically based on user actions within the system. Below we’ll discuss the last three types of rules, Prompt Ratings, E-mail Debug Information and Stop Execution. These three actions can be created independently, or combined with other actions to make more complex rules.


Parts of Rules

Triggers

Triggers are the first step to tell the system when to apply the rule. Triggers are typically based in a user’s actions within the system. The following triggers have been built into the system.

Signing In/Out of a Sign-in Station
  1. When a card is swiped
  2. When a person is automatically signed out
  3. When a user signs in using a multistep kiosk station
  4. When a user signs out using a multistep kiosk station
Waiting Lines
  1. When a user has moved forward in a waiting line
  2. When a user is added to a waiting line
  3. When a user is signed in from a waiting line
Appointments/Events
  1. When an appointment is cancelled
  2. When an appointment is created
  3. When an appointment is edited
  4. When an appointment is restored
  5. When an appointment is voided
  6. When an appointment reminder is processed
  7. When a seminar reminder is processed
  8. When someone does not show for an appointment
Session Logs
  1. When an attendance log is deleted
  2. When an attendance log is saved
  3. When an attendance log is tagged
  4. When an attendance log tag is removed
Action Items
  1. When an action assignment has expired
  2. When an action assignment is due
  3. When an action assignment is updated
  4. When an action assignment is assigned to a user
Users
  1. When a user is manually created or edited
  2. When a user is manually deleted
  3. When a user is tagged
  4. When a user tag is removed
Media
  1. When a media checkout has passed its due date
  2. When a media checkout is about to end
  3. When a media item is checked in
  4. When a media item is checked out
Imports
  1. When an import job finishes

Conditions

Conditions are the second step to tell the system when to apply the rule. Conditions provide more context for the trigger. An example would be a trigger of “when a card is swiped” and the condition specifying the location where the card is swiped. The conditions available depend on the trigger; however, they general involve locations, users, services, etc. You are able to add more than one condition to a trigger.

When creating a condition that pertains to a location, service or course/event, we recommend that you use the Internal ID for that item versus the written name of it. This ensures that if the written name changes, the rule will still stand. To get the Internal ID, follow these instructions.

Navigate to the location, service or course/event you wish to use.


At the end of the web address for that page, you will see id= followed by a string of numbers and letters. Everything after the equals sign is your Internal ID. 

Set your condition to an Internal ID and paste the string of numbers and letters into the condition.


The rule will now remain active, even if the name of the location, service or course/event changes over time.

Using Tokens

When creating your notifications, it’s possible to use tokens. This allows you to create a generic notification that will be personalized based on the tokens contained within it. Much like with Internal IDs in the conditions, this allows the rule to remain active even if the name of a user, location, service or course/event changes. 

Depending on the action you choose, a list of tokens will appear on the right hand side of the screen. These include user ID tokens, location tokens, service tokens, etc. Click on the desired token to add it to your message, or to identify followers for the action. 


Examples
Using the token [[Assignment.Assignee.Id]] ensures that the rule applies to any user that meets the conditions. In this case, any user that is assigned the specific action item in the trigger receives the notification.
 

Using the token [[Assignment.Assignee.FirstName]] causes the message to be addressed to the specific user who was assigned the action item.



Prompt Ratings Rules

You may want to prompt users to rate your location or the services that you offer. One way to do this is to create a rule which sends an automatic notification to a user to prompt them to rate something. 

From the Main Sidebar, hover over Advanced Options.


Click Settings.
 

Click Rules.
 

Click Create New.


Enter a Name for the rule. We recommend that you use a unique and specific name so that the rule can be identified by other users.


Enter a Description for the rule. We recommend that you use a unique and specific name so that the rule can be identified by other users.


Set the rule as Active.


Set a Trigger for the rule.


Set Condition(s) for the rule.


Click Add Action.


Click Asks a User to Rate Something.
 

Choose the Sample size to determine how often the rating  prompt should be sent. This can range from 10% to 100% of users.


Enter the name of the user, location or service the Email should come from.


Enter a Subject for the e-mail.


Enter a Footer for the e-mail.


Choose what users should rate. This could include CoursesLocationsStaffInstructors, and/or Services.


Click Save.
 

If the rule should cause more than one action, click Add Action. If not, click Save.



E-mail Debug Information

This rule type will send debugging information to help pinpoint errors in specific processes. This action can be used in its own rule, or added to other rule types in order to identify errors.

From the Main Sidebar, hover over Advanced Options.


Click Settings.
 

Click Rules.
 

Click Create New.


Enter a Name for the rule. We recommend that you use a unique and specific name so that the rule can be identified by other users.


Enter a Description for the rule. We recommend that you use a unique and specific name so that the rule can be identified by other users.


Set the rule as Active.


Set a Trigger for the rule.


Set Condition(s) for the rule.


Click Add Action.


Click Email debug information.
 

Enter the e-mail address of the Recipient.


Click Save.
 

If the rule should cause more than one action, click Add Action. If not, click Save.



Stop Execution

This rule type will stop the execution of an action within AccuCampus and provide an error message explaining why the user is not allowed to complete the action. It is typically used as an on-screen notification to enforce attendance restrictions.

From the Main Sidebar, hover over Advanced Options.


Click Settings.
 

Click Rules.
 

Click Create New.


Enter a Name for the rule. We recommend that you use a unique and specific name so that the rule can be identified by other users.


Enter a Description for the rule. We recommend that you use a unique and specific name so that the rule can be identified by other users.


Set the rule as Active.


Set a Trigger for the rule.


Set Condition(s) for the rule.


Click Add Action.


Click Stop Execution.
 

Enter the Message to Display.


Click Save.
 

If the rule should cause more than one action, click Add Action. If not, click Save.


    • Related Articles

    • AccuCampus: How do I use the Stop Execution rule?

      Introduction In AccuCampus, Rules are created to execute based on predetermined events, such as: When a user swipes a card, and the card ID has something specific about it. When a log is created. When an appointment is canceled. After a Rule is ...
    • How do I set up a stop execution rule in AccuCampus?

      Note: This article explains how to set up a stop execution rule within AccuCampus. Stop execution rules are used when a user should receive a message after being prevented from taking an action within the system. A typical use case would be if a user ...
    • How do I set up rules in AccuCampus?

      This article explains how to create rules within AccuCampus. Rules are used to automatically trigger actions within the system. They can be used to send notifications, assign or auto-complete action items, add or remove tags, etc. 1. From the Main ...
    • Module 17 - Notifications Rules in AccuCampus

      Module 17: Notifications Rules in AccuCampus Topic: Rules (Notifications) Notification Topics Parts of Rules Creating New Rules Rules Within AccuCampus, you are able to create rules that tell the system to complete tasks automatically based on user ...
    • AccuCampus How to request some ratings based on rules?

      INTRO       in AccuCampus you can use rules to request users to rate a location or service, in this article we describe the process using as an example asking a user to rate a location where a sign-in station is. STEP BY STEP 1-Go to Advanced ...