Skip to content

FOUR-33450 | Draft Status is not Displayed on a Task - #9072

Open
mcraeteisha wants to merge 1 commit into
developfrom
bugfix/FOUR-33450
Open

mcraeteisha wants to merge 1 commit into
developfrom
bugfix/FOUR-33450

Conversation

@mcraeteisha

@mcraeteisha mcraeteisha commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Issue

Ticket: FOUR-33450

The Saved and Autosave callouts on the task page were hidden after the Vite migration in commit a6b9ec5 (FOUR-32412).

a6b9ec5 moved /tasks/{task}/edit onto Vite and stored the drafts setting on window.temporal.taskDraftsEnabled. The task list loader still copies that value onto window.ProcessMaker.taskDraftsEnabled. The task edit loader did not.

Solution

The task edit loader now copies window.temporal.taskDraftsEnabled onto window.ProcessMaker, matching the task list loader, so draft autosave and those callouts run again.

How To Test

  1. Open Tasks → Select an open Form Task → Confirm the Task Details Panel loads.
  2. Type in a Line Input and wait for Autosave.
  3. Confirm the Saved callout and the Autosave panel appear, including the last-save time.
  4. Confirm Clear Draft is available and removes the draft.

ci:deploy

Code Review Checklist

  • I have pulled this code locally and tested it on my instance, along with any associated packages.
  • This code adheres to ProcessMaker Coding Guidelines.
  • This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
  • This solution fixes the bug reported in the original ticket.
  • This solution does not alter the expected output of a component in a way that would break existing Processes.
  • This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
  • This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
  • This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
  • This ticket conforms to the PRD associated with this part of ProcessMaker.

The loader editor now forwards the temporal taskDraftsEnabled flag onto window.ProcessMaker so the task editing runtime can read the feature state consistently. This makes task drafts available in the editor without requiring separate initialization paths.
@cursor

cursor Bot commented Sep 22, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Single-line parity with the existing tasks list loader; no auth or API changes, only restores a feature flag wiring path.

Overview
Restores draft status UI (Saved/Autosave callouts and Clear Draft) on the task edit page after the Vite migration left the flag unset.

The task edit entry (loaderEdit.js) now copies window.temporal.taskDraftsEnabled onto window.ProcessMaker.taskDraftsEnabled, matching the tasks list Vite loader so autosave-related UI that reads that global runs again.

Reviewed by Cursor Bugbot for commit e37650f. Bugbot is set up for automated code reviews on this repo. Configure here.

@decisions-sonarqube

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@vladyrichter

Copy link
Copy Markdown

QA server K8S was successfully deployed https://ci-e3ce8661ca.engk8s.processmaker.net

@eiresendez eiresendez left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change mirrors the existing task-list loader and restores the pre-Vite initialization contract 👍 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants