Using inclusion and exclusion rules to define job scope

When setting up sync jobs, it's helpful to think of each job as a grouping of classes that fit a logical scope for your environment.  For example:

  • Job 1: All classes at the Evergreen Elementary school except homeroom.
  • Job 2: Only first semester high school classes but without "Student Assistant" or "Lunch" included.
  • Job 3: Only full year high school classes, but without "Independent Study" included.

The job scope and rules step of the sync analysis is where this kind of inclusion and exclusion logic can be applied, and the results of the logic previewed and adjusted as needed.



Inclusion rules provide the outermost container of the universe of classes to include. Adding multiple inclusion rules increases the boundaries of the set. In the example above, all classes within the school with School ID "AA" have been included, which is 224 classes.  Exclusion rules can then be used to subtract classes from the total included via inclusion rules. A common catch-all inclusion rule to use would be ensuring the Teacher E-mail isn't blank by setting Teacher Email contains @.

Exclusion rules further reduce the number of classes in the job. In the example above, an exclusion rule has been added for a class containing the name “Physical Education,” reducing the total number of included classes from 224 to 203.