Add controls for optional and batched dynamic inputs in user provisioning node

[Dilusha-Madushan]

What problem are we solving?

When flow designers want to collect dynamic inputs during a user provisioning step, they can currently prompt only required inputs, and they cannot control how many dynamic inputs are requested at one time, which causes limited flow flexibility and a poor experience when provisioning requires more structured input collection.

Who are we solving this for?

Primary: Flow designers

• Goal: Configure user provisioning steps to collect the right dynamic inputs in a controlled and predictable way.
• Pain: They cannot decide whether provisioning should continue with optional inputs behavior in a configurable way, and they cannot limit the number of dynamic inputs prompted in a single step.

Why should we solve this now?

• Value to Persona: Gives flow designers better control over provisioning behavior and makes dynamic input collection more flexible for real-world flows.
• Value to Org: Reduces configuration limitations in provisioning flows, improves product completeness, and lowers the need for workarounds or custom handling in customer setups.

Proposed Solution

• A property to control whether the node should proceed with optional dynamic inputs behavior.
• A property to control how many dynamic inputs can be requested at one time.

Alternatives

No response