Adding dynamic schema inputs from token picker into the definition for hybridTriggers

[bnarayanared]

For the hybrid trigger, the inputs schema gets added to the trigger based on the output we select from the token picker in subsequent steps. Kind of like the manual trigger but for the hybrid trigger the triggerBody outputs are not a fixed set to stamp on to the designer. We have a proposal of defining a custom hook that lets us add this on the ppux side but need a way in LAUX to call this custom hook.

The idea here is:
For a flow structure and we go through all actions, all nodes and turn them into JSON.
When it comes time to get the Jason for the hybrid trigger, have an extension point somewhere in LAUX(Mostly during flow save) which calls into some code that we've written on ppux where goes if hybrid trigger, work out what the scheme should be, put the schema in the in the spot.

Example:
Initial code view on the trigger:

On selecting an output from the trigger:

Updated code view on the trigger:

Here is the video link of how the hybrid triggers currently work and the proposal:
https://microsoft-my.sharepoint.com/:v:/p/bnarayanared/ESKXhFzNrelFtBf6FLggpXYB2bfUvrh_ybn0CIyp2S3lMQ?e=MoqhHY&nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZyIsInJlZmVycmFsQXBwUGxhdGZvcm0iOiJXZWIiLCJyZWZlcnJhbE1vZGUiOiJ2aWV3In19

[preetriti1]

This has been discussed in May before the build during button trigger and hybrid trigger design discussion in office hours.
Summarizing it again here -
"In button trigger this was exactly the intended behavior, we clearly said add all inputs needed in the schema inputs when the trigger is added and since all inputs are shown in token picker so when user picks up any dynamic output there is no need to add it in inputs schema because you guys have already added it. This was confirmed from PA team that there is no runtime issue on having properties in inputs schema which are not used as outputs. The similar approach can be adapted for hybrid trigger"

So i am wondering now why can't the same approach be followed for hybrid trigger.

[bnarayanared]

For the button trigger, there is no runtime issue on having properties in inputs schema which are not used as outputs. But for the hybrid trigger, these input properties are evaluated at runtime and hence there would be an issue on adding additional schema which are not used as outputs. That's where the two triggers differ in behavior.

Having additional schema in inputs would definitely be a problem for hybrid triggers because then during runtime the run widget (which is used to evaluate the inputs added on the trigger) will assume that all the values being added as inputs are being used.

To clarify on how the hybrid triggers use these inputs added in schema during runtime --
The hybrid trigger is used to evaluate row/rows of the selected entity and reference the values present in the inputs schema during a flow run. So, we need to select the minimal set of schema based on the referenced properties from the outputs in the subsequent action steps and add it on the inputs in order for it to evaluate those referenced properties.