Skip to content

feat: add workflow settings and compact nodes workflow variation functionality - #948

Merged
ldyrmishiritech merged 4 commits into
RitechSolutions:origin/developmentfrom
Xhulio233:xhulio/add-compact-nodes-view-workflow
Jul 24, 2026
Merged

feat: add workflow settings and compact nodes workflow variation functionality#948
ldyrmishiritech merged 4 commits into
RitechSolutions:origin/developmentfrom
Xhulio233:xhulio/add-compact-nodes-view-workflow

Conversation

@Xhulio233

Copy link
Copy Markdown
Contributor

Description

add workflow settings and compact nodes workflow variation functionality

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 🏗️ Core implementation (refactoring, architectural changes)
  • 💡 Improvement (enhancement to existing functionality)
  • 📚 Documentation update
  • 🔧 Configuration change
  • 🧪 Test update
  • 💬 New release chat plugin
  • 🚀 New platform release

Changes Made

  • Introduced a settings dialog for workflows to allow users to choose node rendering styles (detailed or compact).
  • Implemented a node actions menu for individual nodes, enabling actions like rename, replace, activate/deactivate, copy, duplicate, and delete.
  • Enhanced the node panel to support replace mode for nodes, providing a clear UI for replacing existing nodes.
  • Added a rename dialog for nodes, allowing users to change node names easily.
  • Updated the backend to include a new settings column in the workflows table to persist user preferences for node styles.
  • Refactored node components to utilize the new context for node actions, improving modularity and maintainability.

Testing

  • Unit tests
  • Integration tests
  • Manual testing
  • E2E tests (if applicable)

Ritech Contribution Checklist

  • My code follows GenAssist's style guidelines (see CONTRIBUTING.md)
  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix/feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • Multi-tenant considerations addressed (if applicable)

Related Issues

Closes #

Screenshots (if applicable)


Note: This PR follows Ritech's contribution guidelines for GenAssist. For questions, refer to CONTRIBUTING.md or contact the Ritech team.

…tionality

- Introduced a settings dialog for workflows to allow users to choose node rendering styles (detailed or compact).
- Implemented a node actions menu for individual nodes, enabling actions like rename, replace, activate/deactivate, copy, duplicate, and delete.
- Enhanced the node panel to support replace mode for nodes, providing a clear UI for replacing existing nodes.
- Added a rename dialog for nodes, allowing users to change node names easily.
- Updated the backend to include a new settings column in the workflows table to persist user preferences for node styles.
- Refactored node components to utilize the new context for node actions, improving modularity and maintainability.
@Xhulio233
Xhulio233 requested a review from a team July 24, 2026 10:15
@github-actions github-actions Bot added backend Means, the <backend> folder is changed in the work progress frontend Means, the <frontend> folder is changed in the work progress database-migration size/extra-large enhancement New feature or request labels Jul 24, 2026
@github-actions github-actions Bot added enhancement New feature or request and removed enhancement New feature or request labels Jul 24, 2026
@github-actions github-actions Bot added enhancement New feature or request and removed enhancement New feature or request labels Jul 24, 2026
@github-actions github-actions Bot added enhancement New feature or request and removed enhancement New feature or request labels Jul 24, 2026
@ldyrmishiritech
ldyrmishiritech merged commit 240af4d into RitechSolutions:origin/development Jul 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend Means, the <backend> folder is changed in the work progress database-migration enhancement New feature or request frontend Means, the <frontend> folder is changed in the work progress size/extra-large

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants