You must rework the custom forms. Please follow the below guidance:
Remove the required constraint on the field altogether
Example: A user has set almost all fields in their custom form to mandatory because they want users to provide values for all of these fields. However, this form has a chained design. When a user provides a value for field A, it is used as an input to an action which returns a value for field B, which is then used as input which returns a value for field C and so on.
Recommended Change: In this case, the form designer needs only to set the last field as mandatory. When set this way, the requesting user would still need to populate all fields prior thus making them required.
Provide default values to required fields
Example: Many use cases include required fields to have some expected value, but not all form designers set it.
Recommended Change: Where possible, the custom form designer should
set a default value for required fields.
Inspect the form field dependency chains and re-order them accordingly
Example: If field B is required in a form that is placed after field A which uses field B as an input to an Orchestrator action, then field A would most likely be empty because the end user has not supplied a value to field B, yet.
Recommended Change: In this case,
re-order the fields in such a way that for any field X, all fields that are used as inputs to an action and provide a value to said action, are placed before field X; No input field should be after it.