I have an Escalation Rule that is built on Attributes but it’s causing issues with batch testing as attributes are not set. I can not use an Audience as that is already needed in my batch testing to control the KB. Ideally you allow us to set the attributes before triggering the batch testing as you allow in simulations.
My escalation rule is Attribute is not [name] and Attribute2 is not [name2]. This allows me to use FinAi for new use cases and then escalate to an existing nonFinAi workflow for existing use cases. Over time we will move all to FinAi but that is not possible right now. This escalation rule is built on Attributes so why is there no solution for batch testing?
I will try creating a test user with the attribute set as a workaround. That will then require everyone to use this test user and that is not ideal.