Hi @masahironaka,
No, it doesn't touch the Assignee field. On-Call: Escalations by Email is purely a notification workflow: it walks the escalation matrix (primary, secondary, tertiary and so on) defined against the on-call rotation and roster, and fires an email to whoever is on-call at each level when the escalation condition, typically the incident sitting with assignment group set and assigned_to still empty, isn't cleared inside the configured reminder interval. It logs each step to the activity log and kicks an event like OnCall.escalated to drive the notification, but there's no GlideRecord update against assigned_to anywhere in that flow. Populating the Assignee is left entirely to whoever actually acts on the page, either by opening the incident and assigning themselves, or through a separate business rule or flow you'd layer on top if you want auto-assignment on acknowledgment. One thing worth flagging since it trips people up more than the assignment question itself: the standard trigger rule for this workflow only fires while the assignment group is unset, so if your assignment rules or category mapping auto-populate the group on insert, the escalation workflow may never fire in the first place.
References
Thank you,
Vikram Karety
Octigo Solutions INC
