Currently when you set the blueprint identifier for a Day-2 Self-Service action, its entity is placed automatically at the top of the form inputs without the option to control its order. There could be scenarios in which the selection list of the target entity is too large and it gets complicated for the user to figure out what instance to choose. This is a limitation that prevents you from having input filters placed before the form's target entity that will help you narrow down the options for the selection list of the target entity.

Example: You have 3 entities A, B and C. The relations goes like this C -> B -> A. If I have a Day-2 Action that takes action on the entity C, I want to be able to include the A and B entities in the form and be able to select them first (for filter purposes) before choosing directly between the instances of C, because unfiltered, there could be a lot of C instances to choose from, and it gets hard to identify the exact instance that you need only by checking its name (not knowing the relation to A and B).