fix(api-service): Workflow schema duplication fixes NV-7040#9830
Conversation
… duplicating workflow The workflow duplication usecase was missing the payloadSchema, validatePayload, and severity fields when building the duplicate workflow DTO. This caused the duplicated workflow to lose these important configuration settings. Fixes NV-7040 Co-authored-by: dima <dima@novu.co>
|
Cursor Agent can help with this pull request. Just |
✅ Deploy Preview for dashboard-v2-novu-staging canceled.
|
WalkthroughThis pull request extends the workflow duplication feature to preserve three additional fields when duplicating workflows. The 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What changed? Why was the change needed?
This PR resolves NV-7040, where the workflow schema (
payloadSchema,validatePayload, andseverity) was not being duplicated when a workflow was copied.The
duplicate-workflow.usecase.tshas been updated to include these missing fields during the duplication process. A new e2e test case has also been added toworkflow.controller.e2e.tsto ensure the correct duplication of these properties.Screenshots
N/A
Expand for optional sections
Related enterprise PR
N/A
Special notes for your reviewer
The approach for duplicating these fields aligns with the existing logic in
sync-to-environment.usecase.ts.Linear Issue: NV-7040