Add UI semantics to fields displayed by association to separate objects

It will help the user if the UI makes a semantic distinction between fields that are intrinsic to an action, and those that are present due to establishing a connection to a separate object.

Examples include:

• actions that have configuration fields that appear due to their association with an Adaptive Card.

• fields that appear in the Run Workflow action, derived from its connection to a workflow that has workflow inputs.

The action configuration panel could usefully have a section that denotes an area where fields will/may appear due to a relationship. It also allows you to say to the user ‘hey, you should watch this space — more fields may appear’ or ‘The inputs workflows you connect will be here’.

This will orientate and prime the user to the concept, leading to an improved UX.