This update consists of the attached database script first being executed against the database for the plant being tested.
The attached script performs multiple database updates as follows:
Updates the CONFIG value for the top-level folder to include a Formats element in the XML value.
Adds a new field to the Formats table named ApplicablePlant.
Updates the Formats table and sets ApplicablePlant to a pre-determined number.
Updates all format-related stored procedures to include the newly created field
Once the script has been executed and database has been updated PROMS will use these values to filter the list of formats in the dropdown list. Because of the way that PROMS stores the selected format, if a plant uses a format that is no longer available to them after this update, the previously-selected format will continue to be used unless the user selects a different format and saves it.
NOTE
The generic update statements from the attached script that need applied to the all customer databases have been included in the PROMSFixes.sql file in the repository. When building a release and sending it to the customer, the only portion of the script that needs to be modified and executed against their database is the first update statement section which updates the CONFIG value of the Folders table. This will need done for the initial release of this code to each customer.
**This update consists of the attached database script first being executed against the database for the plant being tested.**
The attached script performs multiple database updates as follows:
1. Updates the CONFIG value for the top-level folder to include a Formats element in the XML value.
2. Adds a new field to the Formats table named ApplicablePlant.
3. Updates the Formats table and sets ApplicablePlant to a pre-determined number.
4. Updates all format-related stored procedures to include the newly created field
Once the script has been executed and database has been updated PROMS will use these values to filter the list of formats in the dropdown list. Because of the way that PROMS stores the selected format, if a plant uses a format that is no longer available to them after this update, the previously-selected format will continue to be used unless the user selects a different format and saves it.
**NOTE**
The generic update statements from the attached script that need applied to the all customer databases have been included in the PROMSFixes.sql file in the repository. When building a release and sending it to the customer, the only portion of the script that needs to be modified and executed against their database is the first update statement section which updates the CONFIG value of the Folders table. This will need done for the initial release of this code to each customer.
The code that gets the list of formats for a particular plant that was added to frmProcedureProperties.cs also needs to be added to other forms that get this list, i.e. frmSectionProperties.cs, frmVersionProperties.cs and frmFolderProperties.cs
The code that gets the list of formats for a particular plant that was added to frmProcedureProperties.cs also needs to be added to other forms that get this list, i.e. frmSectionProperties.cs, frmVersionProperties.cs and frmFolderProperties.cs
~Moved original code for populating the filtered list to a separate static class named FormatUtility in Volian.Controls.Library
~Renamed method to GetFilteredFormatList
~Updated code to reference new static class and method
~Added logic to other applicable forms
cglavan
requested review from jjenko 2023-10-03 09:06:36 -04:00
kruffing
approved these changes 2023-10-03 09:11:29 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This update consists of the attached database script first being executed against the database for the plant being tested.
The attached script performs multiple database updates as follows:
Once the script has been executed and database has been updated PROMS will use these values to filter the list of formats in the dropdown list. Because of the way that PROMS stores the selected format, if a plant uses a format that is no longer available to them after this update, the previously-selected format will continue to be used unless the user selects a different format and saves it.
NOTE
The generic update statements from the attached script that need applied to the all customer databases have been included in the PROMSFixes.sql file in the repository. When building a release and sending it to the customer, the only portion of the script that needs to be modified and executed against their database is the first update statement section which updates the CONFIG value of the Folders table. This will need done for the initial release of this code to each customer.
Code and the attached SQL script (attached to the Git check-in) looks good for generating test executable
Kathy,
I think the code looks good for proceed onto the testing phase.
if your review is good than please do the Create merge commit.
~ John
The code that gets the list of formats for a particular plant that was added to frmProcedureProperties.cs also needs to be added to other forms that get this list, i.e. frmSectionProperties.cs, frmVersionProperties.cs and frmFolderProperties.cs
Previous recommendation to add plant format list to all dialogs that have the format list has been done. The code has been successfully reviewed.
Changes look good.
PromsFixes changes have been reviewed successfully.
This tested successfully.