Version 3.1 - 05/17/2018
EMF
- Added a new dataset type named "Facility Closure Extended" for use with Project Future Year Inventory control strategies. This dataset type works like the existing "Plant Closure (CSV)" type but uses current inventory terminology.
- Added support for dataset type keywords when exporting and importing module types and associated dataset types
- Fixed an error when trying to upload a file whose name contains a percent sign
- Fixed the Module Manager window refresh so that module information is reloaded correctly
- Fixed errors when module types are imported, caused by blank dataset type creation and last modified dates
- Fixed errors when deleting modules
CoST
- Updated the implicit price deflator values used in cost year conversions for 2014 through 2017
- Added 2017 as an available cost year
- Relabeled the combustion efficiency column in the control measure SCC window for clarity
- Added formatting to numbers in the CMDB export files
- Added formatting to the cost equation parameters in the At-A-Glance report and the control measure view/edit window
- Updated cost equation descriptions
Upgrading from v3.0
Create the new facility closure dataset type
First, download the dataset type definition file: facility_closure_extended.csv
Using the Dataset Type manager, create a new dataset type named "Facility Closure Extended". Set the type to be derived from the Flexible File Format. For the file format Definition File, use the facility_closure_extended.csv file you downloaded.
Database updates
Before starting, shut down the Tomcat server.
Update implicit price deflator values:
Update stored procedures:
\i clean_project_future_year_inventory_control_programs.sql
\i populate_project_future_year_inventory_strategy_messages.sql
\i run_project_future_year_inventory.sql
\i validate_project_future_year_inventory_control_programs.sql
Update cost equation descriptions:
UPDATE emf.equation_types
SET equation = REPLACE(equation, ' x Combustion Efficiency', '')
WHERE equation LIKE '% x Combustion Efficiency%';
EMF server updates
Copy the new emf.war into the Tomcat webapps directory.
Update the EMF version in the database:
UPDATE emf.properties SET value = 'v3.1 - 05/17/2018' WHERE name = 'EMF-version';
Client updates
Copy the new emf-client.jar file into the EMF client directory.
Copy the new epa-commons.jar file into the EMF/lib client directory.
Finishing up
Once all updates are complete, start the Tomcat server.