Conducting a Year-end Close Operation Dry Run right after performing an actual Propagation causes the UI to fail to report that it was a dry run

Bug #1331173 reported by Erica Rohlfs on 2014-06-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Evergreen 2.6.0

I am unsure of how many libraries out there actually conduct a dry run of their Year-end Close Operation right after they perform the actual fund Propagation, so this may be a wishlist item or of low importance.

Admin -> Server Administration -> Acquisitions -> Funds -> click on the Fund Propagation and Rollover button

*The following steps are not including the option to Include Funds for Descendant Org Units*

1. Perform a Dry Run of the Propagation. So, only the Dry Run checkbox is selected.
2. Performed the actual Propagation. No checkboxes selected.
3. Perform a dry run of the year end close out. Both the Year-end Close Operation checkbox and Dry Run checkbox selected.
4. It looks like the user performed the actual Year-end close out, not the Dry Run. The UI fails to display the “These changes have not been committed yet.” message. However, it did actually only perform the dry run (it did not perform the actual year end closeout).

When conducting a dry run of the Year-end Close Operation right after performing the actual fund Propagation, the UI should display the “These changes have not been committed yet.” message.

Tags: acq Edit Tag help
Bill Erickson (berick) wrote :

Quick note, since I'm not sure when/if I'll get to this..

js/ui/default/acq/financial/list_funds.js -- around line 251. the if (!dryRun){} needs an else to in cases where it was previously hidden.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers