[Story] Remove and Deprecate "Loop" and "Loop for Tool" Nodes

[epamLDadayan]

Description:

As a user, I want to transition away from using the Loop Node and Loop for Tool Node in Pipelines, as these nodes have proven to be overly complicated for configuration and usage. Their functionality is now deprecated to allow users to leverage simpler, more intuitive nodes and pipeline design patterns that are easier to set up and maintain. Proper user guidance and instructions must be provided to help users manually convert their pipelines following the removal of these nodes.

Important

Just add deprecation notice for now, and schedule actual removed in 2026

---

Business Context:

The Loop and Loop for Tool Nodes were designed to provide iteration capabilities within pipelines. However, user feedback and usage patterns have revealed that:

• These nodes are too complicated for configuration and everyday usage
• Users struggle with understanding and implementing loop logic correctly
• Alternative pipeline patterns using simpler nodes can achieve the same results with better clarity
• Maintaining these nodes creates unnecessary complexity in the codebase

By deprecating these nodes, we aim to simplify the user experience and encourage the adoption of more straightforward pipeline design patterns that are easier to understand, configure, and maintain.

---

Acceptance Criteria:

1. Usage Analysis (Pre-Implementation):

• @Mykyta Morachov would conduct an analysis to determine:
  • How many users are currently using Loop Nodes in their pipelines
  • How many users are currently using Loop for Tool Nodes in their pipelines
  • Total number of pipelines affected by this deprecation
  • Most common use cases and patterns where these nodes are employed
• Results must be documented and shared with the team before proceeding with deprecation
• Based on usage data, determine if targeted outreach to heavy users is necessary

2. Loop and Loop for Tool Node Deprecation:

• The Loop Node and Loop for Tool Node are removed and deprecated entirely from the application.
• Users will no longer be able to select or add Loop Nodes or Loop for Tool Nodes in Pipelines.
• Rationale for deprecation must be communicated: These nodes are too complicated for configuration and usage, and simpler alternatives are now recommended.

3. No Automatic Migration:

• There will be no automatic migration from Loop Nodes or Loop for Tool Nodes to alternative solutions for existing pipelines.
• Users must manually configure their pipelines to replace legacy Loop and Loop for Tool Nodes with recommended alternative patterns or nodes.

4. Instructional User Guides:

• The QA Team is responsible for creating comprehensive User Guides and instructional notes to assist users in the manual conversion process.
• User Guides must include:
  • Clear explanation of why Loop and Loop for Tool Nodes are being deprecated (complexity issues)
  • Step-by-step instructions on identifying and replacing Loop and Loop for Tool Nodes with simpler alternative solutions
  • Guidelines on manually configuring pipeline logic to replicate looping behavior using easier-to-use patterns
  • Real-world examples of common loop patterns and their simplified alternatives (minimum 3-5 examples)
  • Comparison showing how new patterns are simpler to configure
  • Best practices for ensuring seamless pipeline functionality after the conversion
  • Visual diagrams showing before/after pipeline structures
  • Video tutorials demonstrating the conversion process

---

Notes for Developers and QA:

1. Usage Analysis (@Mykyta Morachov):

   • Run queries against production database to identify:
     • Total count of pipelines using Loop nodes
     • Total count of pipelines using Loop for Tool nodes
     • User distribution (how many users affected)
     • Most common configuration patterns
   • Document findings in this issue before proceeding with implementation
   • Share results with Product Owner for final deprecation decision

2. Migration and Guidance:

   • Since the migration is manual, ensure that all alternative solutions and recommended patterns are fully documented and validated before Loop and Loop for Tool Node removal.
   • QA must provide detailed examples of common pipeline conversion scenarios, including complex looping patterns, to ensure comprehensive hands-on guidance for users.
   • Focus documentation on emphasizing the simplicity and ease of use of alternative approaches