Skip to main content

Ensure Budget Filing Dashboards Data Flows Correctly Regardless of Order of Operations

Feature Request2026

Internal testing of statewide allocations revealed that dashboards only populate correctly when Program Administrators follow a strict sequence of steps. If the steps are completed out of order (e.g., initiating local dashboards before statewide allocation is confirmed), the local dashboards may show incomplete or incorrect data until a manual refresh or re-initiation occurs.

The system should not rely on a specific order of operations. Statewide and local dashboards must refresh and populate correctly whenever prerequisites are met, without requiring users to follow a rigid workflow.

Select the module in CEDARS
Select user type
Posted by cedars team ·
2 comments

Log in to comment and vote

Comments2

  • cedars team

    Team•

    Feb 24

    We’ve completed partial internal testing on this issue.

    There was some internal confusion about the scope of testing. To clarify, the specific scenario we focused on was validating that all steps beyond the initial dependency, where statewide allocation must occur before PA local filings initiation, function correctly without error.

    We’ve tested the reopening and reconfirmation sequences. Based on testing, we did not identify additional pathways that caused dashboard population issues beyond the known statewide-before-local constraint.

    Now that the SW filing deadline has passed, should the part of this ticket to fit the statewide-before-local constraint be treated as a priority item?

    • Jennifer Scheuerell

      Team•

      Mar 1

      Agreed the work to allow local IOU filing initiation before statewide can wait and be done when prioritized by the PCG group.