Enhance Workflow Steps with Primary/Secondary Sections and Feature Flag Implementation

Parent Issue

User Story

As a workflow administrator, I want to have better organized workflow steps with clearly defined primary and secondary sections, so I can create more structured and manageable workflows.

Acceptance Criteria

• Primary Section:

  • Add non-draggable, non-deletable "Primary" title
  • All items are set as Primary by default when no secondary exists
  • Primary items maintain existing drag and delete functionality

• Secondary Section:

  • Maximum one secondary divider allowed per step (SEPARATOR)
  • Replace all instances of "SEPARATOR" terminology with "Secondary"
  • Secondary divider should not be draggable
  • Items in secondary section maintain same functionalities as primary items (draggable, deletable)
  • Add visual placeholder for empty space after secondary divider

• Secondary Button/Action Visibility Logic:

  • Show "Add Secondary" button only when no secondary divider exists in the current step
  • Hide "Add Secondary" button when a secondary divider already exists in the step

• UI Changes:

  • Update interface terminology from "SEPARATOR" to "SECONDARY" throughout
  • Dynamic visibility of Add Secondary button based on existence of secondary divider

• Feature Flag:

  • Implement new feature flag to enable Primary/Secondary functionality in Workflow Portlet
  • Default state of feature flag should be specified during implementation

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

• Existing workflow functionality must remain intact
• UI changes should follow current design patterns
• Feature flag implementation should follow existing patterns

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Start by locating the Workflow Portlet implementation, existing SEPARATOR terminology, and the project's established feature-flag patterns. Verify the primary and secondary section behavior, button visibility, terminology updates, and preserved item interactions against the acceptance criteria; the feature flag's default state should also be defined.