"For Spring 2024, provision Adobe All Apps licenses for the instructor and undergrad students in FUND 104 sections 01 and 02 — but skip two specific people."
This reads like a one-off request, possibly because FUND 104 needed Adobe licenses mid-term or ahead of the normal provisioning cycle.
This is a one-time, class-specific provisioning query — unlike the broad term-wide queries, this one targets a single specific course (FUND 104, sections 01 and 02, Spring 2024) to provision Adobe licenses for just that class. It also stands out because it's the only query in your collection that actually populates Product_Configurations rather than leaving it blank.
Almost everything is hardcoded rather than parameterized:
MAIN.TERM_ID IN UPPER(('24SP')) -- Spring 2024, not a parameter
MAIN.CRSE_ID IN ('104') -- Specific course number
MAIN.DEPT_ID IN ('FUND') -- Fundamentals department
MAIN.OFFR_DEPT_ID IN UPPER(('ARTS'))-- Offered through Arts
MAIN.SECT_ID IN ('01','02') -- Only sections 1 and 2
This was clearly written for a specific provisioning event, not as a reusable tool.
This is the only query of the four that actually assigns software:
'Default All Apps - 100 GB configuration,
Default Adobe Spark for Higher-Ed - 2 GB configuration'
That's a full Adobe CC suite assignment. The other queries leave this blank, meaning they provision the user account but let group membership or another process handle license assignment. This one does it directly.
Two active blocks, one commented-out block:
Block 1 — Instructors