When a self-service trigger uses an ENTITY context, the referenced userInput is prefilled with the entity identifier, but other userInputs cannot default off that entity's properties — jqQuery defaults only see .form and .trigger.by.user, not .entity. DAY-2 actions support this via default.jqQuery against .entity.properties, letting users see and edit current values on a single execute screen. Workflows currently require an extra resolve step followed by a second input node just to surface those same values, turning a one-screen experience into two. Supporting .entity (or equivalent) in trigger userInput defaults would close this gap and restore parity with DAY-2 actions.