EPIC Goal

As a workflow developer, I need the ability to hide form fields while preserving their 
functionality and provide custom review page components, so that I can create more 
flexible and user-friendly workflow forms with better control over what users see 
during data entry and review.

This epic includes:

• Hidden field support with ui:hidden property that preserves widget functionality
• Automatic exclusion of hidden fields from stepper navigation and review pages
• Improved nested object display on the default review page
• Support for custom review page components via plugin API
• Comprehensive documentation and test workflows

  Background/Feature Origin

Customer feedback and workflow implementation requirements revealed limitations in the 
current Orchestrator form system regarding field visibility and review page customization.

PROBLEM STATEMENT:
1. Fields marked as "ui:widget": "hidden" completely lose their widget functionality, 
   making it impossible to have active widgets that are hidden from users (e.g., 
   ActiveText widgets that execute but don't display).

2. Hidden fields appear in the stepper navigation, creating confusion for users who 
   see steps with no visible inputs.

3. Complex workflow reviews are difficult to understand due to poor data formatting

4. Customers need the ability to provide their own custom review page components 
   that match their organization's UI/UX standards and display requirements.

Acceptance Criteria

1. User should be able to hide a field using "ui:hidden": true in the schema while keeping the widget active (e.g., ActiveText, input)
2. Hidden fields should submit their values with the form data
3. Hidden fields should accept and use default values from the schema
4. Hidden fields/steps should not appear in the wizard stepper navigation
5. Step numbers should auto-adjust when hidden steps are filtered out
6. Only visible steps should be counted and displayed in the stepper
7. If all inputs in a step are hidden, the entire step should be hidden from the stepper
8. Steps with at least one visible field should still appear in the stepper
9. Hidden fields should not be displayed on the review page
10. User should see only visible fields when reviewing their submission
11. Nested objects should display in a clear, hierarchical format with indentation on review page
12. User should be able to provide their own custom review page component via plugin
13. Default review page should be used if no custom component is provided
14. Update the documents for all these changes