Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
dsilvam opened this issue Nov 28, 2024 · 2 comments · May be fixed by #31099
Open

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

dsilvam opened this issue Nov 28, 2024 · 2 comments · May be fixed by #31099
Assignees
Labels
on hold In Progress, but paused to work on higher priority card Sprint: Planned Team : Falcon Type : New Functionality

Comments

@dsilvam
Copy link
Contributor

dsilvam commented Nov 28, 2024

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

@oidacra
Copy link
Member

oidacra commented Jan 9, 2025

Implemented as this image.
image (1)

Copy link

github-actions bot commented Jan 9, 2025

@oidacra oidacra moved this from In Progress to Current Sprint Backlog in dotCMS - Product Planning Jan 10, 2025
@oidacra oidacra moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Jan 13, 2025
@oidacra oidacra linked a pull request Jan 13, 2025 that will close this issue
3 tasks
@oidacra oidacra changed the title Include a control to mark a wofklow action as primary or secondary Enhance Workflow Steps with Primary/Secondary Sections and Feature Flag Implementation Jan 14, 2025
@john-thomas-dotcms john-thomas-dotcms added the on hold In Progress, but paused to work on higher priority card label Jan 22, 2025
@oidacra oidacra moved this from In Progress to Current Sprint Backlog in dotCMS - Product Planning Jan 23, 2025
@oidacra oidacra moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
on hold In Progress, but paused to work on higher priority card Sprint: Planned Team : Falcon Type : New Functionality
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

3 participants