"Form Logic" and "Process" have conditions for "Requester Site" and "Requester Department," but the "Requester" cannot be conditioned directly. This condition set already exists withing automation rules. If brought to the Service Catalog, there are lots of unique ways to utilize on a form-by-form basis. For example, when added to Form logic, it would allow the same form to have different fields for different employees/groups, expanding options for customization. Added to a process, it would allow for quicker approval/routing flows for VIPs, etc.
For now, anyone wanting a workaround, our org uses the following:
* Create an automation rule to check the Requester name, group, etc.
* The rule action updates the incident priority. We change it to "None."
* Add a priority condition to your form's process and go from there.
* Optionally, you can "update record" at the end of your process to revert priority it's default value.
