Scope Functions Checklist

SCOPE FUNCTIONS
Scope is a feature designed to minimize the chance that an assigner deletes, assigns, unassigns or publishes games for which they are not responsible by allowing organizations to limit the records an assigner sees on the games screen to only those for which they are responsible. It is not designed, and therefore lacks the features, to entirely prevent assigners from viewing certain games and assignments within an account.  Organizations needing to completely separate assignments between assigners will need separate accounts.

• View Games
  1. Scope ONLY Narrows games on the Games Page.
  2. Formula:  (Bill-To League AND (Site OR Site League) AND (Team OR Team League OR Level))
      OR IF (Team AND NOT (Level AND Team League))
     (Bill-To League AND (Site OR Site League) AND (Team OR TBA Team Games))
     So if we don't have level and team league we get tba games as well
     (assuming we do have team scope)
     If a user isn’t scoped for a particular item, then they have scope for all items of that type.  For example, if the user is scoped by level and site but not teams, the formula would be (Level1 OR Level2) AND (Site1 OR Site2). 
  3. It does not limit the games shown on any of the “related lists”. This means if you go to a site or team you are scope for, you will see all games even if you are not scoped for the level.  However, in line with rule 2, you wouldn’t see the site or team to view those games.
  4. Scope does not limit an officials “Games” count
  5. Scope does not limit the Games seen when you act as an official
• Site Scope (SitesView in A1)
  • Rule: (Site OR League Site OR SubGroup Site)
  • Select subgroups in scope and all sites attached to those subgroups
  • Select sites from site scope and league site scope (or all sites for group if scope doesn’t exist) ** there is a new version of this function script, but it is not being used here
• Team Scope
  1. Rule: (Level Team OR GameTeam Match** OR Team OR League Team OR SubGroup Team)
  2. Select subgroups in scope and all teams attached to those subgroups
  3. If Level Scope
     • Select teams based on level scope matching team level
     • ** Select teams that have a game team record (matching group id) that has the same HSLevel, HSGender, Generic Sport as level scope
  4. If Team Scope
     • Select teams from team scope
  5. If Team League Scope
     • Select teams from team league scope
• Officials Scope
  1. Rule: (Official AND (Level OR Team OR Team League))
  2. If Level Scope
     • Select (results) officials ranked for a position name that has a scoped level
     • Intersection is true
  3. If Team Scope
     • Select (results) officials ranked for a position name with a level that matches a scope team
     • Intersection is true
  4. If Team League Scope
     • Select (results) officials ranked for a position name with a level that matches a scope league team
     • Intersection is true
  5. If Official Scope
     • If Intersection is true (has Level OR Team OR Team League Scope)
       • Select (temp) officials from scope
       • Remove from (results) where (temp) does not match
     • Only has official scope
       • Select (results) officials from scope
  6. Return (results)
• *** Issue here is that non-ranked officials cannot be seen
   
• Misc
  1. Filter Pages should reflect Scope (Official Filter for levels and Games Filter for sites, teams, and levels)
  2. In-App Imports, and the Import Template should reflect scope (New Importer)
  3. Acting as an Official = No Scope applies. You see everything in the group that official sees
  4. Acting as an Admin = Sub Admin Scope applies. This allows Main Admins to test scope and see what their sub's see.
• Scope does not currently apply on the Travel Fees page but should
• Misunderstandings in the past
  1. "Officials with no rank" filter on the "Ranks" page should not be the only place officials without a rank are visible. This filter simply makes it easy to see official without ranks in one place