When creating custom triggers in Dynamics 365 Customer Insights - Journeys, all input parameters are treated equally. There's currently no way to specify whether a parameter should be mandatory or optional. This can lead to confusion, unintended behavior, or the need for additional workarounds.

Proposed Enhancement:

Introduce support for marking input parameters as either:

• Required: The trigger cannot be executed unless this value is provided.
• Optional: The trigger can still run even if this value is missing. Default values could also be supported.

What This Improves:

• Improved data validation and error handling at runtime
• Greater flexibility when integrating with external systems that might not provide all data fields