Skip to content

FOUR-29105 | Add Case Retention Configuration Section to Process Configuration (Feature-Flagged)#8717

Merged
sanjacornelius merged 3 commits intoepic/FOUR-29101from
task/FOUR-29105
Feb 5, 2026
Merged

FOUR-29105 | Add Case Retention Configuration Section to Process Configuration (Feature-Flagged)#8717
sanjacornelius merged 3 commits intoepic/FOUR-29101from
task/FOUR-29105

Conversation

@mcraeteisha
Copy link
Contributor

@mcraeteisha mcraeteisha commented Feb 3, 2026

Feature

Ticket: FOUR-29105

This PR adds a Cases Retention section to the Process Configuration screen. The section is shown and editable only when the Case Retention Policy feature flag is enabled.

Implementation

Config (config/app.php)

  • New case_retention_policy_enabled config key, driven by env CASE_RETENTION_POLICY_ENABLED.

View (resources/views/processes/edit.blade.php)

  • Entire Cases Retention card (header + collapsible body) wrapped in @if(config('app.case_retention_policy_enabled')).
  • Section includes:
    • Retention policy copy (left column)
    • Retention period label and multiselect (right column)
    • “Default retention period is in effect” message with check-circle icon

How To Test

  1. Log in to ProcessMaker. Open a Process' Configurations.
  2. Ensure CASE_RETENTION_POLICY_ENABLED=true in your .env file.
    • The Cases Retention section should appear in the Process Configurations.
  3. Set CASE_RETENTION_POLICY_ENABLED=false in your .env file.
    - The Cases Retention section should not appear in the Process Configurations.

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.

@cursor
Copy link

cursor bot commented Feb 3, 2026

You have run out of free Bugbot PR reviews for this billing cycle. This will reset on February 21.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

@vladyrichter
Copy link

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

@processmaker-sonarqube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube

@sanjacornelius sanjacornelius merged commit 2755edb into epic/FOUR-29101 Feb 5, 2026
9 of 13 checks passed
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